Forum Discussion

SKon1's avatar
SKon1
Icon for Occasional Contributor rankOccasional Contributor
5 years ago

Timing failure on auto assigned pins

Hello, In my design I have 3 output pins that show a timing violation in Timequest. Their location is locked by the "set_location_assignment" TCL command in the project's QSF file. Because the PC...
KhaiChein_Y_Intel's avatar
KhaiChein_Y_Intel
Icon for Regular Contributor rankRegular Contributor
5 years ago

Hi,


The path it takes to the assigned pin (destination) could be different from compilation to compilation. When you run a compilation, the Fitter creates a random initial placement for the logic based on the initial condition of your design. The initial condition of the design is a function of all the source files, optimization settings, and an integer called the Fitter seed value. A change in any of these parameters results in a change in the initial placement. A change in initial placement affects how optimizations proceed, producing a different Fitter result. Any modification, such as changing a net name, pin name, or making a new assignment affects the final results.


Thanks

Best regards,

KhaiY


  • SKon1's avatar
    SKon1
    Icon for Occasional Contributor rankOccasional Contributor
    5 years ago

    Thanks, but this doesn't answer my question. Please read again what I wrote:

    The only thing that was changed between the design that passed to the design that failed. Is copying the locations of the auto assigned pins from the fitter report of the design that passed and locking them (to the same location) using the "set_location_assignment" command in the QSF file.

    So, by definition I'm using the exact pin locations and NOTHING was changed in any of the sources.
    So the only thing that could've changed is the SEED value you mentioned.

    This SEED value presumably changes after every compilation...but I get the same negative slack - no matter how many times I compile afterwards. How do you explain this ?