Re: Zephyr BLE Controller Nordic HW no longer related to SoftDevice?

Carles Cufi

Hi Frank,


The SoftDevice is Nordic’s proprietary BLE protocol stack. It consists of a binary blob that is flashed at the beginning of the flash memory and can be accessed through SV calls, and it is designed to be the arbitrator to control access to certain hardware on the chip. This is incompatible with Zephyr, which already includes a completely different BLE stack which is open source and located in subsys/bluetooth/.

So the answer to your first question is that the SoftDevice cannot be combined with Zephyr, and you should not need to do so since Zephyr already has its own BLE stack.


The answer to the second question is also “yes”. The SoftDevice doesn’t expose an HCI interface, making it unsuitable for use as a BLE Controller, which is what BlueZ requires. Zephyr on the other hand can be built to expose an HCI interface (hci_uart) to work with BlueZ.




From: devel@... <devel@...> On Behalf Of frv
Sent: 20 November 2018 10:53
To: devel@...
Subject: [Zephyr-devel] Zephyr BLE Controller Nordic HW no longer related to SoftDevice?


Hi Community, Carles,


Without having looking into the details for the HCI_UART implementation when using Zephyr RTOS as SW platform for implementing the BLE controller on Nordic HW, the SoftDevice is no longer present in the SW stack. Correct?


Is it further correct to say that the SoftDevice SW which is Nordic specific replaces the standard HCI way on which BlueZ is based.  


I base my understandings on this nice written document:


Thanks in advance,

Best regards,


Join to automatically receive all group messages.