| Gabor Abonyi | f371d27 | 2022-07-19 13:54:05 +0200 | [diff] [blame^] | 1 | ########################### |
| 2 | Musca-S1 Platform Specifics |
| 3 | ########################### |
| 4 | |
| 5 | **************** |
| 6 | DAPLink Firmware |
| 7 | **************** |
| 8 | The code on Musca-S1 is running from embedded flash. Make sure that the DAPLink |
| 9 | FW for QSPI/MRAM is downloaded to the board. You can find on the |
| 10 | `Arm Community page <https://community.arm.com/oss-platforms/w/docs/463/musca-s1-firmware-update-qspi-mram-boot-recovery>`__ |
| 11 | A short description of how to update the DAPLink FW can be found there as well. |
| 12 | |
| 13 | ******************** |
| 14 | Platform pin service |
| 15 | ******************** |
| 16 | |
| 17 | This service is designed to perform secure pin services of the platform |
| 18 | (e.g alternate function setting, pin mode setting, etc). |
| 19 | The service uses the IOCTL API of TF-M's Platform Service, which allows the |
| 20 | non-secure application to make pin service requests on Musca S1 based on a |
| 21 | generic service request delivery mechanism. |
| 22 | |
| 23 | -------------- |
| 24 | |
| 25 | *Copyright (c) 2022, Arm Limited. All rights reserved.* |