Feature Request - Document Tigard Compatibility
melvyn2 opened this issue · comments
Is your feature request related to a problem or missing feature? Please describe.
The Tigard is an FTDI-based hardware multitool. J-Runner detects this as a X-Flasher in SPI mode, and with the correct wiring this board can be used to read/write the 360 nand just like the original X-Flasher. It would be useful for some who already have such hardware to know how to use it to flash their 360.
Describe the solution you'd like
Document somewhere the possibility and method of using a tigard to flash (possibly just linking here).
Additional context
- Plugging in the Tigard should cause J-Runner to recognize an X-Flasher in SPI mode.
- Ensure the Tigard is set to V3.3 mode and SPI/JTAG mode rather than SWD/I2C mode.
- Connect the SPI breakout cable to the 1x8 pins (NOT the 2x4 specifically-designated SPI pins, as these use the second 'B' interface of the tigard)
- Connect the GND, SCK, CS, CIPO, and COPI leads to their labeled wires.
- Connect the SMC_DBG_EN (J2C3 Pad 6) to the wire labeled SRST, and SMC_RST_XDK_N (J2C3 Pad 5) to the wire labeled TRST (guessed, this worked first try).
- Use J-Runner as if using a normal X-Flasher.
Pic of my awful setup:
I don't have any eMMC/4G boards to test the other mode on.
Hi,
If it's detected as an xFlasher SPI, then what is missing in order to make it work?
Josh
Nothing, I simply wanted to publicly document this as working for others to use.
Edit: if there's a better place to post this I'd be happy to move this there.
Hi,
Ah ok. I'll think about where the best place would be. Perhaps a readme should be created listing all tested supported devices.
However since it isn't a change in the application , I will close the request.
Kind Regards,
Josh