Error code NRF_ERROR_INVALID_ADDR returned from sd_softdevice_enable()

RE: Error code NRF_ERROR_INVALID_ADDR returned from sd_softdevice_enable()

jcondon — Tue, 28 Jul 2020 14:19:30 GMT

In case anyone else runs into this issue, to fix the issue you need to disable Live Code Coverage in the VisualGDB project settings and also disable "Instrument Code for Code Coverage" in Visual Studio's Configuration Properties under Embedded Project.

RE: Error code NRF_ERROR_INVALID_ADDR returned from sd_softdevice_enable()

Vidar Berg — Tue, 28 Jul 2020 13:50:30 GMT

Thanks for the update. I'm unfortunately not familiar with VisualGDB so difficult for me to say what breaks the compatibility. I have not had this issue with GDB. I have however encountered similar behavior as you describe with Segger Ozone, because the default debugger script makes the debugger update the PC register with the start address of the application instead of letting the execution start from address 0x0 (execution must start at 0 to invoke Softdevice). Maybe that could be the problem here as well. I would have tried to take a look at the debug startup script to see if maybe the PC/SP is being updated.

RE: Error code NRF_ERROR_INVALID_ADDR returned from sd_softdevice_enable()

jcondon — Tue, 28 Jul 2020 13:37:22 GMT

I have been told by VisualGDB support that this is a bug in their software, specifically with their implementation of Live Code Coverage. This issue breaks compatibility with the nRFx SDK and remains after Live Code Coverage is disabled. I have not yet received any response on how to fix the project and will likely need to recreate the project from scratch.