zephyr/samples/drivers/mbox
Daniel DeGrasse 39ea8ac87a samples: drivers: mbox: remove mimxrt595_evk_cm33
Remove mimxrt595_evk_cm33 from the MBOX sample. Although this SOC has
support for both cores, there is no support in tree for booting the
secondary core from the primary one, so this sample cannot run on
hardware.

Fixes #69092

Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
2024-02-17 14:19:06 +01:00
..
boards samples: drivers: mbox: remove mimxrt595_evk_cm33 2024-02-17 14:19:06 +01:00
remote samples: tests: mbox: Add lpcpresso55s69 support 2024-02-02 09:31:33 -06:00
src
CMakeLists.txt samples: drivers: mbox: remove mimxrt595_evk_cm33 2024-02-17 14:19:06 +01:00
Kconfig samples: mbox: Add support for NXP RT boards 2024-01-16 09:29:28 -06:00
Kconfig.sysbuild samples: drivers: mbox: remove mimxrt595_evk_cm33 2024-02-17 14:19:06 +01:00
prj.conf
README.rst samples/drivers/mbox: Convert to sysbuild and add support for nrf5340bsim 2023-10-26 12:32:53 -05:00
sample.yaml samples: drivers: mbox: remove mimxrt595_evk_cm33 2024-02-17 14:19:06 +01:00
sysbuild.cmake samples: tests: mbox: Add lpcpresso55s69 support 2024-02-02 09:31:33 -06:00

.. 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.