blob: 5052691ebfae2a1fe3676ea628356ab8b5717250 [file] [log] [blame]
Gyorgy Szingdb9783c2019-04-17 21:08:48 +02001###########################
2Musca-B1 Platform Specifics
3###########################
4
5****************
6DAPLink Firmware
7****************
Gabor Abonyi4aa39302022-07-14 16:33:13 +02008The code on Musca-B1 is running from embedded flash. Make sure that the DAPLink
Gyorgy Szingdb9783c2019-04-17 21:08:48 +02009FW for eFlash is downloaded to the board. You can find on the
Gabor Abonyi4aa39302022-07-14 16:33:13 +020010`Arm Community page <https://community.arm.com/oss-platforms/w/docs/552/musca-b1-firmware-update-qspi-eflash-boot-recovery>`__
Gyorgy Szingdb9783c2019-04-17 21:08:48 +020011A short description of how to update the DAPLink FW can be found there as well.
12
Minos Galanakisfc6804e2020-03-10 11:03:34 +000013.. Note::
14 Warm reset of eFlash is not supported on Musca_B1. TF-M may not boot after
15 a warm reset. Further information on the hardware limitation can be
Gabor Abonyi4aa39302022-07-14 16:33:13 +020016 found on `Arm Community page <https://community.arm.com/oss-platforms/w/docs/566/musca-b1-warm-reset-of-eflash>`__.
Minos Galanakisfc6804e2020-03-10 11:03:34 +000017
Miklos Balintc7b1b6c2019-04-24 12:38:36 +020018********************
19Platform pin service
20********************
21
22This service is designed to perform secure pin services of the platform
23(e.g alternate function setting, pin mode setting, etc).
24The service uses the IOCTL API of TF-M's Platform Service, which allows the
25non-secure application to make pin service requests on Musca B1 based on a
26generic service request delivery mechanism.
27
Gyorgy Szingdb9783c2019-04-17 21:08:48 +020028--------------
29
Gabor Abonyi4aa39302022-07-14 16:33:13 +020030*Copyright (c) 2017-2022, Arm Limited. All rights reserved.*