RE: non initialized RAM variable

Arik_S — Thu, 31 Aug 2017 12:17:36 GMT

Hello Martin and thank you for your comment, unfortunately no progress at all :(

I did tried to defined the non init section in both linker files with no success, but perhaps I should try this again. My application linker file is like that:

/* Linker script to configure memory regions. */

SEARCH_DIR(.)
GROUP(-lgcc -lc -lnosys)

MEMORY
{
  FLASH (rx) : ORIGIN = 0x1c000, LENGTH = 0x64000
  RAM (rwx) :  ORIGIN = 0x20002080, LENGTH = 0xdf80
}

SECTIONS
{
  .fs_data :
  {
    PROVIDE(__start_fs_data = .);
    KEEP(*(.fs_data))
    PROVIDE(__stop_fs_data = .);
  } > RAM
} INSERT AFTER .data;

INCLUDE "nrf5x_common.ld"

So since the RAM section is ended in 0x20010000, the non init section should start from there. But when I do the necessary changes in the bootloader linker file (non init section start from 0x20010000) the bootloader is not working at all, not advertising.

Question: If I have multiple non init variables defined both in the application and in the bootloader, how they will get the same absolute address? should they defined static or not?

RE: non initialized RAM variable

MartinBL — Thu, 31 Aug 2017 10:45:08 GMT

Hi, Have you made any progress?

The RAM section should be defined in both linker files. Did you try it already?
I'm pretty sure that is the correct way of doing it.