• State
  • Locked Locked
  • Replies 12 replies
  • Subscribers 56 subscribers
  • Views 1768 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.

LAUNCHXL-CC1352P: SmartRF Sniffer Agent is not able to detect attached LAUNCHXL-CC1352P development board

Timothy Murtaugh
Expert 1475 points
Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: CC1352P, UNIFLASH,

Hello,

I have three CC1352P1 Launchpads. I'm using one as a coordinator, one as and end device, and one as a packet sniffer.
When I run the SmartRF Sniffer Agent (version 1.6.0) it doesn't see any of the connected devices.
After I press the "Detect Devices" button, the toolbar at the bottom shows the message "Sniffer Device(s) Not Found".
I flashed the CC1352P sniffer board successfully using UniFlash with C:\Program Files (x86)\Texas Instruments\SmartRF Tools\SmartRF Packet Sniffer 2\sniffer_fw\bin\cc1352p1lp\sniffer_fw.hex.

The TI tool xdsdfu.exe sees all three Launchpads, the output is shown here:

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2018 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x0451 PID: 0xbef3
Device Name: XDS110 Embed with CMSIS-DAP
Version: 2.3.0.17
Manufacturer: Texas Instruments
Serial Num: L420008V
Mode: Runtime
Configuration: Standard

<<<< Device 1 >>>>

VID: 0x0451 PID: 0xbef3
Device Name: XDS110 Embed with CMSIS-DAP
Version: 2.3.0.17
Manufacturer: Texas Instruments
Serial Num: L420009P
Mode: Runtime
Configuration: Standard

<<<< Device 2 >>>>

VID: 0x0451 PID: 0xbef3
Device Name: XDS110 Embed with CMSIS-DAP
Version: 2.3.0.16
Manufacturer: Texas Instruments
Serial Num: L42000CA
Mode: Runtime
Configuration: Standard

Found 3 devices.

I'm attempting to use the board with serial number L420009P as my packet sniffer (the other two boards are my coordinator and end device).

All three of my CC1352P1 Launchpads have this on the back
HW Rev A
FW SDK 2.10

And all three have a CC1352P MCU rev C.

So I need to know why my Sniffer Agent cannot detect any of my Launchpads. Any help would be greatly appreciated.

Thank you,

Tim Murtaugh

  • 0
    TI__Genius 9215 points
    Hi Tim,

    Is the serial port settings in SmartRF Packet Sniffer setup correctly (921600 baud)?
    Is your Launchpad detected with two com ports in device manager?
    If you use a terminal (like putty) and connect that to your Launcpad's com port, do you see any messenger?

    Best Regards,
    R.M
  • 0 in reply to R.M
    Expert 1475 points

    Yes SmartRF Packet Sniffer is configured to use 921600 baud.

    I'm using Windows 10 Enterprise 64-bit. In Windows Device Manager I see the following:

    Under Ports (COM & LPT)

    XDS110 Class Application/User UART (COM11)

    XDS110 Class Auxiliary Data Port (COM12)

    I also see the COM ports associated with my coordinator and end device.

    I tried connecting to COM11 and COM12 using Putty. I assume you want me to use 921600 baud?

    Putty would not open when I tried connecting to COM11. It did connect to COM12, but I saw nothing in the terminal.

    Which COM port should I connect to using Putty, and when baud rate should I use?

    Thanks

  • 0 in reply to Timothy Murtaugh
    TI__Genius 9215 points
    Hi Tim,

    It's the XDS110 Class Application/User UART (COM11) port you should connect to and the baudrate should be 921600.

    Do you have SmartRF Packet Sniffer running when trying to connect to COM11 with Putty? Only one resource can be using a com port at the time so if SmartRF Packet Sniffer is connected to COM11 you can't connect to the same with Putty at the same time.


    Best Regards,
    R.M
  • 0 in reply to R.M
    Expert 1475 points

    R.M.

    I am able to connect to the my packet sniffer board using Putty at XDS110 Class Application/User UART (COM11) with baudrate 921600. However I see garbage characters in the Putty terminal. Is that normal? What should I see in the Putty terminal?

    Tim

  • 0 in reply to Timothy Murtaugh
    TI__Genius 9215 points
    Hi Tim,

    You should see the text "TI Packet Sniffer ver.1.6.0" printed repeatably every second.

    Garbage characters in the Putty terminal indicate wrong baudrate but that should not be the case if you are flashing with the prebuild image.
    I just tried flashing the sniffer_fw.hex image found in sniffer_fw/bin/cc1352p1lp/ folder on a CC1352P Chip Rev C Launchpad and I can see the test being printed.

    You could try with a different baudrate (115200) just to check.

    Best Regards,
    R.M
  • 0 in reply to Timothy Murtaugh
    Guru 735695 points

    If you check the application UART COM port output from LAUNCHXL-CC1352P, do you see the following output?

  • 0 in reply to YiKai Chen
    Expert 1475 points

    I just flashed my Launchpad with sniffer_fw.hex image found in sniffer_fw/bin/cc1352p1lp/ folder using Uniflash.

    I tried connecting with Putty using 921600 baud, flow none, parity none, stop bits 1, data bits 8.

    I also tried using 115200 baud, flow none, parity none, stop bits 1, data bits 8.

    I both cases the Putty terminal window opens but I see nothing in the terminal.

    I don't know what's wrong.

    The good news is Uniflash is able to flash the Launchpad. And Code Composer Studio can flash and debug my other two Launchpads. It's just the Sniffer Agent that can't detect the Launchpad I'm using as my packet sniffer (in fact it can't detect any of my Launchpads).

  • 0 in reply to Timothy Murtaugh
    Guru 735695 points
    Do you check the output application virtual COM Port not Aux COM port simulated by LaunchPad?
  • 0 in reply to YiKai Chen
    TI__Genius 9215 points
    Hi Tim,

    Your Putty setting is correct so I do not understand why this don't work. I believe you said that you did see garbage characters in the Putty terminal earlier but no you do not see anything?
    Just to be 100% sure, you do have jumpers on the RxD and TxD Launchpad pins right?

    Best Regards,
    R.M
  • 0 in reply to R.M
    Guru 735695 points
    That screen shot is from me not Tim. Tim has not attached his UART output yet.
  • 0 in reply to YiKai Chen
    TI__Genius 9215 points

    Hi YK

    Tim did mention in a earlier post that he did see garbage characters in the Putty terminal:

    Best Regards,

    R.M

  • 0 in reply to YiKai Chen
    Expert 1475 points

    I've been out of the office for a couple of days. Thanks for the replies guys.

    I finally got this working. I did so by unplugging my Launchpad and plugging it in again several times. After doing so the Sniffer Agent finally recognized it. I got Putty to recognize it too, but I had to unplug and replug the board to get Putty to recognize it after shutting down the Sniffer Agent. It's weird.

    Windows Device Manager and CCS and Uniflash and xdsdfu.exe all detect my Launchpads without a problem. It's only the Sniffer Agent that seems to be so fussy, requiring an unplug and replug.

    Thanks for your help.

    Tim