Getting error while compiling:No such file or directory.

Question

I'm using STM32F429-Discovery.

I have gone through all the mentioned steps of configuring embedded wizart.

I have generated the example code using studio.

But while compiling the MakeFile from G:\Embedded wizart\STM32F429-Discovery\Template\Project\GCC using the devenv.cmd ,m getting this error:

 

Thank you.

 

Answer 1

Hello,

the problem is the blank in the directory name G:\Embedded wizart\...  

When you rename the directory to be without the blank, does it solve the problem?

Best regards

Paul Banach

Comments

Thank you Paul for your help.

I've changed the directory name from "G:\Embedded wizart\..." to "G:\Embedded_wizart\..." , changed the paths inside devenv.cmd and re builded the profile,after which that error got fixed.

Now I am getting this new error message:

... source/main.c failed.

the system cannot find the file specified.

Thank you.

---

Hello,

please verifiy, whether GCC is correctly installed and the path to GCC is really correct. The error message indicates, that the make was not able to create the process arm-none-eabi-gcc. This is the GCC compiler. Consequently, the Obj/main.o file could not be processed.

Maybe, it helps you further: make error 1 (arm-none-eabi-gcc: error: CreateProcess: No such file or directory)

Best reagrds

Paul Banach

---

Hello,

I have downloaded the zip file for windows of the arm gcc from the official website.

According to the instruction unzipped the folder in the common folder named "Embedded_wizart":

and edited the devenv.cmd 

but its sure that main.o has not been created.

Thank you.

---

Hello,

the main.o file is ceated by the GCC compiler. Since Make can't find GCC, the file is not created. The problem is still related to incorrect GCC path.

Please change the variable Toolchain_Path to refer to the path G:\Embedded_wizard\arm_gcc. I mean the root directory of the installed GCC as explained in our documentation. Not the sub-directory. Does it solve the problem?

If it still does not help: repeat the steps from our documentation and this time use exact the directory names as found in the documentation.

Best regards

Paul Banach

---

Awesome! It worked. Thank you Paul.