zephyr

History

Jiawei Yang ff112b5e05 tests: Bluetooth: BR: Add test suite RFCOMM_client IUT works as an RFCOMM Client. The peer device, RFCOMM server, is a PC running bumble. Add following test cases: Case 6, RFCOMM MTU Size Data Send/Receive Test. To verify that the RFCOMM client can correctly send and receive data packets that are exactly equal to the negotiated MTU size. Case 7, RFCOMM Data Transfer Exceeding MTU Size Test. To verify that the RFCOMM client can reject sending and receiving data packets that exceed the negotiated MTU size. Case 8, RFCOMM Disconnect and Reconnect Test. To verify that the RFCOMM client can properly handle a normal RFCOMM disconnection and successfully reestablish the connection. Case 9, RFCOMM Recovery After ACL Disconnection Test. To verify that the RFCOMM client can properly recover when the underlying ACL connection is abruptly disconnected, by reestablishing both ACL and RFCOMM connections. Signed-off-by: Jiawei Yang <jiawei.yang_1@nxp.com>		2025-07-10 10:12:20 -05:00
..
boards
pytest
src
CMakeLists.txt
prj.conf
README.rst
testcase.yaml

README.rst

.. _bluetooth_classic_rfcomm_client_tests:

Bluetooth Classic rfcomm client 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/rfcomm_c -O rfcomm_c --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/rfcomm_c -O rfcomm_c --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