c9daed9712
This removes the fixed size bt_bap_base, which provides 2 improvements: 1) The RAM usage of the broadcast sink has been reduced. For the Broadcast Sink sample it is a reduction of 120 octets, but with much better scaling for supporting more or larger BASEs. 2) The functions to parse BASEs now support arbitrary sized BASEs, where they were previously restricted by our local Kconfig options. This allow us to parse any BASE from a remote device, without encounting memory issues. We are still memory restricted on the devices we actually want to sync to. Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no> |
||
---|---|---|
.. | ||
boards | ||
src | ||
CMakeLists.txt | ||
Kconfig | ||
nrf5340_hci_ipc.conf | ||
nrf5340_hci_ipc_cpunet.conf | ||
overlay-le-audio.conf | ||
overlay-mesh-v1d1.conf | ||
overlay-mesh.conf | ||
prj.conf | ||
README | ||
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.