• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 2897 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

hciattach fail with CC2564MODN module

Rex Lin
Intellectual 630 points

Other Parts Discussed in Thread: CC2564MODN

Hi:

We use CC2564MODN as our BT module and our platform is TI6638K2K, bluez version is 5.9.
We try to attach BT device and the result always fail.
Please help to check the return error code and provide your comment for us reference.
 
root@keystone-evm:~# hciattach -n -t 180 /dev/ttyS1 texas 115200
Found
a Texas Instruments' chip!
Firmware file :
/lib/firmware/ti-connectivity/TIInit_6.7.16.bts
Loaded BTS script version
1
texas: changing baud rate to 115200, flow control to 1
Can't init device
hci0: Device or resource busy (16)Can't initialize device: Device or resource
busy

Thanks

Rex Lin

  • 0
    TI__Mastermind 32615 points

    Hi,

    Did you take care of the first three steps from the link http://processors.wiki.ti.com/index.php/CC256x_Testing_Guide

    where did you get the TIInit_6.7.16.bts file from? can you share it.

    and do you have any kernel logs?

     

  • 0 in reply to Sundeep Javvaji
    Intellectual 630 points

    5417.bts.zip

    Hi:

    (1). Yes , this flow should be no problem

    (2). I attach the bts file for you reference

    (3).Currently , with a special hciattach flow, we can bringup the bluetooth device
    and work normally.

    The simple flow as bellow:

    1.Type 'hciattach -n -t 180 /dev/ttyS1 texas 115200' command and load btsTIInit_6.6.15.bts
       It would show as below:
       TI init command failed.
       Can't initialize device: Input/output error
    2.Type 'hciattach -n -t 180 /dev/ttyS1 texas 115200' command and load bluetooth_init_cc2564B_0.1.bts
    It would show as below:
    Cannot send hci command to
    socket: Connection timed out
    Can't initialize device: Connection timed out

    3.Type 'hciattach -n -t 180 /dev/ttyS1 texas 115200' command and load bluetooth_init_cc2564B_0.1.bts again
    It would show as below:
    [  239.926817] Bluetooth: Unknown HCI packet type 0c
    [  239.931612] Bluetooth: Unknown HCI packet type 01
    [  239.936579] Bluetooth: Unknown HCI packet type 01
    [  239.941567] Bluetooth: Unknown HCI packet type 10
    [  239.946550] Bluetooth: Unknown HCI packet type 00
    [ 239.951524] Bluetooth: Unknown HCI packet type 06
    [  239.956510] Bluetooth: Unknown HCI packet type 00
    [  239.961484] Bluetooth: Unknown HCI packet type 00
    [  239.969819] Bluetooth: Unknown HCI packet type 06
    [  239.974877] Bluetooth: Unknown HCI packet type 0d
    [  239.979854] Bluetooth: Unknown HCI packet type 00
    [  239.984827] Bluetooth: Unknown HCI packet type 81
    [ 239.989818] Bluetooth: Unknown HCI packet type 1b
    Device setup complete

    4.Type 'hciconfig hci0 up' to bring hci0 device
    5.Type 'hcitool scan'....

    And then the bluetooth work normally.

    Please check and help to analyze why we need to do this specific flow to make bluetooth work.

    Rex Lin

  • 0 in reply to Rex Lin
    TI__Mastermind 32615 points

    Hi,

    Did you try increasing the timeout value in the command?