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.

CC256XB-BT-SP: Loading mutiple BTS files from Linux (ARM 64-bit)

Part Number: CC256XB-BT-SP
Other Parts Discussed in Thread: CC2564C

Hi there, I am trying to load TIInit_6.7.16.bts and then initscripts-TIInit_6.7.16_avpr_add-on.bts from Linux ARMv8 (64-bit). From what I can tell, Bluetopia is only supported on ARMv7 (32-bit).

The Bluez loader only loads one bts file (and due to the confusing way it is architected, I'm not sure how to add a second file easily).

Is there some spec for how to implement this easily? Or perhaps an example?

Thanks

VB

  • Hi VB,

    The initscripts-TIInit_6.7.16_avpr_add-on.bts file is written to be used as a separate .bts from the original TIInit_6.7.16.bts file. 

    You should only need to load the avpr add-on file to your system for correct functionality--Can you try this for me?

    Thank you,

    -Ryan

  • Hi Ryan,

    Thanks

    Now the BT classic test is working, however the BLE test is not.

    To be clear we are trying to enable continuous BLE transmit for radio verification testing (and this is blocking cerification)

    The sequence of steps (and slight variations of these steps were tried in addition, but these seem like they are the specified steps):

    1. FW initially loaded: TIInit_6.12.26.bts
    2. FW file put in place of original initscripts-TIInit_6.7.16_ble_add-on.bts
    3. Bluetooth service restart
      1. hcitool -i hci0 cmd 0x3F 0x15B 1 1 (tried with and without this command)
      2. hcitool -i hci0 cmd 0x3F 0x177 0x01 0 0 0x71764129 0 0 0 0 0 0
      3. hcitool -i hci0 cmd 0x08 0x01E 0 37 0 (tried to send this once or twice)
    4. wait until we want to stop test
      1. hcitool -i hci0 cmd 0x08 0x01F

     

    Testing guide used: /cfs-file/__key/communityserver-discussions-components-files/538/5621.CC256x-Testing-Guide-_2D00_-Texas-Instruments-Wiki.pdf

    FW files used: http://software-dl.ti.com/dsps/forms/self_cert_export.html?prod_no=cc256xb_bt_sp_v1.8.zip&ref_url=http://software-dl.ti.com/ecs&_ticdt=MTY0MzMwMTEyN3xsaXQ0NzcyMDQyMDQ3NzIwNDIwNDc3MjA0MjA2MTQ4YzMwNzdlMWQ2OWZ8R0ExLjIuMTU2MjYzMTAzMy4xNjMyMTU4NTI1

    Can you please check the above HCI commands to check if they should work for BLE?

    Thanks

    Ville

  • Hi Ville,

    Can you verify that you initially loaded the TIInit_6.7.16.bts file? This file is for the CC256XB-BT-SP (the B revision) whereas the TIInit_6.12.26.bts file is used for the C revision of the hardware. This may be causing some BLE issues--I would try loading this first before anything else.

    Additionally, if you are trying to use both AVPR and BLE functionality, I would recommend adding in the following commands to the TIInit_6.7.16.bts service pack, then loading the new file to the device: 

    To enable AVPR (in the beginning of the script):

    Send_HCI_VS_AVPR_Enable 0xFD92, 0x01, 0x00, 0x01, 0x0000
    Wait_HCI_Command_Complete_VS_AVPR_Enable_Event 5000, 0x00, 0xfd92, 0x00

    To reset AVPR as sink role:

    Send_HCI_VS_AVPR_Enable 0xFD92, 0x01, 0x01, 0x00, 0x0000
    Wait_HCI_Command_Complete_VS_AVPR_Enable_Event 5000, 0x00, 0xfd92, 0x00

    Can you try these for me?

  • We are using the PAN1326C2, which has the CC2564C, so using the Rev C. I can also confirm that we are using the TIInit_6.12.26.bts in all cases, and loading the initscripts-TIInit_6.7.16_ble_add-on.bts before testing. We are also not sure how to edit these .bts files.

  • Hi Ville,

    Thanks for confirming that you're using version C of the hardware. The service pack available for version C can be found here on ti.com: CC256XC-BT-SP

    In this service pack, there is an initscripts add-on file for BLE with version 6.12.26, made for Rev C of the hardware. Can you try downloading this version of the service pack and loading that version of the BLE add on?

    Thanks,

    -Ryan

  • Hi Ryan,

    Ok so we have used this version of the BLE add on. It still displays no other behaviour (I.e: TX test does not work)

    Thanks

    Ville

  • Hi Ville,

    Thank you for trying that for me--now can we try adding the BLE HCI Commands to the AVPR Add-On .bts file?

    You can open and modify .bts files in HCI tester, which can be downloaded here on TI.com: Wireless Tools Package

    Open the initscripts-TIInit_6.12.26_avpr_add-on.bts file and the initscripts-TIInit_6.12.26_ble_add-on.bts file, then transfer the HCI commands in the BLE file to the AVPR add on file. This should allow you to have both functionality of AVPR and BLE in a single .bts file. 

    Thanks,

    -Ryan

  • Hi Ryan

    I have downloaded the HCITester, but it is not successful in opening xxxx_6.12.26.bts files. I have tried the following steps (very similar to before), and the BT classic does work with these steps (with the correct HCI commands):

    1. FW initially loaded: TIInit_6.12.26.bts
    2. FW file put in place of original initscripts-TIInit_6.12.26_ble_add-on.bts
    3. Bluetooth service restart
    4. FW file put in place of original initscripts-TIInit_6.12.26_avpr_add-on.bts
    5. Bluetooth service restart
    6. hcitool -i hci0 cmd 0x3F 0x15B 1 1 (tried with and without this command)
    7. hcitool -i hci0 cmd 0x3F 0x177 0x01 0 0 0x71764129 0 0 0 0 0 0
    8. hcitool -i hci0 cmd 0x08 0x01E 0 37 0 (tried to send this once or twice)
    9. wait until we want to stop test
    10. hcitool -i hci0 cmd 0x08 0x01F

    Thanks

    Ville

  • This is the difficulty we are having with the tool

  • Hi Ville,

    I am able to recreate this issue when I have multiple instances of HCI tester running concurrently. Is this the only instance of HCI tester you have open? 

    Thank you,

    -Ryan

  • Hi Ryan,

    I'm only running one instance I'm sure 

    Are you sure the tool supports loading a BTS? Or do I need to convert it to a script first

    Thanks

    Ville

  • I am now able to edit the scripts and steps done in between were to close it, open it from the start menu, and add the .xml library of commands.

    However, all the BLE script does it the enable BLE command, and set the power, of which only the power command was missing (the .bts script sets the power to seemingly it’s lowest level).

    I have tried using the command which works for BT classic for BLE by changing the modulation type as mentioned in the post below. 2 Questions from this:

    1. Does this actually test the max power that BLE can transmit for radio verification testing
    2. Is there a different way to turn it off to BT classic? As the module does not stop transmitting with the same command that stops the BT classic Tx test. The test sequence for BT classic is below and is the same for this point except that the modulation type is set to 4(BLE) instead of 0(CW)

     

    https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/929844/cc2564c-hci_vs_drpb_tester_con_tx-command-ble-mode-channel-selection

     

    1. FW initially loaded: TIInit_6.12.26.bts
    2. FW file put in place of original initscripts-TIInit_6.12.26_ble_add-on.bts
    3. Bluetooth service restart
    4. FW file put in place of original initscripts-TIInit_6.12.26_avpr_add-on.bts
    5. Bluetooth service restart
    6. hcitool -i hci0 cmd 0x3F 0x184 0 0 0 15 0 0
    7. hcitool -i hci0 cmd 0x3F 0x188
  • 1. There is an HCI command for testing the output power of BLE: 

    2. There is an HCI command to enable/disable BLE as well:

    Let me know if there is any more clarification I can provide with these commands! 

    Best,

    -Ryan