Merged in fvacek/nuttx (pull request #578)

Issue #85: /dev/userleds is not working for nucleo-l432kc fixed

Approved-by: Gregory Nutt <gnutt@nuttx.org>
This commit is contained in:
Fanda 2018-01-20 22:06:09 +00:00 committed by Gregory Nutt
commit c12a34db13
3 changed files with 5 additions and 5 deletions

View File

@ -324,7 +324,7 @@ Hardware
----
The Nucleo F401RE and Nucleo F411RE provide a single user LED, LD2. LD2
is the green LED connected to Arduino signal D13 corresponding to MCU I/O
PA5 (pin 21) or PB13 (pin 34) depending on the STM32target.
PB3 (pin 26).
- When the I/O is HIGH value, the LED is on.
- When the I/O is LOW, the LED is off.

View File

@ -147,8 +147,8 @@
/* LEDs
*
* The Nucleo l476RG board provides a single user LED, LD2. LD2
* is the green LED connected to Arduino signal D13 corresponding to MCU I/O
* PA5 (pin 21) or PB13 (pin 34) depending on the STM32 target.
* is the green LED connected to Arduino signal D13 corresponding to
* MCU I/O PB3 (pin 26).
*
* - When the I/O is HIGH value, the LED is on.
* - When the I/O is LOW, the LED is off.

View File

@ -77,7 +77,7 @@
#endif
/* LED. User LD2: the green LED is a user LED connected to Arduino signal D13
* corresponding to MCU I/O PA5 (pin 21) or PB13 (pin 34) depending on the STM32
* corresponding to MCU I/O PB3 (pin 26)
* target.
*
* - When the I/O is HIGH value, the LED is on.
@ -85,7 +85,7 @@
*/
#define GPIO_LD2 \
(GPIO_PORTA | GPIO_PIN5 | GPIO_OUTPUT_CLEAR | GPIO_OUTPUT | GPIO_PULLUP | \
(GPIO_PORTB | GPIO_PIN3 | GPIO_OUTPUT_CLEAR | GPIO_OUTPUT | GPIO_PULLUP | \
GPIO_SPEED_50MHz)
#define LED_DRIVER_PATH "/dev/userleds"