zephyr/tests/bluetooth/tester
Pavel Vasilyev 981c79b7ce Bluetooth: Mesh: Drop explicit support for Bluetooth Mesh 1.0.1
Bluetooth Mesh Protocol 1.1 is backward compatible with Bluetooth Mesh
Profile 1.0.1, therefore the stack can still be qualified for 1.0.1 if
needed. But explicit support for both versions requires additional
maintenance efforts and doubles the CI time. To make the stack
qualifiable for 1.0.1, the one needs to remove Private Beacons reception
and compile out SHA256 algorithm support.

What is changed:
- Removed `CONFIG_BT_MESH_V1d1` option.
- Removed `transport_legacy.c` which was using 1.0.1 implementation. The
  new transport layer has new SaR logic that should still be possible to
  qualify for 1.0.1.
- Removed the legacy transport Kconfig options. They are superseded by
  the new transport Kconfig options.
- Tester app: `overlay-mesh-v1d1.conf` is merged into
  `overlay-mesh.conf`.
- Removed BabbleSim tests for 1.0.1.
- Updated documentation.

Signed-off-by: Pavel Vasilyev <pavel.vasilyev@nordicsemi.no>
2024-01-19 12:55:40 +01:00
..
boards tests/bluetooth/tester: Enable in native_sim 2023-11-14 09:52:34 +02:00
src bluetooth: tester: Add CCP Tests 2024-01-05 14:41:52 -05:00
CMakeLists.txt tests: Bluetooth: tester: Add initial support for HAP 2024-01-02 10:10:15 +01:00
Kconfig bluetooth: tester: Add CONFIG_BTTESTER_LOG_LEVEL 2023-04-12 13:05:32 +02:00
nrf5340_hci_ipc.conf bluetooth: Rename rpmsg HCI driver and sample to ipc 2023-11-02 08:32:20 +02:00
nrf5340_hci_ipc_cpunet.conf bluetooth: Rename rpmsg HCI driver and sample to ipc 2023-11-02 08:32:20 +02:00
overlay-le-audio.conf bluetooth: tester: Add CCP Tests 2024-01-05 14:41:52 -05:00
overlay-mesh.conf Bluetooth: Mesh: Drop explicit support for Bluetooth Mesh 1.0.1 2024-01-19 12:55:40 +01:00
prj.conf bluetooth: tester: Enable Periodic Advertising support 2023-12-11 09:50:48 +01:00
README tests: bluetooth: tester: reference autoPTS in README 2021-10-25 08:02:58 -04:00
testcase.yaml Bluetooth: Mesh: Drop explicit support for Bluetooth Mesh 1.0.1 2024-01-19 12:55:40 +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.