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.

LAUNCHXL-CC1310: Sniffer connection problem

Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: CC1350, , PACKET-SNIFFER, CC1310

Hi.
I am trying to set up a sniffer fw on LAUNCHXL-CC1310 to sniff sub1ghz packets coming from CC1350 sensortag.
I used C:/ti/simplelink_cc13x0_sdk_1_30_00_06/tools/ti154stack/TiWsPc2/sniffer_fw/bin/sniffer_fw_gfsk_50kbps_868_915.hex with Flash Programmer to flash the launchxl, and it flashed successfully.
When the device is turned on, the green led is blinking and I can see in UART the string "TI Packet Sniffer ver.1.0.0" printed every second.

I installed smartRF packet-sniffer 2 from TI but when I turn it on, it cannot find any devices, also when I press "Search for new Devices".

Can you please help, How do I set up the sniffer?

  • Hello,

    Can you check the serial port settings and make sure you are connected to the correct COM port.

    Regards,
    AB
  • Hey MoonDrop,

    The SmartRF Packet Sniffer 2 has different firmware than the TiWsPc2. You can find the sniffer fw in C:\Program Files (x86)\Texas Instruments\SmartRF Tools\SmartRF Packet Sniffer 2\sniffer_fw.

    After flashing the appropriate fw, the software should now be able to discover the device.

  • .

    Still not working. I flashed firmware sniffer_fw_gfsk_50kbps_868_915.hex from C:/Program Files (x86)/Texas Instruments/SmartRF Tools/SmartRF Packet Sniffer 2/sniffer_fw/bin/cc13x0lp/15.4g/sniffer_fw_gfsk_50kbps_868_915.hex on launchxl-cc1310

    But device is still not showing up in Packet sniffer:

  • Can you please help resolve this issue? How do I setup sub1ghz sniffer with prebuilt firmware and TI packet-sniffer 2?
  • Hello,

    CAn you check device manager and see if the device if the data/UART port is visible by the computer?

    Thanks,
    AB
  • I'm closing this thread due to inactivity. Please free to reopen this thread by replying.
  • I've been using the packet sniffer since the middle of last year. My problem is with PACKET-SNIFFER-2_1.4.0 and the cc1350 launchpad. The firmware for the cc1350  is sniffer_fw_gfsk_50kbps_868_915.hex which I flashed from the PACKET-SNIFFER-2_1.4.0 install. However, when I run the SnifferAgent V1.04.00 and try to start the detected cc1350 selected from the Device Configuration dialog I get a SnifferAgent error dialog saying:

    Error Sending Message

    Device = 21

    Message = CfgPhy

    Problem = The Command Has Invalid Format Or is Not Supported

    I have a 2nd sniffer on a different machine with PACKET-SNIFFER-2_1.3.0 I've also been using that can detect and use the cc1350 with the firmware installed with PACKET-SNIFFER-2_1.4.0. I also have some cc1312 boards that do work with PACKET-SNIFFER-2_1.4.0 but I'd like to use the cc1350 with PACKET-SNIFFER-2_1.4.0 if possible.

  • Hello,

    I just tried this, and I had the same problem. I will reach out to the Packet Sniffer team and update you on this.

    Regards,
    AB
  • Hi,

    Could it be that you are using firmware from an older version with the Sniffer Agent 1.4.0? There is no sniffer_fw_gfsk_50kbps_868_915.hex file in the 1.4.0 installer. From 1.4.0 all PHYs for each device is supported in a single firmware file. For CC1310/CC1350 this file is sniffer_fw\bin\cc13x0lp\sniffer_fw.hex.

    Please try uninstall your SmartRF Packet Sniffer 2. Make sure all folders and files are deleted, then reinstall 1.4.0 and use the firmware there.

    Regards,

    Bjørn

  • Thank you for resolving my confusion and improving your useful tool. 1.4.0 did install over top of 1.3.0 leaving the 1.3.0 firmware files and it was not evident (at least to me) that there is now only one firmware file to use for each controller type. Obviously, a note in readme.txt accompanying the installer would have been helpful. 

  • Hi,
    Yes, thanks for your suggestion and for reporting back on this. Good to hear it is resolved now.

    Regards,
    Bjørn