zephyr/tests/bluetooth/tester
Alberto Escolar Piedras 66a70a2ffd tests/bluetooth: Don't test on native_posix
native_posix is now deprecated.
Building these tests in both native_sim and native_posix does not
improve coverage for the tests or subsystem but doubles CI time.
As anyhow native_posix will be removed all together in
2 releases, let's remove it already for these.

Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
2024-09-25 04:04:36 -04:00
..
boards tests/bluetooth: Don't test on native_posix 2024-09-25 04:04:36 -04:00
src Bluetooth: VCP: Vol ctlr rename flags to vol_flags 2024-09-17 14:52:37 -04:00
CMakeLists.txt
Kconfig
README
nrf5340_hci_ipc.conf tests: bluetooth: tester: Fix buffer sizes on nRF5340 2024-09-02 12:30:06 -04:00
nrf5340_hci_ipc_cpunet.conf tests: bluetooth: tester: Fix buffer sizes on nRF5340 2024-09-02 12:30:06 -04:00
overlay-le-audio.conf Bluetooth: BAP: Add bondable requirement for BAP 2024-09-19 18:27:53 +01:00
overlay-mesh.conf Bluetooth: Tester: Mesh: Added support for Bridge client/server 2024-09-17 05:22:32 -04:00
prj.conf
rd_rw612_bga.overlay
testcase.yaml tests/bluetooth: Don't test on native_posix 2024-09-25 04:04:36 -04: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.