Sen descrición

sakumisu 4ef4a9be98 add gitattributes %!s(int64=3) %!d(string=hai) anos
class 1cb56fe0ef replace ssize_t with int %!s(int64=3) %!d(string=hai) anos
common 6cf67c46f2 update malloc align size when use dcache %!s(int64=4) %!d(string=hai) anos
core b44617212b add usb host stack(class not release completely) %!s(int64=4) %!d(string=hai) anos
demo eb08bcc5a0 update hcd synopsys port, fix speed value when run HAL_HCD_HC_Init %!s(int64=3) %!d(string=hai) anos
docs f4ba2e47ca rename usb_stack to CherryUSB %!s(int64=4) %!d(string=hai) anos
osal 1868589843 check if in interrupt context %!s(int64=3) %!d(string=hai) anos
packet capture 051d127cdc add packet capture %!s(int64=4) %!d(string=hai) anos
port eb08bcc5a0 update hcd synopsys port, fix speed value when run HAL_HCD_HC_Init %!s(int64=3) %!d(string=hai) anos
tools eff1268057 add chryusb_configurator submodule %!s(int64=4) %!d(string=hai) anos
.clang-format 8a143df509 first commit %!s(int64=4) %!d(string=hai) anos
.gitattributes 4ef4a9be98 add gitattributes %!s(int64=3) %!d(string=hai) anos
.gitignore 406036f6d2 update ignore file %!s(int64=4) %!d(string=hai) anos
.gitmodules fefad911b3 specify the submodule chryusb_configurator branch %!s(int64=4) %!d(string=hai) anos
LICENSE 8a143df509 first commit %!s(int64=4) %!d(string=hai) anos
README.md f4ba2e47ca rename usb_stack to CherryUSB %!s(int64=4) %!d(string=hai) anos
README_zh.md f4ba2e47ca rename usb_stack to CherryUSB %!s(int64=4) %!d(string=hai) anos
SConscript f4ba2e47ca rename usb_stack to CherryUSB %!s(int64=4) %!d(string=hai) anos
usb_config.h b44617212b add usb host stack(class not release completely) %!s(int64=4) %!d(string=hai) anos

README.md

CherryUSB

中文版

CherryUSB is a tiny, beautiful and portable USB host and device stack for embedded system.

CherryUSB Directoy Structure

.
├── class
│   ├── audio
│   ├── cdc
│   ├── dfu
│   ├── hid
│   ├── hub
│   ├── midi
│   ├── msc
│   ├── tmc
│   └── video
├── common
├── core
├── demo
│   ├── bouffalolab
│   └── stm32
│   └── mm32
│   └── ch32
├── docs
├── osal
├── packet capture
└── port
    ├── bouffalolab
    │   └── bl702
    ├── ch32
    ├── ehci
    ├── fsdev
    ├── mm32
    ├── synopsys
    ├── musb
    └── template
Directory Description
class usb class driver
common usb spec macros and utils
core usb core implementation
demo different chip demo
osal os wrapper
docs doc for guiding
packet capture packet capture file
port usb dcd and hcd porting

CherryUSB Device Stack Overview

CherryUSB Device Stack provides a unified framework of functions for standard device requests, CLASS requests, VENDOR requests and custom special requests. The object-oriented and chained approach allows the user to quickly get started with composite devices without having to worry about the underlying logic. At the same time, a standard dcd porting interface has been standardised for adapting different USB IPs to achieve ip-oriented programming.

How CherryUSB Device Stack is implemented, this video will tell you: https://www.bilibili.com/video/BV1Ef4y1t73d .

CherryUSB Device Stack has the following functions:

  • Support USB2.0 full and high speed
  • Support endpoint irq callback register by users, let users do whatever they wants in endpoint irq callback.
  • Support Compound and Composite Device
  • Support Communication Device Class (CDC)
  • Support Human Interface Device (HID)
  • Support Custom human Interface Device (HID)
  • Support Mass Storage Class (MSC)
  • Support USB VIDEO CLASS (UVC)
  • Support USB AUDIO CLASS (UAC)
  • Support Device Firmware Upgrade CLASS (DFU)
  • Support USB MIDI CLASS (MIDI)
  • Support Test and Measurement CLASS (TMC)
  • Support Vendor class
  • Support WINUSB1.0、WINUSB2.0

CherryUSB Device Stack resource usage:

file FLASH (Byte) RAM (Byte)
usbd_core.c 3045 373
usbd_cdc.c 302 20
usbd_msc.c 2452 132
usbd_hid.c 784 201
usbd_audio.c 438 14
usbd_video.c 402 4

CherryUSB Host Stack Overview

The CherryUSB Host Stack has a standard enumeration implementation for devices mounted on roothubs and external hubs, and a standard interface for the different Class to indicate what the Class driver needs to do after enumeration and after disconnection. A standard hcd porting interface has also been standardised for adapting different USB IPs for IP-oriented programming. Finally, the protocol stack is managed using os, and provides osal to make a adaptation to different os.

How CherryUSB Host Stack is implemented, the video will be provided in future.

CherryUSB Host Stack has the following functions:

  • Automatic loading of supported Class drivers
  • Support blocking transfers and asynchronous transfers
  • Support Compound and Composite Device
  • Multi-level HUB support, expandable up to 7 levels
  • Support Communication Device Class (CDC)
  • Support Human Interface Device (HID)
  • Support Mass Storage Class (MSC)
  • Support Vendor class
  • Support Andriod AOA Communication

The CherryUSB Host stack also provides the lsusb function, which allows you to view information about all mounted devices, including those on external hubs, with the help of a shell plugin.

lsusb

CherryUSB Device API

More of USB Device API reference, please visit : CherryUSB Device API

CherryUSB Host API

More of USB Host API reference, please visit: CherryUSB Host API

How To Use In RT-Thread package

How to use in RT-Thread package, please visit:RT-Thread package Userguide with CherryUSB