2.0: Device not responding to setup address (IEC-447)

[clackups]

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

I'm trying to utilize esp_tinyusb 2.0 in a new project, using esp32s3:
https://github.com/clackups/esp_hid_serial_bridge/blob/763beec66d239f35071b8a6ff83b04f0c26a99ea/main/esp_hid_serial_bridge.c#L57

Dmesg messages on my linux host: first it was iin bootloader mode, then reset after flashing, then constant error messages, then booted back into bootloader.

Sat Dec 13 19:59:07 2025] usb 3-9: USB disconnect, device number 25
[Sat Dec 13 19:59:07 2025] usb 3-9: new full-speed USB device number 26 using xhci_hcd
[Sat Dec 13 19:59:07 2025] usb 3-9: New USB device found, idVendor=303a, idProduct=1001, bcdDevice= 1.01
[Sat Dec 13 19:59:07 2025] usb 3-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sat Dec 13 19:59:07 2025] usb 3-9: Product: USB JTAG/serial debug unit
[Sat Dec 13 19:59:07 2025] usb 3-9: Manufacturer: Espressif
[Sat Dec 13 19:59:07 2025] usb 3-9: SerialNumber: 74:4D:BD:A6:37:88
[Sat Dec 13 19:59:07 2025] cdc_acm 3-9:1.0: ttyACM0: USB ACM device
[Sat Dec 13 19:59:07 2025] usb 3-9: USB disconnect, device number 26
[Sat Dec 13 19:59:08 2025] usb 3-9: new full-speed USB device number 27 using xhci_hcd
[Sat Dec 13 19:59:09 2025] usb 3-9: device descriptor read/64, error -71
[Sat Dec 13 19:59:10 2025] usb 3-9: device descriptor read/64, error -71
[Sat Dec 13 19:59:10 2025] usb 3-9: new full-speed USB device number 28 using xhci_hcd
[Sat Dec 13 19:59:10 2025] usb 3-9: device descriptor read/64, error -71
[Sat Dec 13 19:59:11 2025] usb 3-9: device descriptor read/64, error -71
[Sat Dec 13 19:59:11 2025] usb usb3-port9: attempt power cycle
[Sat Dec 13 19:59:12 2025] usb 3-9: new full-speed USB device number 29 using xhci_hcd
[Sat Dec 13 19:59:12 2025] usb 3-9: Device not responding to setup address.
[Sat Dec 13 19:59:12 2025] usb 3-9: Device not responding to setup address.
[Sat Dec 13 19:59:13 2025] usb 3-9: device not accepting address 29, error -71
[Sat Dec 13 19:59:13 2025] usb 3-9: WARN: invalid context state for evaluate context command.
[Sat Dec 13 19:59:13 2025] usb 3-9: new full-speed USB device number 30 using xhci_hcd
[Sat Dec 13 19:59:13 2025] usb 3-9: Device not responding to setup address.
[Sat Dec 13 19:59:13 2025] usb 3-9: Device not responding to setup address.
[Sat Dec 13 19:59:13 2025] usb 3-9: device not accepting address 30, error -71
[Sat Dec 13 19:59:13 2025] usb 3-9: WARN: invalid context state for evaluate context command.
[Sat Dec 13 19:59:13 2025] usb usb3-port9: unable to enumerate USB device
[Sat Dec 13 19:59:14 2025] usb 3-9: new full-speed USB device number 31 using xhci_hcd
[Sat Dec 13 19:59:14 2025] usb 3-9: device descriptor read/64, error -71
[Sat Dec 13 19:59:15 2025] usb 3-9: device descriptor read/64, error -71
[Sat Dec 13 19:59:15 2025] usb 3-9: new full-speed USB device number 32 using xhci_hcd
[Sat Dec 13 19:59:16 2025] usb 3-9: device descriptor read/64, error -71
[Sat Dec 13 19:59:17 2025] usb 3-9: device descriptor read/64, error -71
[Sat Dec 13 19:59:17 2025] usb usb3-port9: attempt power cycle
[Sat Dec 13 19:59:18 2025] usb 3-9: new full-speed USB device number 33 using xhci_hcd
[Sat Dec 13 19:59:18 2025] usb 3-9: New USB device found, idVendor=303a, idProduct=1001, bcdDevice= 1.01
[Sat Dec 13 19:59:18 2025] usb 3-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sat Dec 13 19:59:18 2025] usb 3-9: Product: USB JTAG/serial debug unit
[Sat Dec 13 19:59:18 2025] usb 3-9: Manufacturer: Espressif
[Sat Dec 13 19:59:18 2025] usb 3-9: SerialNumber: 74:4D:BD:A6:37:88
[Sat Dec 13 19:59:18 2025] cdc_acm 3-9:1.0: ttyACM0: USB ACM device

I followed the initialization procedure as described in 2.0 migration guide, but something essential seems to be missing.

[github-actions]

Hi @clackups! Please be aware that the following suggestions are generated by a bot and haven't been fact-checked by Espressif Systems. We hope that this message will help you until an Espressif Engineer looks at your issue.

---

Based on the information provided and the referenced documentation, the issue you are experiencing—"Device not responding to setup address" and repeated USB enumeration failures—can be caused by several factors when using esp_tinyusb 2.0 on ESP32-S3.

Key Points from Espressif Documentation

1. Application Interference with USB Peripheral
   If your application reconfigures or disables the USB peripheral pins, or otherwise interferes with the USB stack, the device may disappear from the system or fail to enumerate. This can result in errors like device not responding to setup address or error -71 on the host.

   • Solution: Ensure your application does not reconfigure the USB pins or disable the USB peripheral after initialization. If this happens, you may need to manually enter download mode and erase the flash before reflashing a corrected application.
   • Reference: ESP32-S3 USB Troubleshooting

2. Startup Logic and Unstable USB Connection
   If the flash is empty, corrupted, or the application crashes on boot, the ESP32-S3 may continuously reset, causing the USB device to repeatedly connect and disconnect.

   • Solution: Manually boot into download mode before the first flash or after erasing flash, to ensure a stable connection. Alternatively, pre-flash a stable firmware via UART.
   • Reference: FAQ: USB Serial/JTAG Controller Issues

3. esp_tinyusb 2.0 Migration: External PHY Initialization
   In esp_tinyusb 2.0, external PHY is no longer initialized automatically. If your hardware uses an external PHY, you must explicitly initialize it and set phy.skip_setup = true in your tinyusb_config_t before calling tinyusb_driver_install().

   • Reference: esp_tinyusb 2.0 Breaking Changes

4. Default Descriptor Usage
   If you do not provide custom USB descriptors, ensure the relevant fields in tinyusb_config_t are set to NULL so the stack uses the defaults from menuconfig.

   • Reference: USB Device Stack Descriptor Configuration

Recommended Steps

• Double-check your application code to ensure you are not reconfiguring or disabling the USB peripheral or its pins after initialization.
• If using an external PHY, make sure you initialize it manually and set phy.skip_setup = true in your configuration.
• If the device is stuck in a reset loop (e.g., due to empty or invalid flash), manually enter download mode and flash a known-good firmware.
• Use default descriptors by setting the relevant fields in tinyusb_config_t to NULL if you are not providing custom ones.
• Power supply stability: Ensure your board is receiving stable 3.3V power, as power issues can also cause USB enumeration failures.

If you have already followed the migration guide and the above steps, but the issue persists, please provide details about your hardware setup (e.g., whether you use an external PHY) and your tinyusb_config_t initialization code.

---

References integrated above as per Espressif documentation. If you need further assistance, please share your initialization code and hardware details for more targeted troubleshooting.

[clackups]

My mistake: the task at line 1013 blocks everything else