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


Stuck on Hello World

Help! I cannot even get the simple Hello World Program to operate. I get all the errors below. Any help would be appreciated. I am just starting out on this STM32 Workbench. Also, where are some simple example programs? Thanks

Dave

Description Resource Path Location Type

Program “arm-none-eabi-g++” not found in PATH Hello World DLH Project Properties, C++ Preprocessor Include.../Providers, CDT Cross GCC Built-in Compiler Settings options C/C++ Scanner Discovery Problem

Program “arm-none-eabi-g++” not found in PATH nucleo-l476rg_hal_lib Project Properties, C++ Preprocessor Include.../Providers, Ac6 SW4 STM32 MCU Built-in Compiler Settings options C/C++ Scanner Discovery Problem

Program “arm-none-eabi-gcc” not found in PATH Hello World DLH Project Properties, C++ Preprocessor Include.../Providers, CDT Cross GCC Built-in Compiler Settings options C/C++ Scanner Discovery Problem

Program “arm-none-eabi-gcc” not found in PATH nucleo-l476rg_hal_lib Project Properties, C++ Preprocessor Include.../Providers, Ac6 SW4 STM32 MCU Built-in Compiler Settings options C/C++ Scanner Discovery Problem

Program “g++” not found in PATH Preferences, C++/Build/Settings/Discovery, CDT GCC Built-in Compiler Settings MinGW options C/C++ Scanner Discovery Problem

Program “make” not found in PATH Hello World DLH C/C++ Problem

Symbol ‘cout’ could not be resolved HelloWorldDLH.cpp /HelloWorldDLH/src line 13 Semantic Error

Symbol ‘endl’ could not be resolved HelloWorldDLH.cpp /HelloWorldDLH/src line 13 Semantic Error

Symbol ‘std’ could not be resolved HelloWorldDLH.cpp /HelloWorldDLH/src line 10 Semantic Error

Hi,
I noticed you are using a L476RG board. I attached a simple project just for LED blinking. Warning, as attachment max size is about 950Kb, I removed the used files. It means that this project may not support any evolution. For other application, I would suggest to generate the appropriated project from CubeMX.
How to use the attached project :
- Uncompress the Tiny_Blinky.zip file into yuor workspace : for example in C:\Workspace_1, you should get a Tiny_Blinky folder containing .project, .cproject files ....
- Launch SW4STM32, select the workspace (C:\Workspace_1);
- Right-click in the Project explorer window >> Import >> General >> Existing Projects into Workspace >> Next >> Browse >> Select the Tiny_Blinky folder in C:\Workspace_1 >> Finish

This project should be compiled and debugged without any issue. Feel free to keep me informed.

First off I am definitely a newbie so I apologize in advance for stupid questions. I’m attempting to create the simplest program possible that will work on my STM32F103RxT6 DEMO board. I wanted to use your blinky and I believe I was successful in importing as you described above. Obviously the processor type (chip) and board it different so I tried to edit the project properties to change them for my hardware. Now it seems like they are entered properly but the build process still fails and the files shown in the far left pane showing the project structure still contains the files for your hardware. Any suggestions...

Thanks...Denis

Well I kind of gave up on that approach so to potential contributors thanks anyway. For now I’m using a newly created project with a very basic main.c that just does a for loop increment variable that has no hardware requirement but I’m never the less trying to get to the point where I can single step in debug mode.

Hi Denis,

The best way to use their code you downloaded is not to import it then change the chip/board. There is way many things to configure and the firmware might not be compatible from a board to another. It is better to create a new project with for your board (and selecting HAL Drivers to configure peripherals) then adapt the blinky code.

Regards,
Kevin.

Ok thanks I will give that a try...Denis

Well its a struggle I’ve created a project but once it is done there are no main.c and the import from the blinky example that is found the same work space (/user/blinky) directory as my own (/user/main_for_dumy). Now I’m looking at the auto config versus user defined make file . Somehow I’m violating the way the import is suppose to work hence when I try to build it I get multiple errors. Also I’ve created several trash projects that I can’t figure out how to delete. Deleting the directory in the workspace seems to work but I can’t recreate one with the same name again as the IDE claims such a project already exists so its obviously save the names somewhere other then the workspace.

I hate to waste your time I need to go thru the tutorials but the few I’ve tried the described procedure did not match what I encountered on my IDE. I will revisit them and try to follow step by step. Just the hello world basic C project (not bound to any hardware) failed...Denis


Dear Vetch,

Thanks so much for responding to my plea for help. It turns out that after much frustration the Nucleo 64 board is bad. I t does not connect to the PC. I found this out atthe STM32 workshop at ARM Tech conference. I’m in the process of getting a new board from Mouser.
Dave