3e634268d6
The bt_iso_chan_send function could take an optional timestamp by using 0 as an indicator. The issue with this approach was that a timestamp value of 0 is valid, and could cause potential issue with syncing streams in a group. To fully support transmitting with and without timestamp, bt_iso_chan_send_ts has been introduced, which is the only function of the two (bt_iso_chan_send being the other) that supports timestamps. A new function, rather than adding a boolean to the existing, was chosen as it simplifies the individual functions as well as making it more explicit what the function does. Since the bt_iso_chan_send function is used by LE audio, both the BAP and CAP send functions have similarly been updated. Likewise, all tests and samples have been updated to use the updated function(s), and BT_ISO_TIMESTAMP_NONE has been removed. 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.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.