error Openocd with wrover-e, works with wrover-b

Thibaud
Posts: 4
Joined: Mon Jun 15, 2020 2:36 pm

error Openocd with wrover-e, works with wrover-b

Postby Thibaud » Wed Jul 08, 2020 2:19 pm

Hello,
I recently passed from a wrover-b to a wrover-e (ESP32-D0WD-V3) since this last one fix a problem with the SPI RAM.
Since I use this wrover-e I can't debug it over JTAG using openocd (with eclipse)
I checked the hardware (which worked with the wrover-b) and I don't have any problem (tried it on 2 differents boards).
Here is what I did :
- erase the program with idf.py -p COMXX erase_flash
- change the menuconfig from rev0 to rev3 in the "Minimum supported ESP32 Revision"
- flash a hello-world project (bootloader, partition table and hello-world.bin) with the uart. No JTAG pin configured for something else there. No problem here, I do have a "hello-world" message
- try to debug with openocd.


Here is the log :

-----------------------------------------------------------------
Open On-Chip Debugger v0.10.0-esp32-20190313 (2019-03-13-09:57)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
Info : Configured 2 cores
esp32 interrupt mask on
adapter speed: 6000 kHz
Started by ESP32 Eclipse
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 6000 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 : esp32: Debug controller 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Debug controller 1 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 1 was reset (pwrstat=0x5F, after clear 0x0F).
Info : Listening on port 3333 for gdb connections
Info : Detected debug stubs @ 3ffb2968 on core0 of target 'esp32'
Info : accepting 'gdb' connection on tcp/3333
Error: No symbols for FreeRTOS
Info : Target halted. PRO_CPU: PC=0x400E2C0A (active) APP_CPU: PC=0x400E2C0A
Info : Target halted. PRO_CPU: PC=0x4009171A (active) APP_CPU: PC=0x400E2C0A
Info : Flash mapping 0: 0x10020 -> 0x3f400020, 20 KB
Info : Flash mapping 1: 0x20018 -> 0x400d0018, 75 KB
Info : Target halted. PRO_CPU: PC=0x4009171A (active) APP_CPU: PC=0x400E2C0A
Info : Auto-detected flash size 8192 KB
Info : Using flash size 8192 KB
Info : Target halted. PRO_CPU: PC=0x4009171A (active) APP_CPU: PC=0x400E2C0A
Info : Flash mapping 0: 0x10020 -> 0x3f400020, 20 KB
Info : Flash mapping 1: 0x20018 -> 0x400d0018, 75 KB
Info : Using flash size 76 KB
Info : Target halted. PRO_CPU: PC=0x4009171A (active) APP_CPU: PC=0x400E2C0A
Info : Flash mapping 0: 0x10020 -> 0x3f400020, 20 KB
Info : Flash mapping 1: 0x20018 -> 0x400d0018, 75 KB
Info : Using flash size 24 KB
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)
Error: cpu0: xtensa_write_memory (line 802): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_write_memory (line 802): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_write_memory (line 802): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 4 bytes at address 0x3ff48000, data - 00, 20, 49, 9c, 4c, 00, 00, 00
Error: xtensa_write_uint32_list: error writing to 3ff48000
Warn : esp32_soc_reset xtensa_write_uint32_list (reg_value_pairs_pre) err=-4



Info : xtensa_poll: Target offline
Error: xtensa_poll: Target failure
Polling target esp32 failed, trying to reexamine
Examination failed, GDB will be halted. Polling again in 100ms
Error: xtensa_poll: Target failure
Polling target esp32 failed, trying to reexamine
Examination failed, GDB will be halted. Polling again in 300ms
Error: xtensa_poll: Target failure

Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: xtensa_poll: Target failure
Error: xtensa_poll: Target failure
Error: xtensa_poll: Target failure
--------------------------------------------------------------------------------


Here is what I tried without any success :
- reduce the speed of the JTAG in the cfg file bug I doesnt work.
- check all the hardware
- change the fdti
- re-change the minimum supported esp32 revisision to "Rev 0"

I think there is something wrong in the configuration for the wrover-e but I don't know what, does anyone has an idea ?

ESP_Sprite
Posts: 4114
Joined: Thu Nov 26, 2015 4:08 am

Re: error Openocd with wrover-e, works with wrover-b

Postby ESP_Sprite » Thu Jul 09, 2020 6:55 am

You probably want to upgrade OpenOCD-esp32 to the latest version we provide. ECO3 needs some special handling, this was only introduced in v0.10.0-esp32-20191008 .

Thibaud
Posts: 4
Joined: Mon Jun 15, 2020 2:36 pm

Re: error Openocd with wrover-e, works with wrover-b

Postby Thibaud » Thu Jul 09, 2020 12:13 pm

OK thanks a lot, I did the upgrade to the v0.10.0-esp32-20200526 and it works. I just add to replace the "program_esp32" commands by "program_esp"

Who is online

Users browsing this forum: No registered users and 54 guests