Logs in Bootloader and Main Application

[Szymon]

Environment:

Segger Embedded Studio

nRF52840

S140

Windows

nRF 5 SDK 17

Hi,

I'm developing a device for a small side project. I need to get logs in both the bootloader and main appllication.

I successfully got logs in DFU when I only flashed the secure_bootloader_debug example and got logs in the main application if I flashed the application by itself.

However when I merged the bootloader with the application, it appeared that I only got logs in the application.

I've searched this forum and found a similar problem here.

I tried adding these lines to SEGGER_RTT.c

static char __attribute__((section(".rtt_ac_up"))) _acUpBuffer  [BUFFER_SIZE_UP];
static char __attribute__((section(".rtt_ac_down"))) _acDownBuffer[BUFFER_SIZE_DOWN];
SEGGER_RTT_CB __attribute__((section(".rtt_segger"))) _SEGGER_RTT;

However I get a compile Error in Segger when I want to compile secure_bootloader_debug from the examples in the SDK again:

Output/Release/Exe/secure_bootloader_ble_s140_pca10056.elf section `.rtt_ac_down' will not fit in region `UNPLACED_SECTIONS'
region `UNPLACED_SECTIONS' overflowed by 4232 bytes

Is this the correct way of doing this? I was unable to find any other problems like mine on this forum and a solution to my above problem. Thanks for any guidance/ help.

[Simon]

That solution was quite old, and it might be outdated. Could you take a look at these tickets, which are a little newer:

• https://devzone.nordicsemi.com/f/nordic-q-a/43343/easy-way-to-merge-bootloader-and-application-rtt-output
• https://devzone.nordicsemi.com/f/nordic-q-a/30310/easy-way-to-merge-bootloader-and-application-rtt-output

If you're still not able to make it work, please tell me and I will test it myself with nRF5 SDK 17.

Best regards,

Simon

[Szymon]

Hello Simon, Simon here also :)

I wasnt able to get it working. After trying out those the answers in the main post and the comment section. If you could try it I'd appreciate it.

[Simon]

This is your problem:

"This message indicates that you have a .foo section in your program, but it has not been placed by the linker.

Make sure that you specified where you want to the .foo section to be placed in the section placement/memory map file."

Could you try to place the section rtt_ac_down into flash_placement.xml as explained here

Best regards,

Simon