zephyr/tests/bluetooth/tester
Emil Gydesen 8386929944 tests: Bluetooth: Tester: Log conn changes
Log the address and the err/reason values in the connected
and disconnect callbacks.

Since these values are not part of the BTP events it is
difficult to follow the order and reason why disconnects
happen when debugging.

Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
2024-11-16 14:56:51 -05:00
..
boards tests: bluetooth: tester: Fix bluetooth tester for nucleo_wba55cg 2024-11-16 13:29:39 -05:00
src tests: Bluetooth: Tester: Log conn changes 2024-11-16 14:56:51 -05:00
CMakeLists.txt
Kconfig
Kconfig.sysbuild tests: Bluetooth: tester: Workaround Bus Fault in nRF53x using full RAM 2024-11-08 09:25:28 -06:00
README
nrf5340_hci_ipc.conf
nrf5340_hci_ipc_cpunet.conf tests: Bluetooth: tester: Workaround Bus Fault in nRF53x using full RAM 2024-11-08 09:25:28 -06:00
overlay-le-audio.conf
overlay-mesh.conf
prj.conf
rd_rw612_bga.overlay
sysbuild.cmake tests: Bluetooth: tester: Workaround Bus Fault in nRF53x using full RAM 2024-11-08 09:25:28 -06:00
testcase.yaml tests: Bluetooth: tester: Workaround Bus Fault in nRF53x using full RAM 2024-11-08 09:25:28 -06:00

README

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.