RE: Peer Manager fails to initialize

Vidar Berg — Fri, 15 Nov 2019 11:13:52 GMT

Hi,

I'm sorry for the delay. Have you had any progress on this? If not, please check what the value of the "info" argument is when you get the NRF_FAULT_ID_APP_MEMACC assertion. I suspect it's a RAM access violation if it fails on queue_buf_get(), but it would be nice to confirm.

"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. */"

What IDE/toolchain and SDK are you using? Maybe you could try to add your fstorage implementation to another SDK example such as ble_app_hrs and see if you get the same result? If you do I can try to debug it here.

RE: Peer Manager fails to initialize

Dave_couling — Wed, 06 Nov 2019 17:39:20 GMT

Yup I'd already done this

RE: Peer Manager fails to initialize

tesc — Wed, 06 Nov 2019 15:55:53 GMT

Hi,

When using a SoftDevice, you need to choose the SoftDevice backend for fstorage for nrf_fstorage_init(). See the fstorage Initialization documentation.

Regards,
Terje