How to specific hci event in zephyr based on nrf connect sdk?

[userr]

Hello,

I want to specific a hci event in zephyr RTOS when using nrf connect sdk. But I don't know how to achieve it.

In Bluetooth Core v5.2, vendor specific events have the same event code, so I should how to distinguish diffirent vs events?

And I notice that there is a stuct named 'bt_hci_evt_vs' in ncs\zephyr\include\bluetooth\hci_vs.h:

struct bt_hci_evt_vs {
	uint8_t  subevent;
} __packed;

Under the code there are some other sturcts, which maybe are vendor specific events:

#define BT_HCI_EVT_VS_FATAL_ERROR              0x02
struct bt_hci_evt_vs_fatal_error {
	uint64_t pc;
	uint8_t  err_info[0];
} __packed;

So if I want to define my event, I have to use bt_hci_evt_vs{} struct and my event sturct, then my event total paramters must be 'sizeof(bt_hci_evt_vs)+sizeof(my event struct)'?

After define my event in header file, do I have other things or codes should to change or add? Should I do something change in ncs\zephyr\subsys\bluetooth\host\hci_core.c?

Thanks for your help!

[Einar Thorsrud]

Hi,

I am not sure I understand this. Custom HCI commands and events are useful (only) for communicating some non-standard HCI command between the Bluetooth host and the Bluetooth controller. And in turn, that would only be useful if you modify the implementation of the Bluetooth controller (which is not possible for instance if you are using the SoftDevice controller that we provide for the nRF devices).

May I ask what you want to achieve / why you want to make you own custom HCI event?

[userr]

I have changed to Zephyr's own buletooth stack by using the config:

CONFIG_BT_LL_SW_SPLIT=y;

and I want to transfer a data block from the controller to the host, which maybe achieved asynchronously.

[Einar Thorsrud]

Hi,

If you see a need to do this in HCI context,  I suggest you look at the implementation of some existing vendor specific commands/events, and of course add support in both the host and the controller.

You may refer to this post for a few related configs, and you can search for CONFIG_BT_HCI_VS or CONFIG_BT_HCI_VS_EXT in the code to see where you need to add code in order to support additional VS HCI commands.