CC2650: Trying to use CC2650 LaunchPad v1.2 as a packet sniffer

Make sure you use correct sniffer_fw.hex which should be under C:\Program Files (x86)\Texas Instruments\SmartRF Tools\SmartRF Packet Sniffer 2\sniffer_fw\bin\cc26x0lp

Hi Patrick,

I confirm that I can have CC2650 LaunchPad v1.2 working with packet sniffer.

Once you have flashed the right image (C:\Program Files (x86)\Texas Instruments\SmartRF Tools\SmartRF Packet Sniffer 2\sniffer_fw\bin\cc26x0lp) don’t forget to reset your LaunchPad and click “Detect”.

Note: the serial port is automatically selected.

I hope this will help.

Best regards,

Hello Clement and YK,

Thank you both for your suggestions. I've confirmed that I've installed the correct firmware. In fact, I've flashed the CC2650 with this firmware with Uniflash and SmartRF Programmer 2. Flashing was successful in both cases, but neither case resulted in successful operation. Clement suggested that the port would be assigned automatically, but in my case, no port is assigned or can be chosen as shown below. The Device Manager confirms that the debugger is on COM10. Any other suggestions would be appreciated.

Patrick

Hello,

To check that the CC2650 is connected to the TI Packet Sniffer, I connected via the serial port as shown below.

Since the serial read returns "TI Packet Sniffer ver.1.7.0" I presume that the TI Packet Sniffer Agent should be able to see the device. Furthermore this validates that the correct firmware is on the CC2650 LaunchPad. Other TI software products like Uniflash and Flash Programmer2 recognize the CC2650.

A similar issue was reported by YK Chen here. However in his case moving to a Win10 box resolved it. In my case, I'm already using a Win10 box. In that post, Severin said that he would escalate the problem and report the findings, Unfortunately, no findings were reported.

What else can I try to get a packet sniffer up as soon as possible - other software, a different sniffer (other than the CC2650 LaunchPad), Different installation procedures, etc.?

Thanks,

Patrick

Try to run sniffer agent using administrator privilege.

Hi YK,

Thanks for the suggestion, but that doesn't change the behavior. Running Sniffer Agent using Admin privileges doesn't help :(

Patrick

Do you have another LAUNCHXL-CC2650 to test this? By the way, do you mean to use LAUNCHXL-CC2650 as BLE sniffer?

Yes, I guess I use CC2650 LaunchPad because that what it says on the board, but in fact you're right it's the LAUNCHXL-CC2650. I should be more careful so I don't confuse people - thanks. I don't have another one to try. I may try to load another project to confirm it works with an alternate example. BTW you mentioned that you had this problem on WIN7 but it was mysteriously resolved on WIN10. Any more insight on that?

Patrick

I remember my LAUNCHXL-CC2650 simulated application COM port is larger than COM100 and cause the issue. After I revise it to COM22 for example, the problem is solved. You don't reply my "do you mean to use LAUNCHXL-CC2650 as BLE sniffer?". I ask this because LAUNCHXL-CC2650 seems cannot be used as BLE sniffer. It only supports 802.15.4 sniffer if I remember correctly.

Hi YK,

Yes, I'm using the LAUNCHXL-CC2650 as the BLE sniffer. Interestingly I find that the TI documentation is inconsistent. the Packet Sniffer 2 shows that the LAUNCHXL-CC2650 is supported as a sniffer for the CC26x0 product family as shown below.

Elsewhere I see support for only Bluetooth Low Energy as:

I think we need some clarification from TI on this one.

Thanks again for your help.

Patrick

I try it again just now and I don't see it supports BLE in sniffer agent.

Hi YK,

My problem is that the Sniffer Agent doesn't recognize my LAUNCHXL-CC2650 regardless of radio types. Your point is a good one, the LAUNCHXL-CC2650 doesn't support Packet Sniffer 2 as shown below from Resource Explorer. Since my device won't connect, I'm reluctant to buy one of the LaunchPads that support BLE sniffing.

Thanks again for your help.

Patrick

Hi Patrick,

I'm sorry to hear that you've had so much trouble with Packet Sniffer 2.

I checked internally with the tool’s developers. They were not able to reproduce your problem.

One possible cause could be bad signals on “RXD”/”TXD”. (Can you confirm that you have well mounted the jumpers?)

Best regards,

Hi Clement,

Thank you for investigating this issue further. The RXD & TXD jumpers are properly installed. My previous post shows via Powershell Terminal that the serial connection is made. So, sadly this is not a poor mechanical connection. As this problem has been reported elsewhere on the forum, I'd encourage your developer colleagues to continue their investigation.

Good luck,

Patrick