Open yueduz opened 2 weeks ago
Spritetm
commented
2 weeks ago Note - someone replied with a mediafire link to a 'solution' containing a password-protected rar file. That file contained a trojan. If you downloaded & ran that, please run a virus scan or do a full reinstall of your computer.
erhankur
commented
2 weeks ago @yueduz As a Linux user, you should be able to build from the source. To increase the timeout, you can modify it here. You can set it to 1000 or 5000, whichever works best for you.
Or you can simply disable the FLASH support and try.
openocd -c "set ESP_FLASH_SIZE 0" -f target/esp32.cfg -f <interface_config>
yueduz
commented
2 weeks ago @erhankur After I "set ESP_FLASH_SIZE 0", there is still "Timed out waiting for CPU to be reset, target state=2"
$ openocd -c "set ESP_FLASH_SIZE 0" -f board/esp32-lora.cfg [22:32:09]
Open On-Chip Debugger v0.12.0-esp32-20240318 (2024-03-18-18:25)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
0
WARNING: ESP flash support is disabled!
WARNING: ESP flash support is disabled!
force hard breakpoints
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: JTAG supported
Info : CMSIS-DAP: Atomic commands supported
Info : CMSIS-DAP: FW Version = 0254
Info : CMSIS-DAP: Serial# = 110136025020312038534751313034203032303697969903
Info : CMSIS-DAP: Interface Initialised (JTAG)
Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : clock speed 5000 kHz
Info : cmsis-dap JTAG TLR_RESET
Info : cmsis-dap JTAG TLR_RESET
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 : [esp32.cpu0] Examination succeed
Info : [esp32.cpu1] Examination succeed
Info : starting gdb server for esp32.cpu0 on 3333
Info : Listening on port 3333 for gdb connections
Info : [esp32.cpu0] Debug controller was reset.
Info : [esp32.cpu0] Core was reset.
Info : [esp32.cpu1] Debug controller was reset.
Info : [esp32.cpu1] Core was reset.
Info : [esp32.cpu0] Target halted, PC=0x40085986, debug_reason=00000000
Error: [esp32.cpu0] Timed out waiting for CPU to be reset, target state=2
Info : [esp32.cpu0] Reset cause (52) - (Unknown reset cause)
Info : [esp32.cpu1] Debug controller was reset.
Info : [esp32.cpu1] Core was reset.
Info : [esp32.cpu0] Debug controller was reset.
Info : [esp32.cpu0] Core was reset.
Info : [esp32.cpu1] Target halted, PC=0x40085986, debug_reason=00000000
Error: [esp32.cpu1] Timed out waiting for CPU to be reset, target state=2
Info : [esp32.cpu0] Debug controller was reset.
Info : [esp32.cpu0] Core was reset.
Info : [esp32.cpu1] Debug controller was reset.
Info : [esp32.cpu1] Core was reset.
Info : [esp32.cpu0] Target halted, PC=0x40085986, debug_reason=00000000
Error: [esp32.cpu0] Timed out waiting for CPU to be reset, target state=2
Info : [esp32.cpu0] Reset cause (52) - (Unknown reset cause)
Info : [esp32.cpu1] Debug controller was reset.
Info : [esp32.cpu1] Core was reset.
Info : [esp32.cpu0] Debug controller was reset.
Info : [esp32.cpu0] Core was reset.
Info : [esp32.cpu1] Target halted, PC=0x40085986, debug_reason=00000000
Error: [esp32.cpu1] Timed out waiting for CPU to be reset, target state=2I replaced the idf openocd with my own compiled openocd and got the same result. The timeout value was set to 5000
erhankur
commented
2 weeks ago Even though the timeout explanation does not entirely correct, this is another location that could cause a timeout. https://github.com/espressif/openocd-esp32/blob/master/src/target/espressif/esp_xtensa.c#L234
If it still doesn't work, please save the log with the -d3 -l log.txt option and attach the file here.
yueduz
commented
2 weeks ago log.zip This log uses the OPENOCD compiled by myself. The two parameters you mentioned were changed to 5000. I forgot to describe a phenomenon. The module kept restarting when it timed out. After changing the timeout parameters, the module restart speed did not change. My module has a light-on program that can run normally. I judge the restart speed by observing the speed of the light.
erhankur
commented
5 days ago @yueduz I will give a try with my CMSIS nano adapter and come back. In the meantime I found similar issue here. You can find something useful for you. https://github.com/espressif/openocd-esp32/issues/292
Development Kit
Custom
Module or chip used
ESP32-WROVER-E
Debug Adapter
nanoDAP-HS
OpenOCD version
v0.12.0-esp32-20240318
Operating System
ArchLinux
Using an IDE ?
vscode
OpenOCD command line
ESP-IDF:Flash Device
JTAG Clock Speed
5000
ESP-IDF version
v5.3.0
Problem Description
Click "ESP-IDF: Flash Device" on the status bar of vscode
Debug Logs
Expected behavior
Everything works correctly when I use JLink, but I want my CMSIS-DAP (nanoDAP) to work as well.
Screenshots
This is my custom configuration: