RE: BMD-330 "SOFTDEVICE: INVALID MEMORY ACCESS" for Blinky

Mark — Mon, 17 Jun 2019 20:23:46 GMT

Einar!! Thank you for your answer, you are completely correct!

The app is in fact working exactly as intended, I was too hasty and foolish in my reading of the "Blinky Example" page. I failed to properly recognize the file path as ".../peripheral/..." and not ".../ble_peripheral/...".

In addition, thank you for the info on the performance of the SoftDevice, that will be good to know as I move forward.

RE: BMD-330 "SOFTDEVICE: INVALID MEMORY ACCESS" for Blinky

Einar Thorsrud — Mon, 17 Jun 2019 11:56:30 GMT

Hi,

Since you are using the SoftDevice, I assume the "blinky" example you refer to is the BLE Blinky Application?

Nothing of what you write indicates an error as far as I can see. The BLE Blinky Application will light LED2 by default and advertise waiting for a central to connect. It will sleep for most of the time, and the way it sleeps is by calling the SEV and WFE instructions (via the SoftDevice API). So it is expected that you see the system at SEV when pausing execution. Have you tested if the system is actually working, for instance by using the nRF Blinky app for your smartphone? I expect it is.

Moreover, the SoftDevice has strict timing requirements, so it is expected that you get an assert when you continue after pausing or hitting a breakpoint. This is intended and is always the case as long as the SoftDevice is currently doing something that involves timing (advertising, scanning, in a connection etc.).

PS: The name "BLE Blinky Application" is a confusing (and bad) name for this example, as it does not blink as you would have expected from any example with "blinky" in the name (unless you connect via BLE and toggle the LED from the central) .