You are reading a single comment by @fanoush and its replies.
Click here to read the full conversation.
-
although it is not actually waiting in that "BANK0 error" state, it requires the long-press reboot to enter the waiting mode
that looks like bug to me, espruino bootloader is based on Nordic DFU bootloader code which waits forever for DFU upload if bank0 is invalid, there is nothing better to do in this state anyway - bank0 is space for main application (=espruino javascript runtime), if that is empty=invalid what else can be done(?)
well maybe by default it has some timeout for connection and then it just reboots to do it again and we broke that loop by waiting for button after first connection timeout(?)
fanoush
That would be super useful to show it's not "bricked", and also maybe a message "still waiting for firmware" - although it is not actually waiting in that "BANK0 error" state, it requires the long-press reboot to enter the waiting mode.
And yes, I was able to avoid an engineering kit flashing mode involving the third-party flasher app, but having me prepared for such outcome would be very handy once I click the lucrative glowing yellow button while naively expecting the shiny new firmware after that one click. But instead experiencing a setback of half an hour to figure out what just happened.
Specifically, a message "if something goes wrong, long press & repeat, if it does not help, try another computer/browser, if that does not help too, download firmware from X and use app Y on the phone"