Hacking Hardware Picofly - a HWFLY switch modchip

  • Thread starter Thread starter mathew77
  • Start date Start date
  • Views Views 3,675,231
  • Replies Replies 17,052
  • Likes Likes 15
Hi,

I am very lost, it's the first time I see this issue. On switch lite, i have 1 of 10 times the *== (short long long) error....
I am used to this on OLEDS ==> i fix this by switching to an instinct-nx...

On the lite i've tried two rp2040, and now with a tiny the problem is still there.

Here are my readings and some pictures of the installation.

3v3 : 7,75
d0 (c) : 5.25
cmd (a) : 6,62
clk (d) : 6,68
rst (b) : 12,14
cpu : 5.59
 

Attachments

  • 20241001_230636.jpg
    20241001_230636.jpg
    5 MB · Views: 56
  • 20241001_230708.jpg
    20241001_230708.jpg
    3.1 MB · Views: 52
  • 20241001_230630.jpg
    20241001_230630.jpg
    6.2 MB · Views: 54
  • 20241001_230614.jpg
    20241001_230614.jpg
    5.2 MB · Views: 54
Hi,

I am very lost, it's the first time I see this issue. On switch lite, i have 1 of 10 times the *== (short long long) error....
I am used to this on OLEDS ==> i fix this by switching to an instinct-nx...

On the lite i've tried two rp2040, and now with a tiny the problem is still there.

Here are my readings and some pictures of the installation.

3v3 : 7,75
d0 (c) : 5.25
cmd (a) : 6,62
clk (d) : 6,68
rst (b) : 12,14
cpu : 5.59
I replied to you previously. It is the dat0 connection. Even if the value is correct please just redo it. I had the exact same problem previously.
 
I replied to you previously. It is the dat0 connection. Even if the value is correct please just redo it. I had the exact same problem previously.
It's a switch LITE not OLED, d0 is easy to solder so how could I may missed it ?
I will try and leave feadback
 
Hi,

I am very lost, it's the first time I see this issue. On switch lite, i have 1 of 10 times the *== (short long long) error....
I am used to this on OLEDS ==> i fix this by switching to an instinct-nx...

On the lite i've tried two rp2040, and now with a tiny the problem is still there.

Here are my readings and some pictures of the installation.

3v3 : 7,75
d0 (c) : 5.25
cmd (a) : 6,62
clk (d) : 6,68
rst (b) : 12,14
cpu : 5.59
original 3x 47 ohm resistor on rp2040-tiny sets? replace the dat0 one with 100 ohm and try again
1727818784573.png
 
yeah, arffff i do not have thoses in stock :/ you think it's related to this ?
its been proved many times from many people. 3x 47 ohm in some case would not be enough, and people recommend 100(DAT0), 100(CMD) and 47(CLK) resistor setup.


You could put extra 47 ohm or up resistor on the pot29(dat0) to increase the resistance like old days if you dont have/confident to replace to on-board 47 ohm resistor
 
Last edited by jkyoho,
  • Like
Reactions: Nephiel
Or add another 47 to dat0 and cmd. That's what I usually do by default just so I don't have any issues.
 

Attachments

  • PXL_20240515_014639823.jpg
    PXL_20240515_014639823.jpg
    2.8 MB · Views: 64
  • Like
Reactions: jkyoho
its been proved many times from many people. 3x 47 ohm in some case would not be enough, and people recommend 100(DAT0), 100(CMD) and 47(CLK) resistor setup
ok thanks, when you said "would not be enough", what happends when it's not enough ?
 
Make sure you don't ground any of the connection. Especially the tiny touching the shield can cause issue as well.

I once had *= then =* when the tiny is sitting on top of the shield without anything covering the back of the chip. Causing it to short.
 
"when not enough", the glitch progress would get interference by other datalines or noises so glitch failed and you would see error code *== ( or maybe other error code)
Do you have a link or a ref to buy 100ohm resistor i will replace it directly on the board :)
 

Site & Scene News

Popular threads in this forum