You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to follow your instructions for flashing UF2 firmware using release 1.31 of the norom-firmware.uf2 (which is the only UF2 NoRom firmware I saw available). However the badge never automatically unmounted and when I powered back on my badge I still had the stock defcon firmware. Have you gotten this flashing method to work with NoRom firmware? If so, any idea what might have gone wrong on my end?
Thanks
The text was updated successfully, but these errors were encountered:
My badge is suffering something similar. Although with mine, neither the screen nor the LEDs - with the exception of the power/charge LED - light up. But when I connect it to an OS (either Linux or Windows), the internal storage can be explored. But it doesn't autoamtically reboot once a .uf2 file is copied to it, regardless of which OS it's connected to. Disconnecting and reconnecting the device, or pressing the reset button (under the boot button) on the device, results in the internal storage popping up in the OS again. Only this time, the .uf2 file is no longer present.
I've tried to research this problem and all my research points to either a problem with the bootloader (which is a software problem), or some kind of hardware problem. I don't see this being a software problem because it happened before I tried to make any changes to the installed software. But I'm not not skilled in hardware troubleshooting for devices like this. So I'm stuck.
Hi @jaku ,
I tried to follow your instructions for flashing UF2 firmware using release 1.31 of the norom-firmware.uf2 (which is the only UF2 NoRom firmware I saw available). However the badge never automatically unmounted and when I powered back on my badge I still had the stock defcon firmware. Have you gotten this flashing method to work with NoRom firmware? If so, any idea what might have gone wrong on my end?
Thanks
The text was updated successfully, but these errors were encountered: