STM32 Sniffer for BLE Troubleshooting

Revision as of 16:44, 16 June 2023 by Registered User (Created page with "This article will enumerate some problems you can encounter and their solutions. == Unknown direction == It is a known limitation. Please refer to the indication in the '''D...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This article will enumerate some problems you can encounter and their solutions.

1. Unknown direction

It is a known limitation. Please refer to the indication in the Direction column.

Direction column
Connectivity Sniffer Unknown Direction.png


If you don't have this column, check ST BLE Sniffer profile installation

2. No data after capture start

Check that the sniffer is on a primary advertising channel (37, 38 or 39).

3. Could not open port COM error

If you got the following message:

Could not open port COM error
Connectivity Sniffer Com Error.png


Close and re-open Wireshark.

If it's still not working, do the Other cases procedure.

4. Sniffer interface do not appear

  • Check extcap plugin is installed
  • Check sniffer stack is flashed and started
  • Check sniffer application firmware is flashed
  • Close Wireshark, unplug and replug the board, reset the board and re-open Wireshark

5. Other cases

If the sniffer already worked and stop working or don’t restart :

  • close Wireshark
  • unplug the board
  • plug the board
  • reset the board
  • re-open Wireshark
No categories assignedEdit