How for the the nrf53 application processor to verify the network processor is active on BLE?

[Jordan Archer]

I have some odd cases where an nrf53 based device just disappears from BLE.  It's no longer connected, and not advertising.

I'm looking for a method for the application processor to verify that the network processor is running.  And it's current BLE state.

[Simonr]

Hi

The only feedback internally has been that logging from the network core over to the APP core isn't possible I'm afraid. As we can't log, and it is not reliably reproducible it seems very hard to get to the bottom of this. I guess you could try adding a check if the equivalent to an "advertising_stop()" function is being called in your application.

Do you have any more information on when/how this disappearing happens? Does it happen often, and does it happen after the device has been connected/advertising for a very long time? Does it only occur on specific devices? If so it could be a bad crystal that is drifting too much for example.

Best regards,

Simon

[Jordan Archer]

1) Network logging wasn't really needed.   I am looking for a way to tell if the network processor is running it's BLE thread.  Or at all.

2) For the disconnect and not advertising problem, how do I tell if the BLE thread on the application processor is active (running at all)?