patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 8 Packages Projects Releases Wiki Activity

samples zbus: Swap native_posix with native_sim

Browse source 
In the docs replace references to native_posix with native_sim
Switch the default test platform to native_sim from native_posix

Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
This commit is contained in:
Alberto Escolar Piedras 2023-11-16 09:35:01 +01:00 committed by Carles Cufí
parent 196ceaf2f4
commit bf466da69f
3 changed files with 15 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
samples/subsys/zbus/remote_mock/README.rst
View file

@ -16,12 +16,12 @@ Building and Running
********************
This project outputs to the console. It can be built and executed
on native_posix as follows:
on :ref:`native_sim <native_sim>` as follows:
.. zephyr-app-commands::
:zephyr-app: samples/subsys/zbus/remote_mock
:host-os: unix
:board: native_posix
:board: native_sim
:goals: run
Sample Output
@ -63,7 +63,11 @@ The :file:`remote_mock.py` script can be executed using the following command:
python3.8 samples/subsys/zbus/remote_mock/remote_mock.py /dev/pts/2
Note the run command above prints the value of pts port because it is running in ``native_posix``. Look at the line indicating ``uart_1 connected to pseudotty: /dev/pts/2``. It can be different in your case. If you are using a board, read the documentation to get the correct port destination (in Linux is something like ``/dev/tty...`` or in Windows ``COM...``).
Note the run command above prints the value of pts port because it is running in
:ref:`native_sim <native_sim>`.
Look at the line indicating ``uart_1 connected to pseudotty: /dev/pts/2``.
It can be different in your case. If you are using a board, read the documentation to get the
correct port destination (in Linux is something like ``/dev/tty...`` or in Windows ``COM...``).
From the remote mock (Python script), you would see something like this:

2
samples/subsys/zbus/remote_mock/sample.yaml
View file

@ -9,4 +9,4 @@ tests:
- native_sim
- hifive1_revb
integration_platforms:
- native_posix
- native_sim

10
samples/subsys/zbus/uart_bridge/README.rst
View file

@ -14,12 +14,12 @@ Building and Running
********************
This project outputs to the console. It can be built and executed
on native_posix as follows:
on native_sim as follows:
.. zephyr-app-commands::
:zephyr-app: samples/subsys/zbus/uart_bridge
:host-os: unix
:board: native_posix
:board: native_sim
:goals: run
Sample Output
@ -68,7 +68,11 @@ The :file:`decoder.py` script can be executed using the following command:
python3.8 samples/subsys/zbus/uart_bridge/decoder.py /dev/pts/2
Note the run command above prints the value of pts port because it is running in ``native_posix``. Look at the line indicating ``uart_1 connected to pseudotty: /dev/pts/2``. It can be different in your case. If you are using a board, read the documentation to get the correct port destination (in Linux is something like ``/dev/tty...`` or in Windows ``COM...``).
Note the run command above prints the value of pts port because it is running in
:ref:`native_sim <native_sim>`.
Look at the line indicating ``uart_1 connected to pseudotty: /dev/pts/2``.
It can be different in your case. If you are using a board, read the documentation to get the
correct port destination (in Linux is something like ``/dev/tty...`` or in Windows ``COM...``).
From the serial decoder (Python script), you would see something like this: