Honored Contributor
Honored ContributorCould you answer my question?
--- Quote Start --- -------------------------------------------------------------------------------- Quote: Originally Posted by godfather If the assignments are no longer being ignored as you stated in another post then this is a different issue. Method 1 and 2 are doing different things. Method one creates 1 abstract clock object and applies that same clock object to 360 different ports in the design. Method 2 creates 360 different clock objects and assigns one each to one of 360 different ports in the design. The fitter works by optimizing each clock domain independently so in method one you have only 1 clock domain to be optimized. In method two you have 360 independent clock domains to be optimized. If all 360 clocks arrive at the chip at the exact same time (which seems to be the case if you can use either method 1 or 2) then you should use method 1 in order to save compile time. If each clock domain will eventually be given a slightly different offset with respect to each other than you should use method 2. Hi, The 360 input signals are unrelated so they won't arrive at the chip at the exact same time. But they never crossing into each other domain. So I think the two constraints listed above should result into the same result. Am I wrong? --- Quote End --- P.S. Any other book?
