RE: softdevice fault handler gets called with 0x1001 (NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION) after upgrading to nRF5 SDK 17.0.2

SebastianA — Thu, 07 Jan 2021 06:32:52 GMT

Ah, I looked at the wrong error codes.

info is 0, so it is a case of SoftDevice RAM access violation. I'd forgotten to update the amount of RAM reserved for the SoftDevice, increasing it made it all work again.

Thanks you!

RE: softdevice fault handler gets called with 0x1001 (NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION) after upgrading to nRF5 SDK 17.0.2

Sigurd — Wed, 06 Jan 2021 14:26:31 GMT

Hi,

[quote user=""]PC value in the middle of a function[/quote]

What are you doing in this function?

If app_error_fault_handler() triggers with fault id 0x1001, then this is a NRF_FAULT_ID_APP_MEMACC.

From the documentation here, this fault is described as,

Application invalid memory access. The info parameter will contain 0x00000000, in case of SoftDevice RAM access violation. In case of SoftDevice peripheral register violation the info parameter will contain the sub-region number of PREGION[0], on whose address range the disallowed write access caused the memory access fault.