zephyr/tests/bluetooth/tester
Guotao Zhang 28093cc4ef Bluetooth: tester: Increase the adv buf size to consider the extend adv
[Description]
Device hang is observed when LE Scan
[Root Cause]
For le_ext_adv_report, Data[i] of one adv report is 0-229,
for the adv_buf of saving, it just is 73 bytes, so sometimes
the bytes of adv report is more than the adv_buf, resulted hang
[Fix]
consider the le ext adv case.
[Testing]
After modified, Device hang is not observed after stress
testing with LE Scan

Signed-off-by: Guotao Zhang <guotao.zhang@nxp.com>
2024-08-05 16:29:36 +02:00
..
boards Bluetooth: host: Add lower bound for `CONFIG_BT_BUF_ACL_RX_COUNT` 2024-07-10 11:47:26 -04:00
src Bluetooth: tester: Increase the adv buf size to consider the extend adv 2024-08-05 16:29:36 +02:00
CMakeLists.txt tests: Bluetooth: Move audio related BTP files 2024-06-07 22:08:59 -05:00
Kconfig
README
nrf5340_hci_ipc.conf
nrf5340_hci_ipc_cpunet.conf
overlay-le-audio.conf tests: Bluetooth: tester: Re-add support for checksum 2024-07-06 17:02:23 +02:00
overlay-mesh.conf
prj.conf tests: bluetooth: tester: Enable DIS service 2024-08-01 09:13:55 +01:00
rd_rw612_bga.overlay
testcase.yaml samples: tests: bluetooth: Add support for frdm_rw612 2024-06-10 07:02:06 -07: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.