
2.2. THE USE OF MAKEFILES TO AUTOMATE THE DESIGN FLOW 81
We now route the design using NERO. For this, we modify our Makefile adding the following lines.
NERO = $(ALLIANCE_BIN)/nero
multi4.ap : multi4_p.ap multi4.vst
$(NERO) -V -$(METAL_LEVEL) -p multi4_p multi4 multi4
The environment setting needed by NERO is almost the same of the one used by OCP so we modify nothing
this time. However, we define a new variable to set the number of layers used in the routing of the design.
% setenv METAL_LEVEL 2
We then run NERO with the following command (the output has been shortened to make it fit).
% make multi4.ap
/usr/local/alliance/bin/nero -V -2 -p multi4_p multi4 multi4
@@@ @@@ @@@@@@@
@@ @ @@ @@
@@@ @ @@ @@
@ @@ @ @@@@@ @@ @@ @@@
@ @@ @ @ @ @@ @@ @@ @@
@ @@ @ @@ @@ @@@@@ @@ @@
@ @@ @ @@@@@@@@@ @@ @@ @@ @@
@ @@ @ @@ @@ @@ @@ @@
@ @@@ @@ @ @@ @@ @@ @@
@ @@ @@ @@ @@ @@ @@ @@
@@@ @@ @@@@ @@@@@ @@@ @@@
Negotiating Router
Alliance CAD System 5.0 20040928, nero 5.0
Copyright (c) 2002-2005, ASIM/LIP6/UPMC
S/N 20021117.1
o MBK environment :
MBK_IN_LO := vst
...
MBK_CATA_LIB := .
/usr/local/alliance/cells/sxlib
...
/usr/local/alliance/cells/padlib
MBK_CATAL_NAME := CATAL
MBK_VDD := vdd
MBK_VSS := vss
MBK_SEPAR := .
o Loading netlist "multi4"...
o Loading layout "multi4_p"...
o Flattening layout...
o Flattening netlist...
o Building netlist dual representation (lofigchain)...
o Binding logical & physical views...
o Loading design into grid...
o Local routing stage.
- [ 158] (hp := 9) "r 0"
...
- [ 0] (hp := 192) "x 1"
o Routing stats :
- routing iterations := 314327
- re-routing iterations := 22122
- ratio := 6.57514%.
o Dumping routing grid.
o Saving MBK figure "multi4".
o Saving layout as "multi4"...
We can check the correctness of the design using Cougar and LVX. We must set some variables to run the first
Kommentare zu diesen Handbüchern