I'm running gdb on an ESP32 Wrover Kit (which includes hardware debugging). I have followed the Espressif instructions to the letter. I have summarized these here: http://www.irelandupclose.com/customer/ ... LIPSE.html
As far as I can see there is no way to tell Eclipse where openocd is installed, or how to run it (certainly the Espressif instructions https://esp-idf.readthedocs.io/en/lates ... index.html do not show how to do it.
What I have done is to build & flash from Eclipse, then launch openocd from the command line, then debug from Eclipse. That works fine, but presumably it isn't how it is intended to be done. But if it is (which certainly would not be great!), the Espressif documentation would need to be updated to say so.
Eclipse Hardware Debug problem
Re: Eclipse Hardware Debug problem
Hi RA5040,
Running OpenOCD is listed as one of the steps in Configuring ESP32 target, https://esp-idf.readthedocs.io/en/lates ... p32-target, which preceeds launching GDB section (from command line or Eclipse).
In the Eclipse section, step 12 says: If you previously completed Configuring ESP32 Target steps described above, so the target is running and ready to talk to debugger, go right to debugging by pressing “Debug” button. Otherwise press “Apply” to save changes, go back to Configuring ESP32 Target and return here to start debugging.
We'll update the document to add an explicit note that OpenOCD needs to be started before launching GDB in Eclipse.
Running OpenOCD is listed as one of the steps in Configuring ESP32 target, https://esp-idf.readthedocs.io/en/lates ... p32-target, which preceeds launching GDB section (from command line or Eclipse).
In the Eclipse section, step 12 says: If you previously completed Configuring ESP32 Target steps described above, so the target is running and ready to talk to debugger, go right to debugging by pressing “Debug” button. Otherwise press “Apply” to save changes, go back to Configuring ESP32 Target and return here to start debugging.
We'll update the document to add an explicit note that OpenOCD needs to be started before launching GDB in Eclipse.
Re: Eclipse Hardware Debug problem
Great, thank you. I went through the instructions very carefully and I didn't get it that OpenOCD had to be run manually, so clarifying that in the instructions would be great!
BTW, the instructions are really excellent ... they are very clear and very well written.
I've updated my summary for Windows here (of no use to you, but I may post it somewhere for others): http://www.irelandupclose.com/customer/ ... LIPSE.html. I usually write up notes like this because it can save a lot of time in six months or a year if I have to redo the whole thing.
BTW, the instructions are really excellent ... they are very clear and very well written.
I've updated my summary for Windows here (of no use to you, but I may post it somewhere for others): http://www.irelandupclose.com/customer/ ... LIPSE.html. I usually write up notes like this because it can save a lot of time in six months or a year if I have to redo the whole thing.
Who is online
Users browsing this forum: Google [Bot] and 109 guests