tinyusb-integration
/tinyusb-integration
Use when integrating, porting, configuring, or debugging TinyUSB device, host, CDC, MSC, HID, MIDI, vendor class, descriptors, DCD, or USB enumeration issues
- Author
- easyzoom ↗
- Repository
- aix-skills ↗
- Licence
- MIT
- Last repository change
- 17.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 17.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when integrating, porting, configuring, or debugging TinyUSB device, host, CDC, MSC, HID, MIDI, vendor class, descriptors, DCD, or USB enumeration issues
Original author description
Use when integrating, porting, configuring, or debugging TinyUSB device, host, CDC, MSC, HID, MIDI, vendor class, descriptors, DCD, or USB enumeration issues
How it works
- Overview
- When To Use
- First Questions
- Integration Checklist
- Common Failures
- Verification
- Example
SKILL.md preview
--- name: tinyusb-integration description: Use when integrating, porting, configuring, or debugging TinyUSB device, host, CDC, MSC, HID, MIDI, vendor class, descriptors, DCD, or USB enumeration issues --- # TinyUSB Integration ## Overview Use this skill to integrate TinyUSB by separating board support, USB controller driver, descriptors, class drivers, interrupts, clocks, and endpoint buffers. USB bugs are often descriptor or controller-state problems before application logic. ## When To Use Use this skill when: - The user wants to add or debug TinyUSB on an MCU. - The issue involves USB enumeration, CDC serial, MSC, HID, MIDI, vendor class, device/host mode, descriptors, endpoints, DCD/HCD, or TinyUSB tasks. - The target needs a new MCU/board port or custom USB class configuration. Do not use this skill when board power, USB D+/D- wiring, or clock source is unverified. Use `hardware-interface-debug` first. ## First Questions Ask for: - MCU/board, USB controller, device/host mode, and TinyUSB version. - USB class: CDC, MSC, HID, MIDI, vendor, composite, or host stack. - RTOS/bare-metal runtime and where `tud_task`/host task runs. - USB clock source, VBUS detect, pull-up control, and interrupt routing. - Descriptors and `tusb_config.h`. - Host OS symptoms: no enumeration, code 10, repeated reset, missing COM port, wrong VID/PID, or transfer failure. ## Integration Checklist 1. Prove hardware prerequisites. USB clock, D+/D- wiring, VBUS, pull-up, ESD/protection, and connector orientation must be correct. 1. Configure `tusb_config.h`. Enable only needed roles/classes and set endpoint buffer sizes within RAM limits. 1. Verify descriptors. Device, configuration, interface, endpoint, string, VID/PID, class/subclass/protocol, and composite descriptors must agree. 1. Run TinyUSB task regularly. In bare metal or RTOS, ensure device/host task and interrupt handling are scheduled correctly. 1. Check class-specific behavior. CDC needs line coding/control; MSC needs safe block device hooks; HID needs report descriptors and polling interval. 1. Capture host evidence. Use OS device manager, `lsusb`, USB logs, or protocol analyzer when enumeration fails. ## Common Failures - USB clock is not exactly valid for the controller. - Descriptors report endpoint sizes or counts inconsistent with class config. - `tud_task` is not called regularly. - Composite descriptors have wrong interface association. - CDC appears but no data flows because callbacks are not handled. - MSC exposes a block device without safe read/write/sync policy. ## Verification Before claiming TinyUSB works: - State MCU, role, class, TinyUSB version, USB clock, and task/interrupt model. - Confirm host enumeration with VID/PID and class. - Confirm one class-specific transfer: CDC echo, HID report, MSC read/write, or vendor transfer. - Confirm descriptor consistency and endpoint allocation. - For MSC or firmware update classes, state data-loss safeguards. ## Example User: ```text TinyUSB CDC 插上电脑没有串口。 ``` Agent: 1. Asks for MCU, TinyUSB config, descriptors, USB clock, interrupt setup, and host OS logs. 1. Checks enumeration and descriptor consistency before CDC callbacks. 1. Verifies `tud_task` schedule and a CDC echo transfer.
Versions
The database has no other skills named tinyusb-integration.
Database snapshot: 13.11.2026 · package version 15060bd2a3f8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90esp32-usb-hid-report-contract
Use when designing, reviewing, debugging or validating usb hid report contract for ESP32 firmware; apply target-specific constraints, failure analysis and measurable verification before release. - 91usb-debugging
Diagnose embedded USB enumeration, descriptors, CDC/REPL ports and intermittent disconnects. Use when requests involve a missing USB device, wrong interface, native USB versus serial bridge, endpoint failures or conflicting monitors. - 90esp32-usb-cdc-throughput-budget
Use when designing, reviewing, debugging or validating usb cdc throughput budget for ESP32 firmware; apply target-specific constraints, failure analysis and measurable verification before release. - 100nrf52840-promicro
Firmware development for the ProMicro nRF52840 (V1940) — the nice!nano v2 compatible clone also sold as SuperMini nRF52840, nRF52840 Pro Micro or nRFMicro (nRF52840 QIAA, Cortex-M4F @ 64 MHz, 1 MB flash / 256 KB RAM, BLE 5 + 802.15.4, native USB, Adafruit UF2 bootloader with… - 100meddev-usb-medical
Implement safe USB device connectivity: class selection, enumeration handling, data validation, electrical and safety considerations. Use when working on usb medical in medical device software. - 100stm32f401rc-blackpill
Firmware development for the 40-pin "Black Pill"-format board with an STM32F401RCT6 (STM32F401RC, LQFP64, 256 KB flash, 64 KB RAM, 84 MHz) that ships with the WeAct Studio HID Bootloader (USB 0483:572A, flash 0x08000000-0x08003FFF, app at 0x08004000) — its PC13 LED, KEY button…