981c79b7ce
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>
21 lines
798 B
Bash
Executable File
21 lines
798 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 that an Opcode aggregated message can be sent and received on loopback.
|
|
#
|
|
# Test procedure:
|
|
# 1. The device initializes both Opcode aggregator server and client.
|
|
# The device starts an Opcode aggregator sequence and populates the buffer.
|
|
# 2. The device starts sending the sequence on loopback.
|
|
# 3. The device verifies that the sequence is correctly received by the server model.
|
|
# 4. The device confirms that the client model received all status messages.
|
|
RunTest mesh_op_agg_model_coex_loopback \
|
|
op_agg_dut_model_coex_loopback
|
|
|
|
overlay=overlay_psa_conf
|
|
RunTest mesh_op_agg_model_coex_loopback \
|
|
op_agg_dut_model_coex_loopback
|