nrf52 KEIL's project create .elf with SEGGER, why?

RE: nrf52 KEIL's project create .elf with SEGGER, why?

Sigurd — Tue, 21 Feb 2017 09:12:57 GMT

S132 is the SoftDevice (Bluetooth stack) for the nRF52. The SoftDevice is placed at the bottom of the flash, while the application-code (your code in SES) is placed on top of the SoftDevice. For the BLE/S132 examples to be fully functional and with Bluetooth-support, you need to flash the S132 SoftDevice to your nRF52.

RE: nrf52 KEIL's project create .elf with SEGGER, why?

ndarkness — Tue, 21 Feb 2017 09:08:23 GMT

Hi Sigurd, how do you mean by that? If i do flash the soft device the what happens to my code? I mean, I see the SoftDevice is located in a complete different folder than the hex generated by my compilation

RE: nrf52 KEIL's project create .elf with SEGGER, why?

Sigurd — Tue, 21 Feb 2017 08:35:07 GMT

Hi, you need to flash the S132 SoftDevice.

RE: nrf52 KEIL's project create .elf with SEGGER, why?

ndarkness — Tue, 21 Feb 2017 07:57:35 GMT

Hi Sigurd, thanks to your link I get now the .hex, however I cannot debug with it, I see in the debug terminal unknown function at 0xFFFFFFFFE, as I have updated in the main post, is this a wrong memory setup?

RE: nrf52 KEIL's project create .elf with SEGGER, why?

Sigurd — Mon, 20 Feb 2017 08:55:34 GMT

Hi,

See this answer on how to configure SES to generate a HEX file.