Commit cf315e77 authored by Alberto Escolar Piedras's avatar Alberto Escolar Piedras Committed by Henrik Brix Andersen
Browse files

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: default avatarAlberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
parent 686a8c9e

doc/connectivity/bluetooth/bluetooth-dev.rst

+4 −4
Original line number Diff line number Diff line
@@ -158,10 +158,10 @@ executable. 
You can find more information on how to run simulations with one or several

devices in either of :ref:`these boards's documentation <nrf52bsim_build_and_run>`.



With the :ref:`nrf52_bsim <nrf52_bsim>`, only :ref:`Combined builds

<bluetooth-build-types>` are possible, as this board does not yet have

any models of a UART, or USB which could be used for an HCI interface towards

another real or simulated device.

With the :ref:`nrf52_bsim <nrf52_bsim>`, typically you do :ref:`Combined builds

<bluetooth-build-types>`, but it is also possible to build the controller with one of the

:ref:`HCI UART <bluetooth-hci-uart-sample>` samples in one simulated device, and the host with

the H4 driver instead of the integrated controller in another simulated device.



With the :ref:`nrf5340bsim <nrf5340bsim>`, you can build with either, both controller and host

on its network core, or, with the network core running only the controller, the application

CRA Git | Maintained and supported by SUSTech CRA and CCSE