STM32MP1 support available in SW4STM32

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world.
And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4; you can download a short video showcasing this on the ac6-tools website (registration required).

System Workbench for STM32

You are viewing a reply to Simple GPIO problem  

Re: Simple GPIO problem



Just a few things:

  1. You explicitly set the GPIO bit to 1; I’m not sure if this will light up the led or shut it down (often LEDs are active when the GPIO output is set to 0 as outputs are often able to draw current but not to provide so much.
  2. With your scope you look at PB4, while the LED is on PA5... As you said PB4 is a PWM output or can be used to SPI1, but the LED is not connected there.
  3. If PA13 and PA14 continue to pulse, that really mean that this is not your program’s fault as it does nothing...
  4. When looking more precisely at your first program, I just noticed that you don’t have any delay in your infinite loop, meaning you just toggle the GPIO about 10 miilion times per second... You should probably see it partly lighten-up, but not blinking.
    • To blink it twice per second replace the second call to GPIO_WriteBit (which is useless) by a loop like: for (i=0; i < 5000000; i++);
    • I just tested this on a NUCLEO-f411RE (using GPIOA5 explicitly as this board is not really supported by StdPeriph) and it works like a charm. (BTW on this board setting the GPIO to 1 light-up the LED, resetting it to 0 shut it down).


PS: The “arm-none-eabi-gcc not found” error is a known bug; it can be suppressed by seleting these errors in the “Problems” view and hitting “Delete”; it appears at project creation and will not appear again.