michaelh/zephyr
1
0
Fork 0
Code Releases Activity

docs: Networking with native_posix: Rename

Browse source 
Rename
Networking with native_posix
to
Networking with native_sim
replace all links to this page accordingly
and replace its 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 11:54:11 +01:00 • committed by Carles Cufí
commit e44c43cc2c
5 changed files with 20 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

24
doc/connectivity/networking/native_posix_setup.rst → doc/connectivity/networking/native_sim_setup.rst
View file

@ -1,18 +1,18 @@
.. _networking_with_native_posix:
.. _networking_with_native_sim:
Networking with native_posix board
##################################
Networking with native_sim board
################################
.. contents::
:local:
:depth: 2
This page describes how to set up a virtual network between a (Linux) host
and a Zephyr application running in a native_posix board.
and a Zephyr application running in a :ref:`native_sim <native_sim>` board.
In this example, the :zephyr:code-sample:`sockets-echo-server` sample application from
the Zephyr source distribution is run in native_posix board. The Zephyr
native_posix board instance is connected to a Linux host using a tuntap device
the Zephyr source distribution is run in native_sim board. The Zephyr
native_sim board instance is connected to a Linux host using a tuntap device
which is modeled in Linux as an Ethernet network interface.
Prerequisites
@ -35,13 +35,13 @@ For the steps below, you will need three terminal windows:
directory (``cd net-tools``)
* Terminal #2 is your usual Zephyr development terminal,
with the Zephyr environment initialized.
* Terminal #3 is the console to the running Zephyr native_posix
* Terminal #3 is the console to the running Zephyr native_sim
instance (optional).
Step 1 - Create Ethernet interface
==================================
Before starting native_posix with network emulation, a network interface
Before starting native_sim with network emulation, a network interface
should be created.
In terminal #1, type:
@ -58,8 +58,8 @@ by running ``net-setup.sh`` like this:
./net-setup.sh --help
Step 2 - Start app in native_posix board
========================================
Step 2 - Start app in native_sim board
======================================
Build and start the ``echo_server`` sample application.
@ -68,7 +68,7 @@ In terminal #2, type:
.. zephyr-app-commands::
:zephyr-app: samples/net/sockets/echo_server
:host-os: unix
:board: native_posix
:board: native_sim
:goals: run
:compact:
@ -78,7 +78,7 @@ Step 3 - Connect to console (optional)
The console window should be launched automatically when the Zephyr instance is
started but if it does not show up, you can manually connect to the console.
The native_posix board will print a string like this when it starts:
The native_sim board will print a string like this when it starts:
.. code-block:: console

4
doc/connectivity/networking/networking_with_host.rst
View file

@ -7,7 +7,7 @@ Networking with the host system
:maxdepth: 1
:hidden:
native_posix_setup.rst
native_sim_setup.rst
qemu_eth_setup.rst
qemu_setup.rst
usbnet_setup.rst
@ -60,7 +60,7 @@ possible:
can attach host debugger directly to the running Zephyr instance. This
requires that there is an adaptation driver in Zephyr for interfacing
with the host system. An Ethernet driver exists in Zephyr for this purpose.
See :ref:`networking_with_native_posix` for details.
See :ref:`networking_with_native_sim` for details.
* USB device networking.

4
samples/net/gptp/README.rst
View file

@ -19,13 +19,13 @@ Requirements
************
For generic host connectivity, that can be used for debugging purposes, see
:ref:`networking_with_native_posix` for details.
:ref:`networking_with_native_sim` for details.
Building and Running
********************
A good way to run this sample is to run this gPTP application inside
native_posix board as described in :ref:`networking_with_native_posix` or with
native_posix board as described in :ref:`networking_with_native_sim` or with
embedded device like NXP FRDM-K64F, Nucleo-H743-ZI, Nucleo-H745ZI-Q,
Nucleo-F767ZI or Atmel SAM-E70 Xplained. Note that gPTP is only supported for
boards that have an Ethernet port and which has support for collecting

4
samples/net/lwm2m_client/README.rst
View file

@ -25,7 +25,7 @@ The source code for this sample application can be found at:
Requirements
************
- :ref:`networking_with_eth_qemu`, :ref:`networking_with_qemu` or :ref:`networking_with_native_posix`
- :ref:`networking_with_eth_qemu`, :ref:`networking_with_qemu` or :ref:`networking_with_native_sim`
- Linux machine
- Leshan Demo Server (https://eclipse.org/leshan/)
@ -69,7 +69,7 @@ Build the lwm2m-client sample application like this:
The easiest way to setup this sample application is to build and run it
as a native_sim application or as a QEMU target using the default configuration :file:`prj.conf`.
This requires a small amount of setup described in :ref:`networking_with_eth_qemu`, :ref:`networking_with_qemu` and :ref:`networking_with_native_posix`.
This requires a small amount of setup described in :ref:`networking_with_eth_qemu`, :ref:`networking_with_qemu` and :ref:`networking_with_native_sim`.
Download and run the latest build of the Leshan Demo Server:

4
samples/net/tftp_client/README.rst
View file

@ -19,7 +19,7 @@ The source code for this sample application can be found at:
Requirements
************
- :ref:`networking_with_eth_qemu`, :ref:`networking_with_qemu` or :ref:`networking_with_native_posix`
- :ref:`networking_with_eth_qemu`, :ref:`networking_with_qemu` or :ref:`networking_with_native_sim`
- Linux machine
Building and Running
@ -42,7 +42,7 @@ Build the tftp-client sample application like this:
The easiest way to setup this sample application is to build and run it
as a native_sim application or as a QEMU target using the default configuration :file:`prj.conf`.
This requires a small amount of setup described in :ref:`networking_with_eth_qemu`, :ref:`networking_with_qemu` and :ref:`networking_with_native_posix`.
This requires a small amount of setup described in :ref:`networking_with_eth_qemu`, :ref:`networking_with_qemu` and :ref:`networking_with_native_sim`.
Build the tftp-client sample application for :ref:`native_sim <native_sim>` like this: