Espruino JavaScript
Bangle Js.2 won't get past "Storage OK" message #5356
Replies: 1 comment
-
|
Posted at 2021-12-10 by @gfwilliams Have you tried holding the button a bit longer? It looks to me like you're releasing is as soon as the screen changes, but as a result you're not holding it long enough for the watch to actually do a full reboot. Also, it looks from that like somehow the contents of storage have been erased - in which case you'd have to go into the app loader, about, and install default apps Posted at 2021-12-10 by Muldjord Hi Gordon, thank you for answering. Yes, I have tried pressing in the button for much longer. Then it just keeps cycling back to the screen you see in the video. There are apps on it. When, 1 in 50 times, it actually gets to the clock, I can click the button and get the menu, settings, about app and so on. The reason I immediately release the button when the screen changes in the video, is that I figured out that that gave me the best chances of it getting past that "Storage OK" screen. EDIT: Hang on, I'll upload a video where I keep the button pressed and also, after several cycles, manage to get it to the clock and can show the menu. Posted at 2021-12-10 by Muldjord Here's the video showing a much longer press, and eventually getting to the clock: Posted at 2021-12-10 by johan_m_o Maybe @gfwilliams has some ideas, but I'd try a full reset: Followed by an update to the latest cutting edge firmware: Posted at 2021-12-10 by HughB It looks like the firmware is corrupted. It is possible to do this if you upload a file to FLASH using the Web IDE. Its a bit too easy to do this. If you can connect through the IDE try typing 'Bangle.factoryReset();' in the left hand side. See what happens. Then try reflashing the latest firmware. To do that you need to be able to get your Bangle to reboot to the DFU screen. Gordon has done a good video on this. Dont worry - its pretty hard to brick these watches and as long as you can get Bluetooth connectivity you can usually recover them. Posted at 2021-12-10 by @gfwilliams Thanks - that is really helpful. It looks to me like somehow the bootloader has been corrupted - I have no idea how! Luckily there should be an easy fix for that - I'll update properly in an hour Posted at 2021-12-10 by Muldjord Sounds great, looking forward to that. No idea myself. All I've done is connect to it through Chrome from my smartphone and also through Gadgetbridge. Yesterday I read about the firmware upgrade but never got anywhere with it. But I only did that after this problem occurred so... Posted at 2021-12-10 by @gfwilliams Ok, so I've just deliberately erased the bootloader on a Bangle and I see exactly what you're getting (no blocky 'DFU' screen). So I guess what happened is somehow when programming yours we messed up - programming got as far as doing Bangle.js but not the bootloader at the end of memory. But there's a fix - please nobody else try this without consulting me first!
Now, it's probably best to update your firmware just in case as well - you can use the same Firmware Updater for this. Just go into it the same way but this time click the 'Cutting Edge build' link, then You can then go into the App Loader again, go to 'About' and 'Install default apps' and finally it'll be sorted. Sorry for all the hassle! Attachments: Posted at 2021-12-10 by Muldjord Thank you for the precise intructions. I followed them very closely, alas, no luck. The attached firmware uploaded successfully and I was presented with the "Hold button to reload" message. So I pressed the button and kept pressing it. The boot screen came up with the "Storage ok" message, and I kept pressing it. But it was again stuck in that cycle. It never gets to the clock or the "=====" as you've mentioned. I've never seen those on the screen at any time. So I decided to go ahead and open up the https://banglejs.com/apps link and connect to the watch while it was displaying the "Storage OK" screen. That works, and I can connect to the watch. I then went to "About" on the website on my phone and chose "Install default apps" (I chose "Remove all apps" first, which also went well). This worked, and it reinstalled all apps and I once again got the "Hold button to reload". Again, it got stuck at the "Storage OK" screen. I then reconnected through https://banglejs.com/apps on my phone again, and decided to try and upload the "Cutting Edge build" firmware as you mentioned through the "Firmware update" app. This took a while, but it got uploaded just fine and I again got the "Hold button to reload" message and it would load the clock, seemingly just fine. But when I pressed the button again for 10 seconds, I am right back in that loop where it gets stuck at "Storage OK", just like before. Nothing seems to have changed, unfortunately... I've tried keeping it pressed for a minute, it just keeps cycling back to that "Storage ok" screen. EDIT: Just noticed it still says "2v10.219" on the "Storage OK" screen, so I guess it didn't actually update the firmware although it uploaded something. The version chosen in the updater was "2v10.244". Posted at 2021-12-10 by johan_m_o @gfwilliams Might be that @muldjord isn't seeing any results with the described method since it doesn't seem like the firmware updater in the App loader works. I just now tested updating to 2v10.244, and the fwupdater seems to get uploaded to the watch but when it reboots there's a quick "no new fw" before it boots up to 2v10.243 that I already had installed. Posted at 2021-12-11 by 7kasper Hello! I have exactly the same problems as described here. Interestingly enough if I load or delete or change an app using the web interface the device becomes unbricked and I can do everything fine. However after each reset (10s buttonpress) the Storage Ok screen is up again and I have to do it again. Posted at 2021-12-11 by susticle Hi all, today I received my Bangle.js 2 and I'm running into similar problems. First I noticed that the screen goes black and a SW Reset is performed everytime I tried to access the "Set Time", "LCD" or "Theme" only using the touches and not the button. (Highlighting the desired entry and pressing the button works, though). This is reproducible. I then tried to reboot the watch with a 10s button press and got stuck at "Storage ok". Now and then it's possible to get past this but ending up in the behavior described earlier in this post. Any help is appreciated. Thanks! Posted at 2021-12-13 by @gfwilliams Ok, wow - sorry about this. I'm extremely surprised so many of these have had issues. I realised later in the evening after I wrote this on friday that the bootloader is actually made of two parts - the bootloader and a few bytes at the end of memory that tell the device that there is a bootloader and where it is. I'm still working my way through all the messages I got over the weekend, but I'll get back to this in a few hours, will do some more tests and get back to you - it should just be a single line to paste into the Web IDE needed to fix this (after the bootloader has been installed using the above steps). Posted at 2021-12-13 by Camo Hi ! I updated default apps and downloaded a few ones and some widgets something like 30 minutes ago, and I since have the same stuck-at-"checking storage... Storage ok"-screen issue (2v10.219) I also can't find anything wrong with the apps, so I'll wait for a fix. Just wanted to mention this for more feedback :) Edit : even if set to "stay connectable", the watch is now unable to connect to my smartphone. I didn't have this problem before the changes I did earlier, I don't know if it's linked to the main problem at hand here tho Posted at 2021-12-13 by @gfwilliams @Camo if you long-press the button do you see the low-res 'DFU' text and the '=====' going across the screen? If so I don't think it's this issue, and it could be related to you just having held the button for too long - eg effectively you just accidentally followed these steps: https://www.espruino.com/Bangle.js2#resetting-without-loading-any-code Posted at 2021-12-13 by Camo I tried holding the button when stuck on storage ok screen until the screen changes, and it worked, the reboot ended on the clock this time My watch seems to work pretty well again- at least the whole storage ok screen process didn't reappear yet Now the only issue that I'm aware of, is that I can't connect my phone to the watch (my phone can connect with other Bluetooth devices just fine, I just double checked that) and I'm a bit confused about that unexpected turn of event and new problem I admit ^^' Posted at 2021-12-13 by @gfwilliams @Camo probably best start a new thread for that one, but 2nd entry in the FAQ could be some help: https://github.com/espruino/BangleApps/wiki @muldjord the firmware update needs the bootloader to work (it copies the file over while the Bangle is still running normally, then reboots and lets the bootloader update). As it seems the bootloader update didn't work, it didn't run and then couldn't update the firmware. Please could I remotely access your Bangle? If you go to https://www.espruino.com/ide/relay/ in your PC/phone/whatever, then connect and send me a personal message with the displayed 8 digit key in, I should be able to connect to it from here and have a look and try and figure out what's happened. I'm not sure what time it is there but I'll be around here for the next 3 hours at least - you'll have to leave the window open while I'm connected though so I can still access the Bangle Posted at 2021-12-13 by Muldjord Sure, I can do that. It's 14:50 here right now. I'll probably be home in about an hour. Then I'll connect it up and update this message and PM you the code. Thanks. Posted at 2021-12-13 by Camo I tried what's in the 2nd entry of the FAQ , but nothing works Attachments: Posted at 2021-12-13 by @gfwilliams @muldjord ok great - look forward to it @Camo yes please - make a new thread. Your issues really don't have anything to do with @muldjord's issue and it's just going to be confusing for everyone me trying to sort out your problems alongside his. Posted at 2021-12-13 by Muldjord @gfwilliams, It is now connected, I'll send the code to you in a PM. The watch is currently showing the clock. Posted at 2021-12-13 by @gfwilliams @fanoush I'm not sure if you'be got any ideas, but I'm really stumped now. I've connected to the phone, dumped the entire contents of flash and UICR and copied it to a device here - and I can reproduce the bootloader not working on my watch. However I then fixed it by changing what's written at 0xFF000 and verified the bootloader worked on my watch. I then made the changes on @muldjord's watch and verified with a CRC that flash on both was identical. ... but it's still not working on his watch, even though my presumably identical device works fine. Posted at 2021-12-13 by 7kasper @gfwilliams So I am having the same issue. If you want to try another watch hit me up. Posted at 2021-12-13 by susticle Hi. I'm around for a couple of hours as well. :-) Posted at 2021-12-14 by @gfwilliams Is anyone based in the UK? It'd be handy to actually get my hands on one so I could check the flash memory with the SWD programmer, and obviously there are customs issues with Europe now. @7kasper @Susticle have you ever seen the bootloader on your watches? Or was it working once and now it's not? I believe you can still use your watch just fine. Either log in with the IDE and type Posted at 2021-12-14 by 7kasper Yeah I can use the watch fine and am really enjoying it. I wanted to update fw so I can get twisting to light up the watch but Ill wait a bit with that. Not based in UK unfortunately, but perhaps I can try SWD in the holiday. Never seen the bootloader screen btw. My dad also has the watch and I think I've seen it on that one actually. Posted at 2021-12-14 by @fanoush
well if whole flash (including softdevice and MBR?) and whole uicr is same then it runs same software so something else (hardware) must be different - like button debouncing, or pull resistor preventing also the spi flash - can it say storage OK while the flash is not responding? Posted at 2021-12-14 by @gfwilliams Ok, great. I feel like this is definitely a software problem, and luckily we can change pretty much everything from within Bangle.js, so when I figure out what the problem actually is it should be trivial to fix it remotely. Posted at 2021-12-14 by @fanoush
maybe you could vibrate a bit when entering bootloader (dfu_start is determined to be true)? Posted at 2021-12-14 by @gfwilliams @fanoush thanks - everything from address 0 to 0x100000 (1MB) is the same, and the UICR from 0x10001000 to 0x10001210 is the same. I'm not sure if I should be checking anything else? I believe the issue is it's just not entering the bootloader at all. The bootloader should always turn the LCD on, and even if for some reason the LCD wasn't responding the backlight should come on which should be pretty easy to see. The bootloader should still be fine if the SPI flash isn't responding too - but even if it wasn't by that point it should have drawn some stuff onto the screen that we'd be able to see. It's really hard to know what's up. Posted at 2021-12-14 by 7kasper Would it be possible to write an app that force loads (Branches to) the bootloader? Posted at 2021-12-15 by @gfwilliams Possibly, yes... It's not quite as easy as just jumping there though. Posted at 2021-12-15 by susticle
Sorry, I'm new to this. How does the bootloader look like? Is it the screen saying:
Then I keep seeing it.
Yes, I can do some tests with it as long I don't try to use the touchscreen to choose menu entries (then the watch keeps rebooting every time). Posted at 2021-12-15 by @gfwilliams
Yes. If you're seeing this, it's different to what is happening on the video that @muldjord posted on http://forum.espruino.com/conversations/370830/ Looking back at your past comments I think I understand what's going on (pressing the touchscreen causes a reboot?) but please could you take a video showing what happens and post it in a new thread? It just makes it way easier to see Posted at 2021-12-15 by 7kasper YES! I don't know what changed or @gfwilliams did exactly but I got mine working. Even after the update the bootloader is still not visibile, but it does load and become active. Now the watch still sometimes gets stuck in the storage ok screen. If this happens you can do the same thing, release the button as soon as the screen flickers and then wait until the bootloader times out and the watchscreen will be shown again. Posted at 2021-12-15 by @gfwilliams @7kasper thanks! That is really interesting! It makes a lot of sense too - it's possible that on some devices the LCD takes a tad longer than others to initialise. If the bootloader starts it too early it wouldn't accept any commands until Espruino started - it'd still be showing the old image from Bangle.js! Posted at 2021-12-15 by Muldjord @7kasper, Yes, I actually did exactly what you described yesterday after somehow getting it into DFU mode (even though I couldn't see it and don't quite know how I did it), getting my fw to .244. EDIT: Mine always gets stuck at the "Storage OK" screen though. I seem to be able to get it to the clock if I try releasing the button between one of those faint flashes. But I can't seem to find a pattern in it. Posted at 2021-12-16 by @gfwilliams Thanks - this is really good news then. When I thought @muldjord's was completely broken I arranged to send a replacement - @muldjord when you get that please could you send the old one back? hopefully I can use that to figure out why the screen isn't responding to the bootloader, then I can push an update to the bootloader and everything will be sorted. ... if you get stuck at 'Storage Ok' you can always just connect with the IDE and write 'load()' on the left-hand side to reload the clock. If that fails you can reinstall default apps with the app loader (as I guess during everything that went on the apps might have got corrupted somehow) Posted at 2021-12-16 by Muldjord @gfwilliams, Yes, the watch is now in the mail. Looking forward to receiving the replacement. Posted at 2022-01-06 by @gfwilliams WARNING: THIS FIX SHOULD NOT BE ATTEMPTED NOW. Instead, just go to Watch received from @muldjord, and I'm happy to report that I now have a fix for this! Thanks for waiting everyone! The issue was pretty simple - the bootloader was sending data out to the LCD too quickly (it was way faster than the spec allowed)... So as a result some of the LCDs in watches weren't able to interpret the data. So to fix this you need to update the bootloader. Same steps as before, just new file:
Now, it's probably best to update your firmware just in case as well - you can use the same Firmware Updater for this. Just go into it the same way but this time click the 'Cutting Edge build' link, then Attachments: Posted at 2022-01-06 by johan_m_o Works like a treat! Great work @gfwilliams. Posted at 2022-01-06 by 7kasper Yes can report that my watch is now fixed as well. Neat :-) Posted at 2022-01-07 by @gfwilliams That's great news! Posted at 2022-11-06 by daldred Ok, so after a long time sitting on my shelf my bangle is recharged and ready to play with again - but I'm having this issue and the steps in @gfwilliams 's post (#41 above) don't seem to help. Following ther steps, I upload the file then get 'hold button to reload', the watch goes blank then a screen appears which starts 'WATCHDOG' - but disappears before I can read any more! The I'm back to the screen with 'Bangle', a watch image (actually a bangle 1 picture?), and the fw version remains shown as 2v10.219, below this is a serial number, then at the bottom it says That's followed by a black line, and then nothing else happens. If I hold the button for longer, I get the <===== > bit, then the screen says and after minute or so it then goes to the same screen as above. Am I doing something wrong? Posted at 2022-11-07 by @gfwilliams @daldred I'm not sure if you ever actually had a problem with the bootloader in your watch? I didn't see you post here earlier? If the blocky Either way, it now seems to be fixed. So... If this shows, it's either because the Bangle.js booted with the button held down (in which case it i ntentionally doesn't load any apps as a kind of 'recovery mode') or it's because all apps got removed. I'd suggest you:
Posted at 2022-11-07 by @fanoush
you are holding for too long here. when you hold too long like this you get watchdog reboot, this is designed to get you out of lock ups when nothing else works. you should hold like 3-4 seconds on that screen, not more (the message could say this) Posted at 2022-11-07 by daldred Thanks, @gfwilliams. I think I'm there. After trying again the 'upload to v2.12 bootloader' update, and upgrade to 2.15 now seems to have worked. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2021-12-10 by Muldjord
I just received my Bangle Js.2 a couple of days ago and I've had nothing but issues with it, from bluetooth constantly disconnecting, the watch freezing completely at random times (press, long press does nothing, I have to reboot it), and whenever I reboot it (press for 10 seconds) 49/50 times it will get stuck at "Storage OK" and nothing more happens. Then, seemingly random, sometimes it will actually get past that and show the clock.
I've made a short video showing this. I assume this isn't normal, right?
https://youtu.be/YisufixY8AY
Beta Was this translation helpful? Give feedback.
All reactions