| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| config:netlist [2024/03/31 17:44] – [Device generation and parameters] rajit | config:netlist [2025/02/22 12:53] (current) – [Transistor device names] rajit |
|---|
| |
| <code> | <code> |
| real lambda 0.03e-6 | real lambda 0.3e-6 |
| </code> | </code> |
| This is the scale factor used to convert to metric units from the dimensionless transistor sizes. | This is the scale factor used to convert to metric units from the dimensionless transistor sizes. This is normally set to F/2, where F is the feature size. In this example, we are assuming a 0.6 micron feature size. |
| ===== Device generation and parameters ===== | ===== Device generation and parameters ===== |
| |
| string nfet_hvt "nhvt" | string nfet_hvt "nhvt" |
| </code> | </code> |
| The strings above are used for the device names for each transistor type. Note that the device type names are part of the technology-independent ACT configuration. | The strings above are used for the device names for each transistor type. Note that the device type names are part of the [[config:start#devices|technology-independent ACT configuration]]. |
| |
| If the FET devices being used are floating-body SOI devices, then their spice representation is not of type "M" (model), but of type "X" (subcircuit). The device has the usual source, gate, drain terminals, but the fourth terminal is no longer bulk, but instead the substrate. All substrate terminals are grounded (as opposed to bulk terminals that are connected to the appropriate supply), so this requires a modified netlist. To have the "svt" device correspond to an SOI-type, use the following: | If the FET devices being used are floating-body SOI devices, then their spice representation is not of type "M" (model), but of type "X" (subcircuit). The device has the usual source, gate, drain terminals, but the fourth terminal is no longer bulk, but instead the substrate. All substrate terminals are grounded (as opposed to bulk terminals that are connected to the appropriate supply), so this requires a modified netlist. To have the "svt" device correspond to an SOI-type, use the following: |
| <code> | <code> |
| string rect_inpath "paths:tosearch/for/rect/files" | string rect_inpath "paths:tosearch/for/rect/files" |
| | </code> |
| | This parameter is used to set the search path for ''.rect'' files (when ''rect_import'' is set to one). |
| | |
| | The layout generation tools create fresh rect files. This happens in two scenarios: (a) If rect files are not found, or the ''rect_import'' parameter is set to zero; or (b) When rect files are read in, their LEF bounding box is re-computed and the rectangles are shifted so as to be properly aligned. When saving the final rect files, it can be helpful to keep these two types of outputs separate. The default output directory for rect files is the current directory. |
| | <code> |
| string rect_outdir "outputrectdir" | string rect_outdir "outputrectdir" |
| </code> | </code> |
| These two parameters are used to control the search path for ''.rect'' files (when ''rect_import'' is set to one) and the directory where the final output ''.rect'' files are saved, if ''.rect'' files are generated. | If this parameter is set, then the output directories for (a) and (b) outputs are both set to the specified directory name. |
| | <code> |
| | string rect_outinitdir "out_init" |
| | </code> |
| | If this parameter is set, then //initial// rect outputs (i.e. those generated in case (a) above) are saved to this directory. When both parameters are specified, outputs generated in case (a) are written to ''rect_outinitdir'', while those in case (b) are written to ''rect_outdir''. |
| |
| <code> | <code> |