Support request: Add TinyUSB support for ESP32-C5 (RISC-V Wi-Fi 6 MCU)

[Cheveryluis]

Hello, and thanks for all the work on this project.

I'm using the new ESP32-C5 from Espressif, which is based on a RISC-V core and includes USB Full Speed capability. At the moment TinyUSB supports ESP32-S2/S3/C3, but the C5 is not yet listed.

I'd like to ask if support for the ESP32-C5 is planned or currently under development. If not, is there any guidance or starting point to help bring up a new ESP32 chip using the existing ESP-IDF TinyUSB integration?

Any information about the expected timeline, required contributions, or technical considerations would be very helpful.

Thank you!

[HiFiPhile]

TinyUSB doesn't support C2 or C5, they can't be supported as their USB peripheral is non-programmable who only does serial/JTAG.

6 people clicked thumb up yet none checked datasheet 🤷

[Cheveryluis]

Thanks for the clarification — however, I think there may be some misunderstanding.

TinyUSB has already added MCU definitions for the ESP32-C5 in PR #3217, titled “Add ESP32-C5 and ESP32-C61 definitions”.
This PR was merged recently and explicitly includes:

“For future MAX USB host support.”

This doesn’t mean the C5 USB peripheral is fully supported today, but it does indicate that TinyUSB maintainers consider the C5 a valid MCU target and have prepared the necessary identifiers for future USB functionality (whether device, host, or both, depending on what becomes possible in ESP-IDF).

So while the C5 may not have complete USB support at the moment, the upstream project is actively preparing for it, and the chip is not being treated as “unsupported” or “impossible to support.”

Just sharing this for accuracy — and thanks again to everyone contributing and helping clarify the current state of support.

[HiFiPhile]

That's only a placeholder in case new MCU will be released with a real USB controller.

So while the C5 may not have complete USB support at the moment, the upstream project is actively preparing for it, and the chip is not being treated as “unsupported” or “impossible to support.”

What you mean ? As I've already said C5's USB peripheral is non-programmable.