SOFTDEVICE: ASSERTION FAILED pc: 0x00025B94

RE: SOFTDEVICE: ASSERTION FAILED pc: 0x00025B94

AshLabs — Thu, 28 Oct 2021 14:45:17 GMT

This is resolved. Trying an example project which worked, then ported it over, and changed the transport layer to the -none variant. Thanks for the support

RE: SOFTDEVICE: ASSERTION FAILED pc: 0x00025B94

Hung Bui — Fri, 13 Aug 2021 15:17:48 GMT

HI Robbe,
Please double check on what return NRF_ERROR_INVALID_STATE , as I can see in the code otSysInit() should not return any value it's a void return function.
Please try to compare your application to our examples in the SDK to see if you can spot any difference that can cause the assert.

RE: SOFTDEVICE: ASSERTION FAILED pc: 0x00025B94

AshLabs — Thu, 12 Aug 2021 19:44:45 GMT

Update:
This issue is related to the libUARTe.
It's necessary to set the interrupt priority for the nrf_libuarte_async_config_t.
eg. .int_prio = 2.

This is what was causing the 0x15A80 SD assert.
After some changes, my openthread otSysInit() function is giving me NRF_ERROR_INVALID_STATE.
So i hope after fixing this, that im fully up and running.

RE: SOFTDEVICE: ASSERTION FAILED pc: 0x00025B94

Hung Bui — Thu, 12 Aug 2021 10:02:40 GMT

Hi Robbe,

0x15A80 points to Radio Event Manager. It's an assert about timing of the radio.

When you mentioned disable Openthread function, do you mean you disable completely the operation of Thread stack or you simply disable any activity in the application related to Thread ?

I would suggest to try testing using our example in the SDK just so that you have a platform that can run both BLE and Thread, after that you can start adding your feature /custom service in.

Again, make sure you configure the interrupt priority with correct level (App High/ App Low).

RE: SOFTDEVICE: ASSERTION FAILED pc: 0x00025B94

AshLabs — Thu, 12 Aug 2021 09:54:09 GMT

Ok update. I Disabled the Advertisement block -> No change.
I've disabled the Openthread functions -> 0x00025B94 PC error went away.
So it's coupled to the Openthread stack. I have the room to leave this disabled to meet my deadline, so i will investigate further.

I now use the NUS service to communicate between RS485 and a BLE device. While this flow works, i now sometimes get a softdevice assert with 0x15A80.
Back to searching for this issue.

RE: SOFTDEVICE: ASSERTION FAILED pc: 0x00025B94

Hung Bui — Wed, 11 Aug 2021 16:20:52 GMT

OK I see. I would suggest to try reduce the time you take to handle interrupt. The way the Thread and BLE work together is by using timeslot. I suspect that the could be some timeslot violation here causing the issue.

If you spend lots of time handling interrupt you may try to reduce that.

You can temporarily remove some of the features in your application one by one to check if it is the cause of the crash.
I don't think it's WDT. If the WDT triggers you will just have a reset.

RE: SOFTDEVICE: ASSERTION FAILED pc: 0x00025B94

AshLabs — Wed, 11 Aug 2021 14:04:47 GMT

Hey Hung,

The INVALID MEMORY ACCESS error can be ignored (i cannot edit my original post). This was printed since i accidentally removed the break in this switch case.

Im running the Bluetooth stack together with openthread.
So it's using the multiprotocol stack, 802.15.4 alongside BLE.

So it's not a memory access issue.
From the other issues regarding the same PC error address, i'd surely say it would be the hardfault handler.

Now the question is why the hardfault handler is called. Is it a WDT issue ?
I would think it would be an assert, but question is from which block..

I've tried correlating it with the advertisement updating i'm doing. But that does not seem to be correlated time-wise.
The timestams on the issue are not deterministic. I will give you some crash times since boot:
- 90 seconds
- 40 seconds
- at 120 seconds everything just froze up
- 73 seconds
- 32 seconds

The application has openthread communication, i2c communication running constantly, libuarte for rs485 communication running, NUS over BLE running.

RE: SOFTDEVICE: ASSERTION FAILED pc: 0x00025B94

Hung Bui — Wed, 11 Aug 2021 13:41:54 GMT

Hi Robbe,
We don't have a particular function at location 0x00025B94 but it pretty close to the hardfault handler inside the softdevice.

We would need to look into what the application doing the can potentially cause the invalid memory access issue.

Could you explain what you meant by BLE + OT ?

How long it would take for the issue to occur ?
You may want to try disabling some of the program features to check if the issue occurs.

Is it possible that the program access memory that occupied by the softdevice ? Or if you call a softdevice APIs with some variables that supposed to retain their values but they are not ?