Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32


Issue building from STM32CubeMX generated project - /bin/sh: 1: arm-none-eabi-as: not found

Hi all,

I’m brand new to working with the STM32 (and Linux) and am trying to setup a basic LED flash program using STM32CubeMX and System Workbench. However, whenever I import and then attempt to build the project in System Workbench, it fails for the following reason:

18:54:17 **** Incremental Build of configuration Debug for project basic_led_blink ****
make all
Building file: ../startup/startup_stm32f407xx.s
Invoking: MCU GCC Assembler
/home/seeyou/Documents/STM32CubeMX/Projects/basic_led_blink/basic_led_blink/Debug
arm-none-eabi-as -mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -g -o “startup/startup_stm32f407xx.o” “../startup/startup_stm32f407xx.s”
/bin/sh: 1: arm-none-eabi-as: not found
make: *** startup/startup_stm32f407xx.o Error 127
startup/subdir.mk:15: recipe for target ‘startup/startup_stm32f407xx.o’ failed

18:54:17 Build Finished (took 63ms)

I’ve been trying to figure this out for a while now, but am getting nowhere, mostly due to a lack of experience/knowledge. I’m working on Ubuntu 16.04, version 4.6.3 of System Workbench, trying to get this program to run on an STM32F407 Discovery board (STM32F407G-DISC1). I have a feeling I may be doing something incorrectly in CubeMX rather than System Workbench, but I’ve seen others having similar-ish issues with arm-none-eabi-gcc: not found so thought I would try here. I’ve already tried specifying the Path under C/C++ Build > Settings > MCU Settings to /usr/bin/ where there is the ‘as’ file, but it didn’t make any difference.

Please ask for any more info you need, or point me to some tutorials if it’s a basic mistake I’m making. I’ve tried finding some to no avail.

Thanks

Hi LXL15

The arm-none-eabi-as should be located within SW_INSTALL_DIR/plugins/fr.ac6.mcu.externaltools.arm-none.linux64_xxxx/tools/compiler/bin/.

If not try to reinstall the toolchain by removing the compiler folder and restart System Workbench.

AFAIK the path defined in C/C++ Build > Settings > MCU Settings have to be changed only when you want to configure SW with a third-party toolchain, so I would let ${openstm32_compiler_path} in that field wink