I would like to understand the cause of this very slight video glitch in console startup. OLED with Picofly 2040-Zero 2.75FW. The glitch in both emuemmc and original then everything works perfectly. If I remove the picofly it doesn't happen. The tests I did are picofly replacement, 47/47/47 and 100/100/47 on dat0 cmd and clk, firmware replacement at 2.76, what can it depend on? I exclude the flat video, which is perfect because without Picofly it doesn't happen.
Just got my tinyflies today - DHL express is insanely fast! They seem to be working as intended. Big thanks @psycho-neon
I like how the 0402 components fill the board nicely compare to 0201.
Test it on a switch board see how it performs with the glitching process.
I have with no good results. At this point the Switch has stopped charging which to me means the M92 chip has failed. Would explain why the Aliexpress mod chip didn't work because the M92 was already having issues. I found a shorted resistor on the Aliexpress Rp2040 chip, which could indicate a power failure. I order a couple new M92's and proper sized capacitors and waiting for them to arrive. What I did notice is the USB-C connector has some exposed area on it. Not sure if that's a concern and I need to replace the USB-C connector.
Works great, glitch time 1-3 secondsI like how the 0402 components fill the board nicely compare to 0201.
If your cpu die you can't even see anything in the beginning let alone a error code being shown.
Post automatically merged:
It's sd card slot or sd card itself. Just take yhe card out and insert it again if the problem persist then try taking a look at the sd card slot.
Post automatically merged:
I don't know your problem in detail but m92 does nothing to your rp2040 chip. You can even take the m92 IC out and the console can still boot perfectly , it just show you error when you already completing the boot. Maybe your 3.3v have been shorted . if 3.3v rail be shorted the chip will not have the power to boot so do the console because both use 3.3v for their own purposes.
Last edited by superxoi,
It still boots, at least into Hekate. Beyond that it won't boot and now I get an error code about the charging system. Plus it stopped charging in Hekate. I figure I'll change the M92 and USB-C connector anyway.
Hello, I'm new to the forum. I'm getting a **- error on my OLED device, specifically an EmuMMC block 1 read error. What is the solution for this? I've tried re-soldering the cables with plug-and-play, but I'm still getting the same error.
Have you checked mosfet and dat0 line? If you are using d0 adapter try to reset it
I didn't use a mosfet. I have a ready picofly set. I directly removed the NAND of Dat0 and then molded it.
Attachments
These kind of chip are not really supported on this thread though. However just double check your points and make sure that you test them 1 by 1 using multimeter in diode mode.
Side note, mosfet are on the flex cable you used on the SoC. Just make sure flex cable is soldered properly.
What does the " = USB Flashing done" error code mean?
I'm getting blue, white, yellow and the console boots to OFW but I don't get the No SD Card screen.
Edit: I guess it could also be a single * short pulse, I'm not really sure what is considered long.
I'm getting blue, white, yellow and the console boots to OFW but I don't get the No SD Card screen.
Edit: I guess it could also be a single * short pulse, I'm not really sure what is considered long.
Last edited by AgentMcMuffin,
Similar threads
-
Xdqwerty
what are you looking at? -
BakerMan
I rather enjoy a life of taking it easy. I haven't reached that life yet though. -
K3Nv2
-
-
-
-
-
-
-
-
-
-
@
AncientBoi:
+1
Come to think of it, I might make 
for lunch today. A change of pace With chili, cheese, onions, relish n mustard -
-
-
-
-
-
-
-
-
-
-
-
-
-
@
BakerMan:
fellas, would you rather have a scouter from dragon ball irl or a pip boy from fall out irl?
-
We built the cars first. Ask Mr Ford 
