"No such file or directory" error: STM32F429I-DISC1

[LNdungane]

Greetings All

I am implementing an ADC-based GUI on my board and my code is not building due to the abovementioned error (even when the file exists. I am using STMCubeMX(6.3.0), STM32CubeIDE (1.7.0) and TouchGFX(4.17.0) to develop my GUI. Most of these files are in the simulator folder so I figure there must be a way to omit them as I suspect that they may be giving me problems. This is for my final-year project and I am pressed for a solution. Any assistance will be greatly appreciated.

[Imen.D]

Hello @LNdungane​ and welcome to the Community :)

Maybe you haven't configured correctly the Include paths within your project.

So, you need to examine the example/template projects available with the firmware libraries STM32CubeF4 and use it as source of inspiration to configure the include paths, the defines and the structure with the stm32f4xx_conf.h in the project directory.

Good luck for your final-year project ;) and don't hesitate to come back to the Community if you still have issues.

Imen

[Andrew Neil]

@Imen DAHMEN​ "Maybe you haven't configured correctly the Include paths within your project"

^^^ THAT! ^^^

@LNdungane​ For an explanation of "include paths", see: https://devzone.nordicsemi.com/f/nordic-q-a/46716/simple-adc-code/184681#184681

Note that this is standard C stuff - not specific to STM32

[LNdungane]

Thank you Andrew, I have resolved that matter and been met with compilation errors since. It's frustrating at this point.

[TDK]

What file or directory is it looking for?

Show the full error message, screenshots if helpful. Hard to debug with limited info.

[LNdungane]

Hi TDK I have since resolved that issue. However I am faced with complilation errors. Please see the image below:

[Andrew Neil]

would be better to copy & paste the text - your image has truncated the messages.

Fortunately, when you get loads of messages like that it's often down to just one problem (or a few problems) - fix them, and all the messages will go away.

The key is to address the earliest-reported message first.