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.

Linux/BOOST-CC2564MODA: BOOST-CC2564MODA

Part Number: BOOST-CC2564MODA

Tool/software: Linux

Hi we are using CC2564CMODA which is connected to our processor through UART. To control we are Using bluz and giving below hci commands.

 hciattach /dev/ttyMSM1  texas 115200 flow

we are seeing below message

Initialization timed out.

please let us know how interface getting up.

  • Can, you provide the console logs when you attempted hciattach. Which Bluez version are you using and on which host processor? Also, is the kernel built with Bluez?

    On AM335x beagle bone with TISDK, you would see below messages when hciattach is in invoked..

    root@am335x-evm:~# hciattach /dev/ttyS1 texas 3000000
    Found a Texas Instruments' chip!
    Firmware file : /lib/firmware/ti-connectivity/TIInit_11.8.32.bts
    Loaded BTS script version 1
    texas: changing baud rate to 3000000, flow control to 1
    [ 54.627644] Bluetooth: Core ver 2.22
    [ 54.642072] NET: Registered protocol family 31
    [ 54.646562] Bluetooth: HCI device and connection manager initialized
    [ 54.662218] Bluetooth: HCI socket layer initialized
    [ 54.667146] Bluetooth: L2CAP socket layer initialized
    [ 54.676507] Bluetooth: SCO socket layer initialized
    [ 54.692321] Bluetooth: HCI UART driver ver 2.3
    [ 54.696815] Bluetooth: HCI UART protocol H4 registered
    [ 54.713110] Bluetooth: HCI UART protocol LL registered
    [ 54.718300] Bluetooth: HCI UART protocol Three-wire (H5) registered
    Device setup complete
  • Hi Hari,

    1) We are using bluez5.50 and Qualcomm ipq4029 processor.bluez is built with kernel and kernel version is  4.4

    Download the service pack from  

    We have copied the service pack (initscripts-TIInit_6.12.26.bts) into /lib/firmware folder.

    2).Same  process we tried also by making laptop as host .

  • Hi

    please look at below logs which we are getting while doing hciattch with flow  and with noflow

    sudo hciattach /dev/ttyUSB0 texas 115200 noflow 

    Found a Texas Instruments' chip!
    Firmware file : /lib/firmware/TIInit_6.7.16.bts
    Loaded BTS script version 1
    texas: changing baud rate to 115200, flow control to 1
    Initialization timed out.

    sudo hciattach /dev/ttyUSB0 texas 115200 flow


    Found a Texas Instruments' chip!
    Firmware file : /lib/firmware/TIInit_6.7.16.bts
    Loaded BTS script version 1
    texas: changing baud rate to 115200, flow control to 1

    plese check HW connections.

  • HI Hari

    after copied the initscripts_TIInit_6.7.16.bts into  /lib/firmware it's able to attch the device but pairing is not happening

    hciattach -s 115200 /dev/ttyUSB1 texas 115200

    Found a Texas Instruments' chip!

    Firmware file : /lib/firmware/TIInit_6.7.16.bts

    Loaded BTS script version 1

    Device setup complete

    hciconfig -a

    hci1: Type: BR/EDR  Bus: UART

    BD Address: B0:B4:48:F4:A0:68  ACL MTU: 1021:4  SCO MTU: 180:4

    UP RUNNING

    RX bytes:597 acl:0 sco:0 events:29 errors:0

    TX bytes:394 acl:0 sco:0 commands:29 errors:0

    Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87

    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3

    Link policy: RSWITCH HOLD SNIFF

    Link mode: SLAVE ACCEPT

    Name: ''

    Class: 0x001f00

    Service Classes: Unspecified

    Device Class: Invalid Device Class!

    HCI Version: 4.0 (0x6)  Revision: 0x0

    LMP Version: 4.0 (0x6)  Subversion: 0x1b90

    Manufacturer: Texas Instruments Inc. (13)

    hciconfig hci1 up

    hciconfig

    hci1: Type: BR/EDR  Bus: UART

    BD Address: B0:B4:48:F4:A0:68  ACL MTU: 1021:4  SCO MTU: 180:4

    UP RUNNING

    RX bytes:877 acl:0 sco:0 events:32 errors:0

    TX bytes:406 acl:0 sco:0 commands:32 errors:0

    hcitool scan

    Scanning ...

           4C:BB:58:DE:6B:B7

    bluetoothctl

    Agent registered

    [bluetooth]# list

    Controller B0:B4:48:F4:A0:68 jagadish #2 [default]

    Controller D8:9C:67:A6:1D:96 ubuntu-0

    [bluetooth]# scan on

    Failed to start discovery: org.bluez.Error.NotReady

    [CHG] Controller B0:B4:48:F4:A0:68 Powered: yes

    [bluetooth]# scan on

    Discovery started

    [CHG] Controller B0:B4:48:F4:A0:68 Discovering: yes

    [NEW] Device 9C:AD:97:D7:90:EC 0581--CE--B

    [NEW] Device E4:46:DA:BE:A6:2C Redmi

    [NEW] Device 20:A6:0C:9B:18:33 Mi A2

    [bluetooth]# pair E4:46:DA:BE:A6:2C

    Attempting to pair with E4:46:DA:BE:A6:2C

    Failed to pair: org.bluez.Error.ConnectionAttemptFailed

    [NEW] Device B0:C0:90:69:65:42 VVDN

    [bluetooth]# pair 20:A6:0C:9B:18:3320:A6:0C:9B:18:33

    [bluetooth]# pair 20:A6:0C:9B:18:33

    Attempting to pair with 20:A6:0C:9B:18:33

  • Hi Hari,

    Yes, it's attempting to pair.But pairing  is  unsuccessful. 

    we are using initscripts_TIInit_6.7.16.bts bts file.

    • Is this bts file having support for dual mode(BLE+BT)?
    • if it isn't can you guide us which file should load?

    [bluetooth]# pair E4:46:DA:BE:A6:2C.

    Attempting to pair with E4:46:DA:BE:A6:2C

    Failed to pair: org.bluez.Error.ConnectionAttemptFailed.

    The name of device also not showing on our moblie .so,we can't pair from mobile also.

  • It is likely some Bluez configuration issue, and better to check in the web.. You, can also take firmware logs to see, if things are ok at the controller level..
    processors.wiki.ti.com/.../CC256x_Logger_User_Guide

    Thanks
  • Hi Hari

    we have checked with 3 different versions of bluez in all the cases we are not able to pair.

    I am attaching the debug logs for BOOST-CC2564cMODA.we loaded files which we got form http://www.ti.com/tool/cc256xb-bt-sp.

    what is these logs means?is it expected logs from a working controller?8308.btlogs.zip

  • Hi Hari,

    we need to set our controller in sleep mode.

    we have gone through below link for vendor specific HCI commands.
    As per the command HCI_VS_Sleep_Mode_Configurations (0xFD0C),  we have used below command to set device on sleep mode.
    hcitool -i hci0 cmd 3f 10c  01 01 00 FF FF FF FF 00
    But it's not able make the device into sleep state .Is this command valid to set device into sleep mode?
  • Jagadish,

    Have you tried changing the Deep sleep mode to see if you are able to get into deep sleep? For example try: 

    hcitool -i hci0 cmd 3f 10c  01 01 09 FF FF FF FF 00

    BR,

    Vince 

  • Hi vince

    we have checked below command 

    hcitool -i hci0 cmd 3f 10c 01 01 09 FF FF FF FF 00
    < HCI Command: ogf 0x3f, ocf 0x010c, plen 8
    01 01 09 FF FF FF FF 00
    > HCI Event: 0x0e plen 4
    01 0C FD 00

    we are not sure whether it is in sleep mode or not .How can we identify ? 

  • Jagadish,

    You can monitor the power and see if the current consumption reduced.

    BR,

    Vince 

  • hi Vince,

    We are monitoring the current requirement across the L1 inductor, when power is connected the Boost-CC2564C MODA is about 7milli amps by default,

    And, while scanning its 40milli amps and then after scan it goes back to 7mili amps, If we use the sleep command its still showing 7milli amps .Its not going less than 7 milli amps after sleep mode is asserted.

    Is this process the right way of checking power consumption or any other pin we need to probe?

  • Jagadish,

    Monitor current on the J10 jumper, between BP_3V3 and LP_3V3.

    BR,

    Vince