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

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

Aditya Gandhi — Sun, 13 Apr 2025 06:46:57 GMT

This helped!!

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

Vidar Berg — Wed, 05 Mar 2025 10:35:49 GMT

The issue has been reported internally but there has not been any updates. To get rid of the warning for now you can select CONFIG_SEGGER_RTT_SECTION_NONE.

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

PuffinEgg — Fri, 28 Feb 2025 19:21:17 GMT

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.

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

Vidar Berg — Tue, 11 Feb 2025 16:30:37 GMT

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).

[quote user="taspon98"]

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.

[/quote]

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

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

PuffinEgg — Mon, 10 Feb 2025 21:15:02 GMT

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.

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

Konstantin Klitenik — Mon, 10 Feb 2025 15:18:11 GMT

How does that impact RTT functionality?

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

Vidar Berg — Mon, 10 Feb 2025 14:14:53 GMT

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.

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

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

Konstantin Klitenik — Mon, 10 Feb 2025 13:58:28 GMT

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

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

Konstantin Klitenik — Thu, 06 Feb 2025 19:43:13 GMT

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

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

PuffinEgg — Thu, 06 Feb 2025 18:48:32 GMT

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

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

Vidar Berg — Thu, 06 Feb 2025 17:22:14 GMT

I was able to reproduce the warning thanks to the project you provided, but I have not been able to determine why. So far I’ve found that the error does not occur if I configure the RTT module to not use the named linker section (_RTT_SECTION_NAME) by selecting CONFIG_SEGGER_RTT_SECTION_NONE, or if I disable CONFIG_MEMFAULT. However, I don't see why the warning goes away when memfault is disabled. I tried comparing the linker scripts and map files between these builds, but was unable to spot any relevant differences.

PuffinEgg , could you please confirm if you are using Memfault in your project as well? I don't believe the issue is directly related to memfault, but would be good if we could rule out that possibility.

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

Vidar Berg — Wed, 05 Feb 2025 19:15:02 GMT

I think it would be easiest if you could create a new private support ticket and upload your project folder as a zip file there. Just provide me the link to the case here so I can assign it to myself.

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

PuffinEgg — Wed, 05 Feb 2025 18:46:39 GMT

I am also using the NCS toolchain 2.9.0

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

Konstantin Klitenik — Wed, 05 Feb 2025 18:23:54 GMT

Mine looks similar.

I don't have a minimal example but our project is just getting started and it's basically just initial setup. I can send you the repo if you let me know the best way to do that privately.

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

Vidar Berg — Wed, 05 Feb 2025 18:16:50 GMT

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:

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

Konstantin Klitenik — Wed, 05 Feb 2025 14:57:22 GMT

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

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

Konstantin Klitenik — Wed, 05 Feb 2025 14:54:59 GMT

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

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

Vidar Berg — Wed, 05 Feb 2025 14:49:17 GMT

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?

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

Best regards,

Vidar

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

PuffinEgg — Tue, 04 Feb 2025 19:00:53 GMT

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