Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
No way. The only way to "copy" the circuit, is to simulate and see DC operating point and adjust your new circuit with the same gm/ID. Use appropriate L and adjust current base don budget and choose W based on gm/ID.is there any efficient way to simulate the same circuit we have designed before but now using a different technology?
Yes, just change the technology library in model library definition. Schematic porting from one technology to another technology is very straight forward, and should not take any time. However, the layout cannot be ported that easily.is there any efficient way to simulate the same circuit we have designed before but now using a different technology?
I see, just to make sure.Yes, just change the technology library in model library definition. Schematic porting from one technology to another technology is very straight forward, and should not take any time. However, the layout cannot be ported that easily.
Yes, just change the technology library in model library definition. Schematic porting from one technology to another technology is very straight forward, and should not take any time. However, the layout cannot be ported that easily.
There's probably layers of stuff that need changed.
The symbol libraries that are process-specific, will
have associated netlisting procedures per device
that will refer to corresponding models. Those
names and arguments will need to be mapped or
replaced (the PDK models set's subcircuit layer may
be the efficient place to do this). SPICE "not found"
model errors will show you what's "got a gap", you
can expect a few passes around that loop getting
the schematic, symbol, netlist line, model libs and
model statement detail all self-consistent.
When you get all that straight then you can observe
any effects of process and gemoetry (if the model
fit of one, is appropriate to the geometries of the
other).
Since you use Virtuoso you can check a porting script done by Andrew Beckett.
You have to define the device mapping and also be careful about callbacks.
But bottom line is that it is a very crude porting, you can't really draw any conclusions about the process performance or be sure that the circuit will work. The best outcome would be that you get a good starting point.