You are reading a single comment by @d3nd3-o0 and its replies. Click here to read the full conversation.
  • Yeh I generally flash from ide (execute code at boot).

    I just tried writing directly to .boot0 but having too many glitches to list (it's like it's trying to load the usual Bangle OS as well as my app at the same time, as well as giving me a scrolling screen of bluetooth errors)... do I also need to be modifying and writing the following into the left hand side of the ide:

    require("Storage").write("abc.info",{
    "id":"abc",
    "name":"abc",
    "src":"abc.app.js"
    });

  • Reinstall bootloader from appstore, it uses .boot0 file.

    Now make your app use .boot1 instead of .boot0

    The info file is only for making a normal app that is listed by the app loader app. You might need your app as a clock, and also as a .boot1 file. An app being a clock just means that it is loaded by the bootloader(.boot0 AND .bootcde) App, by default.

    Depending on how your device is reset/loaded, it won't always execute the .bootcde which is the clockLoader. But sometime it will. That is why I suggest a .boot1 and a normal app clock which are identical code. This could be a workaround for you. Ofc there can be other ways to solve this too.

    But this method might cause your code to load twice, in the normal case. So we have to think about it a bit more. Probably you would delete the file : .bootcde if you are relying on .boot1 file as a clock loader instead.

    EDIT: I just realized there is a .bootrst file that overrides .bootcde behaviour, AND runs upon reset too. So instead of deleting .bootcde, and instead of writing to .boot1, you could try writing to .bootrst. Then when you want to revert back to normal behaviour , delete the .bootrst file. Now the Bootloader app's .boot0 will load and then .bootrst (Your App) will load.

    Conslusion: Write your app to .bootrst, the bootloader app(.boot0) should not try to load a clock now. Bear in mind as above has said, all this tinkering can be risky for bricking the device (If you lose access to DFU screen). If you do still have access to DFU screen, you should be fine.

About

Avatar for d3nd3-o0 @d3nd3-o0 started