Maker Pro
Maker Pro

Need a medium size SPICE netlist

M

Mike

Jan 1, 1970
0
I need a medium size SPICE netlist - between 10,000 and 100,000 instances.

The requirements are:

1. It should be 'standard' SPICE syntax. I know there are lots of variations
on 'standard' SPICE syntax, but here's the definition I'm working with:
The
netlist should be readable, without syntax errors, by at least one
commonly
used tool that reads SPICE files. HSPICE, PSPICE, LTSPICE, or various LVS
tools.
2. It needs to be hierarchical (it should have subcircuits)
3. It needs to be complete down to the level transistor level (device
models aren't necessary, but transistor instantiations are).

The circuit doesn't have to work, or even be functional. I don't need to
know what it does, and I don't need the simulation control files. I've
written a SPICE parser, and would like some test cases to throw at it. The
test cases I have all come from a single netlister (Mentor). I'd like to
have netlists generated by other sources (by hand, or from other tools).
SPICE format trace netlists (which often have a somewhat different SPICE
syntax) are also welcome.

If you have a netlist you can give away, please post it as a zip (tar, gzip,
7z, etc) file to abse.

If you can provide a link to a netlist, that would also be fine.

Thanks,

-- Mike --
 
J

Jim Thompson

Jan 1, 1970
0
I need a medium size SPICE netlist - between 10,000 and 100,000 instances.

The requirements are:

1. It should be 'standard' SPICE syntax. I know there are lots of variations
on 'standard' SPICE syntax, but here's the definition I'm working with:
The
netlist should be readable, without syntax errors, by at least one
commonly
used tool that reads SPICE files. HSPICE, PSPICE, LTSPICE, or various LVS
tools.
2. It needs to be hierarchical (it should have subcircuits)
3. It needs to be complete down to the level transistor level (device
models aren't necessary, but transistor instantiations are).

The circuit doesn't have to work, or even be functional. I don't need to
know what it does, and I don't need the simulation control files. I've
written a SPICE parser, and would like some test cases to throw at it. The
test cases I have all come from a single netlister (Mentor). I'd like to
have netlists generated by other sources (by hand, or from other tools).
SPICE format trace netlists (which often have a somewhat different SPICE
syntax) are also welcome.

If you have a netlist you can give away, please post it as a zip (tar, gzip,
7z, etc) file to abse.

If you can provide a link to a netlist, that would also be fine.

Thanks,

-- Mike --

(1) Mike who?

(2) What are you trying to accomplish by parsing?

...Jim Thompson
 
M

Mike

Jan 1, 1970
0
Jim Thompson said:
(2) What are you trying to accomplish by parsing?

All I'm interested in is parsing. The program parses out all the primitives,
subcircuits, instances, and so on, and generates lists and hash-tables of
everything. After that, it's a snap to do things like find a net and report
on everything it attaches to. That can be real convenient if you're trying
to do something like estimate how much driving strength you need for a net.

There are other uses as well. For example, digital synthesizers put buffers
in signal lines. When you're troubleshooting a problem, it's hard to know
whether the signal reaching the output buffer is the right one. Once you
have a parser, you can easily trace back through buffers to find the signal
name at the driver.

I haven't done anything with bipolar in quite a while, but we used to do
lots of stuff with multi-level CML, and the standard problem we'd run into
was connecting the wrong levels together. SPICE wasn't much help with those
mistakes - the circuits would work find in simulation, then fail in silicon.

So, that's what I want to do with the parser.

The only thing I want to do with other netlists is read and parse, to check
the parser with as many different 'standard' SPICE formats as I can. There
are lots of variations, and every schematic / layout / synthesis tool seems
to produce some variation that take special code to parse correctly.

-- Mike --
 
J

Jim Thompson

Jan 1, 1970
0
All I'm interested in is parsing. The program parses out all the primitives,
subcircuits, instances, and so on, and generates lists and hash-tables of
everything. After that, it's a snap to do things like find a net and report
on everything it attaches to. That can be real convenient if you're trying
to do something like estimate how much driving strength you need for a net.

There are other uses as well. For example, digital synthesizers put buffers
in signal lines. When you're troubleshooting a problem, it's hard to know
whether the signal reaching the output buffer is the right one. Once you
have a parser, you can easily trace back through buffers to find the signal
name at the driver.

I haven't done anything with bipolar in quite a while, but we used to do
lots of stuff with multi-level CML, and the standard problem we'd run into
was connecting the wrong levels together. SPICE wasn't much help with those
mistakes - the circuits would work find in simulation, then fail in silicon.

So, that's what I want to do with the parser.

The only thing I want to do with other netlists is read and parse, to check
the parser with as many different 'standard' SPICE formats as I can. There
are lots of variations, and every schematic / layout / synthesis tool seems
to produce some variation that take special code to parse correctly.

-- Mike --

Replied privately.

...Jim Thompson
 
Top