Incompatibility between mcumgr cli and hci_usb when running with BT_LL_SOFTDEVICE enabled

RE: Incompatibility between mcumgr cli and hci_usb when running with BT_LL_SOFTDEVICE enabled

Ian — Thu, 02 Dec 2021 17:47:27 GMT

Hi Carl,

I'm having the same issue when using the Softdevice BLE controller with NCS v1.7.1. Using the Zephyr controller instead does fix the issue. I don't see the pull request changes you linked in the hci_uart sample, so I'm wondering if any changes were made to address the issue with the public address?

Regards,

Ian

RE: Incompatibility between mcumgr cli and hci_usb when running with BT_LL_SOFTDEVICE enabled

ubieda — Tue, 30 Mar 2021 20:15:33 GMT

Hi Carl,

Thanks for your reply!
Gotcha on the BT Address not being set up. I'll also try the workaround.

Best regards,

Luis.

RE: Incompatibility between mcumgr cli and hci_usb when running with BT_LL_SOFTDEVICE enabled

Carl Richard — Tue, 30 Mar 2021 10:06:43 GMT

Hi again, Luis!

The issue is that mcumgr doesn't set an address for the host before scanning. The Softdevice Controller checks the address and throws an error as it's invalid, while the Zephyr LL does not. Hence, the host starts scanning with an invalid address.

We're awaiting more comments on how this could be handled, but a temporary workaround is to set the address in hci_usb directly. You can see how this is done in this pull request for hci_uart. Note that this code sets a public address, which is something you have to pay for. If you want to avoid this you could try to change the code to set a random address instead.

Best regards,
Carl Richard

RE: Incompatibility between mcumgr cli and hci_usb when running with BT_LL_SOFTDEVICE enabled

Carl Richard — Tue, 30 Mar 2021 07:33:21 GMT

Hi!

Thanks for reporting this. I'll check with the developers to see if there are any other configurations required and/or known issues!

Best regards,
Carl Richard