ESP32C5 USB JTAG appears in device manager while configured to JTAG pins (IDFGH-16847)

[FireDeveloper]

Answers checklist.

• I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
• I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

MCU: ESP32-C5
IDF: 5.5.1
Windows 11

I have configured the EFUSE_JTAG_SEL_ENABLE to 1.
According to the datasheet when IO 7 is pulled low, it will use the JTAG pins.

I shorted to ground and I am able to debug with external PROG on JTAG pad, but at the device manager it still appears a USB JTAG device.

I also tried to debug via this interface and failed (as expected, since pins are selected).
But is it normal to appear while not selected via IO7?

This is the error messages when trying to use it while not selected:

Info : esp_usb_jtag: serial (3C:DC:75:83:B6:74)
Info : esp_usb_jtag: Device found. Base speed 24000KHz, div range 1 to 255
Info : clock speed 24000 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.

[ginkgm]

@FireDeveloper

If I understand correctly, the efuse only control the mux close to CPU regarding which control lines are connected. It's possible that the sub-device inside the USJ module is not disabled (though not able to debug).

So you will need to specify the JTAG port yourself when there are two JTAG ports connected. Are you able to do that, or you want to report this as a feature missing of OpenOCD?