ESP32dev - PIO Unified Debugger - setup problem

[botofancalin]

@Nist3l

My os is windows 10. I think I’ve found some problems with FTDI drivers: the FT2232H mini module generates 4 USB-Serial converter instead of two. All of them have “usb migration problem”.
I’ve tried to reinstall the drivers with the latest one from FTDI website, but it doesn’t work. I am stuck because it does the same on other computers.
I’ve try to ask to FTDI support: lets see if they reply.

EDIT: I’ve found that you have to connect also V3V3 to VIO in the FT2232H Mini Module:
CN2, pins 1, 3 & 5 ----> CN2 pins 11 & 21 and CN3, pins 12 & 22
This solve the problem of the USB driver malfunction.

Anyway the debugger session doesn’t start: same messages as above: unable to open ftdi device…

Are you sure that’s a FT2232 minimodule? Maybe you have FT4232 minimodule.
Please read what’s written on the module chip.
They look very similar.

FT2232 minimodule:

FT4232 minimodule:

The FT2232 is detected as 2 USB2Serial converter and FT4232 is detected as 4 USB2Serial converter
They also have different VID/PID.
FT2232: VID_0403&PID_6010
FT4232: VID_0403&PID_6011 (as i remember…)
Those values can be changed using FtProg but i think is easier to adapt the openocd settings to work with FT4232.

To edit the settings, go to
c:\Users[Your User].platformio\packages\tool-openocd-esp32\share\openocd\scripts\interface\ftdi\esp32_devkitj_v1.cfg
and change the PID to the one detected on windows device manager (ex. 6011)

Please check the last post from this thread: ESP32 & PIO Unified Debugger - #19 by ivankravets

I posted there the detailed instructions for FTDI2232 minimodule setup on windows 10.

Please post the results.