Restarting the network core

RE: Restarting the network core

Nick Stoughton — Thu, 26 Sep 2024 13:07:29 GMT

bt_disable() fails with EOPNOTSUPP because, in the 5340 drivers/bluetooth/hci/rpmsg.c driver (we are using NCS 2.5.0) there is no close function.

However, I see that v3.5.99-ncs1 has implemented this, so I will try moving to that. Thanks.

RE: Restarting the network core

Amanda Hsieh — Wed, 25 Sep 2024 18:52:37 GMT

Check out this post.

RE: Restarting the network core

Nick Stoughton — Tue, 24 Sep 2024 20:58:30 GMT

Oh, and I tried the anomaly-161 work-around with no effect.

RE: Restarting the network core

Nick Stoughton — Tue, 24 Sep 2024 16:22:38 GMT

Thanks...unfortunately we have CONFIG_RESET_ON_FATAL_ERROR set to 'y' everywhere except the main app.

I think this is more a matter of "how do I re-initialize hci_rpmsg after a netcore reset" ... the crash I see is an assertion fail while waiting for the sync done semaphore (running NCS 2.5.0, this is a line 338 of hci_core.c). I need a way of (a) cleanly shutting down the net core, and (b) once it is down, handling a restart and re-enabling the entire IPC mechanism.

RE: Restarting the network core

Amanda Hsieh — Tue, 24 Sep 2024 14:15:17 GMT

Hi,

The issue could be caused by [161] RESET: Core is not fully reset after Force-OFF. You can check the workaround or my colleague's code in this post.

Regards,
Amanda H.