Continue to Site

Welcome to EDAboard.com

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.

Register Log in

export placement information- global routing

Status
Not open for further replies.
B

bm810978

Newbie level 3
Joined
Aug 15, 2007
Messages
4
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
1,311
Hi,

I want to export the design after placement stage in Cadence SoC Encounter. I want to use these data to do global routing with other tools and then import the generated global routing back to SoC Encounter to do detailed routing. How can I do that?

Thanks for your help
 

Hi,

I'm assuming that you are not using OA format for the routing tools.
How about using streamOut command if you want to export the physical data?
This command outputs the physical shape data in GDS2 format (remember to map layers correctly).

For connectivity & instance name information, you need to output the netlist also.
I haven't done this before but this is what comes to mind.
Migration between tools can be a major headache, especially when the technology files have slightly differing info.

Best Regards,
I-FAB
 

You can export and import data in DEF format. All the pnr tools support this.
 
Hi,

DEF can also be used - I think you need to also use LEF info. as well for the cell info. (I might be wrong here).
But DEF (& GDS for that matter) only states what layer is used & where it is used.
The thing to also remember is the netlist - this is the info. portion which tells the tool about the connectivity relation between the shapes/cells/pins we have loaded.

Best Regards,
I-FAB
 

it doesn't work by def or gds2. There is no info about the global routing :)
I want to do the global routing with another standalone tool!
 

writing out DEF should work.

Write out DEF, read it into another tool, complete your global routing, write DEF again and use it in your encounter.
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top