patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 8 Packages Projects Releases Wiki Activity
zephyr/samples/drivers/mbox
History
Alberto Escolar Piedras f3360265e6 tests|samples/bluetooth: Fix sysbuild due to BOAD_IDENTIFIER 
After https://github.com/zephyrproject-rtos/zephyr/pull/70438
got merged simultaneously with
https://github.com/zephyrproject-rtos/zephyr/pull/70564
all these tests stopped building properly due to the
change of avaliable variables in Kconfig & cmake.
Let's fix them.
As a bonus, as for kconfig the BOARD_TARGET_STRING is the
same for the hwmv1 backwards compatible name, let's
just remove the check for the old names.

Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
2024-03-21 18:44:04 +01:00
..
boards samples: Replace nRF54H20 PDK with nRF54H20 DK 2024-03-18 19:11:36 +00:00
remote tests|samples/bluetooth: Fix sysbuild due to BOAD_IDENTIFIER 2024-03-21 18:44:04 +01:00
src drivers: mbox: update MBOX consumers to the new API 2024-03-07 14:32:57 +00:00
CMakeLists.txt tests|samples/bluetooth: Fix sysbuild due to BOAD_IDENTIFIER 2024-03-21 18:44:04 +01:00
Kconfig samples: drivers: mbox: use DT 2024-03-07 14:32:57 +00:00
Kconfig.sysbuild tests|samples/bluetooth: Fix sysbuild due to BOAD_IDENTIFIER 2024-03-21 18:44:04 +01:00
prj.conf sample: mbox: Introduce MBOX NRFX IPC sample 2021-10-27 18:27:21 +02:00
README.rst samples: docs: Correct nrf5340bsim hwmv1 naming to hwmv2 2024-03-21 15:23:56 +01:00
sample.yaml samples|tests/* yamls: Replace all nrf5340bsim hwmv1 names w hwmv2 version 2024-03-21 15:23:56 +01:00
sysbuild.cmake samples: drivers: mbox: fix hwmv2 issues 2024-03-05 16:50:36 +00: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.