CC2564C: Linux BlueZ version support

Intellectual 1980 points

Part Number: CC2564C

Hi Team,

My customer wants to use Liunx + BlueZ with CC2564C.

They want to know which version of BlueZ can work fine with CC2564C. Any answers?

Thanks!

over 5 years ago

0 Hari Nagalla over 5 years ago

TI__Mastermind 27080 points

Well, any recent BlueZ versions should work. for example Bluez 5.4 or Bluez5.5.. CC2564C conforms to the BT SIG HCI protocol between the host and controller, so any Host stack confirming to HCI protocol would work..

Thanks

0 jingbo wang over 5 years ago in reply to Hari Nagalla

Prodigy 70 points

Can bluez5.49 works well with cc2564c? Or must use bluez5.54 later?

0 jingbo wang over 5 years ago in reply to Hari Nagalla

Prodigy 70 points

oh, I see.

I used to use bluez protocol 5.49 with TI chipset CC2564B can work well, and use bts file TIInit_6.7.16.bts of package CC256XB_BT_SP\

But it can not work with TI chipset CC2564C, with bts file TIInit_6.12.26.bts of package CC256XC_BT_SP.

It always init timeout. We could ensure that board hardware is ok.

# hciattach /dev/ttyS2 texas 115200 noflow
Initialization timed out.

Could you give me some suggestions?

0 Hari Nagalla over 5 years ago in reply to jingbo wang

TI__Mastermind 27080 points

We do not see an issue with the BTS file on our system (AM335x EVM+CC2564C) with Bluez5.50.

Which, linux kernel version are you using? Does the HCI/UART on your host support hardware flow control i.e RTC/CTS? And does the UART driver support changing baudrate with ioctl calls?

am335x-evm login: root
root@am335x-evm:~# echo 0 > /sys/class/gpio/gpio117/value
root@am335x-evm:~# echo 1 > /sys/class/gpio/gpio117/value
root@am335x-evm:~# echo 0 > /sys/class/gpio/gpio117/value
root@am335x-evm:~# echo 1 > /sys/class/gpio/gpio117/value
root@am335x-evm:~# bluetoothctl -v
bluetoothctl: 5.50
root@am335x-evm:~#
root@am335x-evm:~# hciattach /dev/ttyS1 texas 3000000
Found a Texas Instruments' chip!
Firmware file : /lib/firmware/ti-connectivity/TIInit_6.12.26.bts
Loaded BTS script version 1
texas: changing baud rate to 3000000, flow control to 1
[ 115.099298] Bluetooth: Core ver 2.22
[ 115.115064] NET: Registered protocol family 31
[ 115.119563] Bluetooth: HCI device and connection manager initialized
[ 115.135954] Bluetooth: HCI socket layer initialized
[ 115.140894] Bluetooth: L2CAP socket layer initialized
[ 115.147747] Bluetooth: SCO socket layer initialized
[ 115.184096] Bluetooth: HCI UART driver ver 2.3
[ 115.204408] Bluetooth: HCI UART protocol H4 registered
[ 115.217816] Bluetooth: HCI UART protocol LL registered
[ 115.245048] Bluetooth: HCI UART protocol Broadcom registered
Device setup complete
root@am335x-evm:~#
root@am335x-evm:~#
root@am335x-evm:~# hcitool scan
Scanning ...
40:26:19:17:B7:44 iPhone
root@am335x-evm:~#
root@am335x-evm:~#
root@am335x-evm:~# ls -tlr /lib/firmware/ti-connectivity/ | grep TIInit_6.12.26.bts
-rw-r--r-- 1 1000 1000 6017 Apr 19 11:29 initscripts-TIInit_6.12.26.bts
-rw-r--r-- 1 root root 10137 Aug 26 2020 TIInit_6.12.26.bts
root@am335x-evm:~#

Thanks

0 jingbo wang over 5 years ago in reply to Hari Nagalla

Prodigy 70 points

oh, that's good.But a little bit strange on our board.

For linux version: we've tried linux3.x and 5.x.

For flow contorl: we disable the flow control of hardware and software, when use hciattach to init chip, we use the parameter noflow.

And does the UART driver support changing baudrate with ioctl calls? ----> how to check this ? I'm not sure about it.

Thanks

Best Regards

0 jingbo wang over 5 years ago in reply to Hari Nagalla

Prodigy 70 points

And one more thing, CC2564B works well with our software. So, it seems as if the problem is not due to a software issue, I ween.

Consequently, should we enable hardware and software flow control on CC2564c?

0 Hari Nagalla over 5 years ago in reply to jingbo wang

TI__Mastermind 27080 points

Yes, hardware flow control (H4) is being used. Please make sure, the Host UART port used for HCI connection towards CC2564C supports HW flow control. Which host processor are you using?

Thanks