2.2 Working Environment

The simulation and synthesis software can have their own setup files. Especially if You are using tools from different producers. The principles for initializing the software are quite often similar. Please consult your software documentation for detailed information.

2.2.1 Simulation Setup

Normally a setup file has to be created. You can do this either by hand with an editor (save the file in the current, it is the ~/workshop directory) or within a menu of the software used.

 

Example of a simulation setup file

TIMEBASE = NS

WORK    >    DEFAULT
DEFAULT :    ./WORK




USE = .

Defines the timescale (nano seconds) for the simulation.

The VHDL library WORK is mapped to the logical
library DEFAULT. The physical path for this library is
/WORK, i.e. the analysed files will be stored there
(~user/workshop/WORK).
List of directories where the simulator searches for the
VHDL source code.

2.2.2 Synthesis Setup

Normally a setup file has to be created. You can do this either by hand with an editor (save the file in the current, it is the ~/workshop directory) or within a menu of the software used. If you use a framework perhaps only one setup file for simulation and synthesis is needed.

 

Example of synthesis setup file

search_path = search_path + { . }

define_design_lib work -path ./WORK


link_path      = { vendorlib.db }
target_library = { vendorlib.db }
symbol_library = { vendorlib.sdb }
link_library   = { vendorlib.db }

Adds current directory to the search path

Defines library for the analysed files
(~user/workshop/WORK).

Define the link-, target-, and symbol-library
of the target library.