zephyr

History

Alberto Escolar Piedras 72502938b3 samples/drivers/mbox: Fix test regex In `9d7ee123a5` the regex used to verify the sample is doing what it should was changed in a way in which it cannot possibly pass. Let's fix it. While at it, in the same commit, the simulator version of the test was merged with the real_hw version, but the test name kept "real_hw" which is now missleading => let's fix it. And let's set as integration platform the simulated target, so it can actually be runtime tested in CI. Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>		2025-03-22 02:41:05 +01:00
..
boards	samples: fix spelling of "below"	2025-02-19 18:51:13 +01:00
remote	samples: fix spelling of "below"	2025-02-19 18:51:13 +01:00
src
sysbuild
CMakeLists.txt	samples: enable multicore samples for RT1180 board	2025-02-14 17:11:50 +01:00
Kconfig
Kconfig.sysbuild	samples: enable multicore samples for RT1180 board	2025-02-14 17:11:50 +01:00
prj.conf
README.rst
sample.yaml	samples/drivers/mbox: Fix test regex	2025-03-22 02:41:05 +01:00
sysbuild.cmake	samples: enable multicore samples for RT1180 board	2025-02-14 17:11:50 +01:00

README.rst

.. zephyr:code-sample:: mbox
   :name: MBOX
   :relevant-api: mbox_interface

   Perform inter-processor mailbox communication using the MBOX API.

Overview
********

This sample demonstrates how to use the :ref:`MBOX API <mbox_api>`.

Building and Running
********************

The sample can be built and executed on boards supporting MBOX.

Building the application for nrf5340dk/nrf5340/cpuapp
*****************************************************

.. zephyr-app-commands::
   :zephyr-app: samples/drivers/mbox/
   :board: nrf5340dk/nrf5340/cpuapp
   :goals: debug
   :west-args: --sysbuild

Open a serial terminal (minicom, putty, etc.) and connect the board with the
following settings:

- Speed: 115200
- Data: 8 bits
- Parity: None
- Stop bits: 1

Reset the board and the following message will appear on the corresponding
serial port, one is the application (APP) core another is the network (NET)
core:

.. code-block:: console

   *** Booting Zephyr OS build zephyr-v3.1.0-2383-g147aee22f273  ***
   Hello from APP
   Pong (on channel 0)
   Ping (on channel 1)
   Pong (on channel 0)
   Ping (on channel 1)
   Ping (on channel 1)
   Pong (on channel 0)
   Ping (on channel 1)
   Pong (on channel 0)
   Ping (on channel 1)
   ...


.. code-block:: console

   *** Booting Zephyr OS build zephyr-v3.1.0-2383-g147aee22f273  ***
   Hello from NET
   Ping (on channel 0)
   Pong (on channel 1)
   Ping (on channel 0)
   Pong (on channel 1)


Building the application for the simulated nrf5340bsim
******************************************************

.. zephyr-app-commands::
   :zephyr-app: samples/drivers/mbox/
   :host-os: unix
   :board: nrf5340bsim/nrf5340/cpuapp
   :goals: build
   :west-args: --sysbuild

Then you can execute your application using:

.. code-block:: console

   $ ./build/zephyr/zephyr.exe -nosim
   # Press Ctrl+C to exit

You can expect a similar output as in the real HW in the invoking console.