• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 17 subscribers
  • Views 299 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

PACKET-SNIFFER: CC2540 Sniffer Dongle

PACKET-SNIFFER: TI Launchpad CC26x2

Mehul Dalal
Expert 2140 points
Part Number: PACKET-SNIFFER

I am able to successfully start receiving the BLE packets on the Wireshark.

However, the SmartRF Sniffer Agent is only showing I can sniff channels 37-39. Not 0-36. Any specific issue or configuration am I missing.

  • 0
    TI__Mastermind 25810 points

    Hey Mehul,

    I've assigned a colleague to help with this question.

  • +1
    TI__Mastermind 30119 points

    Hi,

    The SmarfRF Packet Sniffer functions by scanning for advertisement packets. These packets are located in channels 37-39 which is why the tool does not allow you to select different channels. Some of this information is contained in the Packet Sniffer User's guide and the relevant section is shown below:

    Based on the screenshot and the information you provided, it seems everything is configured properly in your end and the tool is functioning as expect.

    Best Regards,

    Jan

  • 0 in reply to Jan
    Expert 2140 points

    Thanks Jan.

    My RF Sniffer appears working fine. However, I am unable to see further trace once the connection is made through CONNECT_REQ. See attached wireshark capture #417. I expect further trace should be showing the data channel specific trace but the wireshark continue to show advertising packets only. 

    Any clue what is really going wrong? I have configured the same address in the initiator box as well.

  • 0 in reply to Mehul Dalal
    TI__Mastermind 30119 points

    Hi Mehul,

    Unfortunately, the Packet Sniffer 2 software is unable to track BLE5 connections. It is only able to track BLE5 advertisements. It can track BLE4 advertisements and connections. The following thread contains some information that you may find useful regarding BLE5 connections and the packet sniffer: https://e2e.ti.com/f/1/t/954044

    If you need the ability to fully track/sniff BLE5 connections, then I would suggest using a dedicated BLE5 sniffer. There are some suggestions in the thread linked above.

    Best Regards,

    Jan