ADDER X-SC Manual de usuario Pagina 49

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 87
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 48
1.20. NERO 49
tool in its manual pages. We have called both files fsm.vhd and fsm.ctl respectively. We first convert the VHDL
file in a behavioral description using the following command
% vasy -Vao -I vhd fsm
After the conversion has been done. We run MOKA as follows.
% moka -VB fsm fsm
@@@ @@@ @@@@ @@@@ @
@@ @@ @@ @ @
@@@ @@@ @@ @ @@@
@@@ @@@ @@@ @@ @ @@@
@ @@ @ @@ @@ @@ @@ @@ @ @@
@ @@ @ @@ @@ @@ @@ @ @@ @ @@
@ @@@ @@ @@ @@ @@@ @@ @ @@
@ @@ @@ @@ @@ @@ @@ @@@@@@@
@ @ @@ @@ @@ @@ @@ @ @@
@ @@ @@ @@ @@ @@ @ @@
@@@ @@@@ @@@ @@@@ @@@@ @@@@ @@@@
MOdel checKer Ancestor
Alliance CAD System 5.0 20040928, moka 5.0
Copyright (c) 2002-2005, ASIM/LIP6/UPMC
Author(s): Ludovic Jacomme
--> Running BEH Compiler
Compiling file fsm
--> Verifying BEH figure
--> Running CTL Compiler
Compiling file fsm
--> Building BDDs
--> Model checking of "fsm"
Checking formula prop1
EX((ack = ’1’))
> states set:
(NOT(a_cs) AND b_cs)
(NOT(a_cs) AND NOT(b_cs)) (first state)
Checking formula prop2
AG((req -> AF(ack)))
> all reachable states
Checking formula prop4
((req = ’1’) AU (ack = ’1’))
> states set:
(a_cs AND b_cs)
(NOT(a_cs) AND b_cs)
(NOT(a_cs) AND NOT(b_cs)) (first state)
<-- done
1.20 NERO
NERO (NEgotiating ROuter) is a simple over the cell router provided in Alliance that can process designs of up
to 4K gates in size. It takes as inputs a netlist and a placement of it. By default it assumes that the netlist and
placement file have the same name. The user can provide with an optional different name for the placement
file.
If a design has a half perimeter greater than 800 lambdas, NERO will use ”global routing” to route it. When
NERO uses ”global routing”, the longest nets will be routed first using layers 3 and 4. Then, the remaining
nets will be routed using all other available layers. When global routing is used at least four layers are used for
routing. The nets in this case are routed from the shortest to the longest one with the same routing algorithm.
NERO provides good results with small netlists (less than 500 gates) and could not converge when handling
complex netlists. We use NERO with the following command.
% nero [options] netlist layout
The netlist and layout file names must be different or the first one will be overwritten. The options available in
NERO are shown in Table 1.20. We already shown an application of NERO to our mux example in the section
explaining , so we will not repeat it here. Other examples will be given in the chapters showing more complex
design examples.
Vista de pagina 48
1 2 ... 44 45 46 47 48 49 50 51 52 53 54 ... 86 87

Comentarios a estos manuales

Sin comentarios