Would this help for a unit that is timing out on glitch? I let it run.. it is blue light for a few minutes. Then I get the 3 long yellow flash… saying timed out. Should this help? I never get a boot screen. Only black screen.
PI2040-Zero PIN13 -> SCL PIN12 ->SDA
Post automatically merged:
Well… I’m not sure if this was the issue. But i plugged the speakers in.. and i get one blue flash. And then the yellow error of =** Emmc initialization failure during glitch… is this a dat0 issue?
Last edited by themine1500,
The partner has already been able to carry out the tests and partition readings and these are the results when connecting the switch to the computer. now, in what situation is the nintendo switch?
Attachments
Anyone know if an emmc just uses the pinouts that are traced on motherboard or it uses all of the points that are on the board? A friend gave me this dat0 adapter wirh this pins broken...wanna know if i can use it whitout interfere on the emmc function
i have a similiar issue with a oled laying around (i didnt do the install)
though on this oled it accured durign a hwfly install with a cheap dat 0 Adapter
i get No sdcard with pico installed , if i use Hekate nothing shows on screen only black .
cannot insert Ofw
Ums-Loader works fine ..
Also have no clue how to go further i can load the partitions without a issue.
They're some people that can rewrite the emmc with the ums-loader.
i can do it, by error i restore the boot0/1 with erista model, but with the emmcgenerator, i got a mariko boot0/1 that get blue screen again, before just black screen trying to boot on ofw.
just that i'm using a universalprod.keys because can't get my keys.
i dont think this has anything to do with nand,
i used a functinall emmc from a v2 (i know its only 32gb) but it should atleast boot hekate if it has something to do with the emmc.
and i can read the emmc on a v2 but i did not to any backups when i installed it Xd was just testing putpose .
ic can do a gppt backup with Nx nand manager.
from some research i think this hwfly that was installes was a clone hwfly with an old ersita software that sends some wrong signals to the ram and destroys them.
but i have no proof for it.
what would be really awesome is a iram payload that does hardware tests that would help us out alot
Hard to see in the pic, but see attached pic for all emmc points that are connected to something (oled emmc board for reference)
Attachments
This is the perfect raspberry PI,Avoid all distractions
Yes - in theory.
But to put in perspective - the ums-loader is close to max size for IRAM - so we are very limited in what we can run there.
Also - without being able to mount the emmc we can't do a backup from there.
I presume your GPP, BOOT0 & BOOT1 menu items are grey in ums-loader?
(which means there was a problem connecting to the emmc).
I'm currently working on converting ums-loader to a bit of a diagnostics tool - so that those of us that have this problem might be able to get some more information.
Post automatically merged:
That screenshot looks just like mine - the app is unable to mount the emmc.
Post automatically merged:
I like your train of thought.
As a test I put in a code snippet for starting the DRAM - that seems to work ok... but I didn't think to actually run a read/write DRAM test. I'll add that to my list for the changes I'm making to ums-loader
Last edited by floxcap,
Similar threads
