cancel
Showing results for 
Search instead for 
Did you mean: 

In STM32CubeIDE How can I fix "arm-none-eabi-gcc: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory"

jdsotack
Associate II

When I create the default project for the NUCLEO-F429ZI board and build without any edits I get the following error repeatedly and would like to get rid of it. I can build the same on a different laptop. How can I solve this problem.

 "arm-none-eabi-gcc: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory"

More complete build output follows:

18:15:37 **** Build of configuration Debug for project 429zi ****

make -j16 all 

arm-none-eabi-gcc "C:/Users/00706947/STM32Cube/Repository/STM32Cube_FW_F4_V1.27.0/Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal.c" -mcpu=cortex-m4 -std=gnu11 -g3 -DDEBUG -DUSE_HAL_DRIVER -DSTM32F429xx -c -I../Core/Inc -IC:/Users/00706947/STM32Cube/Repository/STM32Cube_FW_F4_V1.27.0/Drivers/STM32F4xx_HAL_Driver/Inc -IC:/Users/00706947/STM32Cube/Repository/STM32Cube_FW_F4_V1.27.0/Drivers/STM32F4xx_HAL_Driver/Inc/Legacy -IC:/Users/00706947/STM32Cube/Repository/STM32Cube_FW_F4_V1.27.0/Drivers/CMSIS/Device/ST/STM32F4xx/Include -IC:/Users/00706947/STM32Cube/Repository/STM32Cube_FW_F4_V1.27.0/Drivers/CMSIS/Include -O0 -ffunction-sections -fdata-sections -Wall -fstack-usage -MMD -MP -MF"Drivers/STM32F4xx_HAL_Driver/stm32f4xx_hal.d" -MT"Drivers/STM32F4xx_HAL_Driver/stm32f4xx_hal.o" --specs=nano.specs -mfpu=fpv4-sp-d16 -mfloat-abi=hard -mthumb -o "Drivers/STM32F4xx_HAL_Driver/stm32f4xx_hal.o"

arm-none-eabi-gcc "C:/Users/00706947/STM32Cube/Repository/STM32Cube_FW_F4_V1.27.0/Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal_cortex.c" -mcpu=cortex-m4 -std=gnu11 -g3 -DDEBUG -DUSE_HAL_DRIVER -DSTM32F429xx -c -I../Core/Inc -IC:/Users/00706947/STM32Cube/Repository/STM32Cube_FW_F4_V1.27.0/Drivers/STM32F4xx_HAL_Driver/Inc -IC:/Users/00706947/STM32Cube/Repository/STM32Cube_FW_F4_V1.27.0/Drivers/STM32F4xx_HAL_Driver/Inc/Legacy -IC:/Users/00706947/STM32Cube/Repository/STM32Cube_FW_F4_V1.27.0/Drivers/CMSIS/Device/ST/STM32F4xx/Include -IC:/Users/00706947/STM32Cube/Repository/STM32Cube_FW_F4_V1.27.0/Drivers/CMSIS/Include -O0 -ffunction-sections -fdata-sections -Wall -fstack-usage -MMD -MP -MF"Drivers/STM32F4xx_HAL_Driver/stm32f4xx_hal_cortex.d" -MT"Drivers/STM32F4xx_HAL_Driver/stm32f4xx_hal_cortex.o" --specs=nano.specs -mfpu=fpv4-sp-d16 -mfloat-abi=hard -mthumb -o "Drivers/STM32F4xx_HAL_Driver/stm32f4xx_hal_cortex.o"

arm-none-eabi-gcc "C:/Users/00706947/STM32Cube/Repository/STM32Cube_FW_F4_V1.27.0/Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal_dma.c" -mcpu=cortex-m4 -std=gnu11 -g3 -DDEBUG -DUSE_HAL_DRIVER -DSTM32F429xx -c -I../Core/Inc -IC:/Users/00706947/STM32Cube/Repository/STM32Cube_FW_F4_V1.27.0/Drivers/STM32F4xx_

.

.

.

compilation terminated.

arm-none-eabi-gcc: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

compilation terminated.

make: *** [Drivers/STM32F4xx_HAL_Driver/subdir.mk:106: Drivers/STM32F4xx_HAL_Driver/stm32f4xx_hal_rcc_ex.o] Error 1

arm-none-eabi-gcc: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

compilation terminated.

make: *** [Drivers/STM32F4xx_HAL_Driver/subdir.mk:88: Drivers/STM32F4xx_HAL_Driver/stm32f4xx_hal_flash.o] Error 1

make: *** [Drivers/STM32F4xx_HAL_Driver/subdir.mk:92: Drivers/STM32F4xx_HAL_Driver/stm32f4xx_hal_flash_ramfunc.o] Error 1

arm-none-eabi-gcc: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

arm-none-eabi-gcc: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

arm-none-eabi-gcc: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

compilation terminated.

compilation terminated.

compilation terminated.

make: *** [Drivers/STM32F4xx_HAL_Driver/subdir.mk:98: Drivers/STM32F4xx_HAL_Driver/stm32f4xx_hal_pcd_ex.o] Error 1

make: *** [Drivers/STM32F4xx_HAL_Driver/subdir.mk:94: Drivers/STM32F4xx_HAL_Driver/stm32f4xx_hal_gpio.o] Error 1

make: *** [Drivers/STM32F4xx_HAL_Driver/subdir.mk:9

1 ACCEPTED SOLUTION

Accepted Solutions
jdsotack
Associate II

The problem was that I had the system environment variable GCC_EXEC_PREFIX set for building a different target.

View solution in original post

3 REPLIES 3
jdsotack
Associate II

The problem was that I had the system environment variable GCC_EXEC_PREFIX set for building a different target.

PŁucz.1
Associate II

Hi, I have the same problem but I don't know what path should this variable points. I have GCC_EXEC_PREFIX set for path where I have gcc.exe, but not arm-gcc.exe. Can you help me and show path that you have in this variable?

same issue here

we dont need to firmware by ourselves, lets talk