zephyr/tests/bluetooth/tester
Szymon Janc aa861727e8 bluetooth: tester: Use fixed value for BT_BUF_ACL_RX_SIZE
Default BT_BUF_ACL_RX_SIZE value varies based on selected host options.
Many buffers size (L2CAP COC MPS in particular) depends on that value
and those may affect qualification test cases steps.

To make core tests more predictable just use fixed values big enough to
comply with all configurations requirements.

This was affecting L2CAP/COS/ECFC/BV-04-C.

Signed-off-by: Szymon Janc <szymon.janc@codecoup.pl>
2023-03-31 14:00:48 +02:00
..
boards Bluetooth: Use Zephyr standard log system instead of bluetooth/common/log 2022-11-25 17:08:36 +01:00
src Bluetooth: audio: Expand AICS API 2023-03-31 09:20:15 +02:00
CMakeLists.txt bluetooth: tester: Move core service to separate file 2023-03-08 11:34:43 +01:00
nrf52dk_nrf52832.overlay
nrf5340_hci_rpmsg.conf bluetooth: tester: Add nrf5340_hci_rpmsg.conf file 2023-03-15 15:01:34 +01:00
nrf5340dk_nrf5340_cpuapp.overlay
nrf52840dk_nrf52840.overlay Tests: Bluetooth: Tester: improve stability by Flow Control and UARTE 2023-02-20 09:55:09 +01:00
overlay-le-audio.conf bluetooth: tester: Add MESH and LE Audio overlays 2023-03-27 09:50:09 +02:00
overlay-mesh.conf bluetooth: tester: Add MESH and LE Audio overlays 2023-03-27 09:50:09 +02:00
overlay-native.conf
prj.conf bluetooth: tester: Use fixed value for BT_BUF_ACL_RX_SIZE 2023-03-31 14:00:48 +02:00
README
reel_board.overlay
testcase.yaml

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.