SOFTDEVICE: ASSERTION FAILED PC=0x17660

[cedriczou]

Hi Nordic Dev community ,

using:
nrf52840-DK
SDK 15.2
softdevice S140 6.1.0,

Am getting a SoftDevice assert id=1 PC=0x17660 code=0x62D

App error handler id=1 PC=0x17660 code=0x62D
Filename KGJ`h...@h
Line 536871936

It's a ble appliation acting as a relay, with two connection one peripeheral and one central connection + ADV

ble param:
-phy Coded
-min_conn_interval 40 ms,
-max_conn_interval 42 ms,
-SlaveLatency 0,
-Connecttimeout 4000,
-ADV interval 300 ms,
-NRF_SDH_BLE_GAP_EVENT_LENGTH 6 units


Can you tell me what could be the reason of this assert to fail ?

Thanks

Cedric.

[Edvin]

Hello Cedric,

I had to check with our SoftDevice team, and it looks like this assert is some sort of bug that triggers in some corner cases. Unfortunately, it doesn't look like there is any way to fix this from the application. The bug was patched in S140 v7.0.0, so if this assert is breaking your application, I am afraid the only workaround that I can think of is to port to the new softdevice (and the easiest way to do this is probably to port to SDK v16.0.0.

I do understand that this assert will reset your application. But remember that a restart is not deal breaking. Likely, the connected devices will start scan/advertise when the old connection times out, and they will connect again, so in all, it will mean that you will have a small gap where the devices are not connected.

But if that doesn't work for you, you will need to port to the new SDK. 

The later nRF5 SDKs are mostly bug fixes, and they don't have a lot of API changes, so porting your application to SDK16.0.0 (or 17.1.0 for that matter) shouldn't be a huge job. But yet, I am sorry for the inconvenience.

Best regards,

Edvin