Bluetooth Mesh Protocol 1.1 is backward compatible with Bluetooth Mesh Profile 1.0.1, therefore the stack can still be qualified for 1.0.1 if needed. But explicit support for both versions requires additional maintenance efforts and doubles the CI time. To make the stack qualifiable for 1.0.1, the one needs to remove Private Beacons reception and compile out SHA256 algorithm support. What is changed: - Removed `CONFIG_BT_MESH_V1d1` option. - Removed `transport_legacy.c` which was using 1.0.1 implementation. The new transport layer has new SaR logic that should still be possible to qualify for 1.0.1. - Removed the legacy transport Kconfig options. They are superseded by the new transport Kconfig options. - Tester app: `overlay-mesh-v1d1.conf` is merged into `overlay-mesh.conf`. - Removed BabbleSim tests for 1.0.1. - Updated documentation. Signed-off-by: Pavel Vasilyev <pavel.vasilyev@nordicsemi.no>
22 lines
663 B
Bash
Executable File
22 lines
663 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# Copyright 2023 Nordic Semiconductor
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
source $(dirname "${BASH_SOURCE[0]}")/../../_mesh_test.sh
|
|
|
|
# Test Beacon cache
|
|
#
|
|
# Test procedure:
|
|
# 0. RX device starts monitoring all accepted SNB messages.
|
|
# 1. TX device sends two identical SNBs to the RX device.
|
|
# 2. TX device sends a secondary SNBs to the RX device, marking the end of the test.
|
|
# 3. RX device verifies that only one of the two identical beacons was processed.
|
|
RunTest mesh_beacon_cache \
|
|
beacon_tx_beacon_cache \
|
|
beacon_rx_beacon_cache
|
|
|
|
overlay=overlay_psa_conf
|
|
RunTest mesh_beacon_cache \
|
|
beacon_tx_beacon_cache \
|
|
beacon_rx_beacon_cache
|