-
YOOOOO!!! That fixed it, thank you so much!
Does this mean that a normal version will always not work? And is the watch going to behave normally going forward using this version, or do you think it will still need to be replaced? Or did getting it to work normal once mean it will keep acting normal assuming something else doesn't happen?
Again thank you for the help & your patience with all my questions, this is my first foray into this kind of thing :)
-
YOOOOO!!! That fixed it, thank you so much!
OK, so it is one of those two features I disabled. If you want to test more, here are two more
https://github.com/fanoush/Espruino/commits/f-2.25-no-ext32khz/
this one has only the external low speed oscillator disabled and is forked from latest 2.25 release. To get the build you click the green checkmark on the latest commit, then 'Details' on the "Firmware build / build_dfu (BANGLEJS2) (push)", then expand the "upload BANGLEJS2 build artifact" and the link to zipped build artifact is https://github.com/fanoush/Espruino/actions/runs/12569157706/artifacts/2376029447
again you need to extract it to get the DFU zipHere https://github.com/fanoush/Espruino/commits/f-2.25-no-dcdc/ is the other one disabled
https://github.com/fanoush/Espruino/actions/runs/12569255154/artifacts/2376043065Beware that the zip inside both artifacts has same name as both is one commit on top of same version.
Does this mean that a normal version will always not work? And is the watch going to behave normally going forward using this version, or do you think it will still need to be replaced?
Yes, as long as normal version keeps it enabled you would need custom build. It is few clicks on github website to make your own build but still annoying. And you got faulty watch that passed QA by mistake with slightly worse battery life. It is up to you and @Gordon to sort this out. If you can easily get it replaced then I'd go for it. I heard people e.g. in Brazil(?) pay import taxes that makes that cost too high so it depends.
Oh, that is interesting. The LOCKUP reason means that the CPU runs into hard fault and locks up. That should not happen. But since the bootloader itself works fine and is relatively stable (=you can upload DFU zip file over Bluetooth and update the firmware = it runs for many seconds without fault including BLE and the display and button working) and only the main firmware crashes, in theory it can be some power optimizations not enabled in bootloader. If you want you can try build from
https://github.com/fanoush/Espruino/actions/runs/12564223394/artifacts/2375169802 - clicking the link gives you BANGLEJS2.zip file with github build artifact that you need to extract and there is espruino_2v24.3198_banglejs2.zip file inside which is the DFU zip to flash.
The link to this zip is also in the build output here https://github.com/fanoush/Espruino/actions/runs/12564223394/job/35027073984 when you expand the "Upload BANGLEJS2 build artifact" step.
It is built from 2.24 release with this commit added https://github.com/fanoush/Espruino/commit/279204a8c1e869802bc196f76ecfe28238331911 or see the history here https://github.com/fanoush/Espruino/commits/f-bangle2/
It disables some optional stuff that should normally work and save power but if the hardware is missing some optional components on PCB or they are faulty it may help and avoid crashes.
Trying the build linked previously with SPI flash storage disabled is worth a try too, but if that does not help then this build is worth trying too (but may not help). I am also attaching the DFU zip directly if you have issues with extracting it on your phone.