After installing a flashable 'OLED' modchip in a switch lite, I noticed 2 issues:
- I could not get the modchip into hwfly-toolbox mode by holding VOL+
- frequently, hekate fails to load, and sometimes the graphics appear garbled
Some troubleshooting revealed that the 3.3v supply point that's used for the original sx lite modchips on a capacitor near the SD card reader briefly gets gets interrupted when hekate loads. This causes the modchip to immediately power off, meaning it cannot continue to function in toolbox mode no matter what. When the supply is restored quickly after, the modchip powers up again but notices the switch is already past init/bootrom and immediately suspends itself. My unconfirmed belief is that this brief power spike either leads to RAM corruption or SD card reads corruption, thereby causing hekate to fail its initialization.
Instead, we should be using a 3v3 point from a hardware-controlled location rather than an sw-controlled one. The most suitable one I found is located directly underneath the cart reader. When using this point, all modchip functionality works as expected, and I have not encountered failed attempts to initialize hekate anymore.
Refer to the attached diagram where I modified only the suggested 3v3 point. Refer to the updated diagram in post #4 for the suggested 3v3 point.
- I could not get the modchip into hwfly-toolbox mode by holding VOL+
- frequently, hekate fails to load, and sometimes the graphics appear garbled
Some troubleshooting revealed that the 3.3v supply point that's used for the original sx lite modchips on a capacitor near the SD card reader briefly gets gets interrupted when hekate loads. This causes the modchip to immediately power off, meaning it cannot continue to function in toolbox mode no matter what. When the supply is restored quickly after, the modchip powers up again but notices the switch is already past init/bootrom and immediately suspends itself. My unconfirmed belief is that this brief power spike either leads to RAM corruption or SD card reads corruption, thereby causing hekate to fail its initialization.
Instead, we should be using a 3v3 point from a hardware-controlled location rather than an sw-controlled one. The most suitable one I found is located directly underneath the cart reader. When using this point, all modchip functionality works as expected, and I have not encountered failed attempts to initialize hekate anymore.
Last edited by doom95,