SOFTDEVICE: INVALID MEMORY ACCESS when attempting to use Thread SDK.

[kwigulaker]

Hello everyone!

I've been struggling to get over this error when attempting to use an augmented Thread project based on the thread_mqtt_sn_client_publisher example. Would someone be able to look at my Linker file and flash_placement.xml file and see if they can spot what is wrong here? I have tried setting the macros in the linker page on the project to correct values based on online documentation but I either receive the softdevice error, or I get error 4 nrf_error_no_mem.

Note: I see it happens when the function otSysInit  is called via thread_init in thread_utils.c.

Below is my project as a .zip,

The segger project file is in examples\thread\mqttsn_client_publisher\pca10056\blank\ses.

Using Segger v5.60a.

4606.Thread Example.zip

[Vidar Berg]

Hello,

Please check what the "info" value is when you get the NRF_FAULT_ID_APP_MEMACC assert.

This will tell us if the application tried to access a reserved peripheral or not.

[kwigulaker]

Thank you for a quick response Vidar, here's the call stack below:

[Vidar Berg]

The info value suggests that the application tried to directly access the ACL or NVMC peripheral. The Softdevice reserves access to both as you can see from the table here: Hardware peripherals. 

But I don't see any direct register access being made to either ACL or the NVMC in the project you uploaded, so I'm not sure exactly where the "violation" happens. 

Please look up the PC value in the disassembly view to figure out where it points to in your code. 

[kwigulaker]

Thank you again Vidar, I find it bizarre myself considering I am calling the thread initialization that in the previous project didnt require the softdevice at all, and BLE is able to use it fine. Here is what you requested first:

In the code this refers to:

[kwigulaker]

I can update by saying ive tried disabling CLOCK and NVMC in configuration and removing where CLOCK was initialised in the code, however this did not affect the issue.