Section `_RTT_SECTION_NAME' can't be allocated in segment 2

[Konstantin Klitenik]

I'm getting the following notice/warning/error when building my application (nrfsdk 2.9.0 w/ sysbuild, nrf9151dk board):

/usr/local/zephyr-sdk-0.17.0/arm-zephyr-eabi/bin/arm-zephyr-eabi-objcopy: /Users/kon/Workshop/GitHub/AgX/agmuster-workspace/agmuster/build/agmuster/zephyr/st0gBFbh: section `_RTT_SECTION_NAME' can't be allocated in segment 2
LOAD: .ramfunc _RTT_SECTION_NAME bss noinit
image.py: sign the payload
image.py: sign the payload
[1/10] Performing build step for 'mcuboot'
ninja: no work to do.
[10/10] Generating ../merged.hex

We are using this config. And the error disappears if I set SEGGER_RTT to n.

CONFIG_USE_SEGGER_RTT=y

CONFIG_SHELL_BACKEND_RTT=y

CONFIG_SEGGER_RTT_BUFFER_SIZE_UP=4096

RTT seems to be working when I flash. Is this an expected message? If not, what's the proper way to address?

Thanks,

Konstantin

[taspon98]

I am also running into this issue when migrating from 2.7.0 to 2.9.0.

[Vidar Berg]

Hello,

Unfortunately, I have not been able to reproduce this objcpy error on my end. I'm using the NCS toolchain v2.9.0 (Based on Zephyr SDK v0.16.8). Have you been able to reproduce this with any of the SDK examples? 

taspon98 , are you also using the Zephyr SDK, or are you using the NCS toolchain? 

Best regards,

Vidar

[Konstantin Klitenik]

Not sure how much this matters but I'm on Zephyr SDK 0.17.0.

[Konstantin Klitenik]

Also, we're using sysbuild, again, not sure how much that matters.

[Vidar Berg]

I thought the toolchain version might be relevant since the error was reported by objcopy, but I’m still unable to reproduce this warning using the same toolchain version. Have you managed to reproduce this warning with any of the SDK samples? Or are you able to provide a minimal version of your project that will allow me to reproduce the warning? This would make it easier to troubleshoot and determine if it really is a problem. 

Here I'm building (with sysbuild) the peripheral_uart sample which has logging over RTT enabled by default:

And not sure if it's relevant, but the _RTT_SECTION_NAME linker section appears in segment 5 in my case: