Replies: 3 comments 8 replies
-
Beta Was this translation helpful? Give feedback.
-
|
You can regenerate boot0 just by running setting-utils-rewrite settings. .. But sounds like a really strange problem. Possibly one of your files is corrupt and that is making boot0 broken? You can also enable some boot0 debugging by setting bootDebug:1 in setting.json, and that could really help |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, as of right now, the watch is usable for me, so I might keep it for a bit - I have a ton of custom app modifications that I don't want to see gone if I reinstall all apps. I'll look into the boot0 debugging, though. |
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've recently been tinkering with bootloader scripts, and I noticed that when I upload a new version of that code from IDE, the watch would update boot0, but sometimes would corrupt a line or two from what I can see? What happens is the watch gives errors unrelated to what I uploaded, for example, if I upload a bootloader script for animating loading, it will return an error in the IDE that sleeplog.global is undefined. Same thing with different code, just different unrelated errors. I pushed through that by reuploading, but now many boot scripts are broken on my watch, and it is behaving erratically. I'm wondering, is there a way to fully regenerate the .boot0 file from scratch, hopefully mitigating these errors that have compounded?
EDIT: I found out that just erasing boot0 and running bootupdate will fix it, but I'm still getting an error that I have no idea to decipher, and cannot debug, as all of boot0 is minified and pretokenized.
Beta Was this translation helpful? Give feedback.
All reactions