Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   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 get more information from the ac6-tools website and download (registration required) various documents highlighting:

System Workbench for STM32


Programming fails?

I’ve followed the ‘Importing an STM32CubeMX generated project’ page to blink a LED on a F401RE Nucleo board, I can import and build the project without errors but when I try to program the board with the bin file nothing happens.

I’ve set the LED pin (PD_2) as output in CubeMX and written in the while loop in OpenStm32:
HAL_GPIO_TogglePin(GPIOD, GPIO_PIN_2);
HAL_Delay(500);

Any help would be much appreciated
Marcus

Hi,

The code seems ok, but did you added a LED on PD2 port (also you can check with an oscilloscope) ?

From factory Nucleo F401RE board has an green LED on PA5 (see UM1724 pag 57 - http://www.st.com/web/en/resource/technical/document/user_manual/DM00105823.pdfQuestion and attached screenshot).

This code works for me on F401RE:


/* -3- Toggle PA05 IO in an infinite loop */
while (1)
{
HAL_GPIO_TogglePin(GPIOA, GPIO_PIN_5);

/* Insert delay - ms */
HAL_Delay(500);
}


If you don’t have output on LD2 with above code, check if the board is correctly powered.


There is a LED on PD_2 and I’ve got it working in mbed.
I can get the onboard LED to blink by using an example from ST’s downloaded CubeF4 files but any attempt to change to other pins and it programs but nothing happens.


ok.

Maybe you can try to program the hex files using STM32 ST-LINK Utility.

Ok I managed to solve it by putting
__HAL_RCC_GPIOD_CLK_ENABLE();
before the while loop.

I guess this means I didn’t set it up correctly in CubeMX confused


if you useCubeMX set your gpio as output puhs pull or open drain (in the device view for instance) that all what required
Generate code will have all clk and i/o setup and should work straigh away .
of course your blink code must be after all init in the main (in the infinite while loop) our on the default thread if you have enabled rtos on MX