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


STM32 Upgrade Cube to 5.0 Workbench to compiler revision linux64_1.17.0.201812190825

Italy



Platform Linux mint 17.3
Cube MX rev 5.0
F0 firmware version 1.9.0
L0 firmware version 1.11.0 (upgraded)

Some day ago I upgraded STM32 CubeMX to revision 5.0.
At first glance nothing got worse and code related to F051 continued to compile.

Today I started a new project based on L011, after generating code, imported as usual into workbench. It refused to compile with weird errors related to internal library appeared.
Upgrading workbench too resulted again as exact one year ago refuse to compile at all:
/bin/sh: arm-none-eabi-gcc: command not found
make: *** Src/freertos.o Error 127

again noted new plugin compiler folder was not accessible and all executable files where without execution bit set.
Folders recursive chmod applied to fr.ac6.mcu.externaltools.arm-none.linux64_1.17.0.201812190825

Applied folder access right then execute to all bin folder error changed to a missing object file:

arm-none-eabi-gcc: error trying to exec ‘cc1’: execvp: No such file or directory
make: *** Src/freertos.o Error 1

plugins/fr.ac6.mcu.externaltools.arm-none.linux64_1.17.0.201812190825/tools/compiler/lib/gcc/arm-none-eabi/7.3.1

CC* executables again missing execute bit. Set again STM32F051 project compile fine...

L011 still has problem..
Erased project with Cubemx open. Saved again project on cubeMX, generated again code then imported into workspace it worked fine.

Migration to Mint 19 is planned, it is ready on HDD but I am busy generating embedded code, I report what happen installing on new mint release when I got spare time.
Best wishes to all.
Roberto