ESP32 Forum

after nailing down this nightmare viewtopic.php?f=40&t=25392 I just have to fix the debug/flashing problem.
I will continue using Eclipse plug in as there are the settings cleaner (and easier) to maintain.
Both using the same ESP-IDF location and have almost the same issue.

I am using the simple http server example untouched. Compiles seamlessly, no issues. Flashing OK.

Boards: Kaluga and via Jtag-PROG.

In eclipse the debug session does not halt at app_main() at start. It halts somewhere before in an area where no source file information is available. However if I restart the session while debugging it lands at app_main().

From here on both VScode and Eclipse behave the same.
The 'jump over' and 'jump in' button do not behave like they should. The jump over button jumps most of the time into the function and the jump in button behaves like the run button or jump out button.

Both the Kaluga and our own board worked well until the extension 1.3 was installed in VScode automaticly. Since then the problem occurred.

Remarkable is as well, that the Kaluga is not even flashable with the kaluga cfg file. Only selecting the Jtag-PROG cfg file allows to flash the kaluga.

this looks to me like a timing problem. Question, did the extension install 1.3 update the open OCD binaries ?

a really quick answer would be lifesaving

following up this issue I can not understand why this is happening.

It is known the the ESP32-S2 supports only two hardware breakpoints and if these are used the debug behavior would be exactly the one I experience.

However, I would be interested to know why I can't deselect the startup breakpoint at app_start() to not occupy a hardware breakpoint. And where is the other breakpoint used. It may be used as the breakpoint set for stack overflow. But can this not be controlled somewhere.

I can easily set a breakpoint after a function to symulate the 'jump over' button. So why does it not working automatically?