Skip to content

Commit cf315e7

Browse files
aescolarhenrikbrixandersen
authored andcommitted
doc: Bluetooth dev: Fix mention of nrf52 not supporting split builds
Since #67318 we support split builds in the simulated nRF52 over the UART, and we actually have this configuration tested in CI. This documentation paragraph was still mentioning this is not supported. So let's fix it. Signed-off-by: Alberto Escolar Piedras <[email protected]>
1 parent 686a8c9 commit cf315e7

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/connectivity/bluetooth/bluetooth-dev.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -158,10 +158,10 @@ executable.
158158
You can find more information on how to run simulations with one or several
159159
devices in either of :ref:`these boards's documentation <nrf52bsim_build_and_run>`.
160160

161-
With the :ref:`nrf52_bsim <nrf52_bsim>`, only :ref:`Combined builds
162-
<bluetooth-build-types>` are possible, as this board does not yet have
163-
any models of a UART, or USB which could be used for an HCI interface towards
164-
another real or simulated device.
161+
With the :ref:`nrf52_bsim <nrf52_bsim>`, typically you do :ref:`Combined builds
162+
<bluetooth-build-types>`, but it is also possible to build the controller with one of the
163+
:ref:`HCI UART <bluetooth-hci-uart-sample>` samples in one simulated device, and the host with
164+
the H4 driver instead of the integrated controller in another simulated device.
165165

166166
With the :ref:`nrf5340bsim <nrf5340bsim>`, you can build with either, both controller and host
167167
on its network core, or, with the network core running only the controller, the application

0 commit comments

Comments
 (0)