Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
usually there is some top level budgeting so each block designer knows 'how fast' and 'how big' they can go. it's fairly complicated, as a complex SoC has multi modes, multi VDDs, memories, etc.
Tight constraint is the one that over the actual working condition of a design.
Depends on how much over it is in percentage, you can say it is tight or not.
Eg. clock is 100Mhz, its period is 10ns. Regardless the process margin, you make it 6ns in constraint, so you can called it a tight clock constraint.
Tight constraint is the one that over the actual working condition of a design.
Depends on how much over it is in percentage, you can say it is tight or not.
Eg. clock is 100Mhz, its period is 10ns. Regardless the process margin, you make it 6ns in constraint, so you can called it a tight clock constraint.
It could also be considered an over-constrained constraint. In the past for ASIC tools and currently in most FPGA tools. If you over-constrain with a near impossible or impossible constraint the tools would either a) give up and give you whatever the last pass result was (good or bad) or b) spend a ridiculous amount of time then give you something that is significantly slower than using the exact constraint (e.g. ask for 300 MHz need 250MHz but get 200 MHz result).
It could also be considered an over-constrained constraint. In the past for ASIC tools and currently in most FPGA tools. If you over-constrain with a near impossible or impossible constraint the tools would either a) give up and give you whatever the last pass result was (good or bad) or b) spend a ridiculous amount of time then give you something that is significantly slower than using the exact constraint (e.g. ask for 300 MHz need 250MHz but get 200 MHz result).
Exactly. And it gets even more complicated than that. The way most tools are coded today is that they are timing oriented. Once they meet timing, then they go back and apply area and power recovery tricks. If your timing is never met, I believe the results you see for power and area cannot be trusted, maybe they are good enough for some rough estimation.
The question is "what is a tight constraint" not "what is suitable constraint".
Practical situation show many effects of over-constraint, both bad and good, and they are not discussed in this topic.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
