ESP Prog debugger set up for ESP WROVER E

pranathi
Posts: 3
Joined: Wed Sep 22, 2021 12:39 pm

ESP Prog debugger set up for ESP WROVER E

Postby pranathi » Wed Sep 22, 2021 12:52 pm

Hello,

I am trying to setup ESP Prog for ESP WROVER E kit . I have FTDI driver extension for Mac OS 11 . When I run the Open OCD I do not find the manufacture, product or version information and eventually the connection fails Any help or suggestions would be appreciated . I have attached the logs below .

Code: Select all

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: 0x00000001 (mfg: 0x000 (<invalid>), part: 0x0000, ver: 0x0)
Warn : JTAG tap: esp32.cpu0       UNEXPECTED: 0x00000001 (mfg: 0x000 (<invalid>), part: 0x0000, ver: 0x0)
Error: JTAG tap: esp32.cpu0  expected 1 of 1: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x01000001 (mfg: 0x000 (<invalid>), part: 0x1000, ver: 0x0)
Warn : JTAG tap: esp32.cpu1       UNEXPECTED: 0x01000001 (mfg: 0x000 (<invalid>), part: 0x1000, ver: 0x0)
Error: JTAG tap: esp32.cpu1  expected 1 of 1: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: auto0.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto1.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto2.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto3.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto4.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto5.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto6.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto7.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto8.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto9.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto10.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto11.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto12.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto13.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto14.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto15.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : JTAG tap: auto16.tap tap/device found: 0x01010101 (mfg: 0x080 (<invalid>), part: 0x1010, ver: 0x0)
Info : TAP auto17.tap has invalid IDCODE (0x0)
Info : TAP auto18.tap has invalid IDCODE (0x0)
Warn : Unexpected idcode after end of chain: 610 0x00000000
Error: double-check your JTAG setup (interface, speed, ...)
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu0: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3333 for gdb connections

Who is online

Users browsing this forum: Bing [Bot], Majestic-12 [Bot] and 127 guests