USB and CherryUSB¶

SF32 devices expose USB hardware, and SiFli-SDK documentation and examples reference CherryUSB integration. Treat USB as a software stack, not only as a hardware feature.

USB work crosses firmware, descriptors, host operating systems, power behavior, and factory tooling. A device that enumerates once on a developer laptop is not finished.

Use Cases¶

• USB CDC serial.
• HID devices.
• MSC storage.
• USB audio microphone/speaker.
• MTP.
• USB host modes such as CDC, HID, MSC, UVC, and UAC where supported by the SDK and board.

Practical Workflow¶

1. Confirm the board exposes the required USB connector and power path.
2. Start from the closest SDK USB example.
3. Test enumeration on Windows, macOS, and Linux.
4. Verify suspend/resume and cable reconnect behavior.
5. Record VID/PID, descriptors, and driver expectations.

What to Test¶

• Cold plug and hot plug.
• Reset while connected.
• Host sleep/wake.
• Cable disconnect during transfer.
• Windows, macOS, and Linux enumeration.
• Composite device behavior if multiple classes are enabled.
• Power-only cable failure messaging in user docs.

Descriptor Checklist¶

• VID/PID ownership is clear.
• Product string is final or versioned.
• Serial number behavior is defined.
• Class/subclass/protocol values match the intended host driver.
• Composite interfaces are stable across firmware updates.

SDK Examples¶

The official SiFli-SDK CherryUSB example index separates USB-device and USB-host work. Start with the example that matches the intended USB role and class, then carry its descriptor, power, and host-compatibility checks into the product implementation.