nRF_Sniffer_UG_v2.2--nrf官方说明文档.pdf下载

Introduction The nRF Sniffer is a tool for debugging Bluetooth low energy (BLE) applications by detecting packets between a selected device and the device it is communicating with, even when the link is encrypted. When developing a BLE product, knowing what happens over-the-air between devices can help you isolate and solve any potential issues. By default, the Sniffer lists nearby BLE devices that are advertising, providing the Bluetooth Address and Address type, complete or shortened name, and RSSI. 1.1 Required hardware To set up the Sniffer you will need one of the following kits: • nRF51 Development Kit (PCA10028) v1.0 or later and a micro USB cable • nRF51 Dongle (PCA10031) • nRF51822 Evaluation Kit (PCA10001) and a mini USB cable • nRF51422 Evaluation Kit (PCA10003) v3.0.0 or later and a mini USB cable • nRF51822 Development Kit dongle (PCA10000) • nRF52 Development Kit (PCA10040) and a micro USB cable • nRF52840 Development Kit (PCA10056) and a micro USB cable 1.2 Required software • nRF Sniffer software v2.x or later available on the Sniffer product page under the downloads tab. This also includes the SEGGER J-Link software that is compatible. • Wireshark v2.4.6 or later available from http://www.wireshark.org/. Wireshark is a free software tool that captures wireless traffic and reproduces it in a readable format. • An operating system that runs the required version of Wireshark • Windows 7 or later • 64 bit OS X/macOS 10.6 or later • Linux (check for version compatibility) • python v2.7.x available from https://www.python.org/downloads/ • pyserial v3.4 or later available from https://github.com/pyserial/pyserial • Type “pip --version” in the terminal to verify that the pip installed with python v2.7 is used • For Windows - “C:\Python27\Scripts\pip.exe install -r requirements.txt” to install the python modules required for nRF Sniffer v2 • For OS X/mac OS/Linux - verify that the pip software being used is the pip installed with python 2.7. Then type “pip install -r requirements.txt” into the terminal 1.3 Writing conventions This user guide follows a set of typographic rules that make the document consistent and easy to read. The following writing conventions are used: • Commands are written in Lucida Console. • Pin names are written in Consolas. • File names and User Interface components are written in bold. • Internal cross-references are italicized and written in semi-bold.