I do have an odd thing with one of my repaired Nintendo Switches.
The Switch is a V1 Switch and seems to be fully working - so it can be started normally, can be charged. Dock is working - so everything seems fine.
I can bring the switch in rcm mode, but payload injection does not work - so simply payload won’t be injected.
I currently have no idea what is wrong and how this can be fixed. Any ideas / experiences with such a problem and an idea how to fix this ?
Simply nothing - so the payload won’t be injected. TegraRCM will stay in the attached image. So there is no return code or something - it simply won’t be sent to the switch… I checked with the PC and a dongle - same result… very odd.
Yep. Check resistance on D-/D+ - you should be getting 3.9 MOhm on both IIRC. This is a common failure mode as these lines go straight to the SOC and can kill the USB controller required for the boot CPU to communicate in RCM. Typically caused by a damaged connector and 15v getting to where is shouldn’t.
The other symptom which gives it away would be failure to fast-charge using a standard USB A-C cable as these rely on the D+/D- lines for crude level signalling. I’ve got a couple of old unpatched boards here with knackered D+/D- lines effectively blocking any payload.
What diode or resistance reading do you get on D+/D- relative to ground in both probe polarities do you get? (diode mode is better here due to the differences in board revisions and the typically high resistance)
At least some USB functionality must be remaining if it’s showing up in RCM state in TegraRCMGUI
No, I haven’t checked the Tegra datasheet but would imagine there is more USB bus I/O, though I have no idea if they are broken out anywhere, if they are a potential workaround could in theory be installed - assuming of course it isn’t reliant on the presumed bad I/O
Actually there is another USB controller (USB 3) in there that’s totally separate (this joins the DP data across the USB-C in addition to USB 1) and provides services to the dock etc. I suspect it’s not accessible by the BPMP or at least insuficiently coded in the boot firmware to activate it.
Actually you make a great point here. When the D+/D- lines are damaged in some way, then Windows will generally report USB Device Not Recognised…