TinyUSB is an open-source cross-platform USB Host/Device stack for embedded system, designed to be memory-safe with no dynamic allocation and thread-safe with all interrupt events are deferred then handled in the non-ISR task function. Check out the online documentation for more details.
. ├── docs # Documentation ├── examples # Sample with Makefile build support ├── hw │ ├── bsp # Supported boards source files │ └── mcu # Low level mcu core & peripheral drivers ├── lib # Sources from 3rd party such as freeRTOS, fatfs ... ├── src # All sources files for TinyUSB stack itself. ├── test # Unit tests for the stack └── tools # Files used internally
TinyUSB is funded by
Supports multiple device configurations by dynamically changing USB descriptors, low power functions such like suspend, resume, and remote wakeup. The following device classes are supported:
- Audio Class 2.0 (UAC2)
- Bluetooth Host Controller Interface (BTH HCI)
- Communication Device Class (CDC)
- Device Firmware Update (DFU): DFU mode (WIP) and Runtime
- Human Interface Device (HID): Generic (In & Out), Keyboard, Mouse, Gamepad etc ...
- Mass Storage Class (MSC): with multiple LUNs
- Musical Instrument Digital Interface (MIDI)
- Network with RNDIS, Ethernet Control Model (ECM), Network Control Model (NCM)
- Test and Measurement Class (USBTMC)
- Video class 1.5 (UVC): work in progress
- Vendor-specific class support with generic In & Out endpoints. Can be used with MS OS 2.0 compatible descriptor to load winUSB driver without INF file.
- WebUSB with vendor-specific class
If you have a special requirement, usbd_app_driver_get_cb() can be used to write your own class driver without modifying the stack. Here is how the RPi team added their reset interface raspberrypi/pico-sdk#197
- Human Interface Device (HID): Keyboard, Mouse, Generic
- Mass Storage Class (MSC)
- Communication Device Class: CDC-ACM
- Vendor serial over USB: FTDI, CP210x
- Hub with multiple-level support
Similar to the Device Stack, if you have a special requirement, usbh_app_driver_get_cb() can be used to write your own class driver without modifying the stack.
- Power Delivery 3.0 (PD3.0) with USB Type-C support (WIP)
- Super early stage, only for testing purpose
- Only support STM32 G4
TinyUSB is completely thread-safe by pushing all Interrupt Service Request (ISR) events into a central queue, then processing them later in the non-ISR context task function. It also uses semaphore/mutex to access shared resources such as Communication Device Class (CDC) FIFO. Therefore the stack needs to use some of the OS's basic APIs. Following OSes are already supported out of the box.
- No OS
- FreeRTOS
- RT-Thread: repo
- Mynewt Due to the newt package build system, Mynewt examples are better to be on its own repo
Following CPUs are supported, check out Supported Devices for comprehensive list of driver, features for each CPU.
| Manufacturer | Family | ||
|---|---|---|---|
| Allwinner | F1C100s/F1C200s | ||
| Analog | MAX3421E (usb host shield) | ||
| Brigetek | FT90x | ||
| Broadcom | BCM2711, BCM2837 | ||
| Dialog | DA1469x | ||
| Espressif | ESP32 S2, S3 | ||
| GigaDevice | GD32VF103 | ||
| Infineon | XMC4500 | ||
| MicroChip | SAM | D11, D21, D51, E5x, G55, L2x, E7x, S7x, V7x | |
| PIC | 24, 32mm, 32mk, 32mx, 32mz, dsPIC33 | ||
| Mind Montion | mm32 | ||
| NordicSemi | nRF52833, nRF52840, nRF5340 | ||
| Nuvoton | NUC 120, 121, 125, 126, 505 | ||
| NXP | iMXRT | RT10xx, RT11xx | |
| Kinetis | KL, K32L2 | ||
| LPC | 11u, 13, 15, 17, 18, 40, 43, 51u, 54, 55 | ||
| MCX | N9 | ||
| Raspberry Pi | RP2040 | ||
| Renesas | RX | 63N, 65N, 72N | |
| RA | 4M1, 4M3, 6M1, 6M5 | ||
| Silabs | EFM32GG12 | ||
| Sony | CXD56 | ||
| ST STM32 | F0, F1, F2, F3, F4, F7, H7, G0, G4, L0, L1, L4, L4+ U5, WB | ||
| TI | MSP430, MSP432E4, TM4C123 | ||
| ValentyUSB | eptri | ||
| WCH | CH32F20x, CH32V307, | ||
- Info
- Reference
- Contributing
All TinyUSB sources in the src folder are licensed under MIT
license, the Full license is here. However, each file can be
individually licensed especially those in lib and hw/mcu folder.
Please make sure you understand all the license term for files you use
in your project.