Picofly AIO Thread

[rehius]

Updated to 2.64 but still can't boot into OFW by holding vol+ and vol- 1st then short press power button once?Am I doing the right sequence?

either that or you can press Vol+ / Vol- on the "No SD" screen.

if you get a black screen - looks like your BOOT0 got desynced with the firmware. You should boot into the Full Stock FW using hekate, then update the system over WiFi to the latest one.

If you already have 16.0.1, you can restore clean BOOT0 backup (can be taken from another console of the same type, or generated - I haven't tested that) using hekate

 

[cliffkhew]

My OFW is v15.0.1,emunand v16.0.1,is it fw desysynced because of this?

 

[RexSonic]

Try updating your ofw to 16.0.1

 

[cicci084]

yeah i saw it

I actually received this console with a rp2040 already installed.
It's not my installation, it's a dear friend.
The strange thing is that if I extract the microsd and start the console, the "NO SD CARD" screen appears but it is not the one with the picofly logo, it appears
with the hekate logo.

The picofly logo appears on the 2 consoles I installed.

Yet I disassembled it, once I made sure of the rp2040 zero chip, I upgraded to 2.61.

The picofly toolbox was successful with the update, however I don't know if it was actually successful.

Even if I select info from the toolbox, I don't get information about the fw version.

Maybe the installed firmware is older than 2.5 and doesn't support toolbox update?

I want to specify that everything works great and the startup times are very fast.

Do I have to install the USB port again and install from pc?

 

[rehius]

The strange thing is that if I extract the microsd and start the console, the "NO SD CARD" screen appears but it is not the one with the picofly logo, it appears
with the hekate logo.

That should be v2.5, so no software update feature (don't try to update it, that would break BOOT0). Have to solder USB there. Custom logo comes with v2.6.

 

[ppeach]

Thanks to the developer.

Installed on Lite.
hos using 16.0.1.
picofly is FW2.64.
In case of cold boot, hekate sometimes fails to start.
In that case, hos will boot.
Shutting down and booting again usually works.
Is it because emmc is notorious Toshiba?

 

[rehius]

Thanks to the developer.

Installed on Lite.
hos using 16.0.1.
picofly is FW2.64.
In case of cold boot, hekate sometimes fails to start.
In that case, hos will boot.
Shutting down and booting again usually works.
Is it because emmc is notorious Toshiba?

if you have Cyan light, that means, there was no enough power to glitch the CPU. (a single mosfet used, for example)

with 2.64 you can notice that only on a really cold boot (battery detach, 20s power button press). regular poweroff and reboot use warm boot where less energy is required

 

[cicci084]

That should be v2.5, so no software update feature (don't try to update it, that would break BOOT0). Have to solder USB there. Custom logo comes with v2.6.

Wow, I am honored to reply to your message. Thanking you for your response, allow me to be happy to hear from you.
As a layman, I tried to update and luckily the console works regularly.

All right in all cases I will pay and update.

Thanks

Excellent job bro!

 

[ppeach]

if you have Cyan light, that means, there was no enough power to glitch the CPU. (a single mosfet used, for example)

with 2.64 you can notice that only on a really cold boot (battery detach, 20s power button press). regular poweroff and reboot use warm boot where less energy is required

It uses the shutdown feature of hekate and hos.
mosfet uses hwfly flex cable.
The wire between the flex cable and pikofly is 0.1mm.
Is this problem caused by too thin wire between flex cable and pikofly?

 

[rehius]

luckily the console works regularly

The only thing that breaks there is "Reboot to OFW" / Vol+ & Vol-
by using Atmosphere you won't notice that

Post automatically merged: Apr 11, 2023

Is this problem caused by too thin wire between flex cable and pikofly?

I doubt it, what LED colour do you have when the error happens?

 

[ppeach]

The only thing that breaks there is "Reboot to OFW" / Vol+ & Vol-
by using Atmosphere you won't notice that

Post automatically merged: Apr 11, 2023

I doubt it, what LED colour do you have when the error happens?

I am sorry.
I have rebooted several times and could not reproduce the problem.
The hekate starts normally in green after the blue blinking.
I just opened the back plate and replaced some of the Kapton tape.
It no longer fails.

edit:
The LEDs were orange when the problem occurred.

 

[ngoanrazor]

Hello anyone, When I copy and paste firmware to Rp2040 zero, it auto disconnect pc. So, it is properly? is it upload firmware success?

 

[MXRD4K1LL4]

Hello anyone, When I copy and paste firmware to Rp2040 zero, it auto disconnect pc. So, it is properly? is it upload firmware success?

Every raspberry does that, it is normal and means it should have uploaded the uf2 file into it (it's also normal if the file do not appear when you plug it again but you should upload it again)

 

[linuxares]

Hello anyone, When I copy and paste firmware to Rp2040 zero, it auto disconnect pc. So, it is properly? is it upload firmware success?

Yepp! Thats how a chip that can be programmed via uf2 does. It's really sketch but it's how it programs itself.

 

[rehius]

edit:
The LEDs were orange when the problem occurred.

that is eMMC communication related. might be Toshiba

 

[ngoanrazor]

Every raspberry does that, it is normal and means it should have uploaded the uf2 file into it (it's also normal if the file do not appear when you plug it again but you should upload it again)

Yepp! Thats how a chip that can be programmed via uf2 does. It's really sketch but it's how it programs itself.

Thanks all

 

[ppeach]

that is eMMC communication related. might be Toshiba

The LEDs are almost never orange anymore.
I do not know why.

 

[GodzKratos]

Installed picofly with a single mosfet. LED light would be blue then green but no display. Am I missing something?

 

[rehius]

Installed picofly with a single mosfet. LED light would be blue then green but no display. Am I missing something?

Might be any cable is not connected. For example, on NS Lite without power / volume buttons flat cable the display won't turn on

 

[cicci084]

The only thing that breaks there is "Reboot to OFW" / Vol+ & Vol-
by using Atmosphere you won't notice that

Post automatically merged: Apr 11, 2023

I doubt it, what LED colour do you have when the error happens?

---------------------------------------------------------------------
I have to try when I get home for this console.
---------------------------------------------------------------------
Another console, another question.
But this thing happened to me just now.
I just installed another picofly with fw 2.61 (I hadn't seen the most recent ones) and I can't start it in OFW.

I state that I only installed the chip and turned on the console.
I turn on the console without MICROSD and the picofly NO SD CARD logo appears.

Then it froze on a black (but backlit) screen.
I unplugged the battery and plugged it back in and so I prepared the microSD.
If by hekate I reboot into OFW a loading screen appears which then freezes and the console reboots.
What will I have done wrong? (I did the same procedutre of the other 2 consoles).
Advice? Did I damage something?
I attach photos.