What does a USB device controller do?
It implements the device side of the USB protocol so an SoC can present itself as a peripheral to a host computer — handling enumeration, endpoint management and data transfer.
PRODUCT · FAMILY 01
AXI USB 2.0 Device IP
A USB 2.0 device controller with an AXI interface, for SoCs that need to appear as a USB peripheral to a host. The AXI side means it drops into a standard SoC interconnect rather than requiring a bridge.
WHAT IT IS
The short version.
USB device connectivity is one of those requirements that arrives late and is assumed to be simple. It is not especially difficult, but it is specified in detail, it has to enumerate correctly against a range of host stacks, and the endpoint configuration has to match what the application actually needs.
This core implements the device side of USB 2.0 with an AXI host interface, so integration into a standard SoC interconnect does not require an intermediate bridge. Endpoint configuration is parameterised to the application.
It is used where a product presents itself to a computer — instrumentation, industrial equipment with a service interface, consumer devices, and any design where firmware update or bulk data transfer happens over a cable.
DETAIL
Characteristics
| Parameter | Detail |
|---|---|
| Standard | USB 2.0, device role |
| Host interface | AXI |
| Endpoints | Configurable to the application |
| Delivery | Synthesisable RTL with integration documentation and verification collateral |
| Typical markets | Consumer, industrial, embedded, instrumentation |
Maturity — silicon-proven, FPGA-validated or RTL stage — is confirmed at enquiry for the specific configuration you need, rather than claimed generically here.
APPLICATIONS
Where it is used.
- Instrumentation — bulk data transfer to a host computer for analysis.
- Industrial equipment — service, configuration and diagnostic interfaces.
- Firmware update over cable — a recovery path that does not depend on the network.
- Consumer devices — standard host connectivity without a discrete controller.
- Data loggers — offloading captured data at the end of a run.
- Development and bring-up interfaces — host access during characterisation.
WHAT YOU RECEIVE
Deliverables and support.
- Synthesisable RTL with configured endpoint structure.
- Integration documentation covering the AXI interface and endpoint configuration.
- Verification collateral for integration-level testing.
- Engineering support through integration, enumeration testing and bring-up.
Next step
Send the target node, the interface requirements and the integration context. If this is not the right fit, that will be said early rather than discovered at integration.
COMMON QUESTIONS
Questions asked before an evaluation.
Why an AXI interface?
So the core connects directly into a standard SoC interconnect without an intermediate bridge, which removes both an area cost and an integration step.
KEEP READING
Related work.
BUILD WITH FASTSTREAM
Bring us the difficult part.
Tell us the specification, the constraint and the deadline. Programmes that cross silicon, radio, embedded and AI are where Faststream is strongest.