zephyr/tests/bluetooth/tester
Donatien Garnier 185a6117c0 Bluetooth: Host: Amend existing L2CAP accept callbacks
This patch amends the existing L2CAP accept callbacks to use the new
accept signature that includes a pointer to the L2CAP server structure.

Signed-off-by: Donatien Garnier <donatien.garnier@blecon.net>
2023-09-14 14:36:34 +02:00
..
boards tests: Bluetooth: tester: Move DT overlays to boards directory 2023-08-23 14:44:48 +02:00
src Bluetooth: Host: Amend existing L2CAP accept callbacks 2023-09-14 14:36:34 +02:00
CMakeLists.txt bluetooth: tester: MICP Client tests 2023-09-08 14:43:00 +02:00
Kconfig bluetooth: tester: Add CONFIG_BTTESTER_LOG_LEVEL 2023-04-12 13:05:32 +02:00
nrf5340_hci_rpmsg_cpunet.conf bluetooth: tester: bap: Add support for BAP/USR tests 2023-08-16 14:48:11 +02:00
nrf5340_hci_rpmsg.conf tests: bluetooth: tester: Reduce nrf53 BT_BUF_ACL_RX_SIZE 2023-06-28 06:49:07 +00:00
overlay-le-audio.conf bluetooth: tester: MICP Client tests 2023-09-08 14:43:00 +02:00
overlay-mesh.conf Tests: Bluetooth: tester: add BTP command for connecting Proxy Client 2023-06-26 16:16:01 +02:00
prj.conf bluetooth: tester: Bump supported GATT Prepare Writes to 12 2023-05-16 18:19:50 +02:00
README
testcase.yaml tests: Bluetooth: tester: Change mesh nrf board to nrf52840dk_nrf52840 2023-09-01 15:09:07 +02: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.