michaelh/zephyr
1
0
Fork 0
Code Releases Activity

docs: bluetooth: Replace reference to native_posix w native_sim

Browse source 
Let's replace the references to native_posix with native_sim,

Background: during this release native_sim is replacing
native_posix as the main host test/development platform.

Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
This commit is contained in:
Alberto Escolar Piedras 2023-11-10 10:48:15 +01:00 • committed by Johan Hedberg
commit d427169845
6 changed files with 34 additions and 34 deletions
Download patch file Download diff file Expand all files Collapse all files

4
samples/bluetooth/bluetooth.rst
View file

@ -6,13 +6,13 @@ Bluetooth samples
To build any of the Bluetooth samples, follow the same steps as building
any other Zephyr application. Refer to :ref:`bluetooth-dev` for more information.
Many Bluetooth samples can be run on QEMU or Native POSIX with support for
Many Bluetooth samples can be run on QEMU or :ref:`native_sim <native_sim>` with support for
external Bluetooth Controllers. Refer to the :ref:`bluetooth-hw-setup` section
for further details.
Several of the bluetooth samples will build a Zephyr-based Controller that can
then be used with any external Host (including Zephyr running natively or with
QEMU or Native POSIX), those are named accordingly with an "HCI" prefix in the
QEMU or ``native_sim``), those are named accordingly with an "HCI" prefix in the
documentation and are prefixed with :literal:`hci_` in their folder names.
.. note::

8
samples/bluetooth/hci_uart/README.rst
View file

@ -55,10 +55,10 @@ For example, to build for the nRF52832 Development Kit:
.. _bluetooth-hci-uart-qemu-posix:
Using the controller with QEMU and Native POSIX
===============================================
Using the controller with QEMU or native_sim
============================================
In order to use the HCI UART controller with QEMU or Native POSIX you will need
In order to use the HCI UART controller with QEMU or :ref:`native_sim <native_sim>` you will need
to attach it to the Linux Host first. To do so simply build the sample and
connect the UART to the Linux machine, and then attach it with this command:
@ -84,7 +84,7 @@ If you are running :file:`btmon` you should see a brief log showing how the
Linux kernel identifies the attached controller.
Once the controller is attached follow the instructions in the
:ref:`bluetooth_qemu_posix` section to use QEMU with it.
:ref:`bluetooth_qemu_native` section to use QEMU with it.
.. _bluetooth-hci-uart-bluez:

8
samples/bluetooth/hci_uart_async/README.rst
View file

@ -52,10 +52,10 @@ For example, to build for the nRF52832 Development Kit:
.. _bluetooth-hci-uart-async-qemu-posix:
Using the controller with QEMU and Native POSIX
===============================================
Using the controller with QEMU or native_sim
============================================
In order to use the HCI UART controller with QEMU or Native POSIX you will need
In order to use the HCI UART controller with QEMU or :ref:`native_sim <native_sim>` you will need
to attach it to the Linux Host first. To do so simply build the sample and
connect the UART to the Linux machine, and then attach it with this command:
@ -77,7 +77,7 @@ If you are running :file:`btmon` you should see a brief log showing how the
Linux kernel identifies the attached controller.
Once the controller is attached follow the instructions in the
:ref:`bluetooth_qemu_posix` section to use QEMU with it.
:ref:`bluetooth_qemu_native` section to use QEMU with it.
.. _bluetooth-hci-uart-async-bluez: