Device seems to crash when adding new BLE service

RE: Device seems to crash when adding new BLE service

bjorn-spockeli — Fri, 26 Apr 2019 15:24:15 GMT

Geoffroy: Please create a new question for your issue.

RE: Device seems to crash when adding new BLE service

Geoffroy — Thu, 25 Apr 2019 15:15:59 GMT

Hello, thx for all explanations,

i have a similar problem working with nRF52840.

i have err_code = 0x04 no memory for operation

i don't understand how should i change values on file ble_app_template_gcc_nrf52.ld, now i have default values :

MEMORY
{
FLASH (rx) : ORIGIN = 0x26000, LENGTH = 0xda000
RAM (rwx) : ORIGIN = 0x20002210, LENGTH = 0x3ddf0
}

for p_app_ram_start i have 0x2003ff3c (value found in debug mode)

thank you for help, i'm a bit lost...

Geoffroy

RE: Device seems to crash when adding new BLE service

bjorn-spockeli — Mon, 04 Jun 2018 09:09:29 GMT

Have you made any progress? I can't see any SEGGER_RTT_printf(0, "Error code evt_handler: %d\n", err_code) call in main.c at the line number you're referring to in the git repo?

RE: Device seems to crash when adding new BLE service

sorceressofmaths — Fri, 01 Jun 2018 13:57:39 GMT

It's in main.c, ble_stack_init(), line 1165. I will try looking for a hardfault.

RE: Device seems to crash when adding new BLE service

bjorn-spockeli — Fri, 01 Jun 2018 13:49:07 GMT

Where is SEGGER_RTT_printf(0, "Error code evt_handler: %d\n", err_code); called in the code(file, function, line number)? Unless it reaches NVIC_SystemReset(); in app_error_fault_handler() in app_error_weak.c then the only other cause for a reset is a Hardfault.

You can try to set a breakpoint in HardFault_Handler in arm_startup_nrf52.s

Make sure that you have disabled optimization under Options for Target -> C/C++ -> Optimization Level 0

RE: Device seems to crash when adding new BLE service

sorceressofmaths — Fri, 01 Jun 2018 13:32:00 GMT

Yes, I adjusted the RAM start and length accordingly.

The device still resets even if I comment out the APP_ERROR_CHECK, so I don't think it has anything to do with that.

The code seems to get right to the SEGGER_RTT_printf(0, "Error code evt_handler: %d\n", err_code); statement before failing, and even at times it fails while the statement is printing. Is there any reason in particular why the device would reset in the middle of a print?

RE: Device seems to crash when adding new BLE service

bjorn-spockeli — Fri, 01 Jun 2018 12:11:43 GMT

Oh, sorry, I am mistaken. The sd_ble_enable() call does return app_ram_base. In that case you should adjus the RAM start and length to be identical to what you are told in the log output. Where do you end up if you start a debug session, press run code and then halt the CPU when the device is not advertising?

RE: Device seems to crash when adding new BLE service

sorceressofmaths — Fri, 01 Jun 2018 11:28:36 GMT

I'm using SDK 11.

RE: Device seems to crash when adding new BLE service

bjorn-spockeli — Fri, 01 Jun 2018 11:25:47 GMT

Which SDK version are you using? The tutorial you're using is based on SDK v11.0.0 and the SoftDevices compatible with this SDK does not return the ram_start address.

RE: Device seems to crash when adding new BLE service

sorceressofmaths — Fri, 01 Jun 2018 11:02:23 GMT

The breakpoint in app_error_handler_bare is never being activated. I sprinkled a few breakpoints and prints around the code, and best I can tell it's resetting around here:

err_code = softdevice_sys_evt_handler_set(sys_evt_dispatch);
SEGGER_RTT_printf(0, "Error code evt_handler: %d\n", err_code);
APP_ERROR_CHECK(err_code);
SEGGER_RTT_printf(0, "Passed error check");

The error code is 0, but the app still fails without ever getting to the "passed error check" line, i.e. it's not making it past the APP_ERROR_CHECK even though the error code is NRF_SUCCESS.

RE: Device seems to crash when adding new BLE service

bjorn-spockeli — Fri, 01 Jun 2018 10:15:00 GMT

If sd_ble_enable is returning error code 0, i.e. NRF_SUCCESS, then this is not the cause of the reset and you have allocated enough ram to the SD. Could you place a breakpoint in app_error_handler_bare in app_error.c and see if there is any other function call that is returning a non zero error code?

RE: Device seems to crash when adding new BLE service

sorceressofmaths — Fri, 01 Jun 2018 09:47:25 GMT

Hello Bjorn,
Once I started increasing the memory a bit, I started getting no error message (it was never hitting the breakpoint), and the device started pushing through RTT

"sd_ble_enable: ram_start should be adjusted to 0x20001fe8

RAM length should be adjusted to 0xe018"

When I tried adjusting it to those values, it simply started printing "sd_ble_enable: RAM START at 0x20001FE8" before restarting the program from the beginning.

It still doesn't hit the breakpoint in app_error.c, and it still isn't advertising.

RE: Device seems to crash when adding new BLE service

bjorn-spockeli — Thu, 31 May 2018 08:50:42 GMT

You want to decrease the RAM allocated to the application, by increasing the origin( also the end address of the SoftDevice RAM section). So you're effectivly increasing the size of the SoftDevice RAM section by increasing the application RAM origin.

No, its a trial and error process so you'll have to increase move the origin upwards until the sd_ble_enable() call does not return the NO_MEM error code. We added a second parameter in the sd_ble_enable() call in S132 v3.0.0 which returns the application RAM origin for the configuration passed to the SoftDevice.

RE: Device seems to crash when adding new BLE service

sorceressofmaths — Thu, 31 May 2018 08:13:56 GMT

I don't quite understand. If I want to increase the amount of memory allocated, shouldn't I decrease the origin and increase the length? Also, is there a good rule of thumb for how much extra memory to allocate for a new service?

RE: Device seems to crash when adding new BLE service

bjorn-spockeli — Thu, 31 May 2018 07:59:28 GMT

If you're using Keil then this is done under Options for Target -> Target -> Read/Write Memory Areas.

Increase the IRAM1 Start address and decrease the size accordingly, i.e. so that IRAM1 Start + IRAM1 Size <= Total RAM on your nRF5x device.

If you're using make and GCC you'll have to modify the linker script, i.e. the RAM Origin and Length

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

RE: Device seems to crash when adding new BLE service

sorceressofmaths — Thu, 31 May 2018 07:30:23 GMT

Hello Bjorn,

It appears that I've not allocated enough RAM to the softdevice. How do I adjust this in SDK 11? All the tutorials I can find so far are for later SDK versions. (We plan to port our software to SDK 15 in a few weeks, but at the moment we're on a tight deadline and don't have time to do the port just yet.)

RE: Device seems to crash when adding new BLE service

bjorn-spockeli — Thu, 31 May 2018 06:59:51 GMT

Generally, whenever you're seeing that the nRF device is not advertising after you flashed you should do the following:

Start a debug session
Set a breakpoint in app_error_handler_bare in app_error.c
Run the code and if you end up in the error handler, examine the call stack and identify the function that caused the error.
Look up the error code in the SDK/SoftDevice API documentation on http://infocenter.nordicsemi.com/

Most likely you've not allocated enough RAM to the SoftDevice or you've passed incorrect parameters to the SoftDevice.

Best regards

Bjørn