Hacking Hardware Picofly - a HWFLY switch modchip

[cgtchy0412]

Can u give me your file for test ?

It was only the default atmoshpere 1.5.3 mixed with HekAte 6.0.5
Launched from the Fusee.bin

Post automatically merged: Jul 8, 2023

I think The mosfet already an okay . The rds is around 3-4mohms which already suitable for the glitch.
I agreed, from the picture i can't confirm wether the 1st pin is the right bottom or left top.

Also because the transistor flipped down, we couldn't solder to the center pad. Its important for the D to be soldered as wide as possible.

This can be tested with a multimeter easily right., i mean the orientation debacle.

 

[QuiTim]

I think The mosfet already an okay . The rds is around 3-4mohms which already suitable for the glitch.
I agreed, from the picture i can't confirm wether the 1st pin is the right bottom or left top.

Also because the transistor flipped down, we couldn't solder to the center pad. Its important for the D to be soldered as wide as possible.

So maybe just a weak connection to Drain . Yeah, that might be it, it would not be the first time that the mod fails due to the joint being too weak.

 

[chronoss]

It was only the default atmoshpere 1.5.3 mixed with HekAte 6.0.5
Launched from the Fusee.bin

Post automatically merged: Jul 8, 2023

This can be tested with a multimeter easily right., i mean the orientation debacle.

First try, it give me error package1 and second time, it boot normaly

 

[abal1000x]

This can be tested with a multimeter easily right., i mean the orientation debacle.

Yes, it is.

First try, it give me error package1 and second time, it boot normaly

My hunch says you need to add another resistor on CMD and/or Dat0 to around 100ohms.

 

[Takezo-San]

So maybe just a weak connection to Drain . Yeah, that might be it, it would not be the first time that the mod fails due to the joint being too weak.

Maybe should have flipped the mosfet for the install rather than top down but the dmm readings on both ends of the drain points were fine. Who knows. Maybe my source point was not good. Damn it should have tried changing it because I used the point on the apu chip. Could have tried a different ground point. Heard in some cases it makes a difference.

 

[chronoss]

My hunch says you need to add another resistor on CMD and/or Dat0 to around 100ohms.

i tested it and it give me error on last atmo

 

[abal1000x]

i tested it and it give me error on last atmo

What is your resistor value for CMD/CLK/Dat0 when error occured?
And what error occured?

 

[chronoss]

What is your resistor value for CMD/CLK/Dat0 when error occured.?

same for all 47

And what error occured?

*== No eMMC CMD1 request (poor wiring, or dead CPU)

I boot properly with atmo 1.5.3 and fusée on second try...

 

[cgtchy0412]

So maybe just a weak connection to Drain . Yeah, that might be it, it would not be the first time that the mod fails due to the joint being too weak.

Here you go, Now i just realize that i never directly posted my mosfet solder until now.. lol.
It works everytime, no drama whatsoever, at least from mosfet side.

 

[abal1000x]

same for all 47


*== No eMMC CMD1 request (poor wiring, or dead CPU)

I boot properly with atmo 1.5.3 and fusée on second try...

I think theres misunderstanding. This is what i understand from your comment:

1. The glitch is okay, nosd shown.
2. You goes to atmo throws error package1
3. You add resistor CMD and/or Dat0.
(This is the part that i want to know, you modified the resistor into what value)
4. Error Occured.
(This is what i want to know what error occured, since the only change is the resistor, so this error is directly correlated with the step 3)

 

[QuiTim]

Here you go, Now i just realize that i never directly posted my mosfet solder until now.. lol.
It works everytime, no drama whatsoever, at least from mosfet side.

Thank you. As it seems, the aon6554 works in all scenarios so whatever issue Takezo was having is not mosfet related (model wise).
Anyway, glad we could add another mosfet type to the "tested-and-working" list

 

[jkyoho]

Thanks for this. Which rp2040 is known to be stable with 2.74? WaveShare?

package size doesn't matter, whatever size works for you is ok. I have planty 0201 size from ps5 hdmi reapair so I use them and working for me so far.

 

[chronoss]

I think theres misunderstanding. This is what i understand from your comment:

1. The glitch is okay, nosd shown.
2. You goes to atmo throws error package1
3. You add resistor CMD and/or Dat0.
(This is the part that i want to know, you modified the resistor into what value)
4. Error Occured.
(This is what i want to know what error occured, since the only change is the resistor, so this error is directly correlated with the step 3)

i add same resistance 47 like on the tuto

 

[abal1000x]

i add same resistance 47 like on the tuto

So the configuration become
CMD = 94ohms
CLK = 94ohms
Dat0 = 94ohms
is this correct?

 

[chronoss]

So the configuration become
CMD = 94ohms
CLK = 47ohms
Dat0 = 94ohms
is this correct?

i have this error with this config

 

[abal1000x]

i add same resistance 47 like on the tuto

Actually i've change the resistor combination for experiment like hundreds time, and its never stopped the glitch, the nosd always shows.

I have post part of the experiment data on my previous comment.
https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/post-10192087

The device i use is lite and v1. I heavily experiment on the resistor.

I am pretty sure that the error occured on your case is not because of the resistor.
But who knows maybe in v2 or oled could be a problem.

I change the resistor variantly from 0 ohms to 1000 ohms, all working.

 

[Takezo-San]

Thank you. As it seems, the aon6554 works in all scenarios so whatever issue Takezo was having is not mosfet related (model wise).
Anyway, glad we could add another mosfet type to the "tested-and-working" list

Yep my user error. Apologies @cgtchy0412. I think the problem was d point surface contact of the solder and wires so next time will try it upside down for the install. Thanks for the pictures and thanks @QuiTim for the help and @abal1000x for the input.

edit - @cgtchy0412, no need for pull down resistor for this mosfet install, right!?

 

[chronoss]

Actually i've change the resistor combination for experiment like hundreds time, and its never stopped the glitch, the nosd always shows.

I have post part of the experiment data on my previous comment.
https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/post-10192087

The device i use is lite and v1. I heavily experiment on the resistor.

I am pretty sure that the error occured on your case is not because of the resistor.
But who knows maybe in v2 or oled could be a problem.

I change the resistor variantly from 0 ohms to 1000 ohms, all working.

i'm on v1 and with fusee, it work well on second try on normal config

 

[abal1000x]

i'm on v1 and with fusee, it work well on second try on normal config

After the 94/94/94, first try error *== then power off, and power on, normal, is it correct?

 

[chronoss]

After the 94/94/94, first try error *== then power off, and power on, normal, is it correct?

nevers test this config, only

94/94/47 and error with the chip, no acces to the sd