Re: Porting Zephyr HCI Layer
Combining the Bluetooth Host from Nordic with the Zephyr Controller is not an option, because the SoftDevice is hardcoded to contain both Host and Controller and they cannot be decoupled.
I understand that you have your own Host running on FreeRTOS that you want to combine with the Zephyr Link Layer. Porting the Zephyr controller to FreeRTOS is not going to be trivial, but it shouldn’t be too hard either if you are willing to do the work and maintain it. The controller uses mainly bare-metal with some Zephyr-specific primitives mostly in HCI and the ULL.
Here you have the following options:
From: devel@... <devel@...> On Behalf Of ryan.kayesimmons via Lists.Zephyrproject.Org
Sent: 14 January 2020 22:26
To: Hedberg, Johan <johan.hedberg@...>
Subject: Re: [Zephyr-devel] Porting Zephyr HCI Layer
Thank you for your quick reply.
Yes, as you mentioned and as I already understand, hci_uart is for separating the controller and host on different chips.
In this situation, I need to run my own Bluetooth host stack on the nrf52840 (same chip) with some hci interface - Nordic does not supply this hci interface which is why I'm looking at Zephyr.
The difficulty here is that my Bluetooth host stack is using FreeRTOS.. so as you said, it would be easier to port Zephyr to my Bluetooth host stack than to port the Zephyr LL to FreeRTOS.
That might be the only way to continue with my issue and to get full access to the hci & link layer?