USB CDC 无法连接CH343 (ESF-244)

[Kevincoooool]

Port

ESP32

Target chip

ESP32-S3

Hardware Configuration

USB可以正常连接ESP32S3内置USB并进行下载，CP2102也可以，就是CH343不行,VID=0x1A86, PID=0x55D3

Log output

'usb_cdc_acm_port: Serial state notif 0x0010
I (11162) usb_cdc_acm_port: Serial state notif 0x0010
I (11210) usb_cdc_acm_port: Serial state notif 0x0000
I (11311) usb_cdc_acm_port: Serial state notif 0x0000
W (11410) cdc_acm: TX transfer timeout
W (11610) cdc_acm: TX transfer timeout
W (11810) cdc_acm: TX transfer timeout
W (12010) cdc_acm: TX transfer timeout
W (12210) cdc_acm: TX transfer timeout
W (12410) cdc_acm: TX transfer timeout
W (12610) cdc_acm: TX transfer timeout
W (12810) cdc_acm: TX transfer timeout
W (13010) cdc_acm: TX transfer timeout
W (13210) cdc_acm: TX transfer timeout
E (13210) HAL_OfflineBurner: 连接目标设备失败: 2
ESP_ERROR_CHECK failed: esp_err_t 0x103 (ESP_ERR_INVALID_STATE) at 0x42020d2f
--- 0x42020d2f: cdc_acm_host_close at F:/GitHub_My/KSDIY_Korvo/ESP_TOOL_S3/LVGL_Framwork_demo/managed_components/espressif__usb_host_cdc_acm/cdc_acm_host.c:675
file: "./managed_components/espressif__usb_host_cdc_acm/cdc_acm_host.c" line 675
func: cdc_acm_host_close
expression: usb_host_interface_release(p_cdc_acm_obj->cdc_acm_client_hdl, cdc_dev->dev_hdl, cdc_dev->notif.intf_desc->bInterfaceNumber)

abort() was called at PC 0x40381e23 on core 0
--- 0x40381e23: _esp_error_check_failed at F:/Espressif/frameworks/esp-idf-v5.4.2/components/esp_system/esp_err.c:49'''


Backtrace: 0x4037a0ed:0x3fcbfaf0 0x40381e2d:0x3fcbfb10 0x4038955e:0x3fcbfb30 0x40381e23:0x3fcbfba0 0x42020d2f:0x3fcbfbd0 0x4201f700:0x3fcbfbf0 0x42012527:0x3fcbfc10
--- 0x4037a0ed: panic_abort at F:/Espressif/frameworks/esp-idf-v5.4.2/components/esp_system/panic.c:469
--- 0x40381e2d: esp_system_abort at F:/Espressif/frameworks/esp-idf-v5.4.2/components/esp_system/port/esp_system_chip.c:87
--- 0x4038955e: abort at F:/Espressif/frameworks/esp-idf-v5.4.2/components/newlib/abort.c:38
--- 0x40381e23: _esp_error_check_failed at F:/Espressif/frameworks/esp-idf-v5.4.2/components/esp_system/esp_err.c:49
--- 0x42020d2f: cdc_acm_host_close at F:/GitHub_My/KSDIY_Korvo/ESP_TOOL_S3/LVGL_Framwork_demo/managed_components/espressif__usb_host_cdc_acm/cdc_acm_host.c:675
--- 0x4201f700: loader_port_esp32_usb_cdc_acm_deinit at F:/GitHub_My/KSDIY_Korvo/ESP_TOOL_S3/LVGL_Framwork_demo/managed_components/espressif__esp-serial-flasher/port/esp32_usb_cdc_acm_port.c:241

More Information

No response

[github-actions]

Hi @Kevincoooool! Please be aware that (1) the following suggestions are generated by a bot and haven't been fact-checked by Espressif Systems, (2) burning eFuses and enabling security features are irreversible operations and can damage your ESP32 device. We hope that this message will help you until an Espressif Engineer looks at your issue.

---

Thanks for the detailed report. Based on the logs and your setup, here’s how to proceed and what to check.

What’s happening

• Your ESP32-S3 is acting as a USB Host and talking to a CH343 USB–UART (VID 0x1A86, PID 0x55D3) via the CDC-ACM host driver. You see serial state notifications, but every transmit attempt times out, and then closing the device hits ESP_ERR_INVALID_STATE in cdc_acm_host_close(). This matches a TX timeout condition handled in recent driver updates. [USB Host CDC].
• CH34x/CH343 devices are “CDC-like” vendor-specific. Espressif’s CDC-ACM host component supports such devices via the VCP example/stack (it auto-loads the right sub-driver for CP210x, FTDI, CH34x, etc.). Using the generic CDC example with a vendor-specific device can lead to open/transfer issues like timeouts. [VCP example; USB Host CDC].

Recommended fixes and checks

1. Use the VCP example and registry drivers for CH34x

• Build and run the cdc_acm_vcp example (it auto-detects CP210x/FTDI/CH34x and loads the right driver). This is the supported path for CH343-class devices. [VCP example; USB Host Examples].

2. Update the CDC-ACM host component

• The component has fixes for TX timeout handling and descriptor parsing that can affect vendor devices. Please update to the latest version from the Component Registry. Notable fixes are mentioned in 2.0.3 and later. [USB Host CDC 2.0.3; USB Host CDC].

3. Open the device with flexible matching

• When only one device is on the bus, use CDC_HOST_ANY_VID/PID to let the driver match CDC-like devices more robustly, as suggested by the component docs. [USB Host CDC].

4. Follow host stack requirements

• Ensure usb_host_install() is called and a dedicated FreeRTOS task is servicing USB events (required for host mode stability). [Hardware connections].

5. Power and cabling

• Provide a stable external power source to the target device; many boards’ USB connectors can’t power attached peripherals reliably in Host mode. Use a good-quality USB cable and (if applicable) an OTG adapter. [Hardware connections].

6. Handle close/uninstall errors gracefully

• The error you hit (ESP_ERR_INVALID_STATE during cdc_acm_host_close) can occur if the interface was already released/disconnected underneath. Add error checks around close and tolerate ESP_ERR_INVALID_STATE to avoid aborts while you stabilize the link. Recent component versions also improve multi-threaded close handling. [USB Host CDC 2.0.3].

If you need a quick validation path

• Try the cdc_acm_vcp example unmodified, connect the CH343, and watch the monitor: it should enumerate and receive data in the handle_rx callback. If this succeeds, the issue is likely with using the plain CDC example or older component. [VCP example; USB Host Examples].

Notes/limitations

• CDC-like devices may not support all CDC control APIs. Avoid calling unsupported requests (e.g., send_break) unless confirmed supported by the VCP driver for CH34x. [USB Host CDC].
• Baud rate settings on the host side are part of the line coding for UART bridges; the plain CDC device on ESP chips ignores line coding, but VCP drivers translate it for the bridge ICs. [CDC host example].

If the problem persists after:

• updating to latest usb_host_cdc_acm,
• switching to the cdc_acm_vcp example,
• confirming proper power and USB host task setup,

please share:

• Driver/component version,
• Exact API sequence (open, set line coding, tx),
• Full USB descriptors (you can fetch CDC functional descriptors via the new helper), and
• Whether CDC_HOST_ANY_VID/PID changes behavior. [USB Host CDC 2.0.3].

[Dzarda7]

Hello @Kevincoooool, thanks for the report and testing such a recent feature. CH343 is not officially supported by usb_host_ch34x_vcp. But it might work, did you try CH340? If CH340 works and CH343 I will discuss with colleagues if it can be added. If CH340 does not work, we will fix it. If you can, please test with CH340, I do not have one laying around now, but will try to investigate it.