error code *== (short long long)

[hongtm77]

Hi guys, i encountered an error that is not listed in the error code which is short, long, long (*==) any idea what is this mean?

[Quas7]

from the guide: PicoFlyGuideV.6.2.pdf

** RST is not connected
*= CMD is not connected
=* D0 is not connected
== CLK is not connected
*** No eMMC CMD1 responce (bad eMMC?)
**= No eMMC block 1 read (should not happen)
*=* No eMMC block 0 read (eMMC init failure?)
*== No eMMC CMD1 request (poor wiring, or dead CPU)
=** eMMC init failure during glitch process
=*= CPU never reach BCT check, should not happen
==* CPU always reach BCT check (no glitch reaction, check
mosfet)
=== Glitch attempt limit reached, cannot glitch
=*** eMMC init failure
=**= eMMC write failure - comparison failed
=*=* eMMC write failure - write failed
=*== eMMC test failure - read failed
==** eMMC read failed during firmware update
==*= BCT copy failed - write failure
===* BCT copy failed - comparison failure
==== BCT copy failed - read failure

[shakangel]

Check the CLK cable. This error happened to me in an OLED where I had inavertandly compressed the CLK line with the APU heatsink. I guess the CLK line was shorting to ground or sending strange signals. Worth the check.

[lucasromeiro]

Sometimes I have this type of problem and I don't understand how to solve it! The resistor solder at point A is perfect.... what else could cause this??

[kastras]

I had the same issue and the problem was the dat0 point, i had the flex touching two points. My switch can´t turn on with chip or without it. If you had the same issue, try removing the flex in dat0 and turning on the switch without chip, if it works its that, and you need to put again the flex in the correct possition.

[FabioKastro]

This is now happening to me, spent all day yesterday trying to figure out what was wrong, my Switch was working perfectly. Now that i was able to replicate the problem i found out that if you remove the SD Card while the emunand is booted the console will "crash??" and won't turn ON or show anything on the screen. If you force reboot by holding the power button the modchip will throw this error *== No eMMC CMD1 request (poor wiring, or dead CPU) and nothing on the screen, the switch appears to be completely dead. After resoldering everything step by step what seemed to work was resolder the flex on the CPU, the console was no longer dead and turned ON.

BUT!!! Big BUT!!! Like i said, i was able to replicate this problem. Did the exact same, removed the SD card while booted into emunand and Switch no longer turns ON. So im pretty sure this was never a problem with soldering. The battery is now uplugged while i wait for everything to drain and hopefully fix the problem once again.

[TheCyberQuake]

Based on the finding in another open issue and my own experience, seems like the undocumented *== is usually tied to CLK due to improper handling of the error codes, where CLK isn't actually implemented. For OLED, the most common issue causing it seems to be when the user exposes the CLK point by scrapping the solder mask, they accidentally expose part of the surrounding ground plane. Pulling up the ribbon/cable, applying UV solder mask to any exposed ground plane surrounding it, and then soldering the ribbon back down seems to fix it in most cases.

[slewantoski]

I've had the exact same error code just now. First could not find it. After some trying i realised that it only happens if i have the APU Shielding / Cooling attached. Then found this post.

It was my CLK Line connected to the Shielding. Removed some of the tabs on this side and works perfectly now.

[TheCyberQuake]

I've had the exact same error code just now. First could not find it. After some trying i realised that it only happens if i have the APU Shielding / Cooling attached. Then found this post.

It was my CLK Line connected to the Shielding. Removed some of the tabs on this side and works perfectly now.

Seems like we can confirm it's most often to show if CLK is shorted to ground then