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.

CC1310: cc1310 sniffer not working

Part Number: CC1310

Hi, I´m using CC1310 Launchpad V1.4, flashed with C:\Program Files (x86)\Texas Instruments\SmartRF Tools\SmartRF Packet Sniffer 2\sniffer_fw\bin\cc13x0lp\sniffer_fw.hex.

The led is blinking.

Running under Windows 10, SmartRF Packet Sniffer 2 V 1.04.00

The Sniffer Agent reports always "Sniffer Device Not Found"

When connected to PC the Launchpad is detected as a COMM PORT.

I have not tested with other OS, but as viewed in other questions on the forum, W10 apparently is not the problem.

  • I installed version 1.4.0 of the packet sniffer and flashed a CC1310 LP with the sniffer_fw.hex file. The LED blinks on the LP until I start the sniffer agent. Then the LED stops blinking and the agent shows "Sniffer Devices Connected: 1"

    If you use SmartRF Studio or Flash programmer 2, does CC1310 get detected?
  • Hi TER, yes it is detected. I can Erase and Program the board or use it as packet receiver (RF Studio).
    I´m using Flash Programmer 2 version 1.7.5 and Smart RF Studio 7 2.9.0
    Windows shows this board as XDS110 Class Application/User UART (COM18) and XDS Class Auxiliary Data Port (COM17)
    I´ve already tested on my 3 USB ports, Restarted Windows...
    Sniffer Agent v1.04.00 was completely uninstalled, all files and directory deleted from PC and reinstalled again.
    Thank you for your prompt response.
    Regards
  • So it's only the sniffer agent that does not detect the board? I assume that when you test the only program open that can potentially connect to the CC1310 LP is the sniffer agent?
  • Yes, only the sniffer agent.
    And yes, it´s the only program opened.
    I made this test in this order: Restart Windows, plugged CC1310LP , opened Sniffer agent.
  • I forgot to write...
    I ´ve tested 2 cc1310lp boards.
    A thing that seems weird is that every time I open Packet Sniffer I have to confirm to Windows that this program is safe. It does not occur with CCS for example.
  • Hi Andre,

    After you program the board with the hex file one of the LEDs shall be blinking, and once the Sniffer Agent has successfully detected the board it should stop to blink. It seems that you have programmed the correct firmware on the board.

    Have you tried this with several boards? Can you try connect with a serial terminal program (Hyperterm, Realterm or similar)? Baud rate: 921600, data bits: 8, stop bits: 1, parity None, flow control: No. Once powered, it shall output "TI Packet Sniffer ver 1.4.0" in the serial terminal.

    The unknown publisher warning should have been removed in the 1.4.0 version in the sniffer_agent.exe, however it is still there for the installer. We will fix the same for the installer in the next version so you don't have to confirm that the program is safe and it will be shown with Texas Instruments as the publisher.  

    Bjørn

  • Hi Bjorn, answering your questions:
    I´ve tested running sniffer in 3 CC1310LP boards connected to my laptop -> neither of them were detected.
    So I installed Sniffer Agent in 2 other PCs -> in both, the boards were detected. In one of them everything is working, e.g. I can sniffer packets using Easylink at 5kbps long range (Wireshark).
    In my laptop (Dell Inspiron 1525 - Windows 10 - 1803) I uninstalled CCS7 and CCS8 ( I thought it could be a driver problem) and reinstalled CCS8 but even though the sniffer doesn´t work.
    Maybe cleaning the registers/drivers and so on it works, but clean what exactly I don´t know.
    Do you have any suggestions?
    Thank you
    Regards
  • Hi,

    You could try with a serial terminal as suggested earlier and see if you have output from the board there. It is also possible to send a CMD_PING over the serial interface, and check the response in the serial terminal. But first you could check if you see periodic output in the serial terminal (please see the post above).

    One other thing that could be attempted is to delete all XDS 110 boards from the Windows device manager. Then you open Control Panel and Device Manager, and select View->"Show hidden device". Make sure no boards are connected to the device and then delete each of the XDS 110 COM ports (under Ports (COM & LPT).

    I am not sure this will help but could try.

    Bjørn

  • Hi, the terminal shows the messages from the board.
    The problem was really on my machine. I´ve restored Windows (used an old restore point) and then update the system. After that all worked fine.
    Thank you for your help.