Hacking Hardware Picofly - a HWFLY switch modchip

[floxcap]

Logically its not a corrupted nand content.

I think its more probable the ram is malfunction.
Since ums-load use only iram.

You might check the connection between the ram and the cpu maybe theres some resistor burned.
Or you could check the supplied voltage to the ram, maybe the voltage is not being supplied.
If the voltage in problem, you might track it, which ic supplied the voltage. Maybe some resistor burned.

Post automatically merged: Jun 5, 2023

Before the glitch happened, theres a write to emmc, and read from emmc.
So we could assume the nand is okay hardware perspective.

I assume the next step is, the cpu will fetch the machine code from the emmc to the ram, then run it.
The bootloader (BCT) in the emmc is modified, and it will run the payload.bin (which is loaded to the ram).

So the most probable scenario is theres problem on ram.

Yeah - but if ums-loader is black screen it's not a good sign - ums-loader runs in IRAM (internal ram inside the CPU).
That's why it's a good test - because even if DRAM has a problem ums-loader will still work.
(plus if it runs it can test emmc / backup / restore).

 

[abal1000x]

.

 

[Danook28]

What Software is that @Danook28 ?

It is capacitor value not software!!

 

[floxcap]

Ah i see.
How you know if IRAM is the internal ram inside the apu?
I googling for datasheet erista and mariko but couldn't find a hint at all.

https://switchbrew.org/wiki/Hardware
You can search for the specific CPU - e.g: NVIDIA ODNX10-A1
Plus IRAM and some form of external ram is quite common in the micro-controller world.

 

[abal1000x]

.

 

[FreeLander]

there are two kinds of LED: BGR and RGB, it is easier to use yellow/white/blue rather than ask people to swap colours with jumper

Post automatically merged: Jun 4, 2023

Thanks, Rehius. Just to confirm, on the latest fw, I'm getting a single white led to show success. Is this the new thing? No more yellow?

 

[rehius]

Thanks, Rehius. Just to confirm, on the latest fw, I'm getting a single white led to show success. Is this the new thing? No more yellow?

there were people complaining yellow looks like there is an error.
so white should be more distinguishable. it is a very minor thing, I have no idea why people bring so much attention there. once the case is closed nobody really checks the LED

 

[detilmalala]

Hello, *==, I have a v2 with that code, but I couldn't find it

 

[abal1000x]

.

 

[detilmalala]

What you couldn't find?

What error is that code equivalent to?

 

[abal1000x]

.

 

[poiu15]

there were people complaining yellow looks like there is an error.
so white should be more distinguishable. it is a very minor thing, I have no idea why people bring so much attention there. once the case is closed nobody really checks the LED

It seems most of the people are fine with the color, but I saw a lot of questions related to the confusion over the length of the yellow signal. Maybe a little more delay for each signal?

 

[jmmc]

there were people complaining yellow looks like there is an error.
so white should be more distinguishable. it is a very minor thing, I have no idea why people bring so much attention there. once the case is closed nobody really checks the LED

Have you updated 2.74 with a white led?

 

[abal1000x]

.

 

[vdroid1211]

Is the firmware file provided here same as the one on github ( the first link that pops up when you search picofly firmware on google) New here so cannot post links yet

github. co m / Ansem-SoD/Picofly/tree/main/Firmwares

Can they be used on one of those pre-assembled picofly boards (that look verymuch like hwfly )

 

[jmmc]

Is the firmware file provided here same as the one on github ( the first link that pops up when you search picofly firmware on google) New here so cannot post links yet

You should use this firmware, the GitHub one is a mirror of this.

 

[sergiochendry]

So if we analyze the flows like this:

"when i press the power on
Picofly logo show normaly, when i press volume -+ to get OFW, just show blackscreen"
At this point i suspect the partition corrupted, need to rebuild.

"I unplug battery and plug in back, i got error ** (RST)"
The RST line is not stable.

"I change RST cable and now got =**"
RST line stable, Emmc init worked, but failed in the glitch stage.
I suspect the Dat0 is 'lightly' touch the Dat1, so the emmc its not stable.

"Picofly logo show again and cannot get into OFW
Just blakscreen again"
When the glitch work, the initial problem occured, which is partition corrupted.

"So i add more resistor cause i think toshiba need more resistor (47+47)
And now got =***"
At this point, the initialization of emmc is not even detected, after reset, before glitch.
Could be problem with combination of CLK, CMD, or Dat0.

"this is my first post about my switch oled problem
after i remove pico
i got nintendo logo and switch logo, but never get into menu"
The emmc hardware still okay, but the same problem still not fixed, which is the nand partition corrupted.

"i realize my dat0 adapter suck so i change the good one
and i got succes led light"
If the glitched worked, the picofly should shows.

In current firmware.
The success light pulse should be * (1 short light). (Repeat 3 times as usual).
There is no information about this on Led Indication, i read it from the code.

If the ram still okay, then without the pico, the nintendo logo still shows up, then blackscreen. Means the partition still corrupted. But if the ram failed, i think there will be no nintendo logo shows up.

so its mean even i change with hwfly
the problem still the same
because the RAM is failed

 

[abal1000x]

.

 

[bilalhassan341]

What error is that code equivalent to?

Edit: Sorry my bad. This is the error cmd1.*== No eMMC CMD1 request (poor wiring, or dead CPU)

 

[sergiochendry]

I mean is,
do you really sure that the ending led is white and short pulsed, which means the glitched success?

I am sure led is white and short pulsed