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.

CC2564MODN: RF Testing with SS1Tool Document

Part Number: CC2564MODN
Other Parts Discussed in Thread: CC2564

Hi, I have the swa750 "WL18xx Bluetopia PM Bluetooth RF Testing" document but this is only for the WL18xx devices.  Is there a similar document that's for the CC2564MODN device?  If so, please share.

In particular, I need help with getting the SS1Tool commands needed for BR/EDR and LE RF testing using the CC2564MODN.  Thanks. 

  • Hey Jonathan,

    Yes, we do have this RF testing guide for the CC2564 device: https://www.ti.com/lit/an/swra749/swra749.pdf.

  • Hi Dylan,

    I converted the HCI_VS_DRPb_Tester_Packet_TX_RX 0xFD85, 0x03, 0, 0xFF, 0, 2, 0, 27, 15, 1, 0x01FF command listed in the document to the SS1Tool format (SS1Tool cmd 0x3f 0x0185 0x03 0x00 0xFF 0x00 0x02 0x00 0x1b 0x0f 0x01 0xff 0x01) and am able to analyze the adjacent channel power however the power is very low at -0.8 dBm for BR.  I'm tapping off of the module output and am adjusting for cable loss.  Is there something I'm missing? 

  • Hey Jonathan,

    Did you load the service pack before initiating that command?

  • Yes the service pack was loaded.  The testing guide states that I need to disable AFH so the transmitter is not hopping in order to measure power on one frequency.  Maybe hopping is enabled which is why I'm measuring such low power on Ch 0?

    It says to send these commands before the HCI_VS_DRPb_Tester_Packet_TX_RX command:

    HCI_Write_AFH_Channel_Assessment_Mode 0x1

    HCI_Set_AFH_Host_Channel_Classification

    Can you help me convert these commands to SS1Tool format?  I couldn't find the commands in the CC256x HCI VS document (SWRA751).  I wish the CC256x had a similar document like SWRA750 for the WL18xx which provides examples with SS1Tool conversions.

  • Hey Jonathan,

    Yes, if you are focused on a certain channel then hopping will need to be disabled as mentioned in the guide. I have found this e2e post that provides an easy method for converting the HCI commands to SS1Tool format.

    Check that out and let me know if you have any issues.

  • Hi Dylan, is TIInit_6.7.16.bts (version TI_P7_16.42) the latest version we should be using for the CC2564MODN device?

  • Hey Jonathan,

    Yes, that is the latest version.

  • Ok so I verified I can transmit on BR, EDR and LE with hopping disabled, but the power is very low.  Less than 0 dBm.  I'm using the default TIInit_6.7.16.bts. You can view it here: BTS File

    Is there some setting in the BTS that is limiting power?  The VS_HCI commands I'm sending set the power level index to 15.  So not sure why power is so low.  Like I said previously, I'm measuring conducted right at the output of the module.  So my power measurements should be close to what's listed in the datasheet 8-10dBm. 

    DH5:

    Send_HCI_VS_DRPb_Tester_Packet_TX_RX 0xFD85, 0x03, 0x00, 0xff, 0x05, 0x05, 0x00, 0x0153, 0x0f, 0x01, 0x01ff

    3DH5:

    Send_HCI_VS_DRPb_Tester_Packet_TX_RX 0xFD85, 0x03, 0x00, 0xff, 0x0b, 0x05, 0x00, 0x03fd, 0x0f, 0x01, 0x01f

    LE:

    Send_HCI_BLE_Transmitter_Test 0x00, 0x00, 0x00

  • Hey Jonathan,

    Yes that does seem low for the default power. There are specific commands to adjust the power vectors which you can find in section 3.2.25 of this app note.

    Are these the commands you have already implemented? If not, I would go ahead and add them to see if it results in a different power level.

  • Yes this is what I'm sending:

    # Set power vector
    Send_HCI_VS_DRPb_Set_Power_Vector 0xFD82, 0x00, 0x9c, 0x18, 0xd2, 0xd2, 0xd2, 0xd2, 0xd2, 0xd2, 0xd2, 0xdc, 0xe6, 0xf0, 0xfa, 0x04, 0x0e, 0x18, 0xff, 0x0000
    Wait_HCI_Command_Complete_VS_DRPb_Set_Power_Vector_Event 5000, 0x00, 0xfd82, 0x00
    
    # Enable RF calibration (TPC)
    Send_HCI_VS_DRPb_Enable_RF_Calibration 0xFD80, 0x00, 0x00000800, 0x01
    Wait_HCI_Command_Complete_VS_DRPb_Enable_RF_Calibration_Event 5000, 0x00, 0xfd80, 0x0
    
    # Set BT BR (GFSK)
    Send_HCI_VS_DRPb_Tester_Packet_TX_RX 0xFD85, 0x03, 0x00, 0xff, 0x05, 0x05, 0x00, 0x0153, 0x0f, 0x01, 0x01ff
    Wait_HCI_Command_Complete_VS_DRPb_Tester_Packet_TX_RX_Event 5000, 0x00, 0xfd85, 0x00

    When I analyze the signal on a VSA I see the Adjacent Channel Power and the Eye Diagram looks good.  The issue is the measured power is around -0.9 dBm.  I followed the example in section 3.2.25 that you referred me to and set Power Level 15 to 0x18.  Am I doing something wrong? 

  • Hey Jonathan,

    This sequence of commands should be working to adjust the power. It doesn't seem like the power is changing at all from what you are doing. Are you able to run these with the HCITester Tool so we can rule out the conversion to SS1Tool being the issue?

    I also wanted to check if you are testing on custom HW or one of our EVMs?

  • I used the HCI Tester tool to create the HCI_VS commands and then used BTS Transform to convert to SS1Tool.  I'm pretty sure the commands are correct as the returned value for all the commands were 0x00 (Command succeeded).  Here are the SS1Tool commands I used on custom HW.  I don't have an EVM.

    SS1Tool cmd 0x3f 0x0182 0x00 0x9c 0x18 0xd2 0xd2 0xd2 0xd2 0xd2 0xd2 0xd2 0xdc 0xe6 0xf0 0xfa 0x04 0x0e 0x18 0xff 0x00 0x00

    SS1Tool cmd 0x3f 0x0180 0x00 0x00 0x08 0x00 0x00 0x01

    SS1Tool cmd 0x3f 0x0185 0x03 0x00 0xff 0x05 0x05 0x00 0x53 0x01 0x0f 0x01 0xff 0x01

  • Hey Jonathan,

    I don't have any specific decoder for this, so I will just do the same converting process on my end and see if it comes to the same values. I wanted to run a test on some hardware I have around the lab, it won't be the same as your custom HW obviously but it should show whether or not my power adjusts with these commands. Give me a day to get this set up going, and I'll get back to you tomorrow on my results.

  • Hey Jonathan,

    I have tested these commands for DH5 and confirmed they correctly adjust power

    # Set power vector
    Send_HCI_VS_DRPb_Set_Power_Vector 0xFD82, 0x00, 0x9c, 0x18, 0xd2, 0xd2, 0xd2, 0xd2, 0xd2, 0xd2, 0xd2, 0xdc, 0xe6, 0xf0, 0xfa, 0x04, 0x0e, 0x1a, 0xff, 0x00
    Wait_HCI_Command_Complete_VS_DRPb_Set_Power_Vector_Event 5000, any, 0xfd82, 0x00
    
    # Enable RF calibration (TPC)
    Send_HCI_VS_DRPb_Enable_RF_Calibration 0xFD80, 0x00, 0x00000800, 0x01
    Wait_HCI_Command_Complete_VS_DRPb_Enable_RF_Calibration_Event 5000, any, 0xfd80, 0x0
    
    # Set BT BR (GFSK)
    Send_HCI_VS_DRPb_Tester_Packet_TX_RX 0xFD85, 0x03, 0x00, 0xff, 0x05, 0x05, 0x00, 0x153, 0x0F, 0x01, 0x01ff
    Wait_HCI_Command_Complete_VS_DRPb_Tester_Packet_TX_RX_Event 5000, any, 0xfd85, 0x00

    I tested changing the power vector table (level 15 power) as well as just using the default power levels from the SP. If you aren't seeing at least 10 dBm with these commands, then its possible there is damage to the module.