c1baa8282d
The purpose of this test is to prove that the zephyr host can handle the behavior described in the Bluetooth Core Specification Vol.3 Part.F 3.3.2 "Sequential protocol". The host should be able to handle all of those in parallel: one indication, one write request, multiple commands and multiple notifications. The "tester" part had to be written with a "tiny host" implementation instead of the Zephyr host, as the ZH conflates GATT client and server and doesn't allow a device to enqueue an ATT request + an ATT indication on the same bearer. Signed-off-by: Jonathan Rico <jonathan.rico@nordicsemi.no>
42 lines
981 B
Plaintext
42 lines
981 B
Plaintext
CONFIG_LOG=y
|
|
CONFIG_ASSERT=y
|
|
|
|
CONFIG_BT=y
|
|
CONFIG_BT_CENTRAL=y
|
|
CONFIG_BT_PERIPHERAL=y
|
|
CONFIG_BT_DEVICE_NAME="Sequential"
|
|
|
|
CONFIG_BT_GATT_CLIENT=y
|
|
CONFIG_BT_GATT_ENFORCE_SUBSCRIPTION=n
|
|
|
|
# Enable bt_testing_tx_tid_get()
|
|
CONFIG_BT_TESTING=y
|
|
|
|
# Replace `Execute` with `gdb --args` in the shell script
|
|
# and get a nice backtrace on assert
|
|
CONFIG_ARCH_POSIX_TRAP_ON_FATAL=y
|
|
|
|
# Prepend logs with thread names
|
|
CONFIG_THREAD_NAME=y
|
|
CONFIG_LOG_THREAD_ID_PREFIX=y
|
|
|
|
# Enable those as needed
|
|
# CONFIG_BT_L2CAP_LOG_LEVEL_DBG=y
|
|
# CONFIG_BT_ATT_LOG_LEVEL_DBG=y
|
|
# CONFIG_BT_GATT_LOG_LEVEL_DBG=y
|
|
|
|
# Allow whole L2CAP PDUs to fit on-air
|
|
CONFIG_BT_BUF_ACL_TX_SIZE=251
|
|
CONFIG_BT_BUF_ACL_RX_SIZE=251
|
|
CONFIG_BT_CTLR_DATA_LENGTH_MAX=251
|
|
CONFIG_BT_DATA_LEN_UPDATE=y
|
|
CONFIG_BT_USER_DATA_LEN_UPDATE=y
|
|
|
|
# Disable auto-initiated procedures so they don't
|
|
# mess with the test's execution.
|
|
CONFIG_BT_AUTO_PHY_UPDATE=n
|
|
CONFIG_BT_AUTO_DATA_LEN_UPDATE=n
|
|
CONFIG_BT_GAP_AUTO_UPDATE_CONN_PARAMS=n
|
|
|
|
CONFIG_BT_MAX_CONN=1
|