RE: NRF52 boot sequence problems when adding S132

msglamarca — Fri, 26 May 2017 13:26:41 GMT

I'll answer my own question instead of closing it just in case someone else finds it useful (thanks for the comment, Bjorn).

It turns out that while I was placing the text correctly after the Soft Device at 0x20000, I was using all of the RAM (ORIGIN = 0x20000000, LENGTH = 0x10000) which was probably crushing the S132 Soft Device's background RAM usage. I found the RAM area used by a BLE peripheral app's linker file:

RAM (rwx) : ORIGIN = 0x20002168, LENGTH = 0xde98

Even though I'm not using any BLE functionality, I'm guessing the nrf52 still goes back into the S132 periodically regardless. My application may have initialized correctly but the first time it went to the S132, its memory was hosed and it never came back.

RE: NRF52 boot sequence problems when adding S132

bjorn-spockeli — Fri, 26 May 2017 11:24:25 GMT

Which version of the S132 SoftDevice are you using? The ROM and RAM requirements of the differnet S132 SoftDevice versions are listed in their respective SoftDevice Specifications, e.g. here is the requirements for the S132 v4.0.x. It is important that the application is placed right after the SD due to vector table offsets and interrupt forwarding.