GDS spice extract using Calibre generate empty spice netlist.

P

pskol95

Junior Member level 1
Joined
May 19, 2023
Messages
17
Helped
0
Reputation
0
Reaction score
0
Trophy points
1
Activity points
114
Hi, I wants to extract spice netlist from gdsII. For that I am doing:
"calibre -hier -64 -hyper -turbo -spice my_layout_netlist.sp /path-to-runset.extract"
and runset.extract is:
LAYOUT PATH "/path-to-gds"
LAYOUT PRIMARY "toplevel"
LAYOUT SYSTEM GDSII

But it is generating empty spice netlist like this:
* SPICE NETLIST
***************************************

.SUBCKT toplevel
** N=0 EP=0 IP=0 FDC=0
.ENDS
***************************************
What should I do ?
 

Sort by date Sort by votes
Find the runset and be sure it has anything to do with the layout
technology.

Inspect logfiles for complaints about not finding stuff.
 

Upvote 0 Downvote
sorry I didn't understood.

runset.extract is defined as this :
LAYOUT PATH "/path-to-gds"
LAYOUT PRIMARY "toplevel"
LAYOUT SYSTEM GDSII
 

Upvote 0 Downvote
What you show is the (purported) path to the layout DB.

There is also a path to the rules (runset).

Both need to get you to their object, rightly.

So you should be able to concatenate the "chunks" and paste that
to 'ls' (if directory) or 'more' (if flat-file). If you can't, Caliber can't.
Then fix.
 

Upvote 0 Downvote
For LVS to figure out a netlist, it needs to know how devices are connected. As Dick mentioned, that's normally in the rules that the runset runs.

Two key statements are "Device" and "Connect". The first one tells Calibre how to tell what combination of layers with interacting shapes is a transistor/capacitor/other defined device, and the second one tells Calibre how current is passed from one layer to another.
 

Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…