Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/espressif/openocd-esp32/issues/174 below:

OCD Failure to detect FTDI device (OCD-400) · Issue #174 · espressif/openocd-esp32 · GitHub

• 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

Steps to reproduce the behavior:

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

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

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.

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.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4