tests: Bluetooth: BR: Add general test suite for SMP

IUT works as an SM Initiator/Responder. The peer device,
SM Responder/Initiator, is a PC running bumble on it.

Add shell commands to create and manage L2CAP server and channel with
different security level, reboot the board, and transfer data on the
SDP channel.

In the test suite, there are 28 test cases to verify SMP functions.
The test case list is:
- BR_SM_INIT_001: Basic Pairing with No Input No Output Capability
- BR_SM_INIT_002: Pairing with Display Only Capability
- BR_SM_INIT_003: Pairing with Keyboard Only Capability
- BR_SM_INIT_005: L2CAP Connection Failure After Successful Pairing
- BR_SM_INIT_006: L2CAP Server with Incoming Connection
- BR_SM_INIT_008: ACL Disconnection During Pairing
- BR_SM_INIT_011: Repeated Pairing Between Same Devices
- BR_SM_INIT_012: Security Level Escalation
- BR_SM_INIT_013: Multiple Channel Establishment
- BR_SM_INIT_017: Pairing Rejection by Remote Device
- BR_SM_INIT_018: Pairing Timeout
- BR_SM_INIT_021: Authentication Failure during Pairing
- BR_SM_INIT_022: Secure Connection vs. Legacy Pairing Fallback
- BR_SM_INIT_025: Rejection of Weak Pairing Methods
- BR_SM_INIT_028: Reconnection After Key Deletion
- BR_SM_INIT_029: Pairing with Delayed Response
- BR_SM_INIT_030: Stress Testing with Multiple Connect/Disconnect Cycles
- BR_SM_INIT_032: Power Loss Recovery
- BR_SM_INIT_034: Pairing During Active Data Transfer
- BR_SM_INIT_035: Pairing with Very Long PIN/Passkey
- BR_SM_INIT_037: Pairing with Peripheral Requesting Maximum Key Size
- BR_SM_INIT_039: Security Level Downgrade Attempt
- BR_SM_RSP_001: Basic Non-bondable Pairing with No Input No Output
- BR_SM_RSP_002: Display Only with Secure Connection
- BR_SM_RSP_003: Keyboard Only with Dedicated Bonding
- BR_SM_RSP_006: Security Level Enforcement
- BR_SM_RSP_008: L2CAP Connection with Security Level 1
- BR_SM_RSP_009: L2CAP Server with Security Level 2

Signed-off-by: Can Wang <can.wang@nxp.com>

Author: CanWang001

tests/bluetooth/classic/smp_general/CMakeLists.txt

@@ -0,0 +1,10 @@
+# SPDX-License-Identifier: Apache-2.0
+
+cmake_minimum_required(VERSION 3.20.0)
+set(NO_QEMU_SERIAL_BT_SERVER 1)
+
+find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
+project(bluetooth)
+
+FILE(GLOB app_sources src/*.c)
+target_sources(app PRIVATE ${app_sources})

tests/bluetooth/classic/smp_general/README.rst

@@ -0,0 +1,74 @@
+.. _bluetooth_classic_smp_general_tests:
+
+Bluetooth Classic SMP General Tests
+##################################
+
+Overview
+********
+
+This test suite uses ``bumble`` for testing Bluetooth Classic communication between a host
+PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
+
+Prerequisites
+*************
+
+The test suite has the following prerequisites:
+
+* The ``bumble`` library installed on the host PC.
+The Bluetooth Classic controller on PC side is required. Refer to getting started of `bumble`_
+for details.
+
+The HCI transport for ``bumble`` can be configured as follows:
+
+* A specific configuration context can be provided along with the ``usb_hci`` fixture separated by
+  a ``:`` (i.e. specify fixture ``usb_hci:usb:0`` to use the ``usb:0`` as hci transport for
+  ``bumble``).
+* The configuration context can be overridden using the `hci transport`_ can be provided using the
+  ``--hci-transport`` test suite argument (i.e. run ``twister`` with the
+  ``--pytest-args=--hci-transport=usb:0`` argument to use the ``usb:0`` as hci transport for
+  ``bumble``).
+
+Building and Running
+********************
+
+Running on mimxrt1170_evk@B/mimxrt1176/cm7
+==========================================
+
+Running the test suite on :ref:`mimxrt1170_evk` relies on configuration of ``bumble``.
+
+On the host PC, a HCI transport needs to be required. Refer to `bumble platforms`_ page of
+``bumble`` for details.
+
+For example, on windows, a PTS dongle is used. After `WinUSB driver`_ has been installed,
+the HCI transport would be USB transport interface ``usb:<index>``.
+
+If the HCI transport is ``usb:0`` and debug console port is ``COM4``, the test suite can be
+launched using Twister:
+
+.. code-block:: shell
+
+   west twister -v -p mimxrt1170_evk@B/mimxrt1176/cm7 --device-testing --device-serial COM4 -T tests/bluetooth/classic/smp_general -O smp_general --force-platform --west-flash --west-runner=jlink -X usb_hci:usb:0
+
+Running on Hardware
+===================
+
+Running the test suite on hardware requires a HCI transport connected to the host PC.
+
+The test suite can be launched using Twister. Below is an example for running on the
+:zephyr:board:`mimxrt1170_evk@B/mimxrt1176/cm7`:
+
+.. code-block:: shell
+
+   west twister -v -p mimxrt1170_evk@B/mimxrt1176/cm7 --device-testing --device-serial COM4 -T tests/bluetooth/classic/smp_general -O smp_general --force-platform --west-flash --west-runner=jlink -X usb_hci:usb:0
+
+.. _bumble:
+   https://google.github.io/bumble/getting_started.html
+
+.. _hci transport:
+   https://google.github.io/bumble/transports/index.html
+
+.. _bumble platforms:
+   https://google.github.io/bumble/platforms/index.html
+
+.. _WinUSB driver:
+   https://google.github.io/bumble/platforms/windows.html

tests/bluetooth/classic/smp_general/boards/mimxrt1170_evk_mimxrt1176_cm7_B.conf

@@ -0,0 +1,4 @@
+#select NXP NW612 Chipset
+CONFIG_BT_NXP_NW612=y
+
+CONFIG_ENTROPY_GENERATOR=y

tests/bluetooth/classic/smp_general/boards/mimxrt1170_evk_mimxrt1176_cm7_B.overlay

@@ -0,0 +1,11 @@
+/*
+ * Copyright 2024 NXP
+ *
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+/ {
+	chosen {
+		zephyr,sram = &dtcm;
+	};
+};

tests/bluetooth/classic/smp_general/prj.conf

@@ -0,0 +1,19 @@
+CONFIG_BT=y
+CONFIG_BT_CLASSIC=y
+CONFIG_BT_SMP=y
+CONFIG_BT_SHELL=y
+CONFIG_LOG=y
+CONFIG_ZTEST=y
+CONFIG_BT_SETTINGS=y
+CONFIG_FLASH=y
+CONFIG_FLASH_MAP=y
+CONFIG_NVS=y
+CONFIG_SETTINGS=y
+CONFIG_BT_BR_MIN_ENC_KEY_SIZE=16
+CONFIG_BT_BUF_ACL_RX_COUNT_EXTRA=10
+CONFIG_REBOOT=y
+
+CONFIG_BT_DEVICE_NAME="smp_general"
+
+CONFIG_BT_CREATE_CONN_TIMEOUT=30
+CONFIG_BT_PAGE_TIMEOUT=0xFFFF

tests/bluetooth/classic/smp_general/pytest/conftest.py

@@ -0,0 +1,87 @@
+# Copyright 2025 NXP
+#
+# SPDX-License-Identifier: Apache-2.0
+
+import contextlib
+import logging
+import re
+import time
+
+import pytest
+from twister_harness import DeviceAdapter, Shell
+
+logger = logging.getLogger(__name__)
+
+
+def pytest_addoption(parser) -> None:
+    """Add local parser options to pytest."""
+    parser.addoption('--hci-transport', default=None, help='Configuration HCI transport for bumble')
+
+
+@pytest.fixture(name='initialize', scope='session')
+def fixture_initialize(request, shell: Shell, dut: DeviceAdapter):
+    """Session initializtion"""
+    # Get HCI transport for bumble
+    hci = request.config.getoption('--hci-transport')
+
+    if hci is None:
+        for fixture in dut.device_config.fixtures:
+            if fixture.startswith('usb_hci:'):
+                hci = fixture.split(sep=':', maxsplit=1)[1]
+                break
+
+    assert hci is not None
+
+    shell.exec_command("bt init")
+    lines = dut.readlines_until("Settings Loaded")
+    regex = r'Identity: *(?P<bd_addr>([0-9A-Fa-f]{2}[:-]){5}([0-9A-Fa-f]{2}) *\((.*?)\))'
+    bd_addr = None
+    for line in lines:
+        logger.info(f"Shell log {line}")
+        m = re.search(regex, line)
+        if m:
+            bd_addr = m.group('bd_addr')
+
+    if bd_addr is None:
+        logger.error('Fail to get IUT BD address')
+        raise AssertionError
+
+    shell.exec_command("br pscan on")
+    shell.exec_command("br iscan on")
+    logger.info('initialized')
+    return hci, bd_addr
+
+
+@pytest.fixture
+def smp_initiator_dut(initialize):
+    logger.info('Start running testcase')
+    yield initialize
+    logger.info('Done')
+
+
+def app_handle_device_output(self) -> None:
+    """
+    This method is dedicated to run it in separate thread to read output
+    from device and put them into internal queue and save to log file.
+    """
+    with open(self.handler_log_path, 'a+') as log_file:
+        while self.is_device_running():
+            if self.is_device_connected():
+                output = self._read_device_output().decode(errors='replace').rstrip("\r\n")
+                if output:
+                    self._device_read_queue.put(output)
+                    logger.debug(f'{output}\n')
+                    try:
+                        log_file.write(f'{output}\n')
+                    except Exception:
+                        contextlib.suppress(Exception)
+                    log_file.flush()
+            else:
+                # ignore output from device
+                self._flush_device_output()
+                time.sleep(0.1)
+
+
+# After reboot, there may be gbk character in the console, so replace _handle_device_output to
+# handle the exception.
+DeviceAdapter._handle_device_output = app_handle_device_output