Picofly AIO Thread

Adran_Marit

Adran_Marit

Walküre's Hacker
OP
Member
Level 14
Joined
Oct 3, 2015
Messages
3,781
Trophies
1
Location
42*South
XP
4,558
Country
Australia
TheBad said:
I have a strange OLED that was not boot OFW with HWFLY then I changed with the Picofly it boot both CFW and OFW but some reason after some time it won't boot hekate now, only OFW. What am I missing? If it is because SK Hynix I will loose my mind...
Click to expand...
try rolling back to 2.7.2 or 2.6.7
 
QuiTim

QuiTim

Well-Known Member
Member
Level 7
Joined
Mar 30, 2023
Messages
756
Trophies
0
XP
1,165
Country
Albania
zewin said:
Thank you for your help
can i use AON7506 on switch lite?
Click to expand...
I used the same one on Lite so it should work no problem, 1second glitch
 

Attachments

  • 20230516_205407.jpg
    20230516_205407.jpg
    1.2 MB · Views: 33
  • 20230517_013840.mp4
    6.5 MB
Takezo-San

Takezo-San

Well-Known Member
Member
Level 3
Joined
May 3, 2023
Messages
261
Trophies
0
Age
39
XP
349
Country
Seychelles
@Dee87 & @QuiTim
high-five-walter-white-1.gif

@Dee87 Thanks for the encouraging words and insight, tips and advice on reballing, helped a ton. And @QuiTim. Its all about the next challenge and this was worth it in the end. Want to take out the hit and miss nature of the Dat0 adaptors and go 99% secure and permanent in the process.
 
  • Like
  • Love
Reactions: QuiTim and Dee87
HelloShitty

HelloShitty

Well-Known Member
Member
Level 4
Joined
Jan 16, 2022
Messages
252
Trophies
0
Age
124
XP
402
Country
Iran
Hello.
I bought this modchip from the other side of the world:
20230620-220933.jpg


I'm trying to update it but with Debian BullsEye. I think I'm not being able to do it.
Has anyone did this in Linux?

This is what happens with me:
1 - When trying to plug the chip to the USB cable, I cannot see any new device showing up in the output of:
sudo blkid
Same if I run:
sudo udevadm monitor
2 - If I press BOOT button and then plug in the USB cable, then I can see a device in the output of the 2 commands above:

$ sudo udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[8902.301519] add /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
KERNEL[8902.302148] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
KERNEL[8902.303713] add /devices/virtual/workqueue/scsi_tmf_9 (workqueue)
KERNEL[8902.303786] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9 (scsi)
KERNEL[8902.303827] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/scsi_host/host9 (scsi_host)
KERNEL[8902.303863] bind /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
KERNEL[8902.303940] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1 (usb)
KERNEL[8902.303978] bind /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
UDEV [8902.305280] add /devices/virtual/workqueue/scsi_tmf_9 (workqueue)
UDEV [8902.312688] add /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
UDEV [8902.316047] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1 (usb)
UDEV [8902.316103] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
UDEV [8902.317341] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9 (scsi)
UDEV [8902.318642] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/scsi_host/host9 (scsi_host)
UDEV [8902.320068] bind /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
UDEV [8902.321849] bind /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
KERNEL[8903.332963] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0 (scsi)
KERNEL[8903.333071] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0 (scsi)
KERNEL[8903.333156] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/scsi_device/9:0:0:0 (scsi_device)
KERNEL[8903.333232] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/scsi_disk/9:0:0:0 (scsi_disk)
KERNEL[8903.333317] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/scsi_generic/sg3 (scsi_generic)
KERNEL[8903.333640] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/bsg/9:0:0:0 (bsg)
UDEV [8903.335666] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0 (scsi)
UDEV [8903.336968] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0 (scsi)
UDEV [8903.338340] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/scsi_device/9:0:0:0 (scsi_device)
UDEV [8903.338801] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/scsi_disk/9:0:0:0 (scsi_disk)
UDEV [8903.339848] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/scsi_generic/sg3 (scsi_generic)
UDEV [8903.340630] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/bsg/9:0:0:0 (bsg)
KERNEL[8903.363785] add /devices/virtual/bdi/8:80 (bdi)
UDEV [8903.364450] add /devices/virtual/bdi/8:80 (bdi)
KERNEL[8903.368923] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/block/sdf (block)
KERNEL[8903.368962] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/block/sdf/sdf1 (block)
KERNEL[8903.412974] bind /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0 (scsi)
UDEV [8903.726692] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/block/sdf (block)
UDEV [8904.646772] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/block/sdf/sdf1 (block)
UDEV [8904.649978] bind /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0 (scsi)


and

$ sudo blkid ... ... ... ... /dev/sdf1: SEC_TYPE="msdos" LABEL_FATBOOT="RPI-RP2" LABEL="RPI-RP2" UUID="000C-33D1" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="000c33d1-01"

Then, I try to copy the .uf2 file into the modchip, after mounting it with:
sudo mount -o rw,uid=1000,gid=1000 -t msdos /dev/sdf1 /media/dos

I can see that after a second or two, the led blinks once yellow/green - ish and then, nothing else. I thought this was expected, but I'm not sure it shouldn't blink red instead!

Then, if I unplug the cable and plug it back in, without pressing the BOOT button, the led blinks 1x long blue, 2x fast green/yellow ish, 2x fast green/yellow ish and again 2x fast green/yellow ish. But once more, nothing shows up in sudo udevadm monitor nor in sudo blkid.

However, I can see some concerning messages in dmesg:
[ 7538.002598] sdf: sdf1 [ 7538.050751] sd 9:0:0:0: [sdf] Attached SCSI removable disk [ 7656.421365] fat__get_entry: 22 callbacks suppressed [ 7656.421370] FAT-fs (sde1): Directory bread(block 259) failed [ 7656.421382] FAT-fs (sde1): Directory bread(block 260) failed [ 7656.421386] FAT-fs (sde1): Directory bread(block 261) failed [ 7656.421390] FAT-fs (sde1): Directory bread(block 262) failed [ 7656.421394] FAT-fs (sde1): Directory bread(block 263) failed [ 7656.421399] FAT-fs (sde1): Directory bread(block 264) failed [ 7656.421403] FAT-fs (sde1): Directory bread(block 265) failed [ 7656.421407] FAT-fs (sde1): Directory bread(block 266) failed [ 7656.421412] FAT-fs (sde1): Directory bread(block 267) failed [ 7656.421416] FAT-fs (sde1): Directory bread(block 268) failed

and also

[ 7809.634843] blk_update_request: I/O error, dev sdf, sector 2 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0 [ 7809.634859] Buffer I/O error on dev sdf1, logical block 1, lost async page write [ 7809.634885] blk_update_request: I/O error, dev sdf, sector 131 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [ 7809.634890] Buffer I/O error on dev sdf1, logical block 130, lost async page write [ 7809.634925] blk_update_request: I/O error, dev sdf, sector 260 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [ 7809.634935] Buffer I/O error on dev sdf1, logical block 259, lost async page write [ 7991.308168] FAT-fs (sdf1): unable to read boot sector to mark fs as dirty

Any ideas where am I going wrong?
 
D

Dee87

Well-Known Member
Member
Level 9
Joined
Mar 19, 2023
Messages
1,139
Trophies
1
XP
1,578
Country
Germany
HelloShitty said:
Hello.
I bought this modchip from the other side of the world:
20230620-220933.jpg


I'm trying to update it but with Debian BullsEye. I think I'm not being able to do it.
Has anyone did this in Linux?

This is what happens with me:
1 - When trying to plug the chip to the USB cable, I cannot see any new device showing up in the output of:
sudo blkid
Same if I run:
sudo udevadm monitor
2 - If I press BOOT button and then plug in the USB cable, then I can see a device in the output of the 2 commands above:

$ sudo udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[8902.301519] add /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
KERNEL[8902.302148] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
KERNEL[8902.303713] add /devices/virtual/workqueue/scsi_tmf_9 (workqueue)
KERNEL[8902.303786] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9 (scsi)
KERNEL[8902.303827] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/scsi_host/host9 (scsi_host)
KERNEL[8902.303863] bind /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
KERNEL[8902.303940] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1 (usb)
KERNEL[8902.303978] bind /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
UDEV [8902.305280] add /devices/virtual/workqueue/scsi_tmf_9 (workqueue)
UDEV [8902.312688] add /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
UDEV [8902.316047] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1 (usb)
UDEV [8902.316103] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
UDEV [8902.317341] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9 (scsi)
UDEV [8902.318642] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/scsi_host/host9 (scsi_host)
UDEV [8902.320068] bind /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
UDEV [8902.321849] bind /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
KERNEL[8903.332963] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0 (scsi)
KERNEL[8903.333071] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0 (scsi)
KERNEL[8903.333156] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/scsi_device/9:0:0:0 (scsi_device)
KERNEL[8903.333232] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/scsi_disk/9:0:0:0 (scsi_disk)
KERNEL[8903.333317] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/scsi_generic/sg3 (scsi_generic)
KERNEL[8903.333640] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/bsg/9:0:0:0 (bsg)
UDEV [8903.335666] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0 (scsi)
UDEV [8903.336968] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0 (scsi)
UDEV [8903.338340] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/scsi_device/9:0:0:0 (scsi_device)
UDEV [8903.338801] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/scsi_disk/9:0:0:0 (scsi_disk)
UDEV [8903.339848] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/scsi_generic/sg3 (scsi_generic)
UDEV [8903.340630] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/bsg/9:0:0:0 (bsg)
KERNEL[8903.363785] add /devices/virtual/bdi/8:80 (bdi)
UDEV [8903.364450] add /devices/virtual/bdi/8:80 (bdi)
KERNEL[8903.368923] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/block/sdf (block)
KERNEL[8903.368962] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/block/sdf/sdf1 (block)
KERNEL[8903.412974] bind /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0 (scsi)
UDEV [8903.726692] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/block/sdf (block)
UDEV [8904.646772] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0/block/sdf/sdf1 (block)
UDEV [8904.649978] bind /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host9/target9:0:0/9:0:0:0 (scsi)


and

$ sudo blkid ... ... ... ... /dev/sdf1: SEC_TYPE="msdos" LABEL_FATBOOT="RPI-RP2" LABEL="RPI-RP2" UUID="000C-33D1" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="000c33d1-01"

Then, I try to copy the .uf2 file into the modchip, after mounting it with:
sudo mount -o rw,uid=1000,gid=1000 -t msdos /dev/sdf1 /media/dos

I can see that after a second or two, the led blinks once yellow/green - ish and then, nothing else. I thought this was expected, but I'm not sure it shouldn't blink red instead!

Then, if I unplug the cable and plug it back in, without pressing the BOOT button, the led blinks 1x long blue, 2x fast green/yellow ish, 2x fast green/yellow ish and again 2x fast green/yellow ish. But once more, nothing shows up in sudo udevadm monitor nor in sudo blkid.

However, I can see some concerning messages in dmesg:
[ 7538.002598] sdf: sdf1 [ 7538.050751] sd 9:0:0:0: [sdf] Attached SCSI removable disk [ 7656.421365] fat__get_entry: 22 callbacks suppressed [ 7656.421370] FAT-fs (sde1): Directory bread(block 259) failed [ 7656.421382] FAT-fs (sde1): Directory bread(block 260) failed [ 7656.421386] FAT-fs (sde1): Directory bread(block 261) failed [ 7656.421390] FAT-fs (sde1): Directory bread(block 262) failed [ 7656.421394] FAT-fs (sde1): Directory bread(block 263) failed [ 7656.421399] FAT-fs (sde1): Directory bread(block 264) failed [ 7656.421403] FAT-fs (sde1): Directory bread(block 265) failed [ 7656.421407] FAT-fs (sde1): Directory bread(block 266) failed [ 7656.421412] FAT-fs (sde1): Directory bread(block 267) failed [ 7656.421416] FAT-fs (sde1): Directory bread(block 268) failed

and also

[ 7809.634843] blk_update_request: I/O error, dev sdf, sector 2 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0 [ 7809.634859] Buffer I/O error on dev sdf1, logical block 1, lost async page write [ 7809.634885] blk_update_request: I/O error, dev sdf, sector 131 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [ 7809.634890] Buffer I/O error on dev sdf1, logical block 130, lost async page write [ 7809.634925] blk_update_request: I/O error, dev sdf, sector 260 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [ 7809.634935] Buffer I/O error on dev sdf1, logical block 259, lost async page write [ 7991.308168] FAT-fs (sdf1): unable to read boot sector to mark fs as dirty

Any ideas where am I going wrong?
Click to expand...


Nope ask the creators of the board since they sell them they should be able to help we are here for the Pico's that are listet in the aio thread I think question about this board/s from hwfly and co she be answered in ur own or a hwfly thread
Post automatically merged:

Takezo-San said:
@Dee87 & @QuiTim
View attachment 379052
@Dee87 Thanks for the encouraging words and insight, tips and advice on reballing, helped a ton. And @QuiTim. Its all about the next challenge and this was worth it in the end. Want to take out the hit and miss nature of the Dat0 adaptors and go 99% secure and permanent in the process.
Click to expand...

No problem that's what we are here for :).

Yes get rid of those shitty dat0 adapters and do it the only correct way XD
 
Last edited by Dee87,
  • Like
Reactions: Takezo-San and QuiTim
QuiTim

QuiTim

Well-Known Member
Member
Level 7
Joined
Mar 30, 2023
Messages
756
Trophies
0
XP
1,165
Country
Albania
jkyoho said:
AWG30 wire？
Does it fit flush under the CPU shield cover with heat pipe?
Click to expand...
The wire is 0.2mm so 32awg I think. It fits perfectly, no need to cut anything and it does not touch the shield (although I added some solder mask on top of it before closing just to be safe)
Post automatically merged:

zewin said:
I made this diagram correct?
Click to expand...
Correct. I placed mine upside down because it aligned better with the wires from apu
 
jmccarty

jmccarty

New Member
Newbie
Level 1
Joined
Jun 19, 2023
Messages
3
Trophies
0
Age
50
XP
27
Country
United States
So no one can help? I just figured if someone had a multimeter and their switch took apart, they could measure this capacitor for me. Well guess I'll grab a scrap board and help myself.
capacitor.png
 
  • Angry
Reactions: LogicalMadness
abal1000x

abal1000x

Well-Known Member
Member
Level 8
Joined
Jun 5, 2022
Messages
1,065
Trophies
0
XP
1,377
Country
Gaza Strip
HelloShitty said:
I can see that after a second or two, the led blinks once yellow/green - ish and then, nothing else. I thought this was expected, but I'm not sure it shouldn't blink red instead!
Click to expand...
That seems correct, the flash done.
HelloShitty said:
Then, if I unplug the cable and plug it back in, without pressing the BOOT button, the led blinks 1x long blue, 2x fast green/yellow ish, 2x fast green/yellow ish and again 2x fast green/yellow ish.
Click to expand...
Seems okay. That the same behavior with rp2040-zero or tiny.
Blue means power on, since nothing connected then throws error ** 2 short yellow means RST line disconnected (RST is the first to detect).


Post automatically merged:

zewin said:
is there any other option than using IRF HS8342 MOSFET? because this one is not for sale in my country.
Click to expand...
This is the confirmed working one, i noted from this thread.

AON S36312
Works, Reliable But large package 5x6, Single Mosfet Install

AON 6512
Works, Reliable But large package 5x6, Single Mosfet Install

AON 6792
Works, Reliable But large package 5x6, Single Mosfet Install

FDMC 7672
Works, Reliable, Perfect 3x3 package, Single Mosfet Install

TPN8R903NL
Works on V2 confirmed. From XBox.
 
Last edited by abal1000x,
  • Like
Reactions: HelloShitty
O

ojobenito

Active Member
Newcomer
Level 3
Joined
Jul 20, 2019
Messages
31
Trophies
0
Age
44
XP
289
Country
Spain
Hi.
I made my 1st picofly install. (Fw 2.73 as 2.74 was scrubbed it seems)
When I tested it after installation, I got the "No SD Card" logo on the switch. So, I put a MicroSD card, FAT32 (as I always do with jig switches), with the atmosphere payload (fusee.bin) renamed to payload.bin located at the root of the MicroSD card, and all atmosphere files copied, too.
Now, the console won't show anything on the screen. If I remove the SD card and try again, I get the "No SD Card" logo again. What am I missing here? Any help? Thanks!

PS: If I push both volume buttons before powering on, I can enter official firmware. So I think Rasp.Pico is working ok. I don't know what's happening when inserting the MicroSD card.
 
QuiTim

QuiTim

Well-Known Member
Member
Level 7
Joined
Mar 30, 2023
Messages
756
Trophies
0
XP
1,165
Country
Albania
ojobenito said:
Hi.
I made my 1st picofly install. (Fw 2.73 as 2.74 was scrubbed it seems)
When I tested it after installation, I got the "No SD Card" logo on the switch. So, I put a MicroSD card, FAT32 (as I always do with jig switches), with the atmosphere payload (fusee.bin) renamed to payload.bin located at the root of the MicroSD card, and all atmosphere files copied, too.
Now, the console won't show anything on the screen. If I remove the SD card and try again, I get the "No SD Card" logo again. What am I missing here? Any help? Thanks!

PS: If I push both volume buttons before powering on, I can enter official firmware. So I think Rasp.Pico is working ok. I don't know what's happening when inserting the MicroSD card.
Click to expand...
Can you show pictures of installation?
Where are you getting 3v3 from?
 
abal1000x

abal1000x

Well-Known Member
Member
Level 8
Joined
Jun 5, 2022
Messages
1,065
Trophies
0
XP
1,377
Country
Gaza Strip
ojobenito said:
Hi.
I made my 1st picofly install. (Fw 2.73 as 2.74 was scrubbed it seems)
When I tested it after installation, I got the "No SD Card" logo on the switch. So, I put a MicroSD card, FAT32 (as I always do with jig switches), with the atmosphere payload (fusee.bin) renamed to payload.bin located at the root of the MicroSD card, and all atmosphere files copied, too.
Now, the console won't show anything on the screen. If I remove the SD card and try again, I get the "No SD Card" logo again. What am I missing here? Any help? Thanks!

PS: If I push both volume buttons before powering on, I can enter official firmware. So I think Rasp.Pico is working ok. I don't know what's happening when inserting the MicroSD card.
Click to expand...
Is it similar if you use hekate rather than directly fusee.bin?
 
  • Like
Reactions: Takezo-San
O

ojobenito

Active Member
Newcomer
Level 3
Joined
Jul 20, 2019
Messages
31
Trophies
0
Age
44
XP
289
Country
Spain
QuiTim said:
Can you show pictures of installation?
Where are you getting 3v3 from?
Click to expand...
I got 3v3 from the capacitor to the right of the RAM modules, as shown in the PDF Picofly guide that is uploaded on this forum.

abal1000x said:
Is it similar if you use hekate rather than directly fusee.bin?
Click to expand...
Hekate does indeed load with no problems when put on the MicroSD card root folder renamed to payload.bin

In summary:
- Console is V1 Erista patched updated to last firmware (16.0.3, I think)
- Multimeter installation checked ok. I've been doing console modifications since PSX era. Not new on that. CPU points have the correct hwfly ribbon v1 cable with mofset included on it.
- 1st boot took a while while the chip tested glitching. Following boots take no time. It boots right away, so the chip learned the correct glitch timing.
- If no MicroSD card is present, I get the rasp logo and text "No SD card"
- if powered on with both volume buttons pressed, it boots into Official Firmware
- if I take hekate payload, rename it to payload.bin and put it on the MicroSD card root, it loads Hekate with no problem
- if I take atmosphere fusee payload, rename it to payload.bin and put it on the MicroSD card root (with all atmosphere files too on the SD card), it won't boot. It stays on black screen. And that's my main problem as I can't boot into atmosphere.

Am I missing something?


EDIT: Installation photos attached. (I always put a little coin next to the solder points to scale the size. It's a habit I have)
 

Attachments

  • IMG_20230620_230601.jpg
    IMG_20230620_230601.jpg
    3.4 MB · Views: 28
  • IMG_20230621_110115.jpg
    IMG_20230621_110115.jpg
    3.9 MB · Views: 31
Last edited by ojobenito,
J

jmmc

Well-Known Member
Member
Level 9
Joined
May 8, 2011
Messages
168
Trophies
1
XP
1,685
Country
ojobenito said:
I got 3v3 from the capacitor to the right of the RAM modules, as shown in the PDF Picofly guide that is uploaded on this forum.


Hekate does indeed load with no problems when put on the MicroSD card root folder renamed to payload.bin

In summary:
- Console is V1 Erista patched updated to last firmware (16.0.3, I think)
- Multimeter installation checked ok. I've been doing console modifications since PSX era. Not new on that. CPU points have the correct hwfly ribbon v1 cable with mofset included on it.
- 1st boot took a while while the chip tested glitching. Following boots take no time. It boots right away, so the chip learned the correct glitch timing.
- If no MicroSD card is present, I get the rasp logo and text "No SD card"
- if powered on with both volume buttons pressed, it boots into Official Firmware
- if I take hekate payload, rename it to payload.bin and put it on the MicroSD card root, it loads Hekate with no problem
- if I take atmosphere fusee payload, rename it to payload.bin and put it on the MicroSD card root (with all atmosphere files too on the SD card), it won't boot. It stays on black screen. And that's my main problem as I can't boot into atmosphere.

Am I missing something?


EDIT: Installation photos attached. (I always put a little coin next to the solder points to scale the size. It's a habit I have)
Click to expand...
If you do emmc benchmark test in hekate, it finish with a slow emmc mode?
 
Last edited by jmmc,
hippy dave

hippy dave

BBMB
Member
Level 33
Joined
Apr 30, 2012
Messages
9,897
Trophies
2
XP
29,536
Country
United Kingdom
ojobenito said:
I got 3v3 from the capacitor to the right of the RAM modules, as shown in the PDF Picofly guide that is uploaded on this forum.


Hekate does indeed load with no problems when put on the MicroSD card root folder renamed to payload.bin

In summary:
- Console is V1 Erista patched updated to last firmware (16.0.3, I think)
- Multimeter installation checked ok. I've been doing console modifications since PSX era. Not new on that. CPU points have the correct hwfly ribbon v1 cable with mofset included on it.
- 1st boot took a while while the chip tested glitching. Following boots take no time. It boots right away, so the chip learned the correct glitch timing.
- If no MicroSD card is present, I get the rasp logo and text "No SD card"
- if powered on with both volume buttons pressed, it boots into Official Firmware
- if I take hekate payload, rename it to payload.bin and put it on the MicroSD card root, it loads Hekate with no problem
- if I take atmosphere fusee payload, rename it to payload.bin and put it on the MicroSD card root (with all atmosphere files too on the SD card), it won't boot. It stays on black screen. And that's my main problem as I can't boot into atmosphere.

Am I missing something?


EDIT: Installation photos attached. (I always put a little coin next to the solder points to scale the size. It's a habit I have)
Click to expand...
Did you try booting fusee from Hekate?
 
  • Like
Reactions: QuiTim
abal1000x

abal1000x

Well-Known Member
Member
Level 8
Joined
Jun 5, 2022
Messages
1,065
Trophies
0
XP
1,377
Country
Gaza Strip
ojobenito said:
I got 3v3 from the capacitor to the right of the RAM modules, as shown in the PDF Picofly guide that is uploaded on this forum.


Hekate does indeed load with no problems when put on the MicroSD card root folder renamed to payload.bin

In summary:
- Console is V1 Erista patched updated to last firmware (16.0.3, I think)
- Multimeter installation checked ok. I've been doing console modifications since PSX era. Not new on that. CPU points have the correct hwfly ribbon v1 cable with mofset included on it.
- 1st boot took a while while the chip tested glitching. Following boots take no time. It boots right away, so the chip learned the correct glitch timing.
- If no MicroSD card is present, I get the rasp logo and text "No SD card"
- if powered on with both volume buttons pressed, it boots into Official Firmware
- if I take hekate payload, rename it to payload.bin and put it on the MicroSD card root, it loads Hekate with no problem
- if I take atmosphere fusee payload, rename it to payload.bin and put it on the MicroSD card root (with all atmosphere files too on the SD card), it won't boot. It stays on black screen. And that's my main problem as I can't boot into atmosphere.

Am I missing something?


EDIT: Installation photos attached. (I always put a little coin next to the solder points to scale the size. It's a habit I have)
Click to expand...
It might related, i dont know, but theres issue about it on the newest atmosphere 1.54.
https://github.com/Atmosphere-NX/Atmosphere/issues/2157


Might be related:
You might add the cmd resistor so the total value around 100 ohms. Its to fixed the 'slow emmc' issue.
Usually when in hekate we backup the emmc, shows 'slow emmc'.
i experience this on v2 and lite.
 
O

ojobenito

Active Member
Newcomer
Level 3
Joined
Jul 20, 2019
Messages
31
Trophies
0
Age
44
XP
289
Country
Spain
jmmc said:
If you do emmc benchmark test in hekate, it finish with a slow emmc mode?
Click to expand...
It looks the emmc is not "slow", but a regular one (screenshot attached)
hippy dave said:
Did you try booting fusee from Hekate?
Click to expand...
Yes, I've tried that and it works and loads Atmosphere with no problem.

I don't know what can be causing the issue of not loading Atmosphere directly when booting, but Hekate loads (and Atmosphere loading from Hekate works ok, too)
Anyway, that's a little inconvenient and I'd prefer to load Atmosphere when booting the console.
 

Attachments

  • IMG_20230621_204307.jpg
    IMG_20230621_204307.jpg
    4 MB · Views: 35

Site & Scene News

Go to forum More news

Popular threads in this forum

Emulation Homebrew  duckstation for Switch

Can you trade in a banned switch for an unbanned one?

Why is Atmosphere so dominant?

Crosscode Hacking thread

Hacking  Weird findings from that DQ trilogy switch port

Migswitch backups without certificate files

Hacking Misc Tutorial  Eiyuden Chronicle Hundred Heroes save editing

switch change sd card, but android start fail

General chit-chat
Help Users
  • No one is chatting at the moment.
    Veho @ Veho: Nobody is reading what you post.