EZ-USB™ FX20: USB3 Vision (U3V) application

This code example demonstrates the implementation of a USB3 Vision device streaming image data using Infineon's EZ-USB™ FX20 device.

Note: This code example is applicable for EZ-USB™ FX20, EZ-USB™ FX10, and EZ-USB™ FX5 devices.

View this README on GitHub.

Provide feedback on this code example.

Requirements

ModusToolbox™ v3.5 or later (tested with v3.5)
Board support package (BSP) minimum required version: 4.3.3
Programming language: C

Supported toolchains (make variable 'TOOLCHAIN')

GNU Arm® Embedded Compiler v11.3.1 (GCC_ARM) – Default value of TOOLCHAIN
Arm® Compiler v6.22 (ARM)

Supported kits (make variable 'TARGET')

EZ-USB™ FX20 DVK (KIT_FX20_FMC_001) – Default value of TARGET

Hardware setup

This example uses the board's default configuration. See the kit user guide to ensure that the board is configured correctly. The example demonstrates the implementation of a U3V compliant camera application using the Titanium Ti180 J484 Development Kit as the video source.

Note: Titanium Ti180 J484 Development Kit is used for demonstration purpose only. The Ti180 FPGA bitfiles listed in Table 7 (see Section FPGA BitFile information) supports up to 4K (3840 x 2160) colorbar video streaming.

Software setup

See the ModusToolbox™ tools package installation guide for information about installing and configuring the tools package.

Install a terminal emulator if you do not have one. Instructions in this document use Tera Term.

Install a USB3 Vision host application such as eBUS Player or Aravis to view the video stream.

Using the code example

Create the project

The ModusToolbox™ tools package provides the Project Creator as both a GUI tool and a command line tool.

Use Project Creator GUI

Open the Project Creator GUI tool

There are several ways to do this, including launching it from the dashboard or from inside the Eclipse IDE. For more details, see the Project Creator user guide (locally available at {ModusToolbox™ install directory}/tools_{version}/project-creator/docs/project-creator.pdf)
On the Choose Board Support Package (BSP) page, select a kit supported by this code example. See Supported kits

Note: To use this code example for a kit not listed here, you may need to update the source files. If the kit does not have the required resources, the application may not work
On the Select Application page:

a. Select the Applications(s) Root Path and the Target IDE

Note: Depending on how you open the Project Creator tool, these fields may be pre-selected for you

b. Select this code example from the list by enabling its check box

Note: You can narrow the list of displayed examples by typing in the filter box

c. (Optional) Change the suggested New Application Name and New BSP Name

d. Click Create to complete the application creation process

Use Project Creator CLI

The 'project-creator-cli' tool can be used to create applications from a CLI terminal or from within batch files or shell scripts. This tool is available in the {ModusToolbox™ install directory}/tools_{version}/project-creator/ directory.

Use a CLI terminal to invoke the 'project-creator-cli' tool. On Windows, use the command-line 'modus-shell' program provided in the ModusToolbox™ installation instead of a standard Windows command-line application. This shell provides access to all ModusToolbox™ tools. You can access it by typing "modus-shell" in the search box in the Windows menu. In Linux and macOS, you can use any terminal application.

The following example clones the "EZ-USB™ FX20: USB3 Vision Application" example with the desired name "USB3_Vision" configured for the KIT_FX20_FMC_001 BSP into the specified working directory, C:/mtb_projects:

project-creator-cli --board-id KIT_FX20_FMC_001 --app-id mtb-example-fx20-usb3vision --user-app-name USB3_Vision --target-dir "C:/mtb_projects"

The 'project-creator-cli' tool has the following arguments:

Argument	Description	Required/optional
`--board-id`	Defined in the field of the BSP manifest	Required
`--app-id`	Defined in the field of the CE manifest	Required
`--target-dir`	Specify the directory in which the application is to be created if you prefer not to use the default current working directory	Optional
`--user-app-name`	Specify the name of the application if you prefer to have a name other than the example's default name	Optional

Note: The project-creator-cli tool uses the git clone and make getlibs commands to fetch the repository and import the required libraries. For details, see the "Project creator tools" section of the ModusToolbox™ tools package user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mtb_user_guide.pdf).

Open the project

After the project has been created, you can open it in your preferred development environment.

Eclipse IDE

If you opened the Project Creator tool from the included Eclipse IDE, the project will open in Eclipse automatically.

For more details, see the Eclipse IDE for ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mt_ide_user_guide.pdf).

Visual Studio (VS) Code

Launch VS Code manually, and then open the generated {project-name}.code-workspace file located in the project directory.

For more details, see the Visual Studio Code for ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mt_vscode_user_guide.pdf).

Command line

If you prefer to use the CLI, open the appropriate terminal, and navigate to the project directory. On Windows, use the command-line 'modus-shell' program; on Linux and macOS, you can use any terminal application. From there, you can run various make commands.

For more details, see the ModusToolbox™ tools package user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mtb_user_guide.pdf).

Using this code example with specific manufacturer part numbers (MPNs)

By default, the code example build is targeted for the CYUSB4024-BZXI MPN, which has 512 KB of flash memory and 1024 KB of buffer RAM. Use the BSP Assistant tool to modify the application to target different EZ-USB™ FX20, EZ-USB™ FX10, EZ-USB™ FX5N, or EZ-USB™ FX5 family MPNs as shown in Table 1.

Note: This application utilizes the Quad SPI interface on the EZ-USB™ FX device and hence is not supported on CYUSB4022-FCAXI, CYUSB4012-FCAXI, CYUSB3282-FCAXI, and CYUSB3082-FCAXI devices. It also requires more than 512 KB of DMA buffer RAM and hence is not supported on the CYUSB3081-FCAXI device.

Table 1. MPNs supported by this code example

Part Number	Family	Flash size (KB)	Buffer RAM size (KB)
CYUSB4024-BZXI	FX20	512	1024
CYUSB4021-FCAXI	FX20	512	1024
CYUSB4014-FCAXI	FX10	512	1024
CYUSB4013-FCAXI	FX10	512	1024
CYUSB4011-FCAXI	FX10	512	1024
CYUSB3284-FCAXI	FX5N	512	1024
CYUSB3084-FCAXI	FX5	512	1024
CYUSB3083-FCAXI	FX5	512	1024

Setup for a different MPN

Perform the following steps to modify the code example to work on a different MPN, as listed in Table 1:

Launch the BSP Assistant tool:

a. Eclipse IDE: Launch the BSP Assistant tool by navigating to Quick Panel > Tools

b. Visual Studio Code: Select the ModusToolbox™ extension from the left menu bar and launch the BSP Assistant tool, which is available in the Application menu of the MODUSTOOLBOX TOOLS section
In BSP Assistant, select Devices from the tree view on the left
Choose the desired part from the dropdown menu on the right
Click Save to close the BSP Assistant tool
Build the application and proceed with programming

Operation

Connect the board (J2) to your PC using the provided USB cable
Connect the USB FS port (J3) on the board to the PC for debug logs
Open a terminal program and select the serial COM port. Set the serial port parameters to 8N1 and 921600 baud
Browse the <CE Title>/BitFiles/ folder for Ti180 FPGA binary and program the FPGA. For more details, see the J484 kit user guide
After successful programming, switch off the FPGA DVK power, connect the FPGA (Titanium Ti180 J484 Development Kit) DVK to the FMC (J8) connector of the KIT_FX20_FMC_001 board, and switch on the FPGA DVK power
Perform the following steps to program the board using the EZ-USB™ FX Control Center (Alpha) application
1. To enter Bootloader mode:
  
  a. Press and hold the PMODE (SW2) switch
  
  b. Press and release the RESET (SW3) switch
  
  c. Release the PMODE switch
2. Open the EZ-USB™ FX Control Center application. Observe the EZ-USB™ FX20 device displayed as EZ-USB™ FX Bootloader
3. Select the EZ-USB™ FX Bootloader device in EZ-USB™ FX Control Center
4. Click Program > Internal Flash
5. Navigate to the <CE Title>/build/APP_KIT_FX20_FMC_001/Release folder within the CE directory and locate the .hex file and program. Confirm if the programming is successful in the log window of the EZ-USB™ FX Control Center application
After programming, the application starts automatically. Confirm the following title is displayed on the UART terminal

Figure 1. Terminal output on program startup
Open any third party USB3 Vision application such as eBUS Player. Select the EZ-USB™ FX20 device and video resolution to stream video. By default, the device streams 4K (3840 x 2160 ~60 fps) video data

Debugging

Using the Arm® debug port

If you have access to a MiniProg or KitProg3 device, you can debug the example to step through the code.

In Eclipse IDE

Use the <Application Name> Debug (KitProg3_MiniProg4) configuration in the Quick Panel. For details, see the "Program and debug" section in the Eclipse IDE for ModusToolbox™ user guide.

In other IDEs

Follow the instructions in your preferred IDE.

Log messages

The code example and the EZ-USB™ FX20 stack output debug log messages indicate any unexpected conditions and highlight the performed operations.

By default, the USB FS port is enabled for debug logs. To enable debug logs on UART, set the USBFS_LOGS_ENABLE compiler flag to '0u' in the Makefile file. SCB1 of the EZ-USB™ FX20 device is used as UART with a baud rate of 921600 to send out log messages through the P8.1 pin.

The verbosity of the debug log output can be modified by setting the DEBUG_LEVEL macro in the main.c file with the values shown in Table 2.

Table 2. Debug values

Macro value	Description
1u	Enable only error messages
2u	Enable error and warning messages
3u	Enable error, warning, and info messages
4u	Enable all message types

Design and implementation

This code example demonstrates the implementation of the USB3 Vision Class specification, enabling the EZ-USB™ FX20 device to function as a USB3 Vision-compliant device.

I2C master to configure the video source
U3V specific command/response are handled in U3V device library
Enable debug prints over CDC using the USBFS block on the EZ-USB™ FX20 device

Features

This code example demonstrates the following capabilities of the EZ-USB™ FX20 device:

The usage of the EZ-USB™ FX20 APIs to implement a standard USB3 Vision device. This includes:
- Handling the device control interface (DCI) commands at the application level
- Streaming video data at USB 3.2 Gen2 speeds (4K video stream at ~60 fps) from the SIP to USB endpoint
  - USB specification: USB 3.2 Gen2/Gen1 and USB 2.0 (HS only)
  - Video formats: YUV422_8, YUV422_8_UYVY, and MON16
  - Video resolutions: 3840 x 2160 (4K), 1920 x 1080 (1080p), 1280 x 720 (720p), and 640x480 (VGA)
Interface with FPGA using LVDS or LVCMOS to receive the video data
I2C interface to configure the FPGA control registers to set the video stream parameters
(Optional) in-memory data transfer mode enables video stream in the absence of an FPGA
Option to support init-time configuration of FPGA in x4 passive serial mode using the serial memory interface (SMIF) block

This application is designed to be executed by the Cortex®-M4 core of the FX20 device. The Cortex®-M0+ core of the device is only used to start the Cortex®-M4 core – it then enters the Deep Sleep state.

The code to be executed by Cortex®-M0+ to start Cortex®-M4 and enter Deep Sleep is provided in the binary embedded into the Cm0Code array defined in the cm0_code.c source file, and is linked into the final application. The linker script used to generate the application binary ensures that this Cortex®-M0+ startup code is placed at the beginning of the flash region used by the application, followed by the Cortex®-M4 code at an offset of 1 KB.

Application workflow

The application flow involves four main steps:

Initialization
USB device enumeration
U3V Protocol implementation
U3V data transfer

Initialization

During initialization, the following steps are performed:

All the required data structures are initialized
USBD and USB driver (CAL) layers are initialized
The application registers all descriptors supported by function/application with the USBD layer
The application registers callback functions for different events, such as RESET, SUSPEND, RESUME, SET_CONFIGURATION, SET_INTERFACE, SET_FEATURE, and CLEAR_FEATURE. USBD calls the respective callback function when the corresponding events are detected
The data transfer state machines are initialized
The application registers handlers for all relevant interrupts
When default settings are used, the FX device resets the Ti180 FPGA and waits until it configures itself. If FPGA configuration using FX is enabled, FPGA is configured using the SMIF (in x4 or Quad mode) block to read the bitfile stored in the external flash. The FPGA configures itself by passively receiving the bitstream being read from QSPI memory
FPGA is initialized using I2C writes to FPGA registers
The application initializes the SIP block on the EZ-USB™ FX20 as required based on the compile-time configuration
U3V device library is initialized with device configurations and register base addresses
Application makes the USB device visible to the host by calling the Connect API

USB device enumeration

During USB device enumeration, the host requests for descriptors, which are already registered with the USBD layer during the initialization phase
The host sends SET_CONFIGURATION and SET_INTERFACE commands to activate the required function in the device
After the SET_CONFIGURATION and SET_INTERFACE commands, the application task takes control and enables the endpoints for data transfer

U3V Protocol implementation

U3V protocol is being handled by U3V library. U3V library implements DCI and DSI state machine as per U3V Specification.

U3V library supports the following:

Supports 16 bytes payload size alignment
Minimum and maximum U3V leader and trailer size supported is 64 and 32 bytes respectively
Supports a single Device Streaming Interface (DSI) video channel

Note: The current version of this application is limited in its capabilities and does not include support for the Device Event Interface (DEI) and supports only mandatory features of U3V specification.

U3V XML Features

The U3V XML supports following features as per GenICam:

Device Control
Image Format Control
Acquisition Control
Transport Layer Control

U3V data transfer

DCI Interface

The U3V device’s DCI interface is designed to support two distinct endpoints: In and Out
DCI's Out endpoint is utilized by the host to transmit a command packet to the device, while its In endpoint is employed by the device to send an acknowledgment packet back to the host in response to the command packet received
All the U3V commands are handled in the U3V device library. As soon as the host U3V application (like eBus Player) opens, it sends commands to the FX20 device over the USB DCI command endpoint. The FX device responds to these commands over the USB DCI response endpoint
This response information is used by the host U3V application for its configuration as per device supported features

DSI Interface

The U3V device’s DSI interface is designed to support one In endpoint
When the video streaming is started by the host application, a DSI start command is received and the DMA channel is enabled to receive data from the SIP
After the streaming DMA channel is enabled, the DMA ready flag on the SIP interface asserts and the FPGA data source starts streaming the video data to the EZ-USB™ FX20 device
The video data moves from the LVDS/LVCMOS subsystem to SRAM through high-bandwidth DMA
The data is forwarded on the EP 3-In, based on the active USB connection speed. DataWire DMA channels are used for USBHS transfers while high bandwidth DMA channels are used for USBSS transfers
Video data moves from USB device Bulk endpoint-In to the host U3V application

Modes of USB3 Vision leader and trailer addition

Each USB3 Vision video frame is preceded by a leader and followed by a trailer. The following modes of leader and trailer addition are supported and can be selected through compile time options:

Firmware insertion of leader and trailer: FPGA sends a zero-length packet on the SIP ingress path where required and the firmware replaces this with a 52-byte leader or a 32-byte trailer as appropriate
FPGA insertion of leader and trailer: In this case, the FPGA sends the pre-formatted leader and trailer packets along with the actual video data. The DMA data path on EZ-USB™ FX can be configured to forward the data automatically with no firmware intervention, achieving higher data rates. This mode is selected by setting the FPGA_ADDS_HEADER compiler flag in makefile to '1'
FX hardware based insertion of leader and trailer: The SIP of the EZ-USB™ FX device supports automatic insertion of metadata packets with a user-specified format into the datastream. This mode can be used to format and insert the USB3 Vision leader and trailer into the video stream. This feature can be used when dynamic information such as hardware-derived timestamps need to be added to the leader and/or trailer packets. The FPGA needs to send a special command to trigger the insertion of the leader or trailer. The DMA datapath can function with no firmware intervention as the metadata insertion is done by the SIP hardware block. This mode is selected by setting the INMD_EN compiler flag in makefile to '1'

Note: Metadata-based U3V leader/trailer insertion is only supported by specific FPGA bitfiles which use the LVDS interface to connect to EZ-USB™ FX.

FPGA Interface

Slave FIFO interface

The code example uses a WideLink synchronous slave FIFO interface with 2-bit FIFO addressing when configured in LVCMOS mode. The slave FIFO interface connections are:

Table 3. Control signal usage in LVCMOS Slave FIFO state machine

EZ-USB™ FX pin	Function	Description
P0CLK	PCLK	LVCMOS clock
P0CTL0	SLCS#	Active low chip select signal. Asserted (low) by the master/FPGA when communicating with the EZ-USB™ FX device
P0CTL1	SLWR#	Active low write enable signal. Asserted (low) by the master/FPGA when sending any data to the EZ-USB™ FX device
P0CTL2	SLOE#	Active low output enable signal
P0CTL3	SLRD#	Active low read enable signal. Not used in this application as data is only being received by the EZ-USB™ FX device
P0CTL5	FlagA	Active low DMA ready indication for currently addressed/active thread
P0CTL6	Link Ready	Active high link ready indication. FPGA can start link training when this signal is high
P0CTL7	PKTEND#	Active low packet end signal. Asserted (low) when the FPGA/master wants to terminate the ongoing DMA transfer
P0CTL9	A0	LS bit of 2-bit address bus used to select thread (applicable for Port 0 narrow link)
P0CTL8	A1	MS bit of 2-bit address bus used to select thread (applicable for Port 0 narrow link)

LVDS Interface

The code example uses a WideLink configuration with 16 data lanes when LVDS mode is selected. The LVDS interface operates with a 148.5 MHz clock and 8:1 gearing ratio. While no control signals are required for the operation of the LVDS interface itself, a pair of signals are used to signal the device state to the FPGA as shown in Table 4.

Table 4. Control signal usage for the LVDS interface

EZ-USB™ FX pin	Function	Description
P0CTL5	FlagA	Active low DMA ready indication for currently addressed/active thread
P0CTL6	Link Ready	Active high link ready indication; FPGA can start PHY training when this signal is high

FPGA configuration

FPGA configuration on the J484 development kit

The Ti180 FPGA configures itself by reading data from the on-board SPI flash memory on the J484 Development Kit. The bitfile used in this application can be programmed to the J484 kit using the Efinity Programmer tool. For more details, see the J484 kit user guide.

On every bootup, the EZ-USB™ FX device uses the INT_RESET pin to reset the FPGA and causes it to load the bitfile from the SPI flash memory. Once the Ti180 FPGA has configured itself, it will assert the CDONE pin high to indicate the configuration is complete. The FX application waits until high status is detected on the CDONE pin before moving to the next steps.

Table 5. GPIO for checking FPGA configuration on KIT_FX20_FMC_001 DVK

EZ-USB™ FX20 pin	Function	Description
P4_3	INT_RESET#	Active low signal. EZ-USB™ FX device asserts to reset the FPGA
P4_4	CDONE#	Active high signal. FPGA asserts when the configuration is complete

FPGA configuration on EZ-USB™ FX20 USB MIPI camera demo kit

This code example can be adapter to work on the FX20 USB MIPI camera demo kit where the FPGA bitfile is stored on a Quad SPI (QSPI) flash memory connected to the FX20 device. In this case, the FPGA is configured in Passive Serial mode while FX20 reads the bitfile content from the QSPI memory.

Programming FPGA bitfile on the EZ-USB™ FX20 USB MIPI camera demo kit

The FPGA binary can be programmed to the external flash on the EZ-USB™ FX20 DVK using the EZ-USB™ FX20 USB Bootloader. Perform the following steps to program the binary file to the external flash.

Note: The following steps are assuming that the device is pre-programmed with the EZ-USB™ FX20 USB Bootloader.

Switch the FX20 device into bootloader mode by resetting it while keeping the PMODE switch pressed
Launch the EZ-USB™ FX Control Center application and select the EZ-USB FX BOOTLOADER device
Select Program > External SPI Flash from the menu bar and and browse to the FPGA bitfile in bin format
Wait until programming is completed and verify the status

FPGA configuration in passive serial mode

To enable FPGA configuration in passive serial mode with EZ-USB™ FX, set FPGA_CONFIG_EN in Makefile to 1.

FPGA configuration can be performed using the SMIF block of FX. SMIF (in x4 or Quad mode) interface is used for downloading the FPGA configuration binary on every bootup. FPGA binary files supports passive serial x4 configuration mode.

Steps to configure FPGA (in passive serial x4 mode):

EZ-USB™ FX device deasserts the INT_RESET pin
EZ-USB™ FX device starts sending dummy SMIF (in x4 or Quad mode) clock to read the FPGA bitfile from the SPI flash
FPGA listens to the data on the SMIF lines and configures itself
FPGA asserts CDONE# when configuration is complete

Table 6. GPIOs used for configuring FPGA on FX20 USB MIPI camera demo kit

EZ-USB™ FX20 pin	Function	Description
P4_4	CDONE#	Active high signal; FPGA asserts when FPGA configuration is complete
P4_3	INT_RESET#	Active low signal; the EZ-USB™ FX device asserts to reset the FPGA
P6_4	PROG#	Active low FPGA program signal

FPGA bitfile information

Table 7. bitfile description

Bitfile	Description	Supported features
fxn_ti180_dvk_multi_cam_ref_des_lvds_wl_148m.hex	LVDS Wide Link	LVDS wide link, single thread, FPGA added header
fxn_ti180_dvk_multi_cam_ref_des_lvds_wl_148m_inmd.hex	LVDS Wide Link	LVDS wide link, single thread, metadata insertion
fxn_ti180_dvk_multi_cam_ref_des_lvcmos_ddr.hex	LVCMOS Wide Link	LVCMOS wide link, single and interleaved threads, FPGA added header

On-Device video generation

This code example supports on-device generation of a colorbar video pattern so the USB3 Vision stream can be tested with the standalone KIT_FX20_FMC_001 in the absence of an FPGA development kit. Two methods of video generation are supported.

Link loopback mode (LVDS interface)

This uses a loopback feature of the SIP where one port can receive data sent by the other port through an internal connection. The operation of the receiving port will be the same as in the case of the video data being received from an FPGA.

Loopback program (video data and control bytes) is stored in HBWSS SRAM
Data is moved by Thread 3 to Port 1 through DMA and GPIF
Link level loopback is enabled so the data generated by Port 1 is received by Port 0
Data moves from Port 0 to USB 3.x Bulk endpoint-In through GPIF and DMA
Data moves from device the Bulk endpoint-In to the host UVC application

Firmware generated (in-memory) mode

In this case, the application firmware fills a set of RAM buffers with the colorbar pattern and transfers them to the USB host in the correct sequence based on the USB3 Vision protocol.

A set of memory buffers are allocated in the high-bandWidth RAM region and pre-filled with USB3 Vision leader and trailer as well as the colorbar data
A DMA channel of type memory-to-IP is created to send data from these memory buffers to the USB host
When the command to start video streaming is received, video streaming is started by queuing requests to send data from these buffers
Data moves from the device Bulk endpoint-In to the host UVC application
When DMA consume events indicating the completion of transfer from each buffer are received, firmware queues additional transfer requests on the endpoint to maintain a continuous data flow

Compile-time configurations

This application's functionality can be customized by setting variables in Makefile or by configuring them through make CLI arguments.

Run the make build command or build the project in your IDE to compile the application and generate a USB bootloader-compatible binary. This binary can be programmed onto the EZ-USB™ FX20 device using the EZ-USB™ Control Center application
Run the make build BLENABLE=no command or set the variable in Makefile to compile the application and generate the standalone binary. This binary can be programmed onto the EZ-USB™ FX20 device through the SWD interface using the OpenOCD tool. For more details, see the EZ-USB™ FX20 SDK user guide
Choose between the Arm® Compiler or the GNU Arm® Embedded Compiler build toolchains by setting the TOOLCHAIN variable in Makefile to ARM or GCC_ARM respectively. If you set it to ARM, ensure to set CY_ARM_COMPILER_DIR as a make variable or environment variable, pointing to the path of the compiler's root directory
Run the make build LPBK_EN=yes command or set the variable in Makefile to make the application use an internally-generated colorbar pattern for streaming instead of an external video source. This configuration can be used on the EZ-USB™ FX20 DVK without requiring any additional boards or connections

Note: The internal data path used for this function has throughput limitations and can only support about 48 frames per second of a 4K video stream. Using an external video source is required to achieve the data rates enabled by the USB 3.2 Gen2 data connection.

Run the make build FWGEN=yes command or set the variable in Makefile to make the application use an internally-stored colorbar pattern for streaming instead of an external video source. This configuration can be used on the EZ-USB™ FX20 DVK without requiring any additional boards or connections and without using the SIP block of EZ-USB™ FX

By default, the application is configured to receive data from a 32-bit wide LVCMOS interface in DDR mode and make a USB 3.2 Gen2x2 (20 Gbps) data connection. Additional settings can be configured through macros specified by the DEFINES variable in Makefile:

Table 8. Macro descriptions

Macro name	Description	Allowed values
`USB_CONN_TYPE`	Choose USB connection speed from a set of options	`CY_USBD_USB_DEV_SS_GEN2X2` for USB 3.2 Gen2x2 `CY_USBD_USB_DEV_SS_GEN2` for USB 3.2 Gen2x1 `CY_USBD_USB_DEV_SS_GEN1X2` for USB 3.2 Gen1x2 `CY_USBD_USB_DEV_SS_GEN1` for USB 3.2 Gen1x1 `CY_USBD_USB_DEV_HS` for USB 2.0 HS `CY_USBD_USB_DEV_FS` for USB 1.1 FS
`LVDS_LB_EN`	Enable link loopback	'1u' to enable link loopback '0u' to disable link loopback
`LVCMOS_EN`	Select the LVCMOS/LVDS	'1u' for LVCMOS '0u' for LVDS
`INTERLEAVE_EN`	Enable thread interleave Port 0	'1u' to enable thread interleaving on Port 0 '0u' to select a single thread
`FPGA_ENABLE`	Select FPGA as data source	'1u' if FPGA is interfaced to the EZ-USB™ FX20 '0u' to disable the FPGA interface
`FPGA_ADDS_HEADER`	UVC header addition	'1u' for FPGA added header '0u' for EZ-USB™ FX20 added header
`INMD_EN`	Insert metadata	'1u' to enable insert metadata '0u' to disable insert metadata
`USBFS_LOGS_ENABLE`	Enable debug logs through USBFS port	'1u' for debug logs over USBFS '0u' for debug logs over UART (SCB1)
`U3V_INMEM_EN`	Enable in-memory data transfers	'1u' to enable in-mem data transfers '0u' to disable in-mem data transfers
`FPGA_CONFIG_EN`	Enable FPGA configuration	'1u' to enable FPGA configuration by the FX device '0u' to disable FPGA configuration using the FX device

Application files

Table 9. Application file description

File	Description
cy_u3v.a	U3V device library file contains U3V command/response handling
cy_u3v_interface.h	C Header file contains functions, structures,enums supported by U3V device library
cy_gpif_header_lvcmos.h	Generated header file for GPIF state configuration for LVCMOS interface
cy_gpif_header_lvds.h	Generated header file for GPIF state configuration for LVDS interface
cy_usb_app.c	C source file implementing U3V 1.0 application logic
cy_usb_app.h	C Header file for application data structures and functions declaration
cy_u3v_xml.c	C source file contains the HEX data for Camera Description File
cy_u3v_xml.h	C Header file contains macros for Camera Description File
cy_u3v_device_config.c	C source file contains U3V device configurations structures
cy_u3v_device_config.h	C Header file contains macros for U3V device configuration
cy_usb_u3v_device.h	C Header file with U3V application constants and the video frame configurations
cy_usb_descriptors.c	C source file containing the USB descriptors
main.c	Source file for device initialization, ISRs, LVCMOS/LVDS interface initialization, etc.
cy_usb_i2c.c	C source file with I2C handlers
cy_usb_i2c.h	Header file with I2C application constants and the function definitions
cy_usb_qspi.c	C source file with SMIF handlers and FPGA configuration functions
cy_usb_qspi.h	Header file with SMIF application constants and the function definitions
cy_video_inmem.c	C source file which implements the logic for streaming video from memory
cm0_code.c	CM0 initialization code
Makefile	GNU make compliant build script for compiling this example

Related resources

Resources	Links
Application notes	AN237841 – Getting started with EZ-USB™ FX20/FX10/FX5N/FX5
Code examples	Using ModusToolbox™ on GitHub
Device documentation	EZ-USB™ FX20 datasheets
Development kits	Select your kits from the Evaluation board finder
Libraries on GitHub	mtb-pdl-cat1 – Peripheral Driver Library (PDL)
Middleware on GitHub	usbfxstack – USBFX Stack middleware library and documents
Tools	ModusToolbox™ – ModusToolbox™ software is a collection of easy-to-use libraries and tools enabling rapid development with Infineon MCUs for applications ranging from wireless and cloud-connected systems, edge AI/ML, embedded sense and control, to wired USB connectivity using PSOC™ Industrial/IoT MCUs, AIROC™ Wi-Fi and Bluetooth® connectivity devices, XMC™ Industrial MCUs, and EZ-USB™/EZ-PD™ wired connectivity controllers. ModusToolbox™ incorporates a comprehensive set of BSPs, HAL, libraries, configuration tools, and provides support for industry-standard IDEs to fast-track your embedded application development

Other resources

Infineon provides a wealth of data at www.infineon.com to help you select the right device, and quickly and effectively integrate it into your design.

Document history

Document title: CE240864 – EZ-USB™ FX20: USB3 Vision Application

Version	Description of change
1.0.0	New code example

All referenced product or service names and trademarks are the property of their respective owners.

The Bluetooth® word mark and logos are registered trademarks owned by Bluetooth SIG, Inc., and any use of such marks by Infineon is under license.

PSOC™, formerly known as PSoC™, is a trademark of Infineon Technologies. Any references to PSoC™ in this document or others shall be deemed to refer to PSOC™.

© Cypress Semiconductor Corporation, 2025. This document is the property of Cypress Semiconductor Corporation, an Infineon Technologies company, and its affiliates ("Cypress"). This document, including any software or firmware included or referenced in this document ("Software"), is owned by Cypress under the intellectual property laws and treaties of the United States and other countries worldwide. Cypress reserves all rights under such laws and treaties and does not, except as specifically stated in this paragraph, grant any license under its patents, copyrights, trademarks, or other intellectual property rights. If the Software is not accompanied by a license agreement and you do not otherwise have a written agreement with Cypress governing the use of the Software, then Cypress hereby grants you a personal, non-exclusive, nontransferable license (without the right to sublicense) (1) under its copyright rights in the Software (a) for Software provided in source code form, to modify and reproduce the Software solely for use with Cypress hardware products, only internally within your organization, and (b) to distribute the Software in binary code form externally to end users (either directly or indirectly through resellers and distributors), solely for use on Cypress hardware product units, and (2) under those claims of Cypress's patents that are infringed by the Software (as provided by Cypress, unmodified) to make, use, distribute, and import the Software solely for use with Cypress hardware products. Any other use, reproduction, modification, translation, or compilation of the Software is prohibited.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CYPRESS MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS DOCUMENT OR ANY SOFTWARE OR ACCOMPANYING HARDWARE, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. No computing device can be absolutely secure. Therefore, despite security measures implemented in Cypress hardware or software products, Cypress shall have no liability arising out of any security breach, such as unauthorized access to or use of a Cypress product. CYPRESS DOES NOT REPRESENT, WARRANT, OR GUARANTEE THAT CYPRESS PRODUCTS, OR SYSTEMS CREATED USING CYPRESS PRODUCTS, WILL BE FREE FROM CORRUPTION, ATTACK, VIRUSES, INTERFERENCE, HACKING, DATA LOSS OR THEFT, OR OTHER SECURITY INTRUSION (collectively, "Security Breach"). Cypress disclaims any liability relating to any Security Breach, and you shall and hereby do release Cypress from any claim, damage, or other liability arising from any Security Breach. In addition, the products described in these materials may contain design defects or errors known as errata which may cause the product to deviate from published specifications. To the extent permitted by applicable law, Cypress reserves the right to make changes to this document without further notice. Cypress does not assume any liability arising out of the application or use of any product or circuit described in this document. Any information provided in this document, including any sample design information or programming code, is provided only for reference purposes. It is the responsibility of the user of this document to properly design, program, and test the functionality and safety of any application made of this information and any resulting product. "High-Risk Device" means any device or system whose failure could cause personal injury, death, or property damage. Examples of High-Risk Devices are weapons, nuclear installations, surgical implants, and other medical devices. "Critical Component" means any component of a High-Risk Device whose failure to perform can be reasonably expected to cause, directly or indirectly, the failure of the High-Risk Device, or to affect its safety or effectiveness. Cypress is not liable, in whole or in part, and you shall and hereby do release Cypress from any claim, damage, or other liability arising from any use of a Cypress product as a Critical Component in a High-Risk Device. You shall indemnify and hold Cypress, including its affiliates, and its directors, officers, employees, agents, distributors, and assigns harmless from and against all claims, costs, damages, and expenses, arising out of any claim, including claims for product liability, personal injury or death, or property damage arising from any use of a Cypress product as a Critical Component in a High-Risk Device. Cypress products are not intended or authorized for use as a Critical Component in any High-Risk Device except to the limited extent that (i) Cypress's published data sheet for the product explicitly states Cypress has qualified the product for use in a specific High-Risk Device, or (ii) Cypress has given you advance written authorization to use the product as a Critical Component in the specific High-Risk Device and you have signed a separate indemnification agreement.
Cypress, the Cypress logo, and combinations thereof, ModusToolbox, PSoC, CAPSENSE, EZ-USB, F-RAM, and TRAVEO are trademarks or registered trademarks of Cypress or a subsidiary of Cypress in the United States or in other countries. For a more complete list of Cypress trademarks, visit www.infineon.com. Other names and brands may be claimed as property of their respective owners.

License

Infineon/mtb-example-fx20-usb3vision

About

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages