pelioniot/mbed-bootloader

Generic bootloader to be used in conjunction with Pelion Device Management Client

mbed-bootloader's Issues

Questions for mbed-bootloader

Hi

I'm understanding about bootloader and referring below link.
(https://github.com/ARMmbed/mbed-bootloader)
(https://cloud.mbed.com/docs/current/updating-firmware/bootloaders.html)
(https://cloud.mbed.com/docs/current/porting/porting-the-device-management-update-client.html#bootloader)

I'm confused because could not find the answer or understand about below questions.

1. When a new firmware combined bootloader is initially flashed by drag and drop, is it right that this file is always stored in each active app and bootloader area in internal flash?
2. When we inject the secure information(ex. Device private key and certificate), where is this information stored, internal flash or external flash(SD-card)??

Could you please answer me??

Thanks.

How is bootCounter incremented?

bootCounter in main.cpp is the heap variable.
I think that it is reset by rebooting from the user application.
it incremented in upgradeApplicationFromStorage function, but i couldn't find such a code that this function is called more than once.

How does this variable increment and reach MAX_BOOT_RETRIES?

Need better information on how to configure nvstore

Building for K64F with 5.10 rc, ends up in error:

Building project mbed-bootloader (K64F, GCC_ARM)
Scan: mbed-bootloader
Scan: env
[ERROR] Attempt to override undefined parameter 'nvstore.area_1_address' in 'application[K64F]'

Not able to find documentation on how to actually configure my build correctly.

bootloader readme.md refers to internal repository

The README.md has this about Device Secret Key:

Alternatively you can choose to use a custom device specific RoT by implementing the function mbed_cloud_client_get_rot_128bit. An example can be found here.

The here points to mbed-bootloader-internal repository which is not accessible by the same audience as mbed-bootloader.

Fails to compile with LPC55S69_NS

Following these steps

mbed import https://github.com/ARMmbed/mbed-bootloader

cd mbed-bootloader

mbed compile -t ARM -m LPC55S69_NS --profile=tiny.json

Results in this

[Warning] @0,0: L6320W: Ignoring --keep command. Cannot find argument 'os_cb_sections'.
[Error] @0,0: L6218E: Undefined symbol trng_free (referred from BUILD/LPC55S69_NS/ARM-TINY/mbed-os/features/mbedtls/platform/src/mbed_trng.o).
[Error] @0,0: L6218E: Undefined symbol trng_get_bytes (referred from BUILD/LPC55S69_NS/ARM-TINY/mbed-os/features/mbedtls/platform/src/mbed_trng.o).
[Error] @0,0: L6218E: Undefined symbol trng_init (referred from BUILD/LPC55S69_NS/ARM-TINY/mbed-os/features/mbedtls/platform/src/mbed_trng.o).
Warning: L3912W: Option 'legacyalign' is deprecated.
"C:\Users\PELION~1\AppData\Local\Temp\p1120-3", line 38 (column 3): Warning: L6312W: Empty Execution region description for region RW_IRAM1
Warning: L6320W: Ignoring --keep command. Cannot find argument 'os_cb_sections'.
Error: L6218E: Undefined symbol trng_free (referred from BUILD/LPC55S69_NS/ARM-TINY/mbed-os/features/mbedtls/platform/src/mbed_trng.o).
Error: L6218E: Undefined symbol trng_get_bytes (referred from BUILD/LPC55S69_NS/ARM-TINY/mbed-os/features/mbedtls/platform/src/mbed_trng.o).
Error: L6218E: Undefined symbol trng_init (referred from BUILD/LPC55S69_NS/ARM-TINY/mbed-os/features/mbedtls/platform/src/mbed_trng.o).
Finished: 0 information, 3 warning and 3 error messages.
[ERROR] Warning: L3912W: Option 'legacyalign' is deprecated.
"C:\Users\PELION~1\AppData\Local\Temp\p1120-3", line 38 (column 3): Warning: L6312W: Empty Execution region description for region RW_IRAM1
Warning: L6320W: Ignoring --keep command. Cannot find argument 'os_cb_sections'.
Error: L6218E: Undefined symbol trng_free (referred from BUILD/LPC55S69_NS/ARM-TINY/mbed-os/features/mbedtls/platform/src/mbed_trng.o).
Error: L6218E: Undefined symbol trng_get_bytes (referred from BUILD/LPC55S69_NS/ARM-TINY/mbed-os/features/mbedtls/platform/src/mbed_trng.o).
Error: L6218E: Undefined symbol trng_init (referred from BUILD/LPC55S69_NS/ARM-TINY/mbed-os/features/mbedtls/platform/src/mbed_trng.o).
Finished: 0 information, 3 warning and 3 error messages.

Fail to reboot with ARM/IAR

I build mbed-bootloader by:
mbed compile -m K64F -t ARM --profile tiny.json
Or:
mbed compile -m K64F -t IAR --profile tiny.json
At first boot, I can see log meessage:

[BOOT] mbed Bootloader
[BOOT] ARM: 0000000000000000000000000000000000000000
[BOOT] OEM: 0000000000000000000000000000000000000000
[BOOT] Layout: 0 9420
[BOOT] Active firmware integrity check:
[ERR ] Active firmware integrity check failed

But I see none after reboot.

If I flash attached K64F bootloader tools/mbed-bootloader-k64f-block_device-sotp-v3_3_0.bin in mbed-cloud-client-example (1.3.1.1), reboot is OK:

[BOOT] mbed Bootloader
[BOOT] ARM: 74CE36607E38CD63ECDD72CE2F1262D58BF55448
[BOOT] OEM: 0000000000000000000000000000000000000000
[BOOT] Layout: 0 7188
[BOOT] Active firmware integrity check:
[ERR ] Active firmware integrity check failed
[BOOT] Slot 0 is empty
[ERR ] Active firmware invalid
[ERR ] Failed to jump to application!
[BOOT] mbed Bootloader
[BOOT] ARM: 74CE36607E38CD63ECDD72CE2F1262D58BF55448
[BOOT] OEM: 0000000000000000000000000000000000000000
[BOOT] Layout: 0 7188
[BOOT] Active firmware integrity check:
[ERR ] Active firmware integrity check failed
[BOOT] Slot 0 is empty
[ERR ] Active firmware invalid
[ERR ] Failed to jump to application!

Target
K64F

ARM Toolchain
5.24

GCC_ARM Toolchain
GNU Tools for Arm Embedded Processors 7-2017-q4-major

IAR Toolchain
7.8

mbed-bootloader
v3.3.0

mbed-os
5.8.4

Readme instructions for compile unclear

The readme specifies the following command for compile.

mbed compile -t GCC_ARM -m [target] --profile release --app-config=configs/.json

This doesn't work because you need to explicitly specify the configuration file to use.

It would be of great help to the user to include an intermediate step that asks them to choose the flash layout and other configuration choices.

Fail to build with GCC_ARM

I build mbed-bootloader with:

mbed compile -m K64F -t GCC_ARM --profile tiny.json

but fail with error message:

Compile [100.0%]: test_env.cpp
Link: mbed-bootloader
BUILD/K64F/GCC_ARM/source/bootloader_common.o: In function `printSHA256':
C:\ccli8\iot\mbed\mbed-os\mbed-bootloader/.\source/bootloader_common.c:60: undefined reference to `__wrap_printf'
BUILD/K64F/GCC_ARM/source/bootloader_common.o: In function `printProgress':
C:\ccli8\iot\mbed\mbed-os\mbed-bootloader/.\source/bootloader_common.c:73: undefined reference to `__wrap_printf'
C:\ccli8\iot\mbed\mbed-os\mbed-bootloader/.\source/bootloader_common.c:84: undefined reference to `__wrap_printf'
C:\ccli8\iot\mbed\mbed-os\mbed-bootloader/.\source/bootloader_common.c:95: undefined reference to `__wrap_printf'
C:\ccli8\iot\mbed\mbed-os\mbed-bootloader/.\source/bootloader_common.c:91: undefined reference to `__wrap_printf'
BUILD/K64F/GCC_ARM/source/main.o:C:\ccli8\iot\mbed\mbed-os\mbed-bootloader/.\source/main.cpp:89: more undefined references to `__wrap_printf' follow
collect2.exe: error: ld returned 1 exit status
[ERROR] BUILD/K64F/GCC_ARM/source/bootloader_common.o: In function `printSHA256':
C:\ccli8\iot\mbed\mbed-os\mbed-bootloader/.\source/bootloader_common.c:60: undefined reference to `__wrap_printf'
BUILD/K64F/GCC_ARM/source/bootloader_common.o: In function `printProgress':
C:\ccli8\iot\mbed\mbed-os\mbed-bootloader/.\source/bootloader_common.c:73: undefined reference to `__wrap_printf'
C:\ccli8\iot\mbed\mbed-os\mbed-bootloader/.\source/bootloader_common.c:84: undefined reference to `__wrap_printf'
C:\ccli8\iot\mbed\mbed-os\mbed-bootloader/.\source/bootloader_common.c:95: undefined reference to `__wrap_printf'
C:\ccli8\iot\mbed\mbed-os\mbed-bootloader/.\source/bootloader_common.c:91: undefined reference to `__wrap_printf'
BUILD/K64F/GCC_ARM/source/main.o:C:\ccli8\iot\mbed\mbed-os\mbed-bootloader/.\source/main.cpp:89: more undefined references to `__wrap_printf' follow
collect2.exe: error: ld returned 1 exit status

[mbed] ERROR: "c:\python27\python.exe" returned error code 1.
[mbed] ERROR: Command "c:\python27\python.exe -u C:\ccli8\iot\mbed\mbed-os\mbed-bootloader\mbed-os\tools\make.py -t GCC_ARM -m K64F --profile tiny.json --source . --build .\BUILD\K64F\GCC_ARM" in "C:\ccli8\iot\mbed\mbed-os\mbed-bootloader"
---

Target
K64F

GCC_ARM Toolchain
GNU Tools for Arm Embedded Processors 7-2017-q4-major

mbed-bootloader
v3.3.0

mbed-os
5.8.4

Smoke test doesn't work

I followed the instruction here, and got result below:

10:57:02 smoke $ ./test.sh K64F https://ruka.mbedcloudtesting.com:443
HOST: Inspecting './test/host_tests' for local host tests...
[1591063026.39][HTST][INF] host test executor ver. 0.0.13
[1591063026.39][HTST][INF] copy image onto target... SKIPPED!
[1591063026.40][HTST][INF] starting host test process...
[1591063026.40][CONN][INF] starting connection process...
[1591063026.40][CONN][INF] notify event queue about extra 240 sec timeout for serial port pooling
[1591063026.40][CONN][INF] initializing global resource mgr listener... 
[1591063026.40][GLRM][ERR] unable to load global resource manager 'raas_client' module!
[1591063026.40][GLRM][ERR] No module named 'raas_client'
[1591063026.40][HTST][INF] setting timeout to: 240 sec
[1591063026.40][CONN][ERR] Failed to connect to resource
[1591063026.41][HTST][ERR] None
[1591063026.41][HTST][WRN] stopped to consume events due to __notify_conn_lost event
[1591063026.41][HTST][INF] __exit_event_queue received
[1591063026.41][HTST][INF] test suite run finished after 0.00 sec...
[1591063026.41][HTST][INF] CONN exited with code: 0
[1591063026.41][HTST][INF] No events in queue
[1591063026.41][HTST][INF] host test result() call skipped, received: ioerr_serial
[1591063026.41][HTST][WRN] missing __exit event from DUT
[1591063026.41][HTST][INF] calling blocking teardown()
[1591063026.41][HTST][INF] teardown() finished
[1591063026.41][HTST][INF] {{result;ioerr_serial}}
10:57:06 smoke $ 

How can I run the smoke test for the mbed-bootloader?

Getting value of "update-client.bootloader-details"

The mbed os pelion example json file requires us to enter the update-client.bootloader-details address. The value for this address is taken by running the bootloader binary which shows the following line:
[BOOT] Layout: 0 8006F1C
The value 8006F1C in this case is set in to update-client.bootloader-details.

Since latest commit on mbed-bootloader, this information is not displayed any more. One way i can think of is to add a printf myself to get this address but what do you recommend?

Secondly the mbed os pelion example (currently private) is now updated to mbed-os 5.14.0 so do any idea when this repository will be updated to mbed-os 5.14?

Earlier the pelion example test cases were passing mbed-os 5.13.4 and bootloader v4.0.3 but now i am getting failures so just wanted to confirm if there any compatibilty issues with mbed-os 5.14.0 and bootloader version 4.0.3?

@MarceloSalazar

Enabling BOOT messages

Older versions of Mbed Bootloader used to display BOOT messages as below:

[BOOT] Mbed Bootloader
[BOOT] ARM: 00000000000000000000
[BOOT] OEM: 00000000000000000000
[BOOT] Layout: 0 1006F44
[BOOT] Active firmware integrity check:
[BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
[BOOT] SHA256: ABAF3AC1F2D7B8173BC5540DA50E7093C8A479E4C0148090348BD1EA68A0958F
[BOOT] Version: 1539890967
[BOOT] Slot 0 is empty
[BOOT] Active firmware up-to-date
[BOOT] Application's start address: 0x1008400
[BOOT] Application's jump address: 0x1046081
[BOOT] Application's stack address: 0x20040000
[BOOT] Forwarding to application...

Now, these messages seem gone, and it only shows like this:

Mbed Bootloader
booting...

How can I enable the rich BOOT messages? I need those for debugging purposes.

Thanks a lot.

Update to mbed-os 6.5.0 + CMake

Hi there!

I'm wondering if you are planning on updating the mbed-bootloader to mbed-os 6.5.0+ with CMake support? :)

How do we determine the content of bootloader-details?

Some significant values are not set in the BOOTLOADER_ARM_SOURCE_HASH, BOOTLOADER_OEM_SOURCE_HASH and BOOTLOADER_STORAGE_LAYOUT.

Do you plan to implement them in the future?
Does the user need to set some values?
We understand that these values are bootloader-details, but I could not find a document on this definitions.

https://github.com/ARMmbed/mbed-bootloader/blob/061032fd7604e79785152e00175dcfc15dfe06cb/mbed_bootloader_info.h#L24-L34

Should the bootloader update the onchip firmware if the checksums match?

Perhaps it's a bikeshedding point, but I find it waste of time to write a new firmware if the hash of the new and the onchip one match. See below

[1542449599.40][CONN][RXD] Download completed
[1542449605.79][CONN][RXD] Firmware install requested
[1542449605.79][CONN][RXD] Authorization granted
[1542449606.32][CONN][RXD] [BOOT] Mbed Bootloader
[1542449606.32][CONN][RXD] [BOOT] ARM: 00000000000000000000
[1542449606.32][CONN][RXD] [BOOT] OEM: 00000000000000000000
[1542449606.32][CONN][RXD] [BOOT] Layout: 0 80082A0
[1542449606.32][CONN][RXD] [BOOT] Active firmware integrity check:
[BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
[1542449606.90][CONN][RXD] [BOOT] SHA256: 769800FC671302E02F93A7102ADEF61F0F491D88FBC3DB0908F763E1770CD139
[1542449606.90][CONN][RXD] [BOOT] Version: 1542449405
[1542449606.91][CONN][RXD] [BOOT] Slot 0 firmware integrity check:
[BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
[1542449612.76][CONN][RXD] [BOOT] SHA256: 769800FC671302E02F93A7102ADEF61F0F491D88FBC3DB0908F763E1770CD139
[1542449612.76][CONN][RXD] [BOOT] Version: 1542449505
[1542449612.76][CONN][RXD] [BOOT] Update active firmware using slot 0:
[BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
[1542449628.19][CONN][RXD] [BOOT] Verify new active firmware:
[BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
[1542449628.77][CONN][RXD] [BOOT] New active firmware is valid
[1542449628.77][CONN][RXD] [BOOT] Application's start address: 0x8010400
[1542449628.77][CONN][RXD] [BOOT] Application's jump address: 0x8011041
[1542449628.79][CONN][RXD] [BOOT] Application's stack address: 0x20018000
[1542449628.79][CONN][RXD] [BOOT] Forwarding to application...

RSPIF not supported

I use "internal_kvstore_with_spif.json" as the bootloader configuration file. Then change
"target.components_add": ["SPIF"],
for
"target.components_add": ["RSPIF"],
I found out that SPIFReducedBlockDevice.cpp was not compiled, and there was a link error.

log:

Link: mbed-bootloader-NUCLEO_F412ZG
BUILD/NUCLEO_F412ZG/GCC_ARM-RELEASE/mbed-os/features/storage/system_storage/SystemStorage.o: In function mbed::BlockDevice::get_default_instance()': /home/user/mbed/mbed-bootloader/./mbed-os/features/storage/system_storage/SystemStorage.cpp:111: undefined reference to SPIFReducedBlockDevice::SPIFReducedBlockDevice(PinName, PinName, PinName, PinName, int)'
BUILD/NUCLEO_F412ZG/GCC_ARM-RELEASE/mbed-os/features/storage/system_storage/SystemStorage.o: In function SPIFReducedBlockDevice::~SPIFReducedBlockDevice()': /home/user/mbed/mbed-bootloader/./mbed-os/components/storage/blockdevice/COMPONENT_RSPIF/SPIFReducedBlockDevice.h:59: undefined reference to vtable for SPIFReducedBlockDevice'
collect2: error: ld returned 1 exit status
[ERROR] BUILD/NUCLEO_F412ZG/GCC_ARM-RELEASE/mbed-os/features/storage/system_storage/SystemStorage.o: In function mbed::BlockDevice::get_default_instance()': /home/user/mbed/mbed-bootloader/./mbed-os/features/storage/system_storage/SystemStorage.cpp:111: undefined reference to SPIFReducedBlockDevice::SPIFReducedBlockDevice(PinName, PinName, PinName, PinName, int)'
BUILD/NUCLEO_F412ZG/GCC_ARM-RELEASE/mbed-os/features/storage/system_storage/SystemStorage.o: In function SPIFReducedBlockDevice::~SPIFReducedBlockDevice()': /home/user/mbed/mbed-bootloader/./mbed-os/components/storage/blockdevice/COMPONENT_RSPIF/SPIFReducedBlockDevice.h:59: undefined reference to vtable for SPIFReducedBlockDevice'
collect2: error: ld returned 1 exit status

[mbed] ERROR: "/usr/bin/python3" returned error.
Code: 1
Path: "/home/user/mbed/mbed-bootloader"
Command: "/usr/bin/python3 -u /home/user/mbed/mbed-bootloader/mbed-os/tools/make.py -t GCC_ARM -m NUCLEO_F412ZG --profile release --source . --build ./BUILD/NUCLEO_F412ZG/GCC_ARM-RELEASE -c --artifact-name mbed-bootloader-NUCLEO_F412ZG --app-config configs/internal_kvstore_with_rspif.json"
Tip: You could retry the last command with "-v" flag for verbose output

existsErrorMessageLeadingToReboot function returns always false.

existsErrorMessageLeadingToReboot function returns always false.

bool existsErrorMessageLeadingToReboot(void) { return false; }

Are you going to implement the contents in the future?
Or does the user need to implement them adapted to the user application?

mbed-bootloader build doesn't find mbed_trace.h and fails

mbed-bootloader when built with mbed-cli with newer mbed-os (commit: 3252530e3a94d4d39e70d67c779577e0e57365f1) fails to build. Build logs and steps to reproduce given below. It's suspsected that .mbedignore list is causing this. An analysis of this is needed.

$ git clone https://github.com/ARMmbed/mbed-bootloader.git
Cloning into 'mbed-bootloader'...
remote: Enumerating objects: 21, done.
remote: Counting objects: 100% (21/21), done.
remote: Compressing objects: 100% (13/13), done.
remote: Total 101 (delta 9), reused 15 (delta 8), pack-reused 80
Receiving objects: 100% (101/101), 61.69 KiB | 0 bytes/s, done.
Resolving deltas: 100% (33/33), done.
Checking connectivity... done.
$ cd mbed-bootloader/
$ ls
bootloader_mbedtls_user_config.h  firmware_update_test  LICENSE        mbed_bootloader_info.h  mbed-os.lib         power_cut_test  sd-driver.lib  tiny.json
configs                           fix-mbed-os-compile   mbed_app.json  mbed-cloud-client.lib   minimal-printf.lib  README.md       source
$ mbed deploy
[mbed] Working path "/home/navkaj01/code/mbed-bootloader" (program)
[mbed] Adding library "mbed-os" from "https://github.com/ARMmbed/mbed-os" at rev #610e35ddc6d5
[mbed] Adding library "mbed-cloud-client" from "https://github.com/ARMmbed/mbed-cloud-client" at rev #62de4b89d235
[mbed] Adding library "sd-driver" from "https://github.com/ARMmbed/sd-driver" at rev #ae7e7440054c
[mbed] Adding library "minimal-printf" from "https://github.com/ARMmbed/minimal-printf" at rev #5cbf9d1dcb58

-- set mbed-os tip to latest (as of 2/8) --

$ mbed compile  -c -t GCC_ARM -m K64F --profile=tiny.json
<snip>
Compile [ 51.5%]: HeapBlockDevice.cpp
Compile [ 51.8%]: ssl_cli.c
Compile [ 52.2%]: ProfilingBlockDevice.cpp
Compile [ 52.5%]: ObservingBlockDevice.cpp
Compile [ 52.8%]: SlicingBlockDevice.cpp
Compile [ 53.2%]: ReadOnlyBlockDevice.cpp
Compile [ 53.5%]: ssl_srv.c
Compile [ 53.8%]: MBRBlockDevice.cpp
Compile [ 54.2%]: ffunicode.cpp
Compile [ 54.5%]: x509_crt.c
Compile [ 54.8%]: Dir.cpp
Compile [ 55.1%]: lfs_util.c
Compile [ 55.5%]: File.cpp
Compile [ 55.8%]: FileSystem.cpp
Compile [ 56.1%]: kv_config.cpp
[Fatal Error] kv_config.cpp@30,10: mbed_trace.h: No such file or directory
[ERROR] ./mbed-os/features/storage/kvstore/conf/kv_config.cpp:30:10: fatal error: mbed_trace.h: No such file or directory
 #include "mbed_trace.h"
          ^~~~~~~~~~~~~~
compilation terminated.

[mbed] ERROR: "/usr/bin/python" returned error.
       Code: 1
       Path: "~/code/mbed-bootloader"
       Command: "/usr/bin/python -u ~/code/mbed-bootloader/mbed-os/tools/make.py -t GCC_ARM -m K64F --profile tiny.json --source . --build ./BUILD/K64F/GCC_ARM-TINY -c"
       Tip: You could retry the last command with "-v" flag for verbose output
---
<snip>

Mbed OS PR #12278 breaks compilation

Mbed OS renamed target.default_lib to target.c_lib in PR ARMmbed/mbed-os#12278 which breaks the current configuration files.

@SeppoTakalo I would recommend pinning Mbed OS to a version to your liking.

Update instructions to benefit from `mbed dm` feature

Mbed OS 5.10 (about to be released) supports merging the application with the bootloader automatically.
Requires having Mbed CLI 1.8.x

Instructions on this mbed-bootloader repo should be updated:
https://github.com/ARMmbed/mbed-bootloader#build-instructions

An include references to documentation, for example:

• Mbed CLI
  https://os.mbed.com/docs/latest/tools/cli-update.html (to be made available asap)
• Create an application include a bootloader
  https://os.mbed.com/docs/latest/tutorials/bootloader.html (to be made available asap)

@LiyouZhou is this something you could help with?

sotp configuration in mbed_app.json for UBLOX_EVK_ODIN_W2 seems too small for default bootloader image size

The SOTP configuration in mbed_app.json for UBLOX_EVK_ODIN_W2 places sotp-section-1 at 32k bytes past the start of flash. However, the default bootloader image size is larger than that, at 59k bytes. Assuming the bootloader is written to start of flash, this means that the bootloader image overlaps the sotp section which will result in a corrupted system.

Please either correct my understanding of the flash layout for bootloader+SOTP+App, or suggest corrected offsets for the 2 sotp sections as well as any additional changes that should be applied to the App image. For example, I assume that if the sotp offset is changed in the bootloader's mbed_app.json, then the same change should be made in the app's mbed_app.json; are there any other changes?

Here are the steps to build:

$ git clone [email protected]:armmbed/mbed-bootloader
$ git checkout v3.3.0
$ mbed config ROOT .
$ mbed target UBLOX_EVK_ODIN_W2
$ mbed toolchain GCC_ARM
$ arm-none-eabi-gcc --version
arm-none-eabi-gcc (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
$ mbed compile

This results in the following output:

...
Elf2Bin: mbed-bootloader
+-----------------------------------------------+-------+-------+-------+
| Module                                        | .text | .data |  .bss |
+-----------------------------------------------+-------+-------+-------+
| [fill]                                        |   137 |     4 |    27 |
| [lib]/c.a                                     | 24925 |  2472 |    89 |
| [lib]/gcc.a                                   |  3112 |     0 |     0 |
| [lib]/misc                                    |   208 |    12 |    28 |
| fix-mbed-os-compile/pal_polyfill.o            |     4 |     0 |     0 |
| mbed-cloud-client/factory-configurator-client |  1676 |     0 |    92 |
| mbed-cloud-client/mbed-client-pal             |   708 |     4 |     4 |
| mbed-cloud-client/update-client-hub           |  2275 |     4 |    16 |
| mbed-os/drivers                               |  1476 |     0 |    20 |
| mbed-os/features                              |  2032 |     0 |     0 |
| mbed-os/hal                                   |  1182 |     4 |    64 |
| mbed-os/platform                              |  1504 |     4 |   270 |
| mbed-os/targets                               | 11515 |     4 |   804 |
| sd-driver/SDBlockDevice.o                     |  4469 |     0 |     0 |
| source/active_application.o                   |   842 |     4 |     4 |
| source/bootloader_common.o                    |   246 |     4 | 16385 |
| source/bootloader_platform.o                  |    46 |     0 |     0 |
| source/main.o                                 |   779 |     8 |   328 |
| source/sotp_rot.o                             |    92 |     0 |     1 |
| source/upgrade.o                              |  1367 |     0 |     8 |
| Subtotals                                     | 58595 |  2524 | 18140 |
+-----------------------------------------------+-------+-------+-------+
Total Static RAM memory (data + bss): 20664 bytes
Total Flash memory (text + data): 61119 bytes

Here is the relevant section of mbed_app.json for UBLOX_EVK_ODIN_W2:

            "flash-start-address"              : "0x08000000",
            "flash-size"                       : "(2048*1024)",
            "sotp-section-1-address"           : "(MBED_CONF_APP_FLASH_START_ADDRESS+32*1024)",
            "sotp-section-1-size"              : "(16*1024)",
            "sotp-section-2-address"           : "(MBED_CONF_APP_FLASH_START_ADDRESS+48*1024)",
            "sotp-section-2-size"              : "(16*1024)",

Library name 'sd' is not unique

The upcoming 5.10 has new SD block device and the existing sd-driver conflicts with it.
Ref: ARMmbed/mbed-os#7774