Olimex ARM-USB-OCD-H installation issue

mietz · November 13, 2019, 8:56am

Hi community,

I have a problem getting the Olimex ARM-USB-OCD-H to work on Windows 10 with an esp32. I’m somewhat sure that it is a driver issue.

First I followed the instruction from the platformio website. They pointed me to this driver ESP32 & PIO Unified Debugger - #20 by botofancalin

I tried to follow the instructions, but I’m unable to install the suggested FTDI driver from this website:
http://www.ftdichip.com/Drivers/VCP.htm

Even if I point Windows to the folder which contains the driver, it’s unable to find it for the device.

So I digged a little deeper and found a FTDI driver from Olimex in their official manual:

This one: https://www.olimex.com/Products/ARM/JTAG/_resources/OLIMEX-FTDI-drivers-2-12-04.zip

I can install it without a problem, but as soon as I try to upload it to the esp I get this error:

    Open On-Chip Debugger  v0.10.0-esp32-20190708 (2019-07-08-11:04)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
debug_level: 1
adapter speed: 20000 kHz
esp32 interrupt mask on
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Error: no device found
Error: unable to open ftdi device with vid 15ba, pid 002b, description 'Olimex OpenOCD JTAG ARM-USB-OCD-H', serial '*' at bus location '*'
** OpenOCD init failed **
shutdown command invoked

I then removed the driver and installed the WinUSB driver from the recent zadig tool. With that driver I get this error message:

Open On-Chip Debugger  v0.10.0-esp32-20190708 (2019-07-08-11:04)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
debug_level: 1
adapter speed: 20000 kHz
esp32 interrupt mask on
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
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: 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
*** [upload] Error 253

my platfomio.ini is:

[env:esp32dev]

platform = espressif32

debug_tool = olimex-arm-usb-ocd-h

upload_protocol = olimex-arm-usb-ocd-h

board = esp32dev

framework = arduino

I’m pretty sure that I did the wiring correctly. Maybe I try to install the wrong driver. The docu is lacking of the correct information which one I have to use for the ARM-USB-OCD-H or I couldn’t find the issue. Maybe someone of you could point me to the right direction.

Help would be appreciated.

mietz · November 13, 2019, 3:00pm

So, after fiddling around with the drivers I got it working… But, only one time. Now it says:

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
Info : accepting 'gdb' connection from pipe
Error: No symbols for FreeRTOS
Error: Target not examined yet


Error: Target not halted
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_map disable'.
Error: attempted 'gdb' connection rejected
Error: error during select: Unknown error
Warn : Flash driver of esp32.flash does not support free_driver_priv()
Warn : Flash driver of irom does not support free_driver_priv()
Warn : Flash driver of drom does not support free_driver_priv()
.pioinit:15: Error in sourced command file:
Remote communication error.  Target disconnected.: No error.

Any suggestions?

manuelbl · November 13, 2019, 3:48pm

What do you mean by “I got it working”? Have you been able to upload a program or single step in the debugger?

Anyhow, it looks like a communication problem between the Olimex debug probe and the ESP32 board.

Try to lower the communication speed: In C:\Users\username\.platformio\packages\tool-openocd-esp32\share\openocd\scripts\target\esp-wroom-32.cfg append the line:

adapter_khz 1000

Additionally, show us how you have connected to board to the debug adapter/probe.

mietz · November 14, 2019, 8:15am

Thanks for your reply.

I was able to upload the program and to single step in the code through the debugger.

I reduced the adapter speed to 1000 khz as you pointed out. I get a different result now, but I’m still unable to debug my program.

PlatformIO Unified Debugger -> http://bit.ly/pio-debug
PlatformIO: debug_tool = olimex-arm-usb-ocd-h
PlatformIO: Initializing remote target...
Open On-Chip Debugger  v0.10.0-esp32-20190708 (2019-07-08-11:04)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
adapter speed: 1000 kHz
Info : Configured 2 cores
esp32 interrupt mask on
Info : tcl server disabled
Info : telnet server disabled
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 1000 kHz
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
Info : esp32: Debug controller 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : accepting 'gdb' connection from pipe
Error: No symbols for FreeRTOS
Info : esp32: Debug controller 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : Target halted. PRO_CPU: PC=0x40000288 (active)    APP_CPU: PC=0x00000000
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 0x5F).
Info : esp32: Core 1 was reset (pwrstat=0x5F, after clear 0x5F).
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 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
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 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
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 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
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 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
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 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
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 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
Warn : Received debug request on stalled active core 0.
Info : Target halted. PRO_CPU: PC=0x00000000             APP_CPU: PC=0x00000000 (active)
Info : Flash mapping 0: 0x3ffc0590 -> 0x3ffc0590, 1048321 KB
Info : Flash mapping 1: 0x3ffc0590 -> 0x3ffc0590, 1048321 KB
Info : Flash mapping 2: 0x20324e0e -> 0xfffffffe, 1942452 KB
Info : Flash mapping 3: 0x9bdbc0 -> 0x9cfa50, 10017 KB
Info : Flash mapping 4: 0x94fcac -> 0x4280e9, 9974 KB
Info : Flash mapping 5: 0x13 -> 0x11f1998, 10175 KB
Info : Flash mapping 6: 0x9cfa50 -> 0x9c8480, 0 KB
Info : Flash mapping 7: 0x94fca8 -> 0x9c4cd0, 0 KB
Info : Flash mapping 8: 0x94ffcc -> 0x2b, 10046 KB
Info : Flash mapping 9: 0x9c8480 -> 0x0, 4423 KB
Info : Flash mapping 10: 0x0 -> 0x94fcac, 10017 KB
Info : Flash mapping 11: 0x9c8288 -> 0x1c, 10017 KB
Info : Flash mapping 12: 0x94fca8 -> 0x2, 9535 KB
Info : Flash mapping 13: 0x0 -> 0x94ffcc, 1942519 KB
Info : Flash mapping 14: 0x20327106 -> 0xfffffffe, 0 KB
Info : Flash mapping 15: 0x9bdbc0 -> 0x9ced70, 6358 KB
Info : Flash mapping 16: 0x94fce4 -> 0x9c8288, 10017 KB
Info : Flash mapping 17: 0x94fd2c -> 0x0, 4446 KB
Info : Flash mapping 18: 0x9c8480 -> 0x6356bf, 0 KB
Info : Flash mapping 19: 0x635ae0 -> 0x63593c, 10006 KB
Info : Flash mapping 20: 0x11f19c0 -> 0x45e3bf, 9949 KB
Info : Flash mapping 21: 0x94fd28 -> 0x0, 16464 KB
Info : Flash mapping 22: 0x9c7398 -> 0x635fca, 0 KB
Info : Flash mapping 23: 0x0 -> 0x1, 6391 KB
Info : Flash mapping 24: 0x94ffcc -> 0x721104, 527505 KB
Info : Flash mapping 25: 0xfffffffc -> 0x0, 0 KB
Info : Flash mapping 26: 0x0 -> 0x9c72b8, 9840 KB
Info : Flash mapping 27: 0x0 -> 0x9c70c8, 0 KB
Info : Flash mapping 28: 0x64 -> 0x1d09d0, 0 KB
Info : Flash mapping 29: 0x768e85f4 -> 0x5632168e, 10029 KB
Info : Flash mapping 30: 0x11f19c0 -> 0x94fa28, 1942433 KB
Info : Flash mapping 31: 0x11f0000 -> 0x0, 1942433 KB
Info : Flash mapping 32: 0x563216ae -> 0x9cb500, 18374 KB
Info : Flash mapping 33: 0x9b7640 -> 0x20327106, 4194303 KB
Info : Flash mapping 34: 0x768e85f4 -> 0x5ce868, 9534 KB
Info : Flash mapping 35: 0x9ba8a0 -> 0x94ffcc, 1942519 KB
Info : Flash mapping 36: 0x20327106 -> 0xfffffffe, 1942433 KB
Info : Flash mapping 37: 0x5ce7a9 -> 0x9c72b8, 9949 KB
Info : Flash mapping 38: 0x11f1ae8 -> 0x9ba8a0, 9534 KB
Info : Flash mapping 39: 0x94fa90 -> 0x9b7640, 5990 KB
Info : Flash mapping 40: 0x11f19c0 -> 0x9b7640, 9534 KB
Info : Flash mapping 41: 0x768e87c0 -> 0x1, 0 KB
Info : Flash mapping 42: 0x9afed0 -> 0x94fa90, 0 KB
Info : Flash mapping 43: 0x94fa90 -> 0x9cb500, 9953 KB
Info : Flash mapping 44: 0x9c72c4 -> 0x9d77c0, 0 KB
Info : Flash mapping 45: 0x5ce152 -> 0x9bf058, 1960148 KB
Info : Flash mapping 46: 0x998f94 -> 0x9d7860, 9939 KB
Info : Flash mapping 47: 0x94fb74 -> 0x635a0e, 9926 KB
Info : Flash mapping 48: 0x630000 -> 0x11f1998, 0 KB
Info : Flash mapping 49: 0x17 -> 0x94fea8, 4102 KB
Info : Flash mapping 50: 0x11f1998 -> 0x614215, 18373 KB
Info : Flash mapping 51: 0x61421c -> 0x6141d4, 1942869 KB
Info : Flash mapping 52: 0x0 -> 0x0, 9535 KB
Info : Flash mapping 53: 0x77a31f3e -> 0x94ffcc, 0 KB
Info : Flash mapping 54: 0x11f1798 -> 0x17, 9535 KB
Info : Flash mapping 55: 0x603fa0 -> 0xb, 18373 KB
Info : Flash mapping 56: 0x4 -> 0x0, 18373 KB
Info : Flash mapping 57: 0x17 -> 0x94ff70, 4100 KB
Info : Flash mapping 58: 0xb -> 0x11f1798, 18375 KB
Info : Flash mapping 59: 0x0 -> 0x0, 0 KB
Info : Flash mapping 60: 0x0 -> 0x0, 3355443 KB
Info : Flash mapping 61: 0xcccccccc -> 0xcccccccc, 3355443 KB
Info : Flash mapping 62: 0xcccccccc -> 0xcccccccc, 3355443 KB
Info : Flash mapping 63: 0xcccccccc -> 0x2d99fad6, 0 KB
Info : Flash mapping 64: 0x1 -> 0x30, 0 KB
Info : Flash mapping 65: 0x11f1798 -> 0x0, 0 KB
Info : Flash mapping 66: 0xc0c068 -> 0x0, 0 KB
Info : Flash mapping 67: 0x0 -> 0x0, 0 KB
Info : Flash mapping 68: 0x0 -> 0x0, 0 KB
Info : Flash mapping 69: 0x0 -> 0x0, 0 KB
Info : Flash mapping 70: 0x0 -> 0x0, 0 KB
Info : Flash mapping 71: 0x0 -> 0x0, 0 KB
Info : Flash mapping 72: 0x4014e0 -> 0x4014e0, 9535 KB
Info : Flash mapping 73: 0x22e000 -> 0x4014e0, 4101 KB
Info : Flash mapping 74: 0x94ff80 -> 0x76720419, 2232 KB
Info : Flash mapping 75: 0x76720400 -> 0x94ffdc, 1960281 KB
Info : Flash mapping 76: 0x22e000 -> 0x2ec31cc2, 0 KB
Info : Flash mapping 77: 0x0 -> 0x22e000, 0 KB
Info : Flash mapping 78: 0x0 -> 0x0, 0 KB
Info : Flash mapping 79: 0x0 -> 0x0, 0 KB
Info : Flash mapping 80: 0x0 -> 0x0, 0 KB
Info : Flash mapping 81: 0x94ff8c -> 0x0, 9535 KB
Info : Flash mapping 82: 0x77a686d0 -> 0x59f871ae, 0 KB
Info : Flash mapping 83: 0x94ffec -> 0x77a565fd, 4194303 KB
Info : Flash mapping 84: 0x77a751c4 -> 0x0, 0 KB
Info : Flash mapping 85: 0x4014e0 -> 0x22e000, 0 KB
.pioinit:11: Error in sourced command file:
Remote communication error.  Target disconnected.: No error.

My connections:

JTAG ESP
3 → EN (RST)
4 → GND
5 → 12 (TDI)
7 → 14 (TMS)
9 → 13 (TCK)
13 → 15 (TDO)

I power the ESP through USB so I don’t connect the VTref. I also tried it with it, but it did not work.
I’m pretty sure that the wiring is correct, because it worked once.

manuelbl · November 14, 2019, 10:34am

The completely invalid flash mapping indicates that you either have a unreliably wiring between the Olimex and the ESP32 or that you are trying to use one of the GPIOs that is in fact reserved for the flash memory. So:

Check that the JTAG wiring makes good contact.
Disconnect everything except power supply and JTAG from the ESP32
Upload a simple blink sketch via USB

Then try again…

mietz · November 15, 2019, 10:04am

I rechecked the wiring and disconnected everything except for power and the JTAG. I then started a new project with nothing in it except for a line Serial.begin(115200). The good news is that I was able to step into the programm with 1000 khz adapter speed. Since it is super slow I tried to ramp up the speed to 2000 khz. With this speed it hangs up at:

esp32: Debug controller 0 was reset (pwrstat=0x5F, after clear 0x0F).
esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
esp32: Debug controller 1 was reset (pwrstat=0x5F, after clear 0x5F).
esp32: Core 1 was reset (pwrstat=0x5F, after clear 0x5F).
Info : Target halted. PRO_CPU: PC=0x5000004B (active)    APP_CPU: PC=0x00000000 
Target halted. PRO_CPU: PC=0x5000004B (active)    APP_CPU: PC=0x00000000 
Info : esp32: Core 0 was reset (pwrstat=0x1F, after clear 0x0F).
esp32: Core 0 was reset (pwrstat=0x1F, after clear 0x0F).
Info : Target halted. PRO_CPU: PC=0x40000400 (active)    APP_CPU: PC=0x40000400 
Target halted. PRO_CPU: PC=0x40000400 (active)    APP_CPU: PC=0x40000400 
** Programming Started **
auto erase enabled
** Programming Started **
auto erase enabled
Info : Target halted. PRO_CPU: PC=0x400916EE (active)    APP_CPU: PC=0x40000400 
Target halted. PRO_CPU: PC=0x400916EE (active)    APP_CPU: PC=0x40000400

When I increase the speed to 3000 khz, it generates these errors:

PlatformIO Unified Debugger -> http://bit.ly/pio-debug
PlatformIO: debug_tool = olimex-arm-usb-ocd-h
PlatformIO: Initializing remote target...
Open On-Chip Debugger  v0.10.0-esp32-20190708 (2019-07-08-11:04)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
adapter speed: 3000 kHz
Info : Configured 2 cores
esp32 interrupt mask on
Info : tcl server disabled
Info : telnet server disabled
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 3000 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).
Error: cpu0: esp32_fetch_all_regs (line 273): DSR (240069CA) indicates DIR instruction generated an exception!
Error: cpu0: esp32_fetch_all_regs (line 273): DSR (240069CA) indicates DIR instruction generated an overrun!
Error: Exception reading m2!

Info : Target halted. PRO_CPU: PC=0x00000000 (active)    APP_CPU: PC=0x00000000
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 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Debug controller 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : accepting 'gdb' connection from pipe
Error: No symbols for FreeRTOS
Info : esp32: Debug controller 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
Error: cpu0: esp32_fetch_all_regs (line 273): DSR (000000FC) indicates target still busy!
Error: cpu0: esp32_fetch_all_regs (line 273): DSR (000000FC) indicates DIR instruction generated an overrun!
Error: cpu0: esp32_fetch_all_regs (line 303): DSR (000000FC) indicates target still busy!
Error: cpu0: esp32_fetch_all_regs (line 303): DSR (000000FC) indicates DIR instruction generated an overrun!
Error: Exception reading scompare1!

Info : Target halted. PRO_CPU: PC=0x00000000 (active)    APP_CPU: PC=0x00000000
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 512 bytes at address 0x40090000, data - 1c, 20, f4, 3f, 24, 20, f4, 3f
Error: Failed to write stub section!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 5848 bytes at address 0x40090000, data - 00, 00, 09, 40, 00, 00, 09, 40
Error: failed to restore 5848 bytes of working area at address 0x40090000
Error: Failed to load stub (-4)!
Error: Algorithm run failed (-4)!
Error: Failed to run flasher stub (-4)!
Warn : Failed to get flash mappings (-4)!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 512 bytes at address 0x400916d8, data - 1c, 20, f4, 3f, 24, 20, f4, 3f
Error: Failed to write stub section!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 5848 bytes at address 0x400916d8, data - d8, 16, 09, 40, d8, 16, 09, 40
Error: failed to restore 5848 bytes of working area at address 0x400916d8
Error: Failed to load stub (-4)!
Error: Algorithm run failed (-4)!
Error: Failed to run flasher stub (-4)!
Warn : not enough working area available(requested 5847)
Error: no working area available, can't alloc space for stub code!
Error: Failed to load stub (-308)!
Error: Algorithm run failed (-308)!
Error: Failed to run flasher stub (-308)!
Error: Failed to probe flash, size 0 KB
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_map disable'.
Error: attempted 'gdb' connection rejected
Error: error during select: Unknown error
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 5848 bytes at address 0x40090000, data - 00, 00, 09, 40, 00, 00, 09, 40
Error: failed to restore 5848 bytes of working area at address 0x40090000
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_write_memory (line 807): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 5848 bytes at address 0x400916d8, data - d8, 16, 09, 40, d8, 16, 09, 40
Error: failed to restore 5848 bytes of working area at address 0x400916d8
Warn : Flash driver of esp32.flash does not support free_driver_priv()
Warn : Flash driver of irom does not support free_driver_priv()
Warn : Flash driver of drom does not support free_driver_priv()
.pioinit:15: Error in sourced command file:
Remote communication error.  Target disconnected.: No error.

So it is related to the adapter speed, but why? I used to use the Olimex JTag with Visual Studio and VisualGDB for a year without any bigger issues. Since VisualGDB is a little to expensive for hobbyists and platformio is a superb kit, I switched to platformio a while ago. Having these issues is really disappointing though

maxgerhardt · November 15, 2019, 12:45pm

So what adapter speed was VisualGDB using? They’re all using the same underlying adapter hardware and openocd software, so they should be equivalent when tested on the same board with the same wiring.

mietz · November 15, 2019, 4:26pm

Unfortunately also 20000 khz. I’m unable to test it now through VisualGDB cause my licence was not extended. It’s correct that the hardware wasn’t changed, but there are so many other possible causes which could lead to this issue.