• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1281 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.

SmartRF Protocol Packet Sniffer and cc2564

Alexander Zakharov
Intellectual 295 points

Other Parts Discussed in Thread: CC2540, CC2564

We are in a process of evaluating cc2564 for potential use in our design, and I was wandering if "SmartRF Protocol Packet Sniffer" can be used with cc2564 (assuming that silicon is properly connected to the host via USB-UART bridge). We particulary interested in constant RX (rfmon) for the particular channel of choice. I remember we did it with cc2450, but what about cc2564? If not "SmartRF Protocol Packet Sniffer" what else can be used for this purpose and how?

  • 0
    TI__Expert 5840 points

    Hi Alexander,

    Unfortunately, the CC2564 doesn't have the Packet Sniffer capabilities as the CC2540.

    Regards,

    Dotan

  • 0 in reply to Dotan Ziv
    Intellectual 295 points

    Hi Dotan,

    Thanks for the reply. an you please clarify something for me - what is the purpose of 'Continuous RX' menu in CC256x BT Hardware Evaluation Tool and what it does exactly? (I assume it uses HCI_VS_DRPb_Tester_Con_RX HCI command where we pass channel number/frequency and ADPLL loop mode. Testing guide says that setup is the same as testing Continuous TX, but what one suppose to see on a PC attached? I assumed in a past that it will be exactly capture of everything on that channel (with corresponding demodulation). If it's not packet based  RX, then what is the expected result of this test? How one should see that RX is actually happening? Where the data (if any) goes? What exactly Packet TX/RX does in this case? (HCI Command HCI_VS_DRPb_Tester_Packet_TX_RX). TI CC256x Testing Guide does not explain what are expected result and what actually happening. If test to send a packet exists, then I presume peering test to receive should be somewhere as well. Can you please elaborate a bit more on this topic? Does it have to do something with  TX_DBG line by chance?

    Cheers,
    Alex

  • 0 in reply to Alexander Zakharov
    TI__Mastermind 32615 points

    Hi Alex,

    RX and TX can be verified using spectrum analyzer. See Testing guide wiki.

    Packer RX/TX usage is explained in both the Testing guide wiki Production line testing guide wiki.

    Please also see the "Vendor Specfic HCI command page wiki" to see how to use and expected result from the command line while using the HCI_VS command.

    It has nothing to do with TX_DBG.

  • 0 in reply to Sundeep Javvaji
    Intellectual 295 points

    Hello Sundeep,

    Thanks for the reply. I am looking at Testing Guide and Production test guide. It's fully clear to me what Continuous TX does and how to see the result on Spectrum Analyzer. But... I do have some difficulty to digest what Continuious RX suppose to do and how one actually verifies the result of correct RX in terms of data sent. May be I am missing something, but what Spectrum Analyzer has to do with the RX part of the test? I was kind of hoping to have two devices up and running and use your Hardware tool in order to send modulated patterm from one and see it appearing on the other one. Is it possible with TI Hardware Eval Tool. If not, can I somehow manipulate with HCI command set in order to accomplish something similar?

    Thanks in advance for rersponse.

  • 0 in reply to Alexander Zakharov
    TI__Mastermind 32615 points

    Hi Alex,

    No it is not possible.