Strugling with nRF51 dk/sdk, nRF51822 and Segger Embedded Studios

RE: Strugling with nRF51 dk/sdk, nRF51822 and Segger Embedded Studios

haakonsh — Tue, 27 Nov 2018 12:50:54 GMT

Nice catch, ty! :)

RE: Strugling with nRF51 dk/sdk, nRF51822 and Segger Embedded Studios

Iigori — Mon, 26 Nov 2018 10:30:31 GMT

Thanks for answers. Bought nrf58232 and that one solved my problems ;).

But yeah, i did know something was wrong with softdevice and my memory layout, but didn't have clue how fix those.

RE: Strugling with nRF51 dk/sdk, nRF51822 and Segger Embedded Studios

Turbo J — Sun, 25 Nov 2018 11:17:05 GMT

This project tries to use the whole RAM, wich is forbidden when using MBR and softdevice. The MBR uses the first 8 bytes of RAM (IIRC), and your code overwrites these.See softdevice specification for details.

This explains your early crash as the MBR tries to call the softdevice at a wrong address. Note that the softdevice requires even more RAM to operate.

RE: Strugling with nRF51 dk/sdk, nRF51822 and Segger Embedded Studios

haakonsh — Sat, 24 Nov 2018 10:04:06 GMT

I do not know how to solve this issue. I've sucessfully replicated it, but I do not know what is wrong. I jump to address 740 and 6B0 who's inside the MBR, but then i jumpi into invalid memory like you do.

RE: Strugling with nRF51 dk/sdk, nRF51822 and Segger Embedded Studios

Iigori — Mon, 12 Nov 2018 13:44:18 GMT

Sure thing haakonsh.

Files and target device is MDBT40-256RV3 from raytac.

RE: Strugling with nRF51 dk/sdk, nRF51822 and Segger Embedded Studios

haakonsh — Mon, 12 Nov 2018 12:29:34 GMT

Do you mind sharing your project and relevant files?

RE: Strugling with nRF51 dk/sdk, nRF51822 and Segger Embedded Studios

Iigori — Wed, 07 Nov 2018 12:09:29 GMT

Hi Turbo, Its nice to know that, but it still hangs on there even without debugging. This app is from nRF51 SDK 12.3 examples\ble_peripheral\ble_app_uart it works well when compiled with arm gcc, but can't get it work past softdevice initialization with SeS. I have enabled NRF_LOG logging, but cant see any output from that.

RE: Strugling with nRF51 dk/sdk, nRF51822 and Segger Embedded Studios

Turbo J — Wed, 07 Nov 2018 10:51:57 GMT

You cannot step into sd_softdevice_enable() wit a debugger. This is the place where the softdevice starts up timers, and these will time out during debugging. These timeouts cause a fault, which you see on your last screenshot (Debug10). Your app does not seem to implement a proper fault handler => Lockup (Lockup resets the chip without a connected debugger).

Once the SD is active, you can halt the application (e.g. to check variables) but require a reset afterwards. Using NRF_LOG is usually the simpler option.