|
|
| |
|
|
| |
CONSTRAINT MANAGEMENT |
|
| |
Ideally, constraint design would occur only once on a stable, functionally-complete and bug-free netlist,
and be correct the first time. This is rarely the case. Understanding and validating constraint and design
changes over the project cycle is one of the most time-consuming and repetitive tasks that timing
experts perform, but is also one of the most critical due to it’s downstream impact. Some critical areas
include
|
|
| |
|
IO ports being added, removed or renamed, and their clock interactions changing |
|
Inter-clock interactions are changed (i.e. MUX’ing, logic or inter-clock paths) |
|
Logical subsystems, including third-party IP, are updated, added or removed |
|
|
| |
|
|
| |
TimeVision’s Constraint Manager enables you to |
|
| |
|
Understand, validate and incrementally update constraints due to design changes |
|
Alert you to changes in the design or constraints that invalidate previously validated
relationships or assumptions |
|
Minimize the time and effort in managing changes as design progresses |
|
Provide guidance to downstream users (physical design) on precisely what changed in each
revision, including logical changes to critical path timing |
|
Automatically generate visual aids for the physical designers (clock diagrams and documentation
for CTS, critical path timing diagrams) |
|
Visualize clock propagation and groups |
|
|
| |
|
|
| |
|
|
|