Error: DIR instruction generated an overrun! (OCD-185)

[alexdecei]

So I have that error since severals days:

Hardware

• Esp32 devkit v1
• Wroom32 With Jtag port (those 6 little dots)
• jtag interface: SEGGER jlink

Problem
I type:

bin\openocd -s share\openocd\scripts -f interface\jlink.cfg -f board\esp-wroom-32.cfg -c "program_esp32 c:\xxxxxxxxxxxxxxxxxxxxxxx\bootloader.bin 0x1000 verify; program_esp32 c:\xxxxxxxxxxxxxxxxxxxxxxxxxxxxx\ethernet_demo.bin 0x10000 verify; reset; exit"

I get:

adapter speed: 20000 kHz
esp32 interrupt mask on
Info : No device selected, using first device.
Info : J-Link V10 compiled Jul 23 2019 13:46:10
Info : Hardware version: 10.10
Info : VTarget = 3.310 V
Info : Reduced speed from 20000 kHz to 15000 kHz (maximum).
Info : Reduced speed from 20000 kHz to 15000 kHz (maximum).
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 : 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 : 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: esp32_fetch_all_regs (line 227): DSR (00000088) indicates DIR instruction generated an overrun!
Error: cpu1: esp32_fetch_all_regs (line 227): DSR (00000088) indicates DIR instruction generated an overrun!
Info : Target halted. PRO_CPU: PC=0x400E7EF2 (active) APP_CPU: PC=0x00000000
Error: cpu0: xtensa_write_memory (line 761): DSR (8000CC13) indicates DIR instruction generated an exception!
Warn : esp32: Failed writing 4 bytes at address 0x3FF5F064, data - a1, 3a, d8, 50, a1, 3a, d8, 50
embedded:startup.tcl:21: Error:
in procedure 'program_esp32'
in procedure 'reset' called at file "share\openocd\scripts/target/esp32.cfg", line 120
in procedure 'ocd_bouncer'
in procedure 'ocd_process_reset'
in procedure 'ocd_process_reset_inner' called at file "embedded:startup.tcl", line 248
in procedure 'esp32' called at file "embedded:startup.tcl", line 312
in procedure 'ocd_bouncer'
in procedure 'esp_core_halt'
in procedure 'esp32' called at file "share\openocd\scripts/target/esp32.cfg", line 44
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 21

Info : Detected debug stubs @ 3ffc0448 on core0 of target 'esp32'
Error: cpu0: xtensa_read_memory (line 654): DSR (00000088) indicates DIR instruction generated an overrun!
Warn : cpu0: Failed reading 76 bytes at address 0x50000000
Error: esp32_soc_reset 528 err=-4
embedded:startup.tcl:21: Error:
in procedure 'program_esp32'
in procedure 'reset' called at file "share\openocd\scripts/target/esp32.cfg", line 120
in procedure 'ocd_bouncer'
in procedure 'ocd_process_reset'
in procedure 'ocd_process_reset_inner' called at file "embedded:startup.tcl", line 248
in procedure 'esp32' called at file "embedded:startup.tcl", line 312
in procedure 'ocd_bouncer'
in procedure 'esp_core_halt'
in procedure 'esp32' called at file "share\openocd\scripts/target/esp32.cfg", line 44
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 21
in procedure 'program_esp32'
in procedure 'reset' called at file "share\openocd\scripts/target/esp32.cfg", line 120
in procedure 'ocd_bouncer'

embedded:startup.tcl:454: Error: ** Unable to reset target **
in procedure 'program_esp32'
in procedure 'program_error' called at file "share\openocd\scripts/target/esp32.cfg", line 121
at file "embedded:startup.tcl", line 454

note: if i don't put commands I get no error:

bin\openocd -s share\openocd\scripts -f interface\jlink.cfg -f board\esp-wroom-32.cfg

If you have any idea I would be glad to hear it.

Thanks

[alexdecei]

Found the solution:
I went into the both cfg files (esp-wroom-32.cfg & jlink.cfg) and wrote adapter_khz 10000.

The problem is that openocd used to say that 20000khz is to much and change it to 15000khz. But 15000khz is still too much so it gives an error but that error do not mention any speed issues.
So it's impossible to know that the problem is the adapter speed.