Mbed OS Bootloader.

[yasir-khilji-64]

Hello community, I'm having a hard time working on Bootloader and Over the air update.
As you can see, mbed-os-example-bootloader is deprecated. Can anyone provide with the latest bootloader example and how to perform an over the air update.

Thanks.
Regards, Yasir.

[mbedmain]

@yasir-khilji-64 thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words.
What target(s) are you using?
What toolchain(s) are you using?
What Mbed OS version are you using?
It would help if you could also specify the versions of any tools you are using?
How can we reproduce your issue?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'. This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information.

[0xc0170]

If you follow https://os.mbed.com/docs/mbed-os/v6.15/program-setup/creating-and-using-a-bootloader.html, won't you be able to create your own example?

Or https://github.com/ARMmbed/mbed-os-experimental-ble-dfu-example ?

[yasir-khilji-64]

If you follow https://os.mbed.com/docs/mbed-os/v6.15/program-setup/creating-and-using-a-bootloader.html, won't you be able to create your own example?

Or https://github.com/ARMmbed/mbed-os-experimental-ble-dfu-example ?

Hello @0xc0170, thanks for pointing out the resources.
I'm having following issues.
I read the Mbed-OS Bootloader. Made a new mbed program and did everything suggested.
After the build completes, I place the .bin in the main firmware but as I build and upload the main program, the firmware just hangs.
I'm add logs here,

[INFO: .\src\main.cpp:18] Current bootloader version: 0.0.1
[INFO: .\src\main.cpp:19] Built on: Thu Nov 04 15:01:52 2021
[DEBUG: .\src\

can you please help me here.

[yasir-khilji-64]

The other issue I'm facing is, even if I specify "target.restrict_size": "0x40000", in the bootloader program, whenever I compile main program using this bootloader, the Bootloader size is always: 0x20000.

I'm using mbed-os-5.15.0 with GCC_ARM.
I can't update to mbed-os 6 as it breaks the mbed-http library.

[yasir-khilji-64]

These are my bootloader program Regions.

Using ROM regions application, post_application in this build.
  Region application: size 0x40000, offset 0x8000000
  Region post_application: size 0x1c0000, offset 0x8040000

These are my main application Regions.

Scan: main-app
Using ROM regions bootloader, application in this build.
  Region bootloader: size 0x20000, offset 0x8000000
  Region application: size 0x1e0000, offset 0x8020000

[yasir-khilji-64]

Can anybody help here? I would like to get a work around it so that I can finalize about my hardware workflow as Bootloader and OTA is a crucial feature for my product.

[0xc0170]

I dont have much experience with bootloader. Have you modified the linker script, there are changes required like these

+#if !defined(MBED_APP_START)
+  #define MBED_APP_START 0x08000000
+#endif
+
+#if !defined(MBED_APP_SIZE)
+  #define MBED_APP_SIZE 0x80000
+#endif

And some others.

What about this fix, if you apply it to 5.15 #14994 ?

[yasir-khilji-64]

I dont have much experience with bootloader. Have you modified the linker script, there are changes required like these

+#if !defined(MBED_APP_START)
+  #define MBED_APP_START 0x08000000
+#endif
+
+#if !defined(MBED_APP_SIZE)
+  #define MBED_APP_SIZE 0x80000
+#endif

And some others.

What about this fix, if you apply it to 5.15 #14994 ?

Hello @0xc0170, thanks for your replies, but these didn't help.
I wrote a python script to pad the bootloader binary to specific size 0x40000, but the regions are not of correct size after merging.
I would appreciate if anyone can look into it.

[yasir-khilji-64]

@0xc0170 even in the latest mbed-os-6.15, the bootloader offset and regions are not correct.

In Bootloader: 
Using ROM regions application, post_application in this build.
  Region application: size 0x40000, offset 0x8000000
  Region post_application: size 0x1c0000, offset 0x8040000
  Space used after regions merged: 0x96dc

In Main App: 
Using ROM regions bootloader, application in this build.
  Region bootloader: size 0xc000, offset 0x8000000
  Region application: size 0x1f4000, offset 0x800c000
  Space used after regions merged: 0x95dc

[0xc0170]

The fix #14994 was closed so its not part of 5.15 or master branch. You need to cherry pick. If you did and it does not fix the problem, the issue is a new.

[yasir-khilji-64]

The fix #14994 was closed so its not part of 5.15 or master branch. You need to cherry pick. If you did and it does not fix the problem, the issue is a new.

Hello @0xc0170, thanks for pointing towards the Fix #14994, but unfortunately it doesn't also work. So please look in to the matter at your earliest convenience as bootloader/OTA update is a crucial feature for my project.

Thanks.
Best Regards, Yasir.

[AGlass0fMilk]

See https://github.com/AGlass0fMilk/mbed-mcuboot-demo

That should get you pointed in the right direction.

[yasir-khilji-64]

See https://github.com/AGlass0fMilk/mbed-mcuboot-demo

That should get you pointed in the right direction.

Hi @AGlass0fMilk, thanks for sharing the repo.
I'm having some confusions.
Would you place target.restrict_size in both bootloader and main app
Shouldn't the main app take its starting address from the target.bootlader_img, because in MBED OS Bootloader documentations it is provided like this.