Linker Placement (RAM_START and RAM_SIZE) in SES 3.34: how to modify?

RE: Linker Placement (RAM_START and RAM_SIZE) in SES 3.34: how to modify?

bjorn-spockeli — Tue, 08 May 2018 08:56:26 GMT

FDS will use the last two pages in flash memory to store data and your application linker script is configured to use the entire flash area above the SoftDevice, i.e.

FLASH (rx) : ORIGIN = 0x26000, LENGTH = 0x5a000

so whenever you flash the application you should also clear the FDS pages.

RE: Linker Placement (RAM_START and RAM_SIZE) in SES 3.34: how to modify?

bjorn-spockeli — Tue, 08 May 2018 08:53:00 GMT

rdpoor: You have opened the options for the fds.c file and not the project itself (SES is a bit annoying regarding this). You have to select Project 'ble_app_template_pca10040_s132' in the Project explorer and then click Project => Edit Options... or just right-click on Project 'ble_app_template_pca10040_s132' in the Project explorer and then select Edit Options...

RE: Linker Placement (RAM_START and RAM_SIZE) in SES 3.34: how to modify?

rdpoor — Mon, 07 May 2018 22:04:28 GMT

I believe I fixed the problem, even if I don't completely understand why:

Short form: I erased the part and restarted. Works.

Details:

I noticed that the system was looking for two or more free pages in `pages_init()`, but the call to `page_is_erased()` was returning false. (I don't know what was written there...). So in the Target menu item, I selected 'Erase All' and re-loaded the program.

This time it ran without error.

Lingering question: Is there a reason the pages in question aren't getting initialized?

RE: Linker Placement (RAM_START and RAM_SIZE) in SES 3.34: how to modify?

rdpoor — Mon, 07 May 2018 20:45:24 GMT

For completeness, here is a screenshot of SES just after it got the error. It has just returned from a call to `pages_init()`, and `init_opts` has a value of NO_PAGES.

RE: Linker Placement (RAM_START and RAM_SIZE) in SES 3.34: how to modify?

rdpoor — Mon, 07 May 2018 20:29:51 GMT

Hello Bjørn!

Here's the screenshot of the window I get by clicking Project => Edit Options...

And the contents of ble_pp_template_gcc_nfr52.ld are as follows:

/* Linker script to configure memory regions. */

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

MEMORY
{
  FLASH (rx) : ORIGIN = 0x26000, LENGTH = 0x5a000
  RAM (rwx) :  ORIGIN = 0x20002220, LENGTH = 0xdde0
}

SECTIONS
{
}

SECTIONS
{
  . = ALIGN(4);
  .mem_section_dummy_ram :
  {
  }
  .log_dynamic_data :
  {
    PROVIDE(__start_log_dynamic_data = .);
    KEEP(*(SORT(.log_dynamic_data*)))
    PROVIDE(__stop_log_dynamic_data = .);
  } > RAM
  .fs_data :
  {
    PROVIDE(__start_fs_data = .);
    KEEP(*(.fs_data))
    PROVIDE(__stop_fs_data = .);
  } > RAM
  .cli_sorted_cmd_ptrs :
  {
    PROVIDE(__start_cli_sorted_cmd_ptrs = .);
    KEEP(*(.cli_sorted_cmd_ptrs))
    PROVIDE(__stop_cli_sorted_cmd_ptrs = .);
  } > RAM

} INSERT AFTER .data;

SECTIONS
{
  .mem_section_dummy_rom :
  {
  }
  .sdh_soc_observers :
  {
    PROVIDE(__start_sdh_soc_observers = .);
    KEEP(*(SORT(.sdh_soc_observers*)))
    PROVIDE(__stop_sdh_soc_observers = .);
  } > FLASH
  .pwr_mgmt_data :
  {
    PROVIDE(__start_pwr_mgmt_data = .);
    KEEP(*(SORT(.pwr_mgmt_data*)))
    PROVIDE(__stop_pwr_mgmt_data = .);
  } > FLASH
  .sdh_ble_observers :
  {
    PROVIDE(__start_sdh_ble_observers = .);
    KEEP(*(SORT(.sdh_ble_observers*)))
    PROVIDE(__stop_sdh_ble_observers = .);
  } > FLASH
  .log_const_data :
  {
    PROVIDE(__start_log_const_data = .);
    KEEP(*(SORT(.log_const_data*)))
    PROVIDE(__stop_log_const_data = .);
  } > FLASH
    .nrf_balloc :
  {
    PROVIDE(__start_nrf_balloc = .);
    KEEP(*(.nrf_balloc))
    PROVIDE(__stop_nrf_balloc = .);
  } > FLASH
  .sdh_state_observers :
  {
    PROVIDE(__start_sdh_state_observers = .);
    KEEP(*(SORT(.sdh_state_observers*)))
    PROVIDE(__stop_sdh_state_observers = .);
  } > FLASH
  .sdh_stack_observers :
  {
    PROVIDE(__start_sdh_stack_observers = .);
    KEEP(*(SORT(.sdh_stack_observers*)))
    PROVIDE(__stop_sdh_stack_observers = .);
  } > FLASH
  .sdh_req_observers :
  {
    PROVIDE(__start_sdh_req_observers = .);
    KEEP(*(SORT(.sdh_req_observers*)))
    PROVIDE(__stop_sdh_req_observers = .);
  } > FLASH
    .nrf_queue :
  {
    PROVIDE(__start_nrf_queue = .);
    KEEP(*(.nrf_queue))
    PROVIDE(__stop_nrf_queue = .);
  } > FLASH
    .cli_command :
  {
    PROVIDE(__start_cli_command = .);
    KEEP(*(.cli_command))
    PROVIDE(__stop_cli_command = .);
  } > FLASH
  .crypto_data :
  {
    PROVIDE(__start_crypto_data = .);
    KEEP(*(SORT(.crypto_data*)))
    PROVIDE(__stop_crypto_data = .);
  } > FLASH

} INSERT AFTER .text

INCLUDE "nrf_common.ld"

RE: Linker Placement (RAM_START and RAM_SIZE) in SES 3.34: how to modify?

bjorn-spockeli — Wed, 02 May 2018 13:28:49 GMT

rdpoor: The custom_ble_service_example should run without any issues on the nRF52832. There should be a Linker subsection under the Code section, if not, then please upload a screenshot of the Options window.

Could you also attach the ble_app_template_gcc_nrf52.ld (linker script) file found in custom_ble_service_example-master\pca10040\s132\armgcc ?

Best regards

Bjørn

RE: Linker Placement (RAM_START and RAM_SIZE) in SES 3.34: how to modify?

Turbo J — Tue, 01 May 2018 10:14:00 GMT

Just try to play a bit with LENGTH parameter of the flash in the linker script.

RE: Linker Placement (RAM_START and RAM_SIZE) in SES 3.34: how to modify?

rdpoor — Tue, 01 May 2018 09:01:54 GMT

Thanks for the clarification. Is there a fix? Or are you saying (indirectly) that the https://github.com/bjornspockeli/custom_ble_service_example example won't run on the nRF52832?

RE: Linker Placement (RAM_START and RAM_SIZE) in SES 3.34: how to modify?

Turbo J — Sun, 29 Apr 2018 11:11:44 GMT

FDS_ERR_NO_PAGES has nothing to do with RAM, its about your FLASH memory settings. Basically there is not enough free space between your app area and top-of-flash/bootloader.