<INPUTDEFGENERATE 
"INPUT DEF GENERATE   

Reads DEF files with parametric macro cells, optionally generates the selected macros, and processes the file as a regular netlist.


Syntax

INP*UT D*EF G*ENERATE 
  [	[ ALL*MODELS    
        | M*ODEL macroRegExpr,...    		
        | C*ELL compRegExpr,... ] 	
[O*UTPUT fileName] 	
[CH*ECKOUTPUT 		
   [ CON*CATENATE fileName 			
      | SEP*ARATE prefix ]] ]... 
[N*ETLIST] 
F*ILENAME netlistFile 	
  [R*EPORTFILE fileName] ;


Arguments

GENERATE
In combination with NETLIST, generates the selected macros and then processes the file as a regular netlist. Without NETLIST, only updates the library database.

ALLMODELS
Generates all parametric macros that have not yet been processed.
Default: ALLMODELS applies whenever NETLIST GENERATE is specified

MODEL macroRegExpr,...
Generates all unprocessed parametric macros with model names that match the regular expression.

CELL compRegExpr,...
Generates all unprocessed parametric macros with component instances that match the regular expression.

OUTPUT fileName
Creates a file showing the instantiated macros.

CHECKOUTPUT fileName
Records which generator and parameter values were used to instantiate each macro. CONCATENATE puts this data into a single file. SEPARATE puts the data into separate files with a common file name prefix.

NETLIST
Processes the input file as a regular netlist. Default: if neither NETLIST nor GENERATE is specified, NETLIST applies

FILENAME netlistFile
The name of the ASCII design file to read and process.

REPORTFILE fileName
The name to give the report file. Default: inpDef.rpt in the current directory


Description

INPUT DEF GENERATE reads DEF files that include parametric macro cells. For a particular design, you can use INPUT DEF GENERATE to instantiate parametric macros used as models for the design's components, after assigning them fixed values using alias scripts in the DEF file.

Input Files

Input data for parametric macros are included in LEF and DEF files. Both LEF and DEF have expanded syntaxes to handle parametric macro cells.

Output Files

Because parametric macros are more abstract than regular ones, you might need to repeat design flow steps to characterize the macros, test instances, and debug the generic library. INPUT LEF GENERATE can create the following types of files that help in this process.

- Report file
A copy of the input file with error messages as comments. You can edit it to correct errors and then resubmit it; the LEF and DEF readers strip out comments.

- Output file
A file showing generated macros after instantiation.

- Checkoutput files
Files, either a single file or one file per generated macro, showing the generators and parameter values used for instantiation.

- User-defined files
Arbitrary files you can create and write to during input. Useful during debugging and production to check the validity of design parameters.

Design Flow

Use the following design flow to add parametric macro cells to the library database with INPUT LEF or INPUT DEF.

1. Create the generator macros (top-level models). 
These macros are written as alias scripts in a LEF file and are added to the library with INPUT LEF.

2. Optionally instantiate library macros.
Assign fixed values to all parameters using alias scripts in a LEF file and then running INPUT LEF GENERATE. With INPUT LEF you can combine step 1 and this step.

3. For components particular to the design, assign fixed values to parameters.
Define these values with alias scripts in the DEF file, then instantiate all applicable parametric macros with INPUT DEF GENERATE. 

4. Read the netlist using INPUT DEF NETLIST.
Using INPUT DEF, you can combine steps 3 and 4.


Example

INPUT DEF GENERATE ALLMODELS 
  FILENAME myDesign.nlt ;


Related Commands

INPUT DEF updates a database with design-specific information.

INPUT LEF creates or updates the library database.
"

	<Type QHELP>
	<Header "Input DEF Generate Command Help">
>
