Honored Contributor
Honored ContributorI assume the source and destination clock is the same? The multicycles are based on that period. For example, if the clock period is 10ns, then the default setup requirement is 10ns and the default hold requirement is 0ns. Now, if your opening the window to say you have multiple clock periods to transfer the data, then most likely you will do a multicycle -setup value of N and a multicycle hold value of N-1. For example, if do:
set_multicycle_path -setup 2 -from A -to B set_multicycle_path -hold 1 -from A -to B then you will have a setup requirement of 20ns and a hold requirement of 0ns. So your window is 20ns, and is twice as big to pass the data through. If you do: set_multicycle_path -setup 3 -from A -to B set_multicycle_path -hold 2 -from A -to B Then your setup requirement is 30ns and your hold is 0ns, for a 30ns window to pass the data through. I will try to add a presentation I worked on that goes through this soon.
