clock domain crossing (CDC)

Complex processes and aggressive synthesis interventions are increasing the risks of metastability, creating a need for netlist-level CDC verification

A look at three techniques to verify the validity of signals moving between clock domains

CDC violations are now so complex that it takes a combined block and full SoC level verification strategy to catch and fix all the bugs

Formal techniques can be applied to various parts of the verification challenge, including low-power and clock domain-crossing issues

The argument for an integrated approach to SoC verification

How Wall Street's vastly resourced IT teams already point the way to cheaper, faster and more efficient verification by putting goals not tools first.

As designs get larger and stress the ability of simulation to exercise an SoC, formal techniques have become essential parts of design and verification.

The increased use of IP and a rise in process variability is driving a move to look at alternatives to traditional low-skew clock distribution strategies.

Performing clock-domain crossing (CDC) checks on a flat database is difficult on complex SoCs. Hierarchy improves speed but calls for a smarter approach.

Find how to spot some of the most common false clock-domain crossing (CDC) violations and how to efficiently find actual CDC problems that could kill a design if not corrected.