T2M provides highly configurable USB 3.2 OTG/Dual Role Controller IP Core Our Host, Device, Hub are Silicon Realized and also USB IF certified by our customers. T2M provides highly configurable and scalable USB 3 2 OTG/Dual Role controller IP Core for wide range of applications .
USB 3.2 OTG controller are designed for compliance with USB 2.0
specification Revision 2 0 and all associated ECN’s and USB OTG EH 2 Revision 1.1a and all associated ECN’s While operating in Host mode, based on configuration selected, it is compliant with xHCI enabling standard Windows, Linux, Android drivers to be reused minimizing software development overheads and associated risks involved with custom bare metal driver solutions Its Physical interface is compliant with USB Pipe Specification v 4 3 (for SS/SSP lane rates) and ULPI+ or 8 16 bits UTMI PLUS Level 3 specification (for HS/FS/LS mode) The system interface is compliant with either AHB and/or AXI interface allowing easy integration Optional custom bridges can be bundled as a service offering Additionally, while operating in host mode, USB 3 2 OTG controller can be configured to support either one device connected directly to its port, or multiple devices connected via hubs.
USB 3.2 OTG controller, while operating in device mode, can optionally include a proprietary high performance DMA engine for moving USB payloads The register interface of the DMA Engine is very simple allowing device side class specific function drivers to be implemented easily Reference mass storage class device side function drivers are made available to all licensees All buffering associated with the DMA Engine are configurable based on latency and performance requirements.
USB 3.2 OTG controller while operating in device mode can optionally include a proprietary EP 0 processor block for managing all Standard Requests directed to the control endpoint minimizing software development overhead Class and Vendor specific requests directed to Control endpoint are routed via the DMA engine to software for processing .
Optionally, the controller can be provided with no DMA Engine and no buffering and operates in a cut through mode forwarding and receiving USB payloads and managing only the USB protocol Customer may in this case implement its own differentiated DMA Engine Optionally, a simple transmit and receive buffer is included in this configuration which can be accessed by software over the slave
register access interface which is typically AHB This option results in very low footprint hardware which can be used in cases where the software can completely manage the USB traffic including the sequencing of the USB transactions .