boards: lpcxpresso55s69: update docs with dualcore
Updates lpcxpresso55s69 board's documentation with mailbox and multicore
setups. Explain how _cpu1 and _ns targets are used.
Also fixes TFM related documentation.
Signed-off-by: Andrei Gansari <andrei.gansari@nxp.com>
Other hardware features are not currently enabled such as dual core or secure/non-secure.
Targets available for this board are:
CPU0 is the only target that can run standalone.
- *lpcxpresso55s69_cpu0* secure (S) address space for CPU0
- *lpcxpresso55s69_ns* non-secure (NS) address space for CPU0
- *lpcxpresso55s69_cpu1* CPU1 target, NS only
- *lpcxpresso55s69_cpu1* CPU1 target, no security extensions
CPU0 is the only target that can run standalone.
NS target for CPU0 does not work correctly without a secure image enabling it.
To enable it, run any of the ``tfm_integration`` samples.
CPU1 does not work without CPU0 enabling it.
To enable it, run one of the following samples in ``subsys\ipc``:
- ``ipm_mcux``
- ``openamp``
Connections and IOs
===================
@ -214,6 +220,23 @@ J-Link as follows (reset and erase are for recovering a locked core):
@@ -214,6 +220,23 @@ J-Link as follows (reset and erase are for recovering a locked core):
We need to reset the board manually after flashing the image to run this code.
Building a dual-core image
--------------------------
The dual-core samples are run using ``lpcxpresso55s69_cpu0`` target,
``lpcxpresso55s69_cpu1`` will be automatically built and merged in a single
image when ``SECOND_CORE_MCUX`` is selected.
To run we need to manually flash the resulting image (``multicore.bin``) with a
J-Link as follows (reset and erase are for recovering a locked core):