Versal devices include unique IP that require special consideration as follows:
- Include the Control, Interface, and Processing System (CIPS) IP in
The CIPS IP must be present in every Versal ACAP design, because this IP contains the platform management controller (PMC) required to boot and configure the device. If your design does not include CIPS IP, a post-link/pre-place DRC flags your design. For descriptions of the PMC and PS, see the Versal ACAP Technical Reference Manual (AM011). For information on CIPS IP, see the Control, Interface and Processing System LogiCORE IP Product Guide (PG352). For information on the CPM, see the Versal ACAP CPM CCIX Architecture Manual (AM016), Versal ACAP CPM Mode for PCI Express Product Guide (PG346), and Versal ACAP CPM DMA and Bridge Mode for PCI Express Product Guide (PG347).
- Configure the CPM controller, including GT selection, through the
For information, see the Versal ACAP CPM Mode for PCI Express Product Guide (PG346). The PL access to the PCIe® interface can be configured using the PCI Express® IP through the IP catalog. For more information on PCIe, see the following documents:
- Conduct upfront analysis and early validation of NoC resource
The NoC IP acts as a logical representation of the physical NoC. The Vivado IP integrator aggregates the connectivity and quality of service (QoS) information to form a unified traffic specification. For more information on the NoC and integrated memory controller IP and performance tuning see Versal ACAP Programmable Network on Chip and Integrated Memory Controller LogiCORE IP Product Guide (PG313).
- Use the Hard Block Planner to assign the DDRMC physical locations and
The hardened DDR memory controllers are integrated into the NoC IP. The NoC compiler selects a location for the DDRMC while aggregating design requirements. The physical assignments of the DDRMCs are adjusted appropriately during implementation.
- Limit SmartConnect to connections requiring AXI4-Lite or when supplementing the NoC when the NoC bandwidth is
fully consumed by the rest of the design or there are not enough NoC ports.
The NoC is the preferred method for moving data throughout the Versal device. For more information, see the SmartConnect LogiCORE IP Product Guide (PG247).
- Use block automation in the IP integrator to assist with
connections between IP and the GTs.
You must use this approach because Versal IP that use GT resources no longer integrate the GT components in the IP. Alternatively, these connections can be stitched manually by configuring, instancing, and connecting the IP directly in the RTL. For an overview of creating a design with GT parent IP, see this link in the Versal ACAP Transceivers Wizard LogiCORE IP Product Guide (PG331).
- Configure the Versal ACAP
transceivers using the ACAP Transceivers Wizard IP.
Use the Hard Block Planner to assign the physical locations of the GT quads in Versal ACAP designs. For information on the Hard Block Planner, see the Vivado Design Suite User Guide: I/O and Clock Planning (UG899). For information on the full GT quad layout and supported configuration options, see the Versal ACAP GTY and GTYP Transceivers Architecture Manual (AM002).
- Use the Bridge IP to connect custom IP to the Versal ACAP GT quads.