Extension stopped working after configuration edit

[dadede]

Hello,

I was able to install the extension and get it working. After loading a new project from CubeMX with the Makefile, the extension started with a dry run( can't remember the exact parameter). Then I got an error that says
Something went wrong with importing the project. Error: Error: Could not find CubeIDEProject and another
Unable to resolve configuration with compilerPath "arm-none-eabi-gcc". Using "/usr/bin/clang" instead.
Since then I have uninstalled and reinstalled the extension and tried but failed to set a compiler for use but in the main file, I keep getting errors, the intellisense is trrowing errors that seem to be the headers are not found in the path.

Can I please get some guidance in starting afresh with the removal of config files and reinstall? Also, is it recommended to install from the vscode marketplace or github(can't figure out how to install from github)?

Thank you!

[jortbmd]

Hi! Thanks for opening up an issue.
It might be possible that the CubeIDE project is broken for you. I do not know if you have CubeIDE installed however it helps if you compile the project once over there and then try to re-import it in VSCode. The other option with the compilerPath I am not quite sure what is causing this. Might be the C/C++ intellisense, this should be changed by the extension, however this only happens after a successful import.
You can best install the VSCode extension through the marketplace. This way you have the most up to date and stable version.