Constraints Signoff
SoCs are built hierarchically by assembling subsystems. The subsystems are comprised of legacy designs and many commercially available IP. The IP and their respective timing constraints are developed and validated with their own timing-intent goals before the subsystems and SoCs are realized. Verifying correctness and completeness of the constraints at the IP level and consistency at the SoC level is critical for converging on signoff-quality constraints.
To address these requirements of constraint signoff, Conformal Litmus offers a rich set of built-in rules to verify issues such as missing constraints, timing exception overlaps, and conflicts at the IP level. It also verifies that the intent of the IP-level constraints is consistent with that of the SoC-level constraints.
The Conformal Litmus smart analysis generates accurate, low-noise reports that shorten debug time and help users achieve signoff-quality constraints rapidly.
Constraints Equivalence
Timing constraints are transformed and undergo several refinements as the design progresses from RTL to final layout. During this journey, the design and timing constraints change and may lose the original intent.
For example, synthesis optimizations like cloning, decloning, and buffering could unintentionally corrupt the original intent of the constraints. ECOs can introduce logic that can be erroneously affected by a timing exception.
Logic equivalency checking can ensure that the design intent is equivalent before and after an implementation step. But the designer will also need to verify that the timing constraint intent is also equivalent. If these constraint equivalence checks are not performed, this could result in schedule delays or potentially costly re-spins.
Conformal Litmus offers constraints comparison capabilities, wherein the user can make sure the timing constraints from a previous step in the implementation flow are in sync with the current step. These checks are needed to make sure the constraints intent is preserved from one step to the next, all the way to tapeout.
CDC Signoff
SoC systems have multiple interfaces and sub-blocks that operate on clock domains inherently asynchronous to each other. The designs have extremely complex asynchronous clock schemes that must be verified at every stage in the design flow. If unverified, these crossings can be catastrophic and cause costly chip re-spins.
The Conformal Litmus CDC signoff verifies correctness of CDC structures between the asynchronous clock domains from early RTL through implementation flows.