PlatformIO and VScode. Error: unable to open ftdi

tombaier63 · January 23, 2026, 2:57pm

OK, I checked again all connection, and the ESP-Wrover module for wrong connections. But everything looks perfect. Any futher ideas?

I think about filing a bug report at Github…

maxgerhardt · January 23, 2026, 5:28pm

tombaier63:

#include <Arduino.h>

// put function declarations here:
int myFunction(int, int);

void setup() {
  // put your setup code here, to run once:
  int result = myFunction(2, 3);
}

void loop() {
  // put your main code here, to run repeatedly:
}

// put function definitions here:
int myFunction(int x, int y) {
  return x + y;
}

Have you preloaded this sketch onto the ESP32 via USB to make sure the current sketch is 100% not using any GPIO pins needed for JTAG?

tombaier63 · January 25, 2026, 8:38am

I preloaded an empty sketch, but can’t connect.

Setup

{}

Loop

{}

However, the esp-prog is now visible in my normal Win11 installation. In device manager you can display not only connected devices, but also legacy devices. I deleted a bunch of old stuff and now, the driver is found by PIO.

But still with errors shown above…

tombaier63 · January 30, 2026, 8:09am

I purchased a alternative JTAG debugger with a single FT232H device (https://medium.com/@manuel.bl/low-cost-esp32-in-circuit-debugging-dbbee39e508b) and run into the same problem.

This board has the VID/PID 0x0403 and x06014. I unloaded the driver with ZADIG 2.9 tool. I become crazy not having any idea what happen here.