Parameter Changes
The Video Timing Controller v6.2 is updated to remove arbitrary resolutions from Video Mode parameter in GUI and allow default configuration of standard resolutions when the AXI4-Lite interface is not used. For any non-standard resolution, AMD recommends using the Custom option.
The VTC v5.00.a added parameters for configuring the core in constant mode, thus the core can be initialized to generate timing after reset without a processor or software.
Port Changes
The VTC v5.00.a removed all GPP interface ports. The VTC v4.00.a.0 added the ability to operate on video frame sizes up to 8192 x 8192. Previous versions supported 4096 x 4096 maximum. If the maximum sizes of 8192 are selected, some GPP ports are 13 bits wide where on previous versions of the core, these ports were 12 bits.
The VTC v4.00.a also added the ability to detect and generate vertical signals with a horizontal offset. To report the horizontal start cycle of these vertical signals, the VTC v4.00.a added the following new ports:
-
gen_v0blank_hstart -
gen_v0blank_hend -
gen_v0sync_hstart -
gen_v0sync_hend -
det_v0blank_hstart -
det_v0blank_hend -
det_v0sync_hstart -
det_v0sync_hend
Other Changes
- Migrating to the AXI4-Lite Interface
- The VTC v4.00.a changed from the PLB processor interface to the AXI4-Lite interface. As a result, all of the PLB-related connections have been replaced with an AXI4-Lite interface. For more information, see the Vivado Design Suite: AXI Reference Guide (UG1037).
- Functionality Changes
- The VTC v6.2 added the ability to operate on video frame sizes up to 65,536 x 65,536. Previous versions supported 8192 x 8192 maximum.
- Special Considerations When Migrating to AXI
- The VTC v3.0 added the support for the AXI4-Lite interface with this version. When using the VTC v3.0, the core name changed from "timebase" to "axi_vtc." All software driver functions, data structures and filenames also changed from a "xtimebase" prefix to "xvtc" prefix.