-
Notifications
You must be signed in to change notification settings - Fork 311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: better DEBUGGING.txt and fixing ESP32S2 JTAG bitbang debug (VSC-539) #285
Comments
I went for the following launch settings: {
"version": "0.2.0",
"configurations": [
{
"type": "espidf",
"name": "Launch",
"request": "launch",
"logLevel": 5,
"mode": "auto",
}
]
} Then I see this on the Glasgow (remote_bitbang JTAG side):
And this is the output I'm seeing on the DAP side:
So it's essentially dropping the OpenOCD GDB connection on port |
The OpenOCD daemon is up and running: $ lsof -i tcp:3333
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
openocd 47428 romanvg 7u IPv4 0xec3526865396c27 0t0 TCP localhost:dec-notes (LISTEN) And connects and replies, apparently: $ nc 127.0.0.1 3333
+
$ It shows that Connecting manually it behaves like this, immediately closing the connection on port 3333:
For context, the OpenOCD start manager output looks like this:
The Glasgow side looks fine so far?:
|
Ok, after examining the output from OpenOCD to a single
Looking into how to "examine the target" in OpenOCD... might be related to espressif/openocd-esp32#64 and/or espressif/openocd-esp32#105 |
I got the following but just once (and cannot seem to reproduce), perhaps by mere chance? How can I make sure that the ESP32S2 is in a "good state" upon
|
Passing
The application flashed on the ESP32S2 seems to be running "fine", according to
I guess that next step would be examining https://github.com/espressif/openocd-esp32/blob/master/src/target/esp32s2.c to see what's being reset/halted wrong unless someone can spot an obvious error or omission in the logs I've posted so far? (/cc @igrr) :-S: |
What do you think are reasonable defaults for Based on the information you shared, seems that default launch.json seems sufficient (with the exception of debug level 5, in the debug adapter repository this value is 2 by default) so I believe your desired behavior is related to openOCD project itself. Please let us keep related issues to its respective repository, so we can fix these issues. |
That's right @brianignacio5, I kept this issue as sort-of a journal as I was fixing this, I'll move to openocd-esp32 repo instead. W.r.t DEBUGGING.txt, I would have expected an overall description/diagram of which ports communicate with which components since there are a few moving parts (ports: 4444 (telnet/tcl??), 5555 (openocd), 3333 (gdb), 43474 (DAP), etc... |
@brianignacio5 At least this reference?: https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/api-guides/jtag-debugging/index.html#how-it-works ... but involving the editor's DAP. |
Is your feature request related to a problem? Please describe.
Please see the commit comments on: b4b91b9#r45766576 ... for a good description of the current situation and what I've been trying.
Describe the solution you'd like
I would love to have a "reasonable defaults" config for the
esp_debug_adapter
... I understand that there might not be an "one size fits all" solution for this, but the docs should be less succint for new users?The text was updated successfully, but these errors were encountered: