Segger 5.42: DFU link error section .uicr_bootloader_start_address VMA [0000000000000ff8,0000000000000ffb] overlaps section .reserved_flash VMA [0000000000000000,00000000000f7fff]

[Liam]

After upgrading segger to 5.42 we are now getting the following error when compiling the Bluetooth DFU bootloader part of our existing projects

 section .uicr_bootloader_start_address VMA [0000000000000ff8,0000000000000ffb] overlaps section .reserved_flash VMA [0000000000000000,00000000000f7fff]

As far as I can tell they have always overlapped.

It compiles and works fine with segger 5.10 and before.

Is this is a problem with segger or with my project settings please?

regards

Liam

[Einar Thorsrud]

Hi Liam,

These addresses are where the bootloader start address is placed in the MBR in a few SDK releases If use use releases from before 15 or 17 or later that will not be the case and you will not see this error. In any case this sould not cause an error and is expected, so I am not sure why SES complains.

That said, SES 5.42a is newer than the SDK versions you see this issue with, and if you meet problems I suggest you downgrade SES. You can always find the supported toolchain versions in the SDK release notes (meaning toolchain version we have tested with a specific SDK version).

[StephaneJ]

Thanks ! Which version to you suggest we can use for the SDK15.3 ? Because it was release early 2019 so that would mean SeS version 4.12 if we want a version release before SDK15.3 but I think they are not valid anymore (unable to renew licence, this is why I have updated to the most recent one).

I just tested with SeS v5.34 and it look like the built works

[StephaneJ]

Wrong alert, I can indeed built the bootloader, upload it on my board but I am not able to upload my firmware, the board stays in DfuTarg mode.

But I think this is not the subject of this topic.