zephyr/tests/bluetooth/tester
Emil Gydesen 26e74f75b6 tests: Bluetooth: Tester: Fix typo in PBP announcement
Fixes typo in the event name.
Changes the struct to also use _ev instead of _rp as it
is an event and not a response.

Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
2025-03-31 19:48:25 -04:00
..
boards drivers uart_native_posix: rename to native_pty and support N instances 2025-03-11 18:54:02 +01:00
src tests: Bluetooth: Tester: Fix typo in PBP announcement 2025-03-31 19:48:25 -04:00
CMakeLists.txt
hci_ipc_cpunet.conf test: bluetooth: tester: Fix regression in PBP 2025-03-17 13:57:41 +01:00
hci_ipc.conf tests: bluetooth: tester: make hci_ipc confs generic for multi-core 2024-11-27 08:16:50 +01:00
Kconfig tests: bluetooth: tester: Make BTP CMD thread stack size kconfig 2025-02-12 16:04:48 +01:00
Kconfig.sysbuild
overlay-le-audio.conf Bluetooth: BAP: Add a set of suggested intervals to use with BAP 2025-03-11 08:58:51 +01:00
overlay-mesh.conf Tests: Bluetooth: Fix stack overflow for tester 2025-02-28 18:30:08 +01:00
prj.conf Bluetooth: Host: more secure defaults for key size and legacy pairing 2024-12-04 12:10:54 +01:00
rd_rw612_bga.overlay
README
sysbuild.cmake tests: bluetooth: tester: make hci_ipc confs generic for multi-core 2024-11-27 08:16:50 +01:00
testcase.yaml bluetooth: tester: btp: adds testcase tester legacy adv 2025-02-18 18:37:59 +01:00

Title: Bluetooth tester application

Description:

Tester application uses binary protocol to control Zephyr stack and is aimed at
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.

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.

See https://docs.zephyrproject.org/latest/guides/bluetooth/index.html for full
documentation about how to use this test.

--------------------------------------------------------------------------------

Supported Profiles:

GAP, GATT, SM
--------------------------------------------------------------------------------

Building and running on QEMU:

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.

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.

Note: Target board have to support enough UARTs for BTP and controller.
      We recommend using qemu_cortex_m3.

'bt-stack-tester' UNIX socket (previously set in Makefile) can be used for now
to control tester application.
--------------------------------------------------------------------------------

Next, build and flash tester application by employing the "flash" build
target.

Use serial client, e.g. PUTTY to communicate over the serial port
(typically /dev/ttyUSBx) with the tester using BTP.