Hacking Hardware Picofly - a HWFLY switch modchip

  • Thread starter Thread starter mathew77
  • Start date Start date
  • Views Views 3,675,187
  • Replies Replies 17,052
  • Likes Likes 15
Hello everyone, i have an oled switch that have already installed rp2040 in 2 months ago. But it was suddenly stop working and blinking **= which is no eMMC block 1 read like in the manuals. Do anyone know what is the problem? Thanks alot
View attachment 394296
I had this on switch lite, it was bad solder join
 
  • Like
Reactions: Vault76
Hello guys, Pio Tiny installed on V1 and got slow emmc, I would add another 47 resistor to dat0 but I don't know if I should just solder it directly to the pad given one is already soldered. How do I go on about this? Please advise.
 
Hello guys, Pio Tiny installed on V1 and got slow emmc, I would add another 47 resistor to dat0 but I don't know if I should just solder it directly to the pad given one is already soldered. How do I go on about this? Please advise.
If you're not using v2.75, try to use it.
 
Last edited by FreeLander,
  • Like
Reactions: twins333
Anyone know what is this chip version in my oled ?
I bought on my local store
 

Attachments

  • 4EA4D148-95B7-47EC-82E9-C45468E44027.jpeg
    4EA4D148-95B7-47EC-82E9-C45468E44027.jpeg
    1.7 MB · Views: 86
Hey guys. I know we can also install the rp2040 on erista v1 unpatched. In this scenario is the installation the same like the other chips? (solder wires to testpoints and without using cpu cable)
same and identical procedure as the mariko. always remember to check if the emmc goes into slow mode. check in the info. and do a further check such as start the benchmark and stop it immediately. on an Erista at first glance it was fine but after the benchmark I had the slow mode then resolved with additional 47ohm on cmd and dat0
 
same and identical procedure as the mariko. always remember to check if the emmc goes into slow mode. check in the info. and do a further check such as start the benchmark and stop it immediately. on an Erista at first glance it was fine but after the benchmark I had the slow mode then resolved with additional 47ohm on cmd and dat0

or just do 100/100/47 by default.
 
  • Love
Reactions: LogicalMadness
Personally I think it's a waste of resistance. also because I assemble the PicoFly well in advance. and I repeat on more than 100 switches only the Eristas needed the double resistor.

does your local electronics store charge you per ohm of resistance.....?
 
does your local electronics store charge you per ohm of resistance.....?
obviously I'm not making an economic argument about it, if it's not necessary, why double the resistances when, according to general indications, it's not necessary? I have also read about users who have had problems due to having doubled the resistances by default. then I say why create problems with your own hands?
 
obviously I'm not making an economic argument about it, if it's not necessary, why double the resistances when, according to general indications, it's not necessary? I have also read about users who have had problems due to having doubled the resistances by default. then I say why create problems with your own hands?

because 47/47/47 works well on 80 out of 100 switches while 100/100/47 works well on 98 out of 100 switches.
And the problems caused by 100/100/47 are more immediate and impossible to miss while 47/47/47 sometimes leads to ofw instability which is easy to miss during an install. It's simply a game of numbers - if you want fewer headaches, 100/100/47 by default makes sense.
 
because 47/47/47 works well on 80 out of 100 switches while 100/100/47 works well on 98 out of 100 switches.
And the problems caused by 100/100/47 are more immediate and impossible to miss while 47/47/47 sometimes leads to ofw instability which is easy to miss during an install. It's simply a game of numbers - if you want fewer headaches, 100/100/47 by default makes sense.
I personally don't agree. in my experience obviously.
 
because 47/47/47 works well on 80 out of 100 switches while 100/100/47 works well on 98 out of 100 switches.
And the problems caused by 100/100/47 are more immediate and impossible to miss while 47/47/47 sometimes leads to ofw instability which is easy to miss during an install. It's simply a game of numbers - if you want fewer headaches, 100/100/47 by default makes sense.

What issues have 100\100\47 caused? Guess I missed someone posting about it.
 
  • Love
Reactions: LogicalMadness
https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/page-652#post-10242089
https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/page-652#post-10242197

meanwhile several other installers here report 0 issues with 100/100/47 while tons of people keep asking about why they're getting slow emmc with 47/47/47
In the second link where you quoted me, the problem was more related to the new rp2040 tiny, rather than the resistance value. In that case the issue might have been with improper soldering or uncleaned flux, since we did not do further testing due to lack of time. This is not a good example.
 
  • Like
Reactions: deeps
In the second link where you quoted me, the problem was more related to the new rp2040 tiny, rather than the resistance value. In that case the issue might have been with improper soldering or uncleaned flux, since we did not do further testing due to lack of time. This is not a good example.

Then it appears there haven't been any issues w\ 100\100\47 UNLESS you happen to be using a Pico (MAYBE a tiny), and even then it's still just a chance. Definitely sticking with the 100\100\47 configuration. I'd love to hear @rehius' opinion though.
 

Site & Scene News

Popular threads in this forum