Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Feature Request]: better DEBUGGING.txt and fixing ESP32S2 JTAG bitbang debug (VSC-539)

See original GitHub issue

Is your feature request related to a problem? Please describe.

Please see the commit comments on: https://github.com/espressif/vscode-esp-idf-extension/commit/b4b91b959b884d2dfae2776380c42f066021bdd6#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?

Issue Analytics

State:
Created 3 years ago
Comments:8

Top GitHub Comments

1reaction

brainstormcommented, Jan 11, 2021

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…

1reaction

brianignacio5commented, Jan 11, 2021

What do you think are reasonable defaults for launch.json ? Can you expand on your feature request ?

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.