2025-03-27 17:04:42 +01:00
|
|
|
Bluetooth Tester application
|
|
|
|
############################
|
2016-04-18 10:22:33 +02:00
|
|
|
|
2025-03-27 17:04:42 +01:00
|
|
|
The Tester application uses binary protocol to control Zephyr stack and is aimed at
|
2016-04-18 10:22:33 +02:00
|
|
|
automated testing. It requires two serial ports to operate.
|
|
|
|
The first serial is used by Bluetooth Testing Protocol (BTP) to drive Bluetooth
|
|
|
|
stack. BTP commands and events are received and buffered for further processing
|
|
|
|
over the same serial.
|
|
|
|
|
2019-03-11 10:08:11 +01:00
|
|
|
BTP specification can be found in auto-pts project repository:
|
|
|
|
https://github.com/intel/auto-pts
|
|
|
|
The auto-pts is an automation framework for PTS Bluetooth testing tool provided
|
|
|
|
by Bluetooth SIG.
|
|
|
|
|
2021-10-07 12:11:46 -04:00
|
|
|
See https://docs.zephyrproject.org/latest/guides/bluetooth/index.html for full
|
|
|
|
documentation about how to use this test.
|
|
|
|
|
2016-04-18 10:22:33 +02:00
|
|
|
|
2025-03-27 17:04:42 +01:00
|
|
|
Supported Profiles and Services
|
|
|
|
*******************************
|
|
|
|
|
|
|
|
Host/Core
|
|
|
|
=========
|
|
|
|
|
|
|
|
* GAP
|
|
|
|
* GATT
|
|
|
|
* IAS
|
|
|
|
* L2CAP
|
|
|
|
* OTS
|
|
|
|
* SM
|
|
|
|
|
|
|
|
LE Audio
|
|
|
|
========
|
|
|
|
|
|
|
|
* AICS
|
|
|
|
* ASCS
|
|
|
|
* BAP
|
|
|
|
* CAP
|
|
|
|
* CAS
|
|
|
|
* CCP
|
|
|
|
* CSIP
|
|
|
|
* CSIS
|
|
|
|
* HAP
|
|
|
|
* HAS
|
|
|
|
* MCP
|
|
|
|
* MCS
|
|
|
|
* MCIP
|
|
|
|
* MICS
|
|
|
|
* PACS
|
|
|
|
* PBP
|
|
|
|
* TBS
|
|
|
|
* TMAP
|
|
|
|
* VCP
|
|
|
|
* VCS
|
|
|
|
* VOCS
|
|
|
|
|
|
|
|
Mesh
|
|
|
|
====
|
|
|
|
|
|
|
|
* Mesh Node
|
|
|
|
* Mesh Model
|
|
|
|
|
|
|
|
Building and running on QEMU
|
|
|
|
****************************
|
2016-04-18 10:22:33 +02:00
|
|
|
|
|
|
|
QEMU should have connection with the external host Bluetooth hardware.
|
|
|
|
The btproxy tool from BlueZ can be used to give access to a Bluetooth controller
|
|
|
|
attached to the Linux host OS:
|
|
|
|
|
|
|
|
$ sudo tools/btproxy -u
|
|
|
|
Listening on /tmp/bt-server-bredr
|
|
|
|
|
|
|
|
/tmp/bt-server-bredr option is already set in Makefile through QEMU_EXTRA_FLAGS.
|
|
|
|
|
2017-11-11 12:59:51 +02:00
|
|
|
To build tester application for QEMU use BOARD=qemu_cortex_m3 and
|
|
|
|
CONF_FILE=qemu.conf. After this qemu can be started through the "run"
|
|
|
|
build target.
|
2016-11-03 12:39:04 +01:00
|
|
|
|
|
|
|
Note: Target board have to support enough UARTs for BTP and controller.
|
|
|
|
We recommend using qemu_cortex_m3.
|
2016-04-18 10:22:33 +02:00
|
|
|
|
|
|
|
'bt-stack-tester' UNIX socket (previously set in Makefile) can be used for now
|
|
|
|
to control tester application.
|
|
|
|
|
2017-11-11 12:59:51 +02:00
|
|
|
Next, build and flash tester application by employing the "flash" build
|
|
|
|
target.
|
2016-04-18 10:22:33 +02:00
|
|
|
|
|
|
|
Use serial client, e.g. PUTTY to communicate over the serial port
|
|
|
|
(typically /dev/ttyUSBx) with the tester using BTP.
|
2016-11-03 12:39:04 +01:00
|
|
|
|
2025-03-27 17:04:42 +01:00
|
|
|
Building for LE Audio
|
|
|
|
*********************
|
|
|
|
|
|
|
|
The tester application can be built with support for BT LE Audio by applying the
|
|
|
|
the ``overlay-le-audio.conf`` and ``hci_ipc.conf`` with ``--sysbuild`` for the supported boards,
|
|
|
|
e.g.:
|
|
|
|
|
|
|
|
west build -b nrf5340dk/nrf5340/cpuapp --sysbuild \
|
|
|
|
-- -DEXTRA_CONF_FILE=overlay-le-audio.conf;hci_ipc.conf
|
2025-06-03 11:53:43 +02:00
|
|
|
|
|
|
|
Building with support for btsnoop and rtt logs
|
|
|
|
**********************************************
|
|
|
|
|
|
|
|
Add following options in desired configuration file:
|
|
|
|
|
|
|
|
CONFIG_LOG=n
|
|
|
|
CONFIG_LOG_BACKEND_RTT=y
|
|
|
|
CONFIG_LOG_BACKEND_RTT_BUFFER=1
|
|
|
|
CONFIG_LOG_BACKEND_RTT_MODE_DROP=n
|
|
|
|
|
|
|
|
CONFIG_USE_SEGGER_RTT=y
|
|
|
|
CONFIG_SEGGER_RTT_SECTION_CUSTOM=y
|
|
|
|
|
|
|
|
CONFIG_BT_DEBUG_MONITOR_RTT=y
|
|
|
|
CONFIG_BT_DEBUG_MONITOR_RTT_BUFFER=2
|