en caractere gras
This commit is contained in:
parent
6ecf04a37a
commit
7156c6781e
|
@ -47,16 +47,16 @@ BooG \- Binding and Optimizing On Gates.
|
|||
|
||||
.SH DESCRIPTION
|
||||
.br
|
||||
\fBBoog\fP is a mapper of a behavioural description onto a predefined standard cell library as SXLIB.
|
||||
\f4boog\fP is a mapper of a behavioural description onto a predefined standard cell library as SXLIB.
|
||||
It is the second step of the logic synthesis: it builds a gate network using a standard cell library.
|
||||
.br
|
||||
|
||||
.br
|
||||
\fB Input file description\fP
|
||||
\f4 Input file description\fP
|
||||
.br
|
||||
The logic level behavioural description (.vbe file) uses the same VHDL subset as the logic simulator \fBasimut\fP, the FSM synthesizer \fBsyf\fP, the functional abstractor \fByagle\fP and the formal prover \fBproof\fP (for further information about the subset of VHDL, see the "vbe" manual).
|
||||
The logic level behavioural description (.vbe file) uses the same VHDL subset as the logic simulator \f4asimut\fP, the FSM synthesizer \f4syf\fP, the functional abstractor \f4yagle\fP and the formal prover \f4proof\fP (for further information about the subset of VHDL, see the "vbe" manual).
|
||||
.br
|
||||
Some constraints due to hardware mapping exist. These attributes are only supported by technology mapping onto a standard cell library as \fBsxlib\fP.
|
||||
Some constraints due to hardware mapping exist. These attributes are only supported by technology mapping onto a standard cell library as \f4sxlib\fP.
|
||||
.br
|
||||
For the register signal description, only one condition statement must appear. STABLE must be strictely used as a negativ motion and joined to clock setup value. Setup can be on high or low value, but it would be worthy to choose it accordingly with hardware register cell.
|
||||
\fI# Example\fP
|
||||
|
@ -74,26 +74,26 @@ You can also put a write enable condition to your register:
|
|||
.ti 7
|
||||
|
||||
A special feature has been introduced in the VHDL subset in order to allow the don't care description for external outputs and internal registers : A bit signal can take the 'd' value.
|
||||
This value is interpreted as a '0' by the logic simulator \fBasimut\fP.
|
||||
Don't Cares are automatically generated by \fBsyf\fP in the resulting '.vbe' file.
|
||||
This value is interpreted as a '0' by the logic simulator \f4asimut\fP.
|
||||
Don't Cares are automatically generated by \f4syf\fP in the resulting '.vbe' file.
|
||||
|
||||
|
||||
.br
|
||||
\fB Output file description\fP
|
||||
\f4 Output file description\fP
|
||||
.br
|
||||
A pure standard cell netlist is produced by \fBboog\fP. This file is destinated for /fBloon/fP alliance utility to improve RC delays.
|
||||
A pure standard cell netlist is produced by \f4boog\fP. This file is destinated for /fBloon/fP alliance utility to improve RC delays.
|
||||
Any equipotential keeps its name from connector to connector. In trouble case, buffers are inserted to respect this VHDL constraint.
|
||||
|
||||
.br
|
||||
\fB lax Parameter file description\fP
|
||||
\f4 lax Parameter file description\fP
|
||||
.br
|
||||
The lax file is common with other logic synthesis tools and is used
|
||||
for driving the synthesis process.
|
||||
See \fBlax\fP(5) manual for more detail.
|
||||
See \f4lax\fP(5) manual for more detail.
|
||||
|
||||
.br
|
||||
\fBlax\fP uses a lot of parameters to guide every step of the synthesis process.
|
||||
Some parameters are globally used (for example, \fIoptimization level\fP whereas others are specifically used (\fBload capacitance\fP for the netlist optimization only).
|
||||
\f4lax\fP uses a lot of parameters to guide every step of the synthesis process.
|
||||
Some parameters are globally used (for example, \fIoptimization level\fP whereas others are specifically used (\f4load capacitance\fP for the netlist optimization only).
|
||||
Here is the default lax file (see the user's manual for further information about the syntax of the '.lax' file):
|
||||
.br
|
||||
|
||||
|
@ -109,36 +109,36 @@ Here is the default lax file (see the user's manual for further information abou
|
|||
|
||||
|
||||
.br
|
||||
\fB Mapping with a standard cell library\fP
|
||||
\f4 Mapping with a standard cell library\fP
|
||||
.br
|
||||
Every cell appearing in the directory defined by the environment variable MBK_TARGET_LIB may be used by \fBboog\fP since they are described as a '.vbe' file. There are some restrictions about the type of the cell used. Every cell has to have only one output.
|
||||
The cell must be characterized. The timing and area informations required by \fBboog\fP are specified in the "generic" clause of the ".vbe" file.
|
||||
Every cell appearing in the directory defined by the environment variable MBK_TARGET_LIB may be used by \f4boog\fP since they are described as a '.vbe' file. There are some restrictions about the type of the cell used. Every cell has to have only one output.
|
||||
The cell must be characterized. The timing and area informations required by \f4boog\fP are specified in the "generic" clause of the ".vbe" file.
|
||||
.br
|
||||
|
||||
.SH OPTION
|
||||
.TP 10
|
||||
\f4\-h\fP
|
||||
Help mode. Displays possible uses of \fBboog\fP.
|
||||
Help mode. Displays possible uses of \f4boog\fP.
|
||||
.TP 10
|
||||
\f4\-m optim_mode\fP
|
||||
Optimization mode. Can be defined in lax file, it's only a shortcut to define it on command line. This mode number has an array defined between \fI0\fP and \fI4\fP. It indicates the way of optimization the user wants. If \fI0\fP is chosen, the circuit area will be improved. On the other hand, \fI4\fP will improve circuit delays. \fI2\fP is a medium value for optimization.
|
||||
.TP 10
|
||||
\f4\-x xsch_mode\fP
|
||||
Generate a '.xsc' file. It is a color map for each signals contained in \fIoutput_file\fP network. This file is used by \fBxsch\fP to view the netlist. By choosing level 0 or 1 for xsch_mode, you can color respectively the critical path or all signals with delay graduation.
|
||||
Generate a '.xsc' file. It is a color map for each signals contained in \fIoutput_file\fP network. This file is used by \f4xsch\fP to view the netlist. By choosing level 0 or 1 for xsch_mode, you can color respectively the critical path or all signals with delay graduation.
|
||||
.TP 10
|
||||
\f4\-o output_file\fP
|
||||
Just another way to show explicitely the \fBVST\fP output file name.
|
||||
Just another way to show explicitely the \f4VST\fP output file name.
|
||||
.TP 10
|
||||
\f4\-l lax_file\fP
|
||||
Just another way to show explicitely the \fBLAX\fP parameter file name.
|
||||
Just another way to show explicitely the \f4LAX\fP parameter file name.
|
||||
.TP 10
|
||||
\f4\-d debug_file\fP
|
||||
Generates a \fBVBE\f debug file. It comes from internal result algorithm. Users aren't concerned.
|
||||
Generates a \f4VBE\f debug file. It comes from internal result algorithm. Users aren't concerned.
|
||||
.br
|
||||
|
||||
.SH ENVIRONMENT VARIABLES
|
||||
.br
|
||||
The following environment variables have to be set before using \fBboog\fP :
|
||||
The following environment variables have to be set before using \f4boog\fP :
|
||||
.HP
|
||||
.ti 7
|
||||
\fIMBK_CATA_LIB\fP gives the auxiliary paths of the directories of input files (behavioural description).
|
||||
|
@ -152,7 +152,7 @@ The following environment variables have to be set before using \fBboog\fP :
|
|||
|
||||
.SH EXAMPLE
|
||||
.br
|
||||
You can call \fBboog\fP as follows :
|
||||
You can call \f4boog\fP as follows :
|
||||
.br
|
||||
.br
|
||||
boog alu alu
|
||||
|
|
Loading…
Reference in New Issue