ESP-PROG Flash stalls using JTAG
Posted: Fri Jan 28, 2022 4:21 am
Hardware: (ESP-PROG with ESP32 DEVKITV1 ((ESP-WROOM-32).
This hardware I've previously verified to compile, flash and debug as guided by the popular Yuri R Youtube videos.
Then I noticed that there was an the official tool (VSCode ESP-IDF extension),
Quick User Guide for the ESP-IDF VS Code Extension https://www.youtube.com/watch?v=Lc6ausiKvQM
However, after studying that video, and the related pages
(including https://github.com/espressif/vscode-esp ... install.md
https://github.com/espressif/vscode-esp ... leshooting
https://github.com/espressif/openocd-es ... ooting-FAQ
and installing (first I removed all Yuri R video's related setup),
I can compile an example project but not JTAG flash it.
The Output window for OpenOCD reports:
a lot of detail is added to the above, but the final lines are again as above.
So in summary, flashing this hardware succeeded in my previous setup,
but not with the ESP-IDF VSCode extension.
Curiously, if I hit F5 to debug, that succeeds!
Please advise.
This hardware I've previously verified to compile, flash and debug as guided by the popular Yuri R Youtube videos.
Then I noticed that there was an the official tool (VSCode ESP-IDF extension),
Quick User Guide for the ESP-IDF VS Code Extension https://www.youtube.com/watch?v=Lc6ausiKvQM
However, after studying that video, and the related pages
(including https://github.com/espressif/vscode-esp ... install.md
https://github.com/espressif/vscode-esp ... leshooting
https://github.com/espressif/openocd-es ... ooting-FAQ
and installing (first I removed all Yuri R video's related setup),
I can compile an example project but not JTAG flash it.
The Output window for OpenOCD reports:
In VSCode Command Pallete, esp-idf, if I set "OpenOCD Server debug level" to 3,Open On-Chip Debugger v0.10.0-esp32-20211111 (2021-11-10-21:40)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
debug_level: 2
adapter speed: 20000 kHz
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi_tdo_sample_edge falling"
Info : clock speed 20000 kHz
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : Listening on port 3333 for gdb connections
Info : accepting 'tcl' connection on tcp/6666
Info : dropped 'tcl' connection
a lot of detail is added to the above, but the final lines are again as above.
So in summary, flashing this hardware succeeded in my previous setup,
but not with the ESP-IDF VSCode extension.
Curiously, if I hit F5 to debug, that succeeds!
Please advise.