warning in build (Stm32CubeIDE 1.18.0) load segment with RWX permissions

[chriskuku]

/Applications/STM32CubeIDE.app/Contents/Eclipse/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.13.3.rel1.macos64_1.0.0.202411102158/tools/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld: warning: pedal13.elf has a LOAD segment with RWX permissions

 

When launching a build in my project (IDE C/C++) , I'm getting the above in the console window from the build.
Is this normal? Should I care?

[Pavel A.]

Usually you should care about warnings and unusual messages. This one can be ignored for many STM32 models because yes, the memory is defined in the linker scripts as RWX. If this annoys, change the attributes so that no memory block has W and X together.

 

[chriskuku]

I'm a bit clueless where this is made. I can find a piece of code in

<project_name>.map (excerpt):

Memory Configuration
 
Name Origin Length Attributes
RAM 0x20000000 0x00005000 xrw
FLASH 0x08000000 0x00010000 xr
*default* 0x00000000 0xffffffff

Linker script and memory map

But wouldn't  it  be normal to give RAM these attributes (rwx)?

Defined in the loader file:
STM32F103C8TX_FLASH.ld

/* Memories definition */
MEMORY
{
 RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 20K
 FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 64K
}

 

And I changed this to `rw` to no avail. The warning persists.

 

Would it be possible to increase the linker verbosity to find out which segment is the culprit?

[Andrew Neil]

This is defined in the linker script - the .ld file; eg,

/* Memories definition */
MEMORY
{
 RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 8K
 FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 64K
}

 

Remove the 'x' from RAM, if you wish

[Andrew Neil]

This article explains what the warnings are, why they've "suddenly" started appearing, and what to do about them - including just disabling the warning:

https://www.redhat.com/en/blog/linkers-warnings-about-executable-stacks-and-segments

 

#rwxWarning

[Andrew Neil]

Follow-on question about adding compiler options:

https://community.st.com/t5/stm32cubeide-mcus/add-compiler-options-find-reason-for-yellow-warning-exclamation/td-p/791175