RE: Intermittent Failure of nRF52832

Susheel Nuguru — Mon, 29 Jun 2020 07:17:56 GMT

Hi Jeffery,

There seems to be a deadlock in your application and it looks like it is timing dependent (Since it is not effecting 100% of your devices)

In the release of the softdevice 5.1, we have

Fixed an issue where Radio Notification could be suppressed between connection events when Connection Event Length
Extension was enabled (DRGN-7687).

Flash events are notified through radio notification. So if there was a suppressed radio notification event, there could be a flash event missing and if you application was waiting on flash activity or other radio notification to proceed, then this could create a deadlock on version 5.0 which was fixed in 5.1

Fixed an issue where the SoftDevice could get stuck in a deadlock where it would always NACK what the peer was sending.
This could happen if LE Data Packet Length Extension was used and ble_cfg.conn_cfg.params.gap_conn_cfg.eve
was less than 5 (DRGN-9494). nt_length
Fixed an issue where the SoftDevice could get stuck in a deadlock where it would always NACK what the peer was sending.
This could happen if the peer reduced the data length during the Data Length Update procedure (DRGN-9367).

This is something most likely you would be seeing if the application is using an event length of less than 5 or the peer reduced the data length of the connection events (you can check this if you manage to get the air sniffer log when the deadlock happens).

/Susheel

RE: Intermittent Failure of nRF52832

Jeffery Bahr — Fri, 26 Jun 2020 15:01:28 GMT

Thanks! I did look at the release notes and nothing jumped out at me.

RE: Intermittent Failure of nRF52832

Susheel Nuguru — Fri, 26 Jun 2020 12:17:19 GMT

Hi,

I can take a look at the change log of SD132v5.1 to see what has changed and reply to you on Monday.

Thanks for waiting.