SDK12.3. Secure Bootloader : UART and ld config

RE: SDK12.3. Secure Bootloader : UART and ld config

Martin — Wed, 24 May 2017 10:23:41 GMT

Okay, I found the root cause of all my problems:

Inside the Makefile the CFLAG+= -flto was set, which caused the debug symbols to be discarded and caused the debugger to not find the symbols...

Maybe this helps somebody too

RE: SDK12.3. Secure Bootloader : UART and ld config

Martin — Wed, 24 May 2017 09:37:49 GMT

:INFO:Inside main :INFO:In nrf_bootloader_init :INFO:In real nrf_dfu_init :INFO:running nrf_dfu_settings_init :INFO:Enter nrf_dfu_continue :INFO:Single: Invalid bank :INFO:Application sent bootloader request :INFO:In nrf_dfu_transports_init :INFO:num transports: 2 :INFO:vector table: 0x00035c00

This is my init output, but the break point at main is not hit...

RE: SDK12.3. Secure Bootloader : UART and ld config

Martin — Wed, 24 May 2017 09:26:48 GMT

Hi, I erased the chip a couple times. But still no luck in hitting the break point. The puzzling thing about it is, I see the NRF_LOG output printed in the RTT console...

RE: SDK12.3. Secure Bootloader : UART and ld config

Hung Bui — Wed, 24 May 2017 09:24:09 GMT

Hi Martin,

BOOTLOADER_REGION_START is replaced by BOOTLOADER_START_ADDR in Secure DFU.

The .ld file was inherited from Legacy DFU (SDK v11 and earlier). The comment and some other configuration (such as the NOINIT sectioN) should be updated. We will try to fix this in next release of the SDK.

I can see that you move the bootloader up a little bit. It's fine if you want to have more space to receive image and for application. But in case in the future we need to update the bootloader and make it larger size you may have an issue. It's better to have some buffer.

Note that when you change the bootloader start address, you need to do a full erase of the chip , so that the UICR is erased properly.

I don't see any problem back porting the serial DFU from SDK v13 back to SDK v12 or earlier.