cancel
Showing results for 
Search instead for 
Did you mean: 

STM32CubeIDE 1.15.0: elf has a LOAD segment with RWX permissions

RajeevAroraCrcEvans
Associate III

Hi @Imen.D  , @Khouloud ZEMMELI ,

After updating the STM32CubeIDE to version 1.15.0 (today) I am observing below warning.

The LD file has not changed. It has RAM and MRAM RWX

C:/ST/STM32CubeIDE_1.15.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.12.3.rel1.win32_1.0.100.202403111256/tools/bin/../lib/gcc/arm-none-eabi/12.3.1/../../../../arm-none-eabi/bin/ld.exe: warning: xxx.elf has a LOAD segment with RWX permissions

Memory sections in LD file:

MEMORY
{
ITCMRAM (xrw) : ORIGIN = 0x00000000, LENGTH = 64K
FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 2048K
DTCMRAM (xrw) : ORIGIN = 0x20000000, LENGTH = 128K
RAM_D1 (xrw) : ORIGIN = 0x24000000, LENGTH = 512K
RAM_D2 (xrw) : ORIGIN = 0x30000000, LENGTH = 288K
RAM_D3 (xrw) : ORIGIN = 0x38000000, LENGTH = 64K
MRAM (xrw) : ORIGIN = 0x60000000, LENGTH = 1024K
}

Please help resolve the concern.

Regards,

Rajeev

46 REPLIES 46

Hi JensH, 

Thank you for idea, 

If those regins were (Readonly), is flash function going to work well ? 

 

Best Regards, 

BrianZ 

it works, the warning has disappeared, thanks buddy!😊

i am sorry,where can i find the "Miscellaneous" in the cubeIDE?, i copy this word to the search bar under the Window/Preference, but still cannot find it

PHolt.1
Senior III

The linker options supplied further back in this thread are invalid for GCC.

PHolt1_0-1721984414214.png

 

I have Cube IDE v 1.16.0.

Hi,

make sure to use -Wl,--no-warn-rwx-segment in order to pass the --no-warn-rwx-segment option to the linker. See option for linking in the GCC documentation.

BrianTIDAL_0-1721994097485.png

 

Rgds

BT

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
PHolt.1
Senior III

Thank you, but I went back to 1.14.1 because I could not get 1.16.0 to work with any debugger I have. I might revisit this with 1.16.1 😀