Most recent activity
-
Update! Got annoyed by the screen flashing next to my bed while I was waiting for it to discharge, so I kept looking around for any other ideas (sorry!). Saw some of the same recommendations to upgrade the firmware, and was reminded that there's a cutting-edge build I could try. Pushed through flashing that twice in the web IDE and once through nRF Connect on my android phone and it eventually loaded up alright. I checked the firmware version reported using the "About" app and there's been no issue since (about 30hrs have passed). Haven't reinstalled the "default apps" or had to upgrade the bootloader.
Before this, I was running the most recent stable firmware, which I believe is 2v16?
Bootloader said 2v15, which I gather is normal as you mentioned (somewhere else?) that the BL and FW dont necessarily have the same version. Rebooting the device now, it still says bootloader 2v15.Unfortunately, it didn't occur to me to take video of the loop, but from memory, I was seeing the white screen of the bootloader with the version number, "NO NEW FW" after checking storage(?), and the line "Booting...".
The backlight would then turn off after a second, and after 5 or so more seconds it would go blank for a few ms and boot back up into the same screen.
I was able to get into DFU mode just fine by holding the button during boot and releasing during the <====>, and as I've found flashing did work eventually. I was not able to boot without loading code by holding the button longer (tried up to a minute) and at no point was I able to get to the Bangle.js loading screen with the MAC address.Everything seems alright from my end now, but if you reckon there's anything I can do to help diagnose this in future, I'm able to help (again, sorry for moving forward on this so impatiently).
-
Hi @Gordon, you wanted updates if this happened again! I'm pretty sure I'm experiencing the same issue myxor was having. My Bangle.js 2 is (currently) bootlooping in the same way they described and firmware reflashes aren't getting anywhere.
I've also tried flashing both the modified firmware you originally uploaded, and the newer one that fanoush uploaded, and those haven't produced any change.
Situ was, I had uploaded some new code of mine to the device from the web IDE maybe a minute ago, and was trying to get it connected back to my phone to try out a function I'd just written. The watch wasn't reconnecting to my phone after disconnecting from my computer, so I held the button to reset it. Screen went blank, got the normal WATCHDOG message, and after showing "BOOTING..." the backlight turned off and it rebooted into the same screen.
Unsure if the code I uploaded caused the issue directly (doesn't look like it should, I can upload snippets) or I've done the same thing as myxor and corrupted the SPIFLASH.
Can cooperate helping you get a clone of the flash if that's what you need.
I've switched back to 2v16 as I think I was having stability issues with the cutting-edge firmware, I'll let you know if this happens again.