[andreapedica]

Hi,

 

your suggestion to switch to GNU compile system actually solved the problem in VisualGDB under VS.

Whenever possible I will check also if problem is present outside of VisualGDB, in that case I will check on ESP-IDF side.

 

Thanks for your help.

[andreapedica]

Hi,

I fell in this “old” topic by searching on google about a very simlar problem with CLang + VS2017 + VisualGDB.

Actually, I found that Clang Diagnostics Console shows problems with .c modules recently added to a project, or where we add some new includes. If we close the solution and reopen to try to fix IntelliSense, this will continue to give a failure until we close all open files of the solution: it seems like Clang fails to reparse modules that are automatically opened when we open the solution (VS remembers the last modules opened before we close a solution).

So, if sometimes I still encounter the failure of IntelliSense, I do following steps:

• close all open modules and files of the solution (right click on a file tab, and select “close all documents”
• close the solution
• reopen the solution, verifying that no document is automatically opened by VS
• check the Clang Intellisense Diagnostic Console that wil no more show problems on modules parsing

Hope this can help someone else.

[andreapedica]

Hi,

 

thanks for your suggestions. I’ve solved the issue by setting CMake as project type and adding to PATH variable the path to the ULP binaries, using latest release of VisualGDB.

 

Thanks again for your help.

[andreapedica]

Hi,

 

thanks for your suggestion. Actually, I’ve already followed the description at the link you’ve suggested, but the problem in Visual Studio is still present. Please consider that “outside”of visual studio, i can run succesfully the make command for the project including the ULP code, this measn that the “standard” GCC compiler is set-up correctly.

It seems like the VS cannot find the path to the esp32ulp-elf-binutils\bin even if the path has been put in the PATH system variable (and is correctly running using GCC outside VS).

Do I have to manually insert in the VS project the path to the tool? If yes, how can I do this?

the compiling process reaches end signaling failure, and the error log output is:

 

make[1]: esp32ulp-elf-as: Command not found
make[1]: *** [/esp-idf/v3.2/components/ulp/component_ulp_common.mk:41: KnobMonitor.ulp.o] Error 127
make: *** [/esp-idf/v3.2/make/project.mk:505: component-main-build] Error 2
make: *** Waiting for unfinished jobs….

 

Thanks for your help.

[Author]

Posts