cyw43012 how to run bluetooth with wiced hci cmd

[Leo_liu1]

Hi Sir,

We use stm32 as host mcu,communicate with cyw43012 through uart interface.

Now we known that bt stack and profiles run in the chip.

About BT function,we intend to customize api use wiced hci cmd on platform stm32 instead of using wiced studio SDK ,is that ok？I guess we only need to do above,or what else we need to do？Meanwhile,do we still nedd to download bt firmware？

Thanks,

Leo

[RaktimR_11]

You would still need to download the BT firmware. It's a byte array which you can download from your choice of SDK but it has to be downloaded.  Based on your comment, it seems like you are running the BT Stack in embedded mode but sending different HCI commands from ST Host needs to be done through WICED SDK only (Because WICED HCI is a protocol supported through WS). Please clarify what do you mean when you say that you need to customize the api to use wiced hci in stm32. Are you trying to run the stack in st host or are you trying to configure the uart in raw mode and send hci commands through that?

[Leo_liu1]

Hi Raktim,

In embedded mode,we still need to develop application through WICED SDK to support wiced hci cmd from ST?

About "customize api use wiced hci cmd on platform stm32" means we want to refer to WICED SDK api like wiced_hci_send(HCI_CONTROL_AUDIO_COMMAND_INIT, data, length) send wiced hci cmd from ST host instead of using WICED SDK to develop ,in cyw43012 side,we still have to develop application through WCIED SDK?

Thanks,

Leo

[Leo_liu1]

Hi Raktim，

In other words，in addition to downloading BT FW，send wiced hci commands，receive events ，what else we need to do if we don't use WICED SDK to develop application ？

Thanks，

Leo

[RaktimR_11 · Accepted solution]

If you run the WICED BT stack in your ST-host, then after downloading the firmware, you can start sending standard HCI commands. But if you are running the stack in Embedded mode; i.e 43012 is running the BT stack and then you want to use standard HCI commands, that is not going to work because WICED_HCI is a little different than the standard HCI (You can check 43xxx_Wi-Fi/libraries/protocols/wiced_hci to understand more on this).