Hi,
It looks like this issue is related to the new CDT LSP editor. To fix it, you’ll need to update the LSP4E dependencies first.
1. Go to Help → Install New Software…
2. In the Work with field, paste the following update site:
http://download.eclipse.org/lsp4e/releases/latest/
3. From the list ...
Search found 4 matches
- Thu Nov 20, 2025 8:39 am
- Forum: IDEs for ESP-IDF
- Topic: Lost automatic code indentation
- Replies: 2
- Views: 7088
- Mon Jun 27, 2022 7:09 am
- Forum: IDEs for ESP-IDF
- Topic: Can not get running the debugging with "Espressif IDF plugins for Eclipse"
- Replies: 4
- Views: 7310
Re: Can not get running the debugging with "Espressif IDF plugins for Eclipse"
Hi Michael,
The dialog "Debug Configuration", tab "Debugger" does not contain the fields "Flash voltage", "Target" and "Board"!
The first problem after making these changes you can see in the attached screen shot. Nothing happens when I press one of both buttons! I can't recognize what I should ...
The dialog "Debug Configuration", tab "Debugger" does not contain the fields "Flash voltage", "Target" and "Board"!
The first problem after making these changes you can see in the attached screen shot. Nothing happens when I press one of both buttons! I can't recognize what I should ...
- Tue Dec 28, 2021 10:07 am
- Forum: IDEs for ESP-IDF
- Topic: ESP-Prog debugger cannot start
- Replies: 5
- Views: 21886
Re: ESP-Prog debugger cannot start
Hi, I am using MACOS, VScode and ESP-Prog with ESP32.
I found that the On-Chip Debugger always have the following error message
Open On-Chip Debugger v0.10.0-esp32-20210401 (2021-04-01-15:46)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
debug_level ...
- Tue Nov 30, 2021 11:37 am
- Forum: IDEs for ESP-IDF
- Topic: how to work with ESP32-S2-Saola-1R borad using eclipse
- Replies: 1
- Views: 8800
Re: how to work with ESP32-S2-Saola-1R borad using eclipse
Hi,
try to put '_' character in the interface name, like on the screenshot below (marked yellow). This issue occurs due to an older version of the openocd where there was a bug in esp-config.json where the names of some of the config paths are incorrect.
try to put '_' character in the interface name, like on the screenshot below (marked yellow). This issue occurs due to an older version of the openocd where there was a bug in esp-config.json where the names of some of the config paths are incorrect.