exmple/demo fails to build: 'Starting addresses are different' when merging

[ATM-HSW]

When calling:

hexmerge.py -o merged.hex --no-start-addr ..\..\mbed-mcuboot-demo\BUILD\mbed-mcuboot-demo.hex signed.hex signed-update_mv.hex

I've got this messages:

Merging: signed-update_mv.hex
Starting addresses are different

and no merged.hex is generated. What is the problem?

I created signed-update_mv.hex by calling:

arm-none-eabi-objcopy --change-addresses 0x8040000 signed-update.hex signed-update_mv.hex

Maybe I don't understand where 0x40000 does come from in your example. I thing it is mcuboot.primary-slot-address + 0x20000 but I' not sure.

But creating signed-update_mv.hex by calling:

arm-none-eabi-objcopy --change-addresses 0x40000 signed-update.hex signed-update_mv.hex

follwed by merging creates the same error.

I build everything for DISCO_L475VG_IOT01A with mbed 6.6 and uVision 5.32

[AGlass0fMilk]

Just seeing this, I will try out building for the DISCO target you mentioned. The README is very much geared towards the nRF52840. It can be difficult to configure this example properly if you're just getting started.