On the host-side system, the gadget serial device looks like a CDC ACM compliant class device or a simple vendor specific device with bulk in and bulk out endpoints, and it is treated similarly to other serial devices. On the device-side Linux system, the gadget serial driver looks like a serial device. The gadget serial driver talks over USB to either a CDC ACM driver or a generic USB serial driver running on a host PC.

It runs on a Linux system that has USB device side hardware for example, a PDA, an embedded Linux system, or a PC with a USB development card. The gadget serial driver is a Linux USB gadget driver, a USB device side driver. and, also step by step procedure to test the Zynq® UltraScale+™ MPSoC USB 3.0 communication device class functionality on windows/Linux host machines. This section explains the CDC Abstract Control Model (ACM) Linux gadget driver details, how to configure the Linux source to support serial gadget driver for Zynq® UltraScale+™ MPSoC USB 3.0. Linux: Step by Step procedure for creating Zynq® UltraScale+™ MPSoC USB 3.0 controller’s communication device class functionality Setup to test the CDC functionality with Windows as well as Linux host machineįigure 1: Zynq ultrascale + MPSoC USB 3.0 CDC reference block diagram.

How to configure all the Zynq® ultrascale +™ MPSoC Linux kernel and dependent files for the CDC class reference.

The CDC design example block diagram and overview.

You can typically use it in applications like serial COM or UART communication This design covers: The CDC (ACM) class in the USB Component is used for data communication. This Tech Tip explains how to enable all the configuration options, step by step procedure to use the Zynq® UltraScale+™ MPSoC USB 3.0 controller in device mode and make use of bulk transfer type for a serial communication device abstraction using the USB 3.0. Zynq® UltraScale+™ MPSoC USB3.0 controller supports all four types of transfers. These transfer types are Control Transfer, Bulk Transfer, Isochronous transfer and Interrupt transfer. There are four primary types of communication defined by the USB protocol, based on which any required application can be built without changing the firmware or underlying hardware for different applications. An internal DMA engine is present in the controller and it utilizes the AXI master interface to transfer data.

The USB 3.0 DRD controller provides an eXtensible host controller interface (xHCI) to the system software through the advanced eXtensible interface (AXI) slave interface. Both can be individually configured to work as host or device at any given time. Summary The Zynq® UltraScale+™ MPSoC USB 3.0 controller consists of two independent dual-role device (DRD) controllers. Designed for ZCU102 Rev1.0 and RevB/C/D Prod silicon Boards Designed for ZCU102 Rev1.0 and RevB/C/D BoardsĢ.

Linux usb cdc acm driver