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

[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]

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

[taspon98]

I don't seem to have Memfault enabled in my project.

[Konstantin Klitenik]

I know memfault also uses the .noinit section in RAM to store reboot reasons, etc. I wonder if those 2 conflict.

[Konstantin Klitenik]

I wonder if this has something to do with conflicting .noinit sections. I know memfault creates a .noinit section for some things.

[Vidar Berg]

I did not see any changes to the placement of the .noinit when I was comparing the linker scripts. I would recommend using CONFIG_SEGGER_RTT_SECTION_NONE for now.

taspon98 , did you also have a minimal project you can share that will allow me to reproduce the warning without memfault?

[Konstantin Klitenik]

How does that impact RTT functionality?

[Vidar Berg]

The  CONFIG_SEGGER_RTT_SECTION_CUSTOM config setting was added fairly recently to allow the RTT buffer to be placed in a specific RAM location shared between multiple images such as bootloader and app (see commit message for more details). I don't think this should have any impact on RTT in your case since you have RAM split between secure and non-secure regions (bootloader and app will not share the same RAM start address anyway).

taspon98 said:

I have been experimenting with zephyr's ble peripheral example (zephyr/samples/bluetooth/peripheral) using my nRF52dk board and setting 

CONFIG_BUILD_OUTPUT_STRIPPED=y

in the sample's prj.conf with 2.9.0 SDK and toolchain will cause the build warning to appear.

Thanks. This is an interesting clue. I will investigate further and check internally if anyone else has encountered this. 

[taspon98]

Hi, are there any updates to the investigations? We are looking to update the SDK to 2.9.0 and this is the only remaining issue that is preventing us for making the jump due to stability concerns.