This message will disappear after all relevant tasks have been resolved.
Semantic MediaWiki
There are 1 incomplete or pending task to finish installation of Semantic MediaWiki. An administrator or user with sufficient rights can complete it. This should be done before adding new data to avoid inconsistencies.Registered User mNo edit summary |
Registered User mNo edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
STM32 MPU Evaluation boards and Discovery kits share the same usage for LEDs and buttons. The following paragraphs describe the functional mapping of the LEDs and buttons, so that you can refer to the respective board-hardware descriptions to determine to which GPIO each function is mapped: | STM32 MPU Evaluation boards and Discovery kits share the same usage for LEDs and buttons. The following paragraphs describe the functional mapping of the LEDs and buttons, so that you can refer to the respective board-hardware descriptions to determine to which GPIO each function is mapped: | ||
* [[ | * [[STM32MP157x-EV1_-_hardware_description#User_buttons_and_LEDs|STM32MP157x-EV1 - hardware description]] for the Evaluation boards | ||
* [[ | * [[STM32MP157x-DKx_-_hardware_description#User_buttons_and_LEDs|STM32MP157x-DKx - hardware description]] for the Discovery kits. | ||
== Description == | == Description == | ||
| Line 21: | Line 14: | ||
| This '''button''' allows the platform to be woken from any low-power mode<ref>[[Power overview]]</ref> | | This '''button''' allows the platform to be woken from any low-power mode<ref>[[Power overview]]</ref> | ||
|- | |- | ||
| | | <span style="color: green;">Green</span><br />(*) | ||
| USER1<br />(*) | | USER1<br />(*) | ||
| This can be used at boot time as a '''button''', by [[U-Boot overview|U-Boot]], to enter USB programming mode with [[STM32CubeProgrammer]]. This avoids manipulation of the [[STM32MP15_ROM_code_overview#Boot device selection via the boot pins and OTP|boot pins]] when a valid U-Boot image is already present in the board.<br /> | | This can be used at boot time as a '''button''', by [[U-Boot overview|U-Boot]], to enter USB programming mode with [[STM32CubeProgrammer]]. This avoids manipulation of the [[STM32MP15_ROM_code_overview#Boot device selection via the boot pins and OTP|boot pins]] when a valid U-Boot image is already present in the board.<br /> | ||
| Line 28: | Line 21: | ||
* a '''button''' for STM32Cube examples | * a '''button''' for STM32Cube examples | ||
|- | |- | ||
| | | <span style="color: red;">Red</span><br />(*) | ||
| USER2<br />(*) | | USER2<br />(*) | ||
| This can be used at boot time as a '''button''', by [[U-Boot overview|U-Boot]], to enter [[STM32MPU distribution for Android|Android]] Fastboot mode.<br /> | | This can be used at boot time as a '''button''', by [[U-Boot overview|U-Boot]], to enter [[STM32MPU distribution for Android|Android]] Fastboot mode.<br /> | ||
It is also used as a '''LED''' to show Cortex-A boot information<ref name="boot info">[[How to diagnose a boot failure]]</ref>, then it can be used, at runtime, as a '''button''' for Linux examples. It is not used by STM32Cube.<br /> | It is also used as a '''LED''' to show Cortex-A boot information<ref name="boot info">[[How to diagnose a boot failure]]</ref>, then it can be used, at runtime, as a '''button''' for Linux examples. It is not used by STM32Cube.<br /> | ||
|- | |- | ||
| | | <span style="color: blue;">Blue</span> | ||
| - | | - | ||
| Linux heartbeat '''LED''', which blinks as long as the Linux<ref>[[STM32MP15 Linux kernel overview]]</ref> is alive<ref name="boot info"/> on the Cortex-A | | Linux heartbeat '''LED''', which blinks as long as the Linux<ref>[[STM32MP15 Linux kernel overview]]</ref> is alive<ref name="boot info"/> on the Cortex-A | ||
|- | |- | ||
| | | <span style="color: orange;">Orange</span> | ||
| - | | - | ||
| STM32Cube<ref>[[STM32CubeMP1 architecture]]</ref> examples verdict '''LED'''. | | STM32Cube<ref>[[STM32CubeMP1 architecture]]</ref> examples verdict '''LED'''. | ||
| Line 46: | Line 39: | ||
== References == | == References == | ||
<references /> | <references /> | ||
<noinclude> | |||
{{PublicationRequestId | 8857 | 2018-09-17 | PhilipS}} | |||
[[Category:Getting started with STM32MP1 boards]] | |||
[[Category:STM32MP15 Evaluation boards]] | |||
[[Category:STM32MP15 Discovery kits]] | |||
</noinclude> | |||
Latest revision as of 17:19, 10 April 2020
1. Introduction[edit source]
STM32 MPU Evaluation boards and Discovery kits share the same usage for LEDs and buttons. The following paragraphs describe the functional mapping of the LEDs and buttons, so that 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.
2. Description[edit source]
| LED color | Button label | Purpose |
|---|---|---|
| - | WAKE UP | This button allows the platform to be woken from any low-power mode[1] |
| Green (*) |
USER1 (*) |
This can be used at boot time as a button, 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:
|
| Red (*) |
USER2 (*) |
This can be used at boot time as a button, by U-Boot, to enter Android Fastboot mode. It is also used as a LED to show Cortex-A boot information[2], then it can be used, at runtime, as a button for Linux examples. It is not used by STM32Cube. |
| Blue | - | Linux heartbeat LED, which blinks as long as the Linux[3] is alive[2] on the Cortex-A |
| Orange | - | STM32Cube[4] examples verdict LED. |
3. References[edit source]