40
CHAPTER 3. LAB TASK 1 - INTERFACING TO THE WISHBONE BUS
3.6 Useful Commands
We have prepared a makefile based build system that is responsible for both building
the monitor firmware and synthesizing the hardware from the RTL source code. You
can use it on the Linux computers in Muxen 1. The following targets will be useful for
you:
• make lab1 Creates a bit file of the computer in this lab task.
• make sim_lab1 Launches Modelsim on the “lab1” system.
• make sim_uart Launches Modelsim on your UART.
• make dafk Creates a bit file of the complete system.
• make sim Launches Modelsim on the complete system.
• make simfiles Recompiles all source files for use with Modelsim but does
not launch Modelsim itself. This is mainly useful if you already have Modelsim
running and want to try out some changes to your source code. This way you
don’t need to close Modelsim, it is enough to issue a restart command in
Modelsim.
• make clean Removes intermediate files and backup files.
• make updatebit Compiles the monitor and updates dafk.bit, and lab1.bit
with the new monitor. This way you don’t need to resynthesize the design to test
changes in your monitor. The updated bit file is named updated_dafk.bit for
dafk.bit and so on.
We also have some utilities that you might be interested in. The first of these is
download.sh which you can use to download your design. (You may use this script
either in Windows or Linux. In Windows it will invoke Impact in batch mode and in
Linux it will invoke xc3sprog.) Invoke it as in the following example:
utils/download.sh dafk.bit
Another utility is designed to highlight the error and warning messages in the var-
ious reports that the Xilinx flow will output. Use it on (for example) the synthesis
report with the following command:
utils/checklogs.pl synthdir/dafk.syr | less -r
The other alternative is to pipe the output of make through checklogs:
make dafk.bit | utils/checklogs.pl
3.6.1 Synthesis Reports
If you use make, the following files will be of special interest to you: (look in /nobackup/local/<your
name>/
Komentarze do niniejszej Instrukcji