zephyr/tests/bluetooth/tester
Emil Gydesen f58ac3476f Bluetooth: CAP: Add reference to the set member for CAP discover
Since the CSIP API expects a set member struct for nearly all
functionality, the reference to the full set member (along with
the CAS specific CSIS) should be given to the application.

Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
2024-05-18 15:51:26 +03:00
..
boards tests: bluetooth: tester: add nrf54l15 configs 2024-03-04 22:13:37 +01:00
src Bluetooth: CAP: Add reference to the set member for CAP discover 2024-05-18 15:51:26 +03:00
CMakeLists.txt bluetooth: tester: Add support for OTS 2024-05-02 16:51:42 +02:00
Kconfig
nrf5340_hci_ipc_cpunet.conf bluetooth: tester: add missing config 2024-04-02 14:31:30 +01:00
nrf5340_hci_ipc.conf bluetooth: tester: add missing config 2024-04-02 14:31:30 +01:00
overlay-le-audio.conf Bluetooth: BAP: Unicast server depend on PACS 2024-04-30 14:30:45 -04:00
overlay-mesh.conf Bluetooth: Mesh: use bt_rand instead of sys_rand 2024-04-29 11:00:00 +02:00
prj.conf bluetooth: tester: Add support for OTS 2024-05-02 16:51:42 +02:00
README
testcase.yaml hwmv2: Introduce Hardware model version 2 and convert devices 2024-03-02 16:56:33 -05: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.