arm: V2M Musca-S1: Update board's index.rst file
Change-Id: I211817620db2130ffb275a5962a24bf90aad57e9 Co-authored-by: Kevin Townsend <kevin@ktownsend.com> Signed-off-by: David Vincze <david.vincze@linaro.org>
This commit is contained in:
parent
79cac4e58d
commit
ec923274b6
|
@ -319,17 +319,21 @@ Open a serial terminal (minicom, putty, etc.) with the following settings:
|
|||
Uploading an application to V2M Musca-S1
|
||||
----------------------------------------
|
||||
|
||||
To upload the :ref:`hello_world` application to the board no extra steps are
|
||||
required, you can upload directly the ``build/zephyr/zephyr.hex`` build
|
||||
artefact. However, in general the applications must be converted to Intel's hex
|
||||
To upload the :ref:`hello_world` application to the board, no extra steps are
|
||||
required. You can directly upload ``build/zephyr/zephyr.hex``, which is
|
||||
generated by Zephyr's build system.
|
||||
|
||||
In other situations, applications must first be converted to Intel's hex
|
||||
format before being flashed to a V2M Musca-S1. An optional bootloader can also
|
||||
be prepended to the image.
|
||||
The eMRAM base address alias is 0xA000000, and the QSPI flash base address alias
|
||||
is 0x0. The image offset is calculated by adding the flash offset to the
|
||||
|
||||
The eMRAM base address alias is ``0xA000000``, and the QSPI flash base address
|
||||
alias is ``0x0``. The image offset is calculated by adding the flash offset to the
|
||||
bootloader partition size (when there is one).
|
||||
|
||||
A third-party tool (srecord) can be used to concatenate the images and generate
|
||||
the Intel formatted hex image.
|
||||
|
||||
For more information refer to the `Srecord Manual`_.
|
||||
|
||||
.. code-block:: bash
|
||||
|
@ -392,13 +396,16 @@ description are met before building.
|
|||
:board: v2m_musca_s1_nonsecure
|
||||
:goals: build
|
||||
|
||||
To upload the build artefact to the board first connect the Musca-S1 to your
|
||||
computer using the USB port, power it on and copy the ``build/tfm_zephyr.hex``
|
||||
file onto the newly appeared MUSCA_S mass storage device (for a more detailed
|
||||
description of these steps, please read the 'Uploading an application
|
||||
to V2M Musca-S1' section). Once it is done, you may reset the board.
|
||||
To upload the build artifact to the board, first connect the Musca-S1 to your
|
||||
computer using the USB port, press the PBON button, and copy
|
||||
the ``build/tfm_zephyr.hex`` file onto the MUSCA_S mass storage device.
|
||||
(For a more detailed description of these steps, please read the 'Uploading
|
||||
an application to V2M Musca-S1' section.)
|
||||
|
||||
Once the file transfer has completed, you may reset the board.
|
||||
|
||||
The ``tfm_zephyr.hex`` file was generated by concatenating the signed TF-M and
|
||||
Zephyr binaries with the MCUboot image and converting it to Intel's hex format.
|
||||
Zephyr binaries with the MCUboot image, and converting it to Intel's hex format.
|
||||
These steps are all performed automatically by CMake.
|
||||
|
||||
For alternative build options and more information, please read the
|
||||
|
|
Loading…
Reference in a new issue