RE: Softdevice crashes with error 1405

Peter Lerup — Wed, 07 Nov 2018 14:35:34 GMT

Found it now. The problem was that the BLE_GAP_EVT_DISCONNECTED wasn't passed to the db_discovery module in the case with premature disconnect and this made the next discovery start to crash.

My bad, sorry.

RE: Softdevice crashes with error 1405

Kenneth — Wed, 07 Nov 2018 13:18:29 GMT

It wasn't much to go on here. You will need to find where it is actually "crashing", I assume that there is api call that return an error code (hopefully not ignored), this typically should be caught by an assert and forwarded to the fault handler. Maybe if you set DEBUG define and disable optimization you might get some more debugging information.

I assume the case here may be that you have a BLE_GAP_EVT_CONNECTED event shortly followed by a BLE_GAP_EVT_DISCONNECTED, if your application rely on executing a sequence of api calls and for instance start of application timers based on the BLE_GAP_EVT_CONNECTED event, I assume that may give various strange issues if you have not considered this.

Best regards,
Kenneth