That definitely made a change, but still not quite working as expected. Here's the logs:
[OpenOCD]
Info : New GDB Connection: 1, Target esp32.cp
[OpenOCD]
u0, state: halted
Warn : ignoring character 0x43
Warn : ignoring character 0x6f
Warn : ignoring character 0x6e
.....
Warn : ignoring character 0x22
Warn : ignoring character 0x3a
Warn : ignoring character 0x31
Warn : ignoring character 0x7d
[OpenOCD]
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1142). Workaround: increase "set remotetimeout" in GDB
The debugger is definitely connected, as I can see the ESP app has stopped doing anything. In the Run and Debug tab of vs code the status indicator just seems to be stuck on loading. The debug tooks palette comes up and I can hit restart or stop. If I hit restart it says "'Debug ESP' is already running. Do you want to start another instance?", which of course does not work since there's already a connection. That kills gdb and my program does not continue to execute.I'm then stuck where it thinks its still running, but the debug tool palette disappears.
I then have to stop openOCD, start openOCD, reboot the ESP, and try again. If I hit stop, I have to hit it several times before the gdb connection is dropped.
Is it something with my launch.json?
Code: Select all
{
"version": "0.2.0",
"configurations": [
{
"type": "espidf",
"name": "Debug ESP",
"request": "launch",
"debugPort": 3333,
// "program": "${workspaceFolder}/build/main.elf"
}
]
}