Script for Laboratory: Designing embedded ASIPs - CES

included. This template is a good starting point to create a new project from the scratch.
Usually you can copy from your last project to create a new one, but sometimes it is better to
start from the scratch.
TEMPLATE_
PROJECT TEMPLATE_
PROJECT
ASIPMeisterProjects
dlx_basis AnotherProject
dlx_basis AnotherProject
dlx_basis AnotherProject
Figure 2-1
The directory structure for all ASIP Meister Projects
The biggest part of the directory structure is placed inside each ASIP Meister project directory,
e.g. “dlx_basis”, as shown in Figure 2-2. Every project directory contains three subdirectories
and a set of local files. Those directories and files will be explained in the remainder
of this section.
The “Applications” directory contains all your user applications that you want to run and
simulate on the CPU, and the scripts that are needed to support those tasks. Every application
is placed inside a specific subdirectory for this application. When you want to work with the
scripts, then you allays do so from this specific subdirectory. For example, you might want to
work with “Application 1”, as shown in Figure 2-2. Your first step is to compile this application.
Inside the “Application 1” directory, you have provided the source code “application1.c”.
To compile it you have to enter the “Application 1” directory and to execute
../mkimg application1.c
The reference “../” to access the mkimg-script is important. The script expects to be called
from the place, where the results shall be placed, so always execute the scripts from the
application specific subdirectory, never from the “Applications” directory itself! The details
about the parameters, the created output files and the different versions of the script
(mkimg_fromS, mkall, …) are explained in Chapter 8.3. The concept of calling the scripts
from the specific application subdirectory is also important for the scripts dlxsim and
initMem, which are explained in Chapter 3.3 and Chapter 6.3 respectively.
The scripts inside the “Applications” directory are only wrappers for the real scripts. Those
wrappers first read the “env_settings” file from your project directory (e.g. “dlx_basis” in
Figure 2-2). This file contains all information about your current project, e.g. which compiler
to use and which dlxsim to call. Afterwards the wrapper scripts call the real scripts. The real
scripts are placed at a global position. This enables us to make changes to those scripts
without the need to copy those changes to all your projects. The env_settings file is explained
in a later paragraph of this subchapter.
- 12 -