michaelh/zephyr
1
0
Fork 0
Code Releases Activity

arm: V2M Musca-S1: Update board's index.rst file

Browse source 
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:
David Vincze 2020-12-17 18:02:26 +01:00 • committed by Anas Nashif
commit ec923274b6
1 changed files with 18 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

29
boards/arm/v2m_musca_s1/doc/index.rst
View file

@ -319,17 +319,21 @@ Open a serial terminal (minicom, putty, etc.) with the following settings:
Uploading an application to V2M Musca-S1 Uploading an application to V2M Musca-S1
---------------------------------------- ----------------------------------------
To upload the :ref:`hello_world` application to the board no extra steps are 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 required. You can directly upload ``build/zephyr/zephyr.hex``, which is
artefact. However, in general the applications must be converted to Intel's hex 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 format before being flashed to a V2M Musca-S1. An optional bootloader can also
be prepended to the image. 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). bootloader partition size (when there is one).
A third-party tool (srecord) can be used to concatenate the images and generate A third-party tool (srecord) can be used to concatenate the images and generate
the Intel formatted hex image. the Intel formatted hex image.
For more information refer to the `Srecord Manual`_. For more information refer to the `Srecord Manual`_.
.. code-block:: bash .. code-block:: bash
@ -392,13 +396,16 @@ description are met before building.
:board: v2m_musca_s1_nonsecure :board: v2m_musca_s1_nonsecure
:goals: build :goals: build
To upload the build artefact to the board first connect the Musca-S1 to your To upload the build artifact 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`` computer using the USB port, press the PBON button, and copy
file onto the newly appeared MUSCA_S mass storage device (for a more detailed the ``build/tfm_zephyr.hex`` file onto the MUSCA_S mass storage device.
description of these steps, please read the 'Uploading an application (For a more detailed description of these steps, please read the 'Uploading
to V2M Musca-S1' section). Once it is done, you may reset the board. 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 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. These steps are all performed automatically by CMake.
For alternative build options and more information, please read the For alternative build options and more information, please read the