OCD Failure to detect FTDI device (OCD-400)

[dsbonomi]

Environment

• Development Kit: ESP-WROVER-KIT (V4?)
• Module or chip used: ESP32-WROVER-E
• Debug Adapter: OnBoard FT2232HL
• OpenOCD version: v0.10.0-esp32-20210401
• Operating System: Win7 Pro 64bit
• Using an IDE?: vs_code and cmd line
• OpenOCD command line:openocd -d3 -f board/esp32-wrover-kit-3.3v.cfg
• JTAG Clock: default, esp32_devKitj_v1 sets adapterk khz to 20000. Probably not an Issue since not getting that far
• ESP-IDF version: v4.3

Problem Description

Steps to reproduce the behavior:

1. Copy and build HelloWorld
2. Press F-5
3. Wait for error messages
4. See error

Debug Logs

Attach verbose debug logs for OpenOCD and GDB. See item 3 here for how to generate verbose logs.

Expected behavior

A clear and concise description of what you expected to happen.

I expect OpenOCD to report finding the debug port, identifying the ESP32 under test, finding two processing elements and checking to see if the flash matches the elf image. and waiting at symbol app_main.

Screenshots

If applicable, add screenshots to help explain your problem.
Result from trying to Run from VSCode

Running Command Line

Device Manager, interface 0 with winusb driver

Zadig after changed driver, just to check version number on driver

Doctor Report
ErrorReportDoctorResult.txt

OCD Log
ErrorRptLog.txt

I believe that something is wrong between OpenOCD and the windows system management and it is not getting to see the devices involved. Running with Admin authority does not seem to affect the result. If libusb were not installed, I would expect a link error not a failure to get data.

[gerekon]

Hi @dsbonomi
Have you installed USB divers with IDF installer?

[dsbonomi]

Thank you for responding @gerekon
I believe I followed the instructions in step 6 of https://docs.espressif.com/projects/esp-idf/en/v4.3/esp32/api-guides/jtag-debugging/configure-ft2232h-jtag.html correctly. It says replace the FTDIBUS driver with the WinUSB driver for entry 0 in the Dual RS232-HS interface as I have done. This worked for me previously when using a JLINK device.
I do not recognize your reference to the "IDF Installer" with reference to USB drivers.

[gerekon]

I mean to use automatic IDF Tools installer https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/windows-setup.html#esp-idf-tools-installer. But not sure it was tested with Win7.

It says replace the FTDIBUS driver with the WinUSB driver for entry 0 in the Dual RS232-HS interface as I have done. This worked for me previously when using a JLINK device.

This should be enough. Have you tried to reboot?
According to your log OpenOCD can not find the device.

[dsbonomi]

@gerekon
I have rebooted several times. The issue does not clear on a reboot. I agree that the OCD Software is not finding the device. I do not know if going to "-d4" will provide any more information about the connection, I would expect detail information about commands but not connection strings. I have not read the code that is supposed to be getting a device list yet. I see several versions of libusb are available , and do not yet know which is operational on my system or how to discover that yet. I recall using a package that listed all loaded DLLs, but I do not recall the details.

I see that options are either a poor installation, or a non-standard responses from my system. My prior instantiation was on a work computer I no longer have access to so I cannot compare the organization of the device manage groupings. I can completely remove and re-install to adress the installation issue. I had to use the Offline version of the installer, as there was some fault in the online version getting an incomplete file I believe.

If there is a separate diagnostic tool to verify the jtag device path, I would like to hear about it.

Regards,

• • Scott Bonomi

[dsbonomi]

@gerekon
I have deleted and reloaded the entire esp-idf package and rerun the ESP-ID Extension initilization. Online Install had an issue reported there. a file needed for certificate checking was not found. I am still getting the message from mpsse_open(),in mpsse.c as called from ftdi_initialize() that says no matching device found.
This exactly matches the error strings when I tried running it with the FTDIBUS driver active.

[Jason2866]

Have you tried to reinstall the driver with zadig? I had the same issue. Everything looked good (same as yours) and it didnt worked.
It worked before. In the meantime there where some windows and other updates... After reinstalling with zadig it started working again.

[erhankur]

Closing due to inactivity.