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 easiest explanation to this I think is that the advertisement or connection times out. Does the "disappearing" device disappear after a set amount of time? An easy fix to this would be to just restart the advertisement from the nRF53. Are you able to recreate this on a DK, and if so are you able to see something by logging to see what's happening when it "disappears". 

Unfortunately, I'm not aware of a way to monitor the network core like you're asking for, but I can ask internally if you'd like. Do you have some more information on what exacttly is happening when the device is disappearing? What central device are you using? What kind of application is this, a beacon that is only advertising or a device that connects to a central and stays connected, providing service information over time, or what?

Best regards,

Simon

[Jordan Archer]

Please ask internally, on detection by the application processor that the network processor's BLE section is running.

[Jordan Archer]

On the device disappearing, I personally haven't been able to catch it.  Several testers have.  I have verified that the advertising is set to not timeout.  And I've tested that it doesn't time out.  

[Simonr]

Hi

I just wanted to let you know that I have asked internally on what this could be and if it's possible to monitor the network core somehow and I'm waiting for a reply. If you have any more details on what's happening when the device disappears that might help us narrowing down the issue as well. Does it only happen when the device is advertising or only when it is connected, or can it happen in any state for example?

Best regards,

Simon

[Simonr]

Hi Jordan

Sorry about the delay. Do you have an opportunity to do logging from the network core, as this is the recommended way to keep tabs on the NET core. Getting logging from the NET core via the APP core is currently not possible it seems unfortunately.

Best regards,

Simon