[ABANDONED] segger studio seems to ignore the memory map file

Hi.
I have the following memory map file:

<!DOCTYPE Board_Memory_Definition_File>
<Root name="nrf52840">
  <MemorySegment name="FLASH" start="0x0" size="0x100000" access="ReadOnly" />
  <MemorySegment name="RAM" start="0x20000000" size="0x40000" access="Read/Write" />
  <MemorySegment name="uicr_bootloader_start_address" start="0x00000FF8" size="0x4" access="ReadOnly" />
  <MemorySegment name="bootloader_settings_page" start="0x000FF000" size="0x1000" access="ReadOnly" />
  <MemorySegment name="uicr_mbr_params_page" start="0x00000FFC" size="0x4" access="ReadOnly" />
  <MemorySegment name="mbr_params_page" start="0x000FE000" size="0x1000" access="ReadOnly" />
 </Root>

when it's processed to generate an ld script for gcc this is the header of the ld script:

MEMORY
{
  UNPLACED_SECTIONS (wx) : ORIGIN = 0x100000000, LENGTH = 0
  uicr_mbr_params_page (wx) : ORIGIN = 0x00000ffc, LENGTH = 0x00000004
  uicr_bootloader_start_address (wx) : ORIGIN = 0x00000ff8, LENGTH = 0x00000004
  mbr_params_page (wx) : ORIGIN = 0x000fe000, LENGTH = 0x00001000
  bootloader_settings_page (wx) : ORIGIN = 0x000ff000, LENGTH = 0x00001000
  RAM (wx) : ORIGIN = 0x20000000, LENGTH = 0x00040000
  FLASH (wx) : ORIGIN = 0x00000000, LENGTH = 0x00100000
}

I verified using all kind of parameters and trying to use options->build->memory segment playing with various RWX permissions, i always get (RW) eventually in the ld script.
i tried to look in the generated ld script to see if i see somewhere lese restrictions for read only sections but i cannot find any.

i'm using segger studio for nordic nrf52840, the flash memory is not writable in any case, but memory map should also define peripherals and registers which are also read only, what's the point defining it right if eventually the ld script does not enforce it ?
I have verified the same behavior with various nrf sdk 15.2 examples, changing the permissions in the memory map results in the same ld script permissions. is that a bug or done on purpose ?

Hi.
i'm using version 4.18 of the segger arm studio.
The Nordik SDK indeed uses segments, i also tried playing with them as well. it did not change the ld script. yes it's consistent with all samples i tried and i tried a few. indeed i am setting the memory map in the project options.

For ref i'm using nordik SDK 15.2 example: nRF5_SDK_15.3.0_59ac345/examples/dfu/secure_bootloader/pca10056_ble/

the memory file i used instead of the segment is already published here, but you can see the segments definitions as well of RX that results in ld (wx) as well.

Thanks for the response.
My problem is not with the placement itself in memory, at least not yet.
My problem is the top part of the generated ld script and the fact that all sections are with permission '(wx)' is there a way to use the flasdh_placement.xml file or the section placement macro to change those permission to what they should be ? eventually, and correct me if i'm wrong, the executable is linked using gnu ld which means it uses the generated ld script, and so what matters is the generated def:

FLASH (wx) : ORIGIN = 0x00000000, LENGTH = 0x00100000

flash section should not be writable as you need hardware to write to it. and i prefer tha the ld will alert on such events which can be done if the linker script will be:

FLASH (r) : ORIGIN = 0x00000000, LENGTH = 0x00100000

same goes for registers in the MCU that are defined in those sections, they might be read only, it's always better that the compiler\linker will verify that then it will happen in run-time...

any update if it's indeed a bug or i am doing something wrong ?

I'm not 100% we are talking about the same thing.
in the ld script a memory region that is defined RO only means that this region if written to by the program should generate compile time\link time error.
All flash regions should be defined RO according to best practice since write to flash is not done by copying from register to mem but using a controller + buffer.

This is what i mean and this is why i want to make it read only, memory regions that are just memory mapped regions like bootloader start address or secure bootloader settings address should be readonly since it's not writable memory in reality (you just can't write to it as it's not ram...)

If i'm missing something here do let me know.

In any case if you compare an ld script we manually wrote to the one generated by segger studio you can clear see the difference. i have no problem burning the .hex files myself but i really don't see how it is a problem in my configurations :-\

I use memory_map.xml and not the macros. You can see my memory map xml in the beginning of this thread. if i had the time i would defiantly try out the segger linker instead i'm sure it will behave properly , but i'm also sure it doesn't generate .ld script but actually linking on it's own, am i right ? so i can't compare and i can't currently do the conversion.

Thanks,

Eyal.

i'm a bit off that project now. but i'll try to repoen it later on and send a link to a simple project on github.