I seem to understand now...

The printf function is precompiled in ROM, and the source code is not available, so the file content cannot be displayed during debugging.

launch.json：


{
"version": "0.2.0",
"configurations": [
{
"type": "gdbtarget",
"request": "attach",
"name": "Eclipse CDT GDB Adapter"
},
{
"type": "espidf",
"name": "Launch",
"request": "launch"
}
]
}

Hello,

I'm using the ESP-IDF extension in VS Code to debug an ESP32-S3 project.

When I set a breakpoint and try to "Step Into" a printf function call, VS Code shows an error: "The editor could not be opened because the file was not found."

Is this a bug, or is there a misconfiguration on my end ...

Hi Fabricio,

Thank you for the clear update. We’ll align our beginner tutorial with EIM (including the offline install workflow) and will test the VS Code extension 2.x preview, reporting any issues via the GitHub repos you shared.

We’re looking forward to the official releases of EIM and the VS ...

Hello everyone,

We’re developing a beginner-focused ESP-IDF tutorial and would like to understand the official roadmap for installation methods so our content remains current and forward-looking. Our tutorial is centered on VS Code development, and we’ve noted three mainstream installation options ...

Hi Smallfry,

Sorry for the trouble. The fastest way to get this resolved is to contact Waveshare’s official support so they can track your case and check board-specific configs:

- Ticket: https://service.waveshare.com/
- Email: support@waveshare.com

Please include your exact board model/revision ...