Hacking Hardware Picofly - a HWFLY switch modchip

  • Thread starter Thread starter mathew77
  • Start date Start date
  • Views Views 3,677,151
  • Replies Replies 17,052
  • Likes Likes 15
When updating v2 Mariko Samsung eMMC from 2.70 to 2.72, the error message "== CLK is not connected" occurs, and I am unable to update the firmware. It remains at version 2.70.
 
woops, I completely missed the reply. In regards of the sarcasm stuff I'm not used to the notifications of GBATemp and I missinterpreted that comment as a reply to my direct comment, my bad :P I'm still learning my "foruming".

As for the lenght, I agree. I can try to make them a little more flush on the board. I'll definitely take that advice

As for shorts, I usually run continuity mode to the next-most points to confirm if they're shorting or not, but I couldn't pinpoint anything at the moment I performed the check... maybe it happend after I closed it if at all?

In regards to the mosfet I think that's due to the angle I took the photo. They're actually not touching, let me post another picture rq.View attachment 372279

I was most concerned with the emmc connector or the motherboard socket for said connector.
 

Attachments

  • MosfetInstall(lite).jpg
    MosfetInstall(lite).jpg
    222.4 KB · Views: 92
  • Like
Reactions: malicks250
When updating v2 Mariko Samsung eMMC from 2.70 to 2.72, the error message "== CLK is not connected" occurs, and I am unable to update the firmware. It remains at version 2.70.
oh, please download files again
Post automatically merged:

Already compiled it, and success generated the uf2, but still not yet test it on real device.
I don't know the purposes of busk, only compile usk. :rofl2:
usk is "no_flash", so you have to use prepare.py to make a complete .uf2
until that the firmware is RAM only
 
I try to copy pins.h from usk, and the compilation succeed. Is it the same file?
yes

This is the uf2 that we usually copy, isn'it?
yes, + update.bin

I read in the readme in busk. Do we need to modify the memmap_default.ld in the pico_sdk according to that address?
I think it would work without such modifications. I do that just in case since in a boot process the main firmware overwrites interrupt vector table
 
  • Love
Reactions: abal1000x
oh, please download files again
Post automatically merged:


usk is "no_flash", so you have to use prepare.py to make a complete .uf2
until that the firmware is RAM only
I successfully updated to version 2.72 using the new update.bin Thank you!
 
What changed in v2.72? Also is the color code different? I had a strange behavior whee the glitching starts until after the console started booting and this never happened on v2.67 😳
 
What is the problem with my Switch OLED? I measured diode value and it shown as below :
RST= 1.239v
CLK= 0.763v
CMD= 0.530v
DAT0= 0.760v
SDA= 0.912v
SCL= 0.903v
anyone know the solution, pls kindly share. thank
 

Attachments

  • video6287108981995342468.mp4
    14.9 MB

Site & Scene News

Popular threads in this forum