Softdevice assertion failed pc: 16346

[bart]

Using:

• nRF52832
• SDK 15.3.0
• SD S132 6.1.1
• nRF5 SDK for Mesh 3.2.0
• NRF_SDH_DISPATCH_MODEL == NRF_SDH_DISPATCH_MODEL_APPSH

Hi, i'm sometimes getting a crash when a phone connects, caused by softdevice assertion failed, pc: 16346. Can you tell me what could be the reason of this assert to fail?

[Amanda Hsieh]

Hi, 

What is the application or the based example?

Please kindly upload the completed debug log with the failed message. That could help us investigate the issue. Thanks. 

Regards,
Amanda

[bart]

Hi,

GDB showed it crashed into:

app_error_fault_handler(uint32_t id, uint32_t pc, uint32_t info)

with: id=1, pc=16346, info=0

Of course, the backtrace was empty, as it's a softdevice assert.

I will try to reproduce the crash, but it takes several hours, and I don't think it shows any extra info, since the info parameter is empty.

It's a rather big application, that uses connections, advertisements, and a lot of mesh traffic. You can find it here.

[bart]

Yes indeed, but only after a long time with a lot happening. Since it's a softdevice assert, I have no clue where something goes wrong. Normally, a nordic engineer can tell from the PC.

[Amanda Hsieh]

Hi, 

Can you check if the application is using both a connectable and non-connectable advertiser?

-Amanda

[bart]

It's using the softdevice to advertise connectable advertisements. When a connection is made, it will start advertising non-connectable advertisements.

[Amanda Hsieh]

Hi, 

Our softdevice team confirmed that 

When the application starts a non-connectable advertiser right after a connection gets established, an assert may occur. The workaround is After pulling the event BLE_GAP_EVT_CONNECTED, pull events until sd_ble_evt_get returns NRF_ERROR_NOT_FOUND. 

This bug is present in all released SoftDevices since 6.0.0. Please let me know if you are satisfied with the workaround.

-Amanda

[bart]

Thanks!

The assert that may occur is the same as what I get?

[Amanda Hsieh]

Yes.