In-to-out paths start from an input port and end at an output port. Figure 1 below shows an in-to-out path. As shown in figure 1, most of the times (not always), in-to-out paths are subset of a reg-to-reg path seen from a higher level of hierarchy. For instance, an in-to-out path at the level of a block-level design may be a reg-to-reg path as seen at SoC flat.
For in-to-out paths, the clock path is always assumed fully outside the design.
Constraining in-to-out paths: There are two ways that we can constrain in-to-out paths:
Constraining with respect to a virtual clock: We can consider in-to-out path as a sub-segment of a larger reg-to-reg path. And we can constrain these paths using a virtual clock. Using "set_input_delay" for input port and "set_output_delay" for output port with respect to same virtual clock, these paths can be constrained.
- Create a clock VCLK without any source
- "set_input_delay" at input_port with respect to VCLK
- "set_output_delay" at output_port with respct to VCLK
Constraining as point-to-point paths: We can constrain in-to-out paths using "set_max_delay" command as point-to-point paths. However, using this approach, we may need to apply some extra constraints as well depending upon the behavior of the tool we are using.
No comments:
Post a Comment
Thanks for your valuable inputs/feedbacks. :-)