VSCode + Debug with ESP-EYE

[aaronp]

Hi,

I'm trying to debug the ESP-EYE board with vscode extension, but I'm not sure of how to do it. As far as I know, it can be debugged using the same microUSB connection, so no extra hardware is required.

I'm following this guide https://github.com/espressif/vscode-esp ... bugging.md, but pressing F5 does nothing.

Also, if I try to start OpenOCD manually, it says that:

Code: Select all

❌ Error: no device found❌ 
Error: unable to open ftdi device with vid 0403, pid 6010, description '*', serial '*' at bus location '*'
❌ Error: no device found
❌ Error: unable to open ftdi device with vid 0403, pid 6014, description '*', serial '*' at bus location '*'

Any clue of how to do it?

Thank you

[ESP_bignacio]

This is one of the first issues listed in the openOCD troubleshooting FAQ here:

https://github.com/espressif/openocd-es ... ooting-FAQ

Make sure you are setting the correct serial port in the extension settings (idf.port or idf.portWin in Windows) and configure drivers properly.

[aaronp]

I used the auto-installer to setup everything, and those drivers generated a COM5 port → I could flash properly. The problem is just when debugging.

I tried to change the drivers like in the guide (image attached), but all of them work worse: Not even a COM is generated.

Also, I'm not using ESP-WROVER-KIT but ESP-EYE (not explained there) and the device I get is not FT2232H, so I'm not sure if these steps apply to me. And when following the "generic steps" (https://docs.espressif.com/projects/esp ... -jtag.html) the JTAG pins from the ESP-EYE schematic doesn't seem connected to anywhere

[jamilu]

Hi all

What are the correct openocd parameters for the esp-eye? flash and monitor work. the opneocd gives the following error:
Error: esp_usb_jtag: co[OpenOCD]
could not find or open device!

Thank you for help

[ESP_bignacio]

Have you configure openOCD in the vscode extension ?

Make sure, if you are using Windows, to do the Zadig configuration as shown before or in this forum FAQs.

In the extension, check the debugging tutorial