Skip to content

Semantic Errors in Espressif IDE - Unresolved Identifiers (CONFIG_BLINK_PERIOD, portTICK_PERIOD_MS, uint8_t) (IDFGH-14875) (IEP-1496) #1189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Prroyal opened this issue Mar 18, 2025 · 2 comments

Comments

@Prroyal
Copy link

Prroyal commented Mar 18, 2025

I am facing semantic errors in Espressif IDE while working on a simple blink example. The IDE is unable to resolve CONFIG_BLINK_PERIOD, portTICK_PERIOD_MS, and uint8_t, even though the project builds successfully using idf.py build.

@github-actions github-actions bot changed the title Semantic Errors in Espressif IDE - Unresolved Identifiers (CONFIG_BLINK_PERIOD, portTICK_PERIOD_MS, uint8_t) Semantic Errors in Espressif IDE - Unresolved Identifiers (CONFIG_BLINK_PERIOD, portTICK_PERIOD_MS, uint8_t) (IDFGH-14875) Mar 18, 2025
@igrr igrr transferred this issue from espressif/esp-idf Mar 18, 2025
Copy link

Hi @Prroyal! This is an automated response.
If you don’t find the answer helpful, please check the ESP32 IDE forum (https://www.esp32.com/viewforum.php?f=40) or GitHub issues (https://github.com/espressif/idf-eclipse-plugin/issues) to see if the issue has already been discussed.


It seems like you are encountering semantic errors in the Espressif IDE related to unresolved identifiers, even though your project builds successfully. This issue might be related to the IDE's indexer not correctly resolving headers and identifiers.

Based on the information from the Espressif IDE documentation, here are some steps you can take to address this issue:

  1. Indexer Improvements: The Espressif IDE has made improvements to the indexer in version 2.4.0 to better resolve headers and functions based on compile_commands.json. Ensure you are using the latest version of the IDE, as these improvements might help resolve your issue.

  2. Linking esp-idf Components: When an IDF project is built, all dependent esp-idf components should be linked to the project. This allows the IDE to navigate to function definitions and resolve identifiers. Make sure that your project is correctly linking these components.

  3. Refreshing the Index: After building your project, the IDE should automatically trigger linking of esp-idf components and indexing of all files. This process might take a few seconds. Ensure that this indexing process completes successfully.

  4. Check for Updates: Make sure your Espressif IDE and all related plugins are up to date, as updates often include bug fixes and improvements.

For more detailed troubleshooting, you can refer to the Espressif IDE documentation for additional guidance.

If the issue persists, consider opening an issue on the Espressif GitHub repository for further assistance.

@github-actions github-actions bot changed the title Semantic Errors in Espressif IDE - Unresolved Identifiers (CONFIG_BLINK_PERIOD, portTICK_PERIOD_MS, uint8_t) (IDFGH-14875) Semantic Errors in Espressif IDE - Unresolved Identifiers (CONFIG_BLINK_PERIOD, portTICK_PERIOD_MS, uint8_t) (IDFGH-14875) (IEP-1496) Mar 18, 2025
@sigmaaa
Copy link
Collaborator

sigmaaa commented Mar 18, 2025

Hi @Prroyal,

If you're using Espressif-IDE, there's no need to build the project with idf.py build you can simply use the build button in the IDE. More details are in the official documentation: Espressif-IDE Build Project.

Even if the project is built using the idf.py build command, it's recommended to use the build button at least once to automatically configure Clangd options for a current project. This ensures proper functionality, such as:

Image

@sigmaaa sigmaaa self-assigned this Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants