esp-S3 USB keeps getting recognized in windows 11 as JTAG debug port even though it meant to be NCM (IEC-256)

[emaayan]

Answers checklist.

• I have read the documentation of the component in question and the issue is not addressed there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

when i upload a firmware that turns the USB jtag port into net USB NCM one, i have problem making look like a network device.
i need to always uninstall the driver so that windows would back to recognize it as espressif usb net driver (no need to manually install ncm device driver like windows 10)
how can i make this more streamlined so it would recognize it as net device driver? I'm using the default USB descriptors.
in the pic below i have 2 S3's connected to my machine, (they both have 2 usb ports, but only one of them is connected windows )

[peter-marcisovsky]

Hi @emaayan

I can confirm, that on Linux, the NCM device is recognized correctly, not like a JTAG Debug unit. We will try on Windows.

Did you try using esp32s2 for example? As it does not have USB Serial JTAG unit?

[emaayan]

Hi @emaayan

I can confirm, that on Linux, the NCM device is recognized correctly, not like a JTAG Debug unit. We will try on Windows.

Did you try using esp32s2 for example? As it does not have USB Serial JTAG unit?

no i mainly have s3, because i also wanted serial com repl features (for example to be able to change the IP of the internal LWIP)

[emaayan]

Hi @emaayan

I can confirm, that on Linux, the NCM device is recognized correctly, not like a JTAG Debug unit. We will try on Windows.

Did you try using esp32s2 for example? As it does not have USB Serial JTAG unit?

make sure to use win 11, win10 requires manual ncm driver install.