Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MTX tools output to the console #44

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

Gualdimar
Copy link

Hello. First of all, thank you for your great contribution to the console mods!
J-Runner is a cool tool that includes everything you need to perform RGH in one window, but I've encountered some inconveniences.
nandpro and xsvf run in a separate window that closes automatically when they are finished. This prevents you from seeing the result of the operation. I have redirected the output to the J-Runners`s console, similar to the xebuild output.

Also, a few observations that are not related to this PR:

  1. xsvf.exe, which is included in the J-Runner package, has version 1.0a. And the archive from the original se7ensins thread has version 1.1f. I haven't tested 1.0a, but 1.1f flashes 64 and 128 chips without any problems.
  2. firmwares for MTX nand flasher matrix_64a.HEX and matrix_128.hex are identical. Both flash 64 and 128 chips(tested with xsvf.exe 1.1f). No need to include them both.
  3. there is a way to install libusb0 drivers without any problems with signatures on modern systems. There is a tool called zadig that signs and installs the driver for the selected VID/PID on the fly. Version 2.0.1.154 is the latest with libusb0 1.2,5.0. There is also a cmd tool called wdi-simple, which I think can be used by J-Runner.
Screenshots

Screenshot 2023-10-15 161157

Screenshot 2023-10-15 161223

Screenshot 2023-10-15 161250

@Octal450
Copy link
Owner

Hi my friend,
Thanks for this. Regrettably I must inform you that I cannot test until I am home in December.

Once I am home, I will test everything and if it all looks good, will merge into dev for the next release.

Kind Regards,
Josh

@Octal450 Octal450 changed the base branch from release to dev October 15, 2023 21:40
@Pheeeeenom
Copy link
Contributor

This was initially how I implemented it, for reasons I don't remember...this caused issues that I couldn't fix which is why we did it the way we did. (I'm talking about the console output)

@Octal450 Octal450 self-assigned this Oct 31, 2023
@halotroop2288
Copy link

until I am home in December.

January bump

@Octal450
Copy link
Owner

Pls don't do that. Am aware of the existence of this.

Am busy person and this is extremely low priority issue. I didn't get to it during home due to that I could not found my Matrix flasher... and without it, I cannot test. Nobody else that I work with for testing had the flasher available so, I was not able to test anything.

Once I have the ability to test sufficiently, then I can merge if everything ok.

But again - it's a low priority issue so pls have your patience, try to understand.

Kind Regards,
Josh

@halotroop2288
Copy link

👍🏻 I'm not invested in this issue, let alone impatient about it. There just hasn't been an update comment since October, so I just wanted to be sure you hadn't forgotten, given the time-frame you provided.

Thank you for the update. That's good enough. ❤️

@Octal450
Copy link
Owner

OK fair enough. Just pls maybe not write "bump", because it comes off very impatient.
I am always accept anyone to ask, hey, have you gotten to this yet?

Thx,
Josh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants