Picofly doesn't trigger on version 2.82

[sdalmeida]

Switch Model: OLED
OFW Version: 17.0.1
CFW Version: 22.1.0
Method of update: Modchip Toolbox
Description of issue:

After updating my picofly from version2.75 to 2.82, the modchip turned on, beige light came up and the Hekate screen showed up. I powered the console off (via the power button on Hekate), but after that, the modchip would not glitch anymore. No lights on the modchip would come on. It's as if the modchip couldn't detect that the console had been turned on.

After unplugging the battery, and plugging it back in, the same issue appeared. Beige light on, Hekate screen appeared, then the modchip would not trigger again.
I reflashed version2.75 and the modchip is now working as expected.

No sure if there are logs that I can provide, or steps to replicate. I have 3 OLED consoles, and I can only replicate on 1 of them.

[DefenderOfHyrule]

that is definitely interesting, it sounds like the actual flashing process went wrong/the rp2040's flash experienced corruption for some reason. did updating to 2.82 via modchip toolbox after reflashing 2.75 manually fix the issue? and was it an actual beige light or yellow/amber?

(i've personally done all of the testing i can think of myself, including purposefully "bricking" my own consoles, which recovered fine with 2.82)

[sdalmeida]

I didn’t try re-flashing to 2.82 after going back to 2.75. As for the light color, it’s hard to know if it’s yellow/amber or beige. It looks beige to me.

[codewizdevs]

I used this firmware version on normal non oled switch and same thing happened. But on my oled it works fine, however i would like to downgrade my oled to 2.75 when using picofly toolbox to downgrade it wont do it, version always stays the same, i need usb flash?

Also on 2.82 ofw boot works fine, 22.1.0 latest, fuse count 23.

[DefenderOfHyrule]

I used this firmware version on normal non oled switch and same thing happened. But on my oled it works fine, however i would like to downgrade my oled to 2.75 when using picofly toolbox to downgrade it wont do it, version always stays the same, i need usb flash?

Also on 2.82 ofw boot works fine, 22.1.0 latest, fuse count 23.

you should be able to freely downgrade firmware versions without issue. I have not been able to reproduce this issue from a few hours of messing around with 2.82 this morning, can both of you record the modchip debug LED (if you can reproduce this)?

[DefenderOfHyrule]

and also, could you guys tell me what modchip you're using exactly? (stock dev board or pre-made modchip)

it may actually be due to the added detection of CLK, which i didn't expect to be an issue. please also test the release below, the only change is that it has the CLK check removed

2.83.zip

[codewizdevs]

I am using premade picofly on both devices, will test oled tomorrow as i am not at home, however the non oled i think my picofly is bricked, this is how it behaves:

When powered on even when battery disconected, nothing no lights, boots straight into ofw.

I tried connecting usb flash addon and it just heats up on the capacitors side of usbc connector. This started after i flashed 2.81 i think, it booted fine, pico toolbox said v2.81 then after i rebooted again picofly died and it would only boot into ofw. So now i am waiting for another picofly.

Also boot and reset buttons do nothing, it goes to ofw either way.

[DefenderOfHyrule]

I am using premade picofly on both devices, will test oled tomorrow as i am not at home, however the non oled i think my picofly is bricked, this is how it behaves:

When powered on even when battery disconected, nothing no lights, boots straight into ofw.

I tried connecting usb flash addon and it just heats up on the capacitors side of usbc connector. This started after i flashed 2.81 i think, it booted fine, pico toolbox said v2.81 then after i rebooted again picofly died and it would only boot into ofw. So now i am waiting for another picofly.

Also boot and reset buttons do nothing, it goes to ofw either way.

that sounds very odd, the bootloader is untouched during any payload based flashing so it should at least still be fixable through the means of physically flashing via the USB debug port.

for the time being i'll replace the latest 2.82 release with the release above (with CLK detection removed) as i'm 99% sure that's what caused this issue in the first place, i will continue investigating myself as well though

[codewizdevs]

As i am new to the scene, why would someone use 2.75+ version when 2.75 works perfectly fine and it did for months on my oled? Are there any downsides to it?

[DefenderOfHyrule]

As i am new to the scene, why would someone use 2.75+ version when 2.75 works perfectly fine and it did for months on my oled? Are there any downsides to it?

it's mainly for possible performance and compatibility improvements. but as you already mentioned, there's no need to update if everything works the way it does for you currently

at the moment I'm just trying to improve several aspects of this firmware (including restoring the ability to boot OFW after a syscfw firmware update) but it requires a lot of troubleshooting and research, it's good to have people test my releases but at the same time I hate to be the one causing issues like this issue, despite many hours of testing I did on my own consoles

[codewizdevs]

Why did you mention that OFW have problems booting i never had these problems on your latest firmware versions?

Also thank you for your time, not a lot of people would take projects like these.

[codewizdevs]

@DefenderOfHyrule

Sorry to bother again, i have some knowledge in firmware dev and used dev boards before, however not near knowledgable as you are, but i tried to help by looking the code and pushed it over 10 agents with opus 4.7, we come up with these two snippets, now i know you dont like to use AI for dev like this but if you would have time to read these 3 snippets, maybe there is something that can help with CLK and BCT.

Edited:

bct_snippet.txt
clk_snippet.txt
code_review.txt

[sdalmeida]

and also, could you guys tell me what modchip you're using exactly? (stock dev board or pre-made modchip)

it may actually be due to the added detection of CLK, which i didn't expect to be an issue. please also test the release below, the only change is that it has the CLK check removed

2.83.zip

I am using a pre-made modchip.

I've acquired a few more consoles over the weekend and tried to replicate this issue without avail 😞

I'll re-flash my consoles with the latest version and I'll let you know if I run across any issues 👍

[KimPig]

I have the same issue. It was a Picofly OLED model, and I updated from version 2.74 to 2.82 using the toolbox. The update completed successfully, but after rebooting, the LED initially turned green and the console booted into OFW. After rebooting again, now no LED lights up at all. If I flash the previous firmware version, is there a chance the modchip will come back to life?

[codewizdevs]

@KimPig

When this happened to me my modchip died, however some people report that it works for them after flashing the firmware with usbc. This was probably my own fault as i reversed polarity of usbc so i maybe killed it.

[DefenderOfHyrule]

I have the same issue. It was a Picofly OLED model, and I updated from version 2.74 to 2.82 using the toolbox. The update completed successfully, but after rebooting, the LED initially turned green and the console booted into OFW. After rebooting again, now no LED lights up at all. If I flash the previous firmware version, is there a chance the modchip will come back to life?

was this with the latest uploaded build of 2.82? either way, the bootloader of the rp2040 itself is untouched so you can always reflash the chip no matter what