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.
CTS is clock tree synthesis. Clock is an example high fanout net(HFN). We declare any signal such as reset or enable, which will be supplied to a lot of flops, as high fanout net during synthesis. Incase of clock, i think the tool understands that clock is a HFN and assumes its going to be updated in later part of the process with buffers of higher drive strength and treats it as an ideal net. So, my guess is, it need not be specified as a HFN.
yes ,generally set and reset pins are HFN out nets, to minimize insertion delay and fanout we build buffer tree during CTS.but these r not constrained much like clk in clk spec
scan enable is another example for High fanout net. Some of the P&R tools are intelligent enough to detect the high fanout nets during placement optimisation (based on the threshold given for no: of nets) and do HFN synthesis.
Most tools today understand the difference between HFN and clocks. Typically you can set the threshold of what is defined as an HFN, but the tool default is fine. HFN synthesis typically tries to me requirements like max cap, max slew, max fanout.
You can create clock tree like structure (with buffers and inverters) for HFN to satisfy design rules (max cap, slew etc). The command in PKS used to be - build physical tree <net_name>.
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.