• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 354 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.

CC2564 Power control

Russell Wetherley1
Expert 4255 points

Hello E2E.

This is a continuation from this thread:

When running the RF calibration I notice that I am receiving a bad status from the HCI after I send the enable_rf_calibration command. In a nutshell, I’m simply not getting a response within the internal timeout period used by HCI_Send_Raw_Command(). Following the instructions here (http://processors.wiki.ti.com/index.php/CC256x_Testing_Guide#Continuous_TX), I am issuing the enable_rf_calibration command to kick off my FCC constant TX test. When I connect my device to a spectrum analyzer, I can see that the module does indeed start constantly transmitting packets, but I want the UI on my host device to reflect this fact (i.e. accurately report whether the command was successful or not). What options do I have here? I’m wondering if it’s safe to simply ignore the fact that  enable_rf_calibration doesn’t return a valid status within the internal timeout period used by the API for HCI_Send_Raw_Command()?

Thank you very much!

Russell

  • 0
    TI__Mastermind 29301 points
    Hi Russell,

    Most likely, the response to the HCI_Send_Raw_Command() is returning, it's just that your code is not able to detect this response properly.

    The wiki instructions are for the setup where the HCI commands are sent directly to the CC256x using HCITester/SS1tool. If trying continuous TX using the bluetooth stack, it is better to use VS_Enable_FCC_Test_Mode() api from the BTVS.c. This function has implementation of the vendor specific commands necessary to put the device in continuous TX mode.

    Best regards,
    Vihang