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

[Iigori]

Hello,

I have problems to get SES working with nrf51822 projects. If i import project with help of tutorial from nordic semi i get undefined symbol __data_start__. Now i have made stuff from scratch and i have "almost" working example. It hangs on sd_softdevice_enable function, i know my clocks are ok, becourse example works just fine using arm-gcc toolkit. I doubt the actual problem is in memory layout but i have been trying to solve this problem for quite long time and cant get pass it. I have took some screenshots from debug session to https://imgur.com/a/Pj2fQSU and included some pictures from memory_map and memory_placement. i have nrf51 dk and programming nrf51822_XXAC with that.

Using nrf51 sdk 12.3 and Segger Studio 4.10a

I really need some help and would appreciate if some one could point my error.

[Turbo J]

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.

[Iigori]

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.

[haakonsh]

Do you mind sharing your project and relevant files? 

[Iigori]

Sure thing haakonsh.

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

[haakonsh]

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.