AMD Vivado™ Design Entry & Implementation

Logic synthesis supports the latest synthesizable constructs consistent with industry standards:

• SystemVerilog, Verilog, VHDL, and VHDL-2008 Hardware Description Languages (HDLs)
• Ability to mix different HDL types in the same design and pass parameters and generics to each type
• Language templates to ensure reliable mapping of inferred complex functions to suitable device resources

HDL descriptions can be visually reviewed using an elaborated design schematic that cross-probes to the related HDL source code.

Logic synthesis provides control over all aspects of inference and optimization. Assignments can be made:

• Globally using tool and command options
• On specific modules or instances of logical hierarchy using the BLOCK_SYNTH XDC constraint
• On cells and nets using HDL attributes

Types of control include:

• Keeping, flattening, and rebuilding hierarchy
• Inferring or not inferring technology-specific structures
• Selecting the type of dedicated memory resources used for mapping memory arrays
• Assigning the encoding type for Finite State Machines (FSMs)
• Prioritizing performance, utilization, or power
• Applying advanced optimizations such as logical retiming
• Conversion of gated clocks to register enable signals

Vivado logic synthesis supports all levels of customization from pushbutton operation to exploration of different compilation strategies.

Logic synthesis:

• Works with Vivado projects and non-project flows
• Can be run interactively or in batch mode using Tcl
• Runs multiple processes to reduce compile times
• Provides compilation strategies to explore solutions for different design goals
• Supports an incremental compilation mode that reuses data from previous runs to speed up compilation iterations

After synthesis, the logical netlist is further optimized at a global level to reduce utilization and reduce logic levels.

The design power is reduced using activity gating techniques, with no required intervention and no changes to functionality, and minimal timing impact.

Logical netlist cells are placed into physical device resources according to XDC constraints which include timing, floorplan, and manual placement requirements. Placement begins with global resources including IO and clocking resources and logic clusters based on design hierarchy. The global placement phase is followed by the detailed placement and post-placement optimization phases. Placement is guided by ML models that predict routing delays and predict routing congestion which provides greater accuracy and faster compilation compared to traditional statistical methods.

Connections between netlist components are assigned to physical device interconnect resources. Similar to placement, routing begins with global resources such as IO and clocking then prioritizes resource assignments according to XDC timing constraints. Final routing phases further optimize routes to meet sign-off setup and hold requirements. Routing congestion is reduced by the use of ML routing congestion prediction during placement.

Physical optimization is a timing-driven process that occurs throughout placement and routing. Unlike logic optimization, physical optimization uses the most accurate timing data available based on placement and routing. Timing impact is evaluated such that only optimization performed results in improved timing. Optimization techniques include replication, retiming, and register re-placement as well as other optimizations specific to the target architecture. Physical optimization can also be run separately after placement and after routing to further improve results.

A design can be analyzed at any compilation stage within implementation. A comprehensive XDC constraint management system allowing modification and verification of timing, power, and physical constraints.

A powerful static timing analyzer that supports XDC constraints to drive implementation toward specified timing goals. Generates timing reports of critical timing paths, clock interaction, and clock domain crossings (CDCs).

Vectorless propagation supporting XDC switching activity for power analysis. Generates reports to identify areas of higher power consumption.

A graphical representation of design placement and routing, along with logical netlist schematics. Enables cross-probing between physical, logical, and source code design views to quickly trace the sources of critical timing paths.

It supports all levels of customization from pushbutton operation to exploration of different compilation strategies and iterative flows for designs with difficult-to-meet requirements.

• Works with Vivado projects and non-project flows
• Can be run interactively or in batch mode using Tcl
• Runs multiple threads to reduce compile times
• Provides compilation strategies to explore solutions for different design goals
• Supports an incremental compilation mode that reuses data from previous runs that can prioritize either compilation speedup or timing closure