Description
Question:
How can I constrain a few paths between two asynchronous clock domains?
Answer:
Specifying asynchronous relationship between clocks does two things:
- Sets a false_path exception internally for all the paths between the two clock domains
- Infinite arrival_window is used for SI analysis between the nets corresponding from these domains
The internal false_path exception suppresses the default timing analysis and as false_path has highest priority over all the other exceptions, you can't use set_max_delay
to constrain the required paths directly.
The solution is to use the switch -allow_paths
while specifying the asynchronous relationship. The switch enables the timing analysis between the paths and preserves SI analysis using an infinite arrival window:
pt_shell> create_clock -period 1 \ -name Clock_A [ get