ADDER X-SC Bedienungsanleitung PDF herunterladen (Seite 74)

74 CHAPTER 2. COMBINATIONAL DESIGN EXAMPLES

implemented using the leaf designs we provide with the sources of the book.

2.2 The use of Makeﬁles to automate the design ﬂow

Here we will use the 4-bit multiplier design of the alliance-example directory to explain in some detail the use

of Makeﬁles to automate the design process and make it easier modifying ﬁles in your designs. The example we

will show here already has its own make ﬁle. We will explain here how to build your own one. At the end you

will have a Makeﬁle almost identical to the one provided with the example. Since we worked all the text in a

tcsh shell environment, we will follow an approach similar to that used in the tutorials of Alliance. We will set

environment variables in the command line and leave the running of tools to the Makeﬁle. First, we will obtain

a behavioral (Alliance) description from the VHDL ﬁle provided in the example. For this we use VASY. We

will set the environment variables as indicated in the original Makeﬁle.

setenv MBK_WORK_LIB .; setenv MBK_CATAL_NAME NO_CATAL

And, we will edit the following Makeﬁle.

ALLIANCE_BIN=$(ALLIANCE_TOP)/bin

VASY = $(ALLIANCE_BIN)/vasy

multi4.vbe : multi4.vhdl

$(VASY) -a -B -o -p -I v hdl multi4

This is a simpliﬁed version of the original Makeﬁle, having only what is needed to run VASY. Let’s explain the

above Makeﬁle. At the top we used what is called macros. Macros are similar to variables. They let us store

name of ﬁles, directory paths, etc. In our make ﬁle we use one macro to deﬁne the path to the bin directory in

Alliance. The se cond macro uses the ﬁrst one to point to the VASY tool. In the second macro we expand the

ﬁrst one by typing $(macro)

The second half of our make ﬁle deﬁnes a dependency. The multi4.vbe4 is the target and the argument after

the : is the source ﬁle needed to get the target. In other words, it has the following format target : sourcefile(s).

In the lines following this dependency deﬁnition we deﬁne the commands to generate the target using the source

ﬁle(s). In this c ase we need just one command to run VASY on the source ﬁle with the corresponding options

to obtain the behavioral Alliance description. Remember that the command lines must be preceded by a tab.

With this make ﬁle we can now run VASY as follows.

% make multi4.vbe

/usr/local/alliance/bin/vasy -a -B -o -p -I vhdl multi4

@@@@ @@@ @ @@@@ @ @@@@ @@@@

@@ @ @ @ @@ @@ @

@@ @ @@@ @@ @ @@ @

@@ @ @@@ @@@ @@ @

@@ @ @ @@ @@@@ @@

@@ @ @ @@ @@@ @@

@@@ @@@@@@@ @ @@ @@

@@@ @ @@ @@ @@ @@

@ @ @@ @@@ @ @@

@ @@@@ @@@@ @ @@@@ @@@@@@

VHDL Analyzer for SYnthesis

Alliance CAD System 5.0 20040928, vasy 5.0

Author(s): Ludovic Jacomme

Contributor(s): Frederic Petrot

E-mail : [email protected]

--> Run VHDL Compiler

--> Compile file multi4

--> Drive Alliance file multi4

We now simulate the behavioral description with the pat ﬁle provided in the example. Before that we need to

change some environment variables.

% setenv MBK_CATAL_NAME CATAL_ASIMUT_VASY

% setenv MBK_IN_LO vst

% setenv MBK_OUT_LO vst

1 2 ... 69 70 71 72 73 74 75 76 77 78 79 ... 86 87

Kommentare zu diesen Handbüchern

Keine Kommentare

ADDER X-SC Bedienungsanleitung Seite 74

Kommentare zu diesen Handbüchern