Reset on SVCALL BLE enable

RE: Reset on SVCALL BLE enable

Vidar Berg — Tue, 21 Feb 2017 10:40:58 GMT

Glad to hear that it's working now. It's not a problem to set the RAM base 'too' high, it just means that you have an unused area that could have been used by the application (0x4000-2128 = ~7KB)

RE: Reset on SVCALL BLE enable

Tostikoning — Tue, 21 Feb 2017 10:28:14 GMT

The error seems to be gone. app_ram_base is still 0x20002128. I'm not sure if this is still ok? I do not see it advertising yet, but we are moving forward. I do not see any other error code pop up in the debugger.

It does not reset anymore, and the error_code is 0.

EDIT:

I have the board advertising! Thank you Vidar!

RE: Reset on SVCALL BLE enable

Vidar Berg — Tue, 21 Feb 2017 10:16:25 GMT

You only need to edit the project specific linker file (gcc_nrf52.ld in this case) to change the memory layout. Do you get the same assertion (NRF_NO_MEM) if you try with the following values:

MEMORY
{
  FLASH (rx) : ORIGIN = 0x1f000, LENGTH = 0x61000
  RAM (rwx) :  ORIGIN = 0x20004000, LENGTH = 0xC000
}

RE: Reset on SVCALL BLE enable

Tostikoning — Tue, 21 Feb 2017 10:04:57 GMT

Thanks for the response Vidar! The linker scripts I use are from the SDK. I use the gcc_nrf52.ld and included the nrf52_common.ld which sets the data_start. I do not see how I have control over this value. In the code the p_app_ram_base is 0x20002128. This is over the minimum and the same I see when I try the template in KEIL. The code compiled in KEIL works. I can see the board advertising with the KEIL compiled file. I am going to dig some more in the memory allocation of the softdevice and the ble params.

RE: Reset on SVCALL BLE enable

Vidar Berg — Tue, 21 Feb 2017 09:43:38 GMT

[sd_ble_enable()](infocenter.nordicsemi.com/.../group___b_l_e___c_o_m_m_o_n___f_u_n_c_t_i_o_n_s.html cp=2_3_0_1_1_2_0_2_2_0#ga812ea2c6258c1cf705c7c114b6297aab) returns the lowest RAM start address you can use based on your softdevice configuration (ble_enable_params_t). Make sure that this corresponds to the RAM start address set in your linker file (*.ld). Background: devzone.nordicsemi.com/.../