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.
The basic idea is the synthesis tool will know the placement of macro, pads, and could estimated more precisely the wire length and sizing the cells appropriately.
What is "topolofical view"? As you wrote, firstly we should run a "dirty" Logic Synthesis for just having an idea about the gates count and only then pass the Netlist to Floorplaning. Correct? So, for the first "dirty" synthesis the DC-T doesn't have any floorplaning info, correct? Can DC-T constrain gates count according to floorplaning info?
- - - Updated - - -
What Output files from DC-T?
My guess is:
1) Netlist (*.v, *.db)
2) Timing constraints (*.sdc)
3) DEF(?) Milkyway(?) files
First of all, it is not tolpological flow;it is topographical flow.
Flow:
1.Run DC using a basic WLM and correct constraints to get a netlist.
2.Use this netlist to get a DEF.
3.Run DC-T again using this def, removing the WLM and with the same constraints.This run of DC-T will require Milkyway libraries as well apart from normal .db's.
4.This run will also realise a netlistddc & sdc.
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.
