Revision as of 11:19, 12 May 2021 by Registered User (→Buttons)
1. Introduction[edit source]
The following paragraphs describe the functional mapping of the LEDs and buttons.
2. Description[edit source]
2.1. LEDs[edit source]
| LED color | Purpose |
|---|---|
| Green |
Can be used at runtime as a LED for Linux examples |
| Red |
Used as a LED to show Cortex-A boot information[1] |
| Blue | U-Boot entering / exit indication then Linux heartbeat LED, which blinks as long as Linux[2] is alive[1] on the Cortex-A |
| Orange | STM32Cube[3] examples verdict LED, on STM32MP15. Free for user on STM32MP13. |
2.2. Buttons[edit source]
| Button label | Purpose |
|---|---|
| WAKE UP | Allows the platform to be woken from any low-power mode[4] |
| USER1 |
Used at boot time by U-Boot to enter USB programming mode with STM32CubeProgrammer. This avoids manipulation of the boot pins when a valid U-Boot image is already present in the board. It can be used at runtime as a button for Linux (STM32MP1x) or STM32Cube (STM32MP15) examples. |
| USER2 |
Used at boot time by U-Boot to enter Android Fastboot mode. |
| TAMPER | Allows to generate an external tamper event. Only present on STM32MP13 board. |
3. On STM32MP13x lines 
[edit source]
You can refer to the respective board-hardware descriptions to determine to which GPIO each function is mapped:
4. On STM32MP15x lines [edit source]
You can refer to the respective board-hardware descriptions to determine to which GPIO each function is mapped:
- STM32MP157x-EV1 - hardware description for the Evaluation boards
- STM32MP157x-DKx - hardware description for the Discovery kits.
5. References[edit source]