Date
1 - 5 of 5
Bluetooth: Starting dev for TI CC256x support
Arnaud Mouiche
Hi all,
I wish to develop the required driver to interface Zephyr with the TI Bluetooth CC256x chipset family. Here are the requirements: a) Need to upload an initialization script (what they call a 'BTS' file), mainly a binary file which is sequence of action (HCI command, host baudrate change, delays...) It is a mix of device configuration, firmware patching (new features like BLE support are enabled through the init script). Each silicon version may require a different init script content. b) A basic protocol called HCILL to manage Host and/or adapter sleeping. b) is described here: https://processors.wiki.ti.com/index.php/CC256x_eHCILL_Low_Power_Protocol. The Linux driver is also a good reference: https://github.com/torvalds/linux/blob/master/drivers/bluetooth/hci_ll.c a) Init process is described in https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools/hciattach_ti.c Questions: - Is there already somebody working on the subject ? - I'm interesting by some advice to manage such "binary initialisation script" file integration. Here is what think to implement: + a python script to transform the initial binary BTS file into a C file where each action has been split in a array of strcut ready to be walk through by the driver. + the list of BTS files to embed in the firmware is managed in the cmake file of the board + the HCI driver performing init and power management can be implemented as a fresh copy of https://github.com/zephyrproject-rtos/zephyr/blob/master/drivers/bluetooth/hci/h4.c if I don't find easy way to manage a factorization. Regards, Arnaud
|
|
Peter A. Bigot
https://github.com/zephyrproject-rtos/zephyr/pull/22012 removed support for this SOC. If you're interested in maintaining this platform, it could be resurrected. Please comment on that issue to get started.
Peter
|
|
Christopher Friedt
On Mon., Feb. 3, 2020, 6:57 a.m. Arnaud Mouiche, <arnaud.mouiche@...> wrote: Questions: I'm working on the split-LL BLE stack [1] implementation currently, but that is for the "Single Chip" configuration. From what you describe, it sounds as though you would like to use the SoC as a BLE coprocessor, either over UART or SPI or something. Is that correct? In that case there may be a way to add a vendor-specific HCI command [2] or simply call the command from within your application.
|
|
Arnaud Mouiche
Hello Peter,
toggle quoted messageShow quoted text
The chipset I expect to support first is the CC2564 which is not a SOC but a simple HCI adapter. Zephyr will run on another MCU. Regards, Arnaud Le 03/02/2020 à 13:35, Peter A. Bigot a
écrit :
https://github.com/zephyrproject-rtos/zephyr/pull/22012 removed support for this SOC. If you're interested in maintaining this platform, it could be resurrected. Please comment on that issue to get started.
|
|
Arnaud Mouiche
Hello Christopher,
Le 03/02/2020 à 13:44, Christopher
Friedt a écrit :
Yes, I will use the Bluetooth chipset with HCI over UART connection. I will check your advice. Thanks, Arnaud
|
|