1 |
2 |
vv_gulyaev |
################################################################################
|
2 |
|
|
# Vivado (TM) v2017.4 (64-bit)
|
3 |
|
|
#
|
4 |
|
|
# README.txt: Please read the sections below to understand the steps required to
|
5 |
|
|
# run the exported script and information about the source files.
|
6 |
|
|
#
|
7 |
|
|
# Generated by export_simulation on Tue Jul 28 11:34:43 MSK 2020
|
8 |
|
|
#
|
9 |
|
|
################################################################################
|
10 |
|
|
|
11 |
|
|
1. How to run the generated simulation script:-
|
12 |
|
|
|
13 |
|
|
From the shell prompt in the current directory, issue the following command:-
|
14 |
|
|
|
15 |
|
|
./axi_uartlite_module_sim.sh
|
16 |
|
|
|
17 |
|
|
This command will launch the 'compile', 'elaborate' and 'simulate' functions
|
18 |
|
|
implemented in the script file for the 3-step flow. These functions are called
|
19 |
|
|
from the main 'run' function in the script file.
|
20 |
|
|
|
21 |
|
|
The 'run' function first executes the 'setup' function, the purpose of which is to
|
22 |
|
|
create simulator specific setup files, create design library mappings and library
|
23 |
|
|
directories and copy 'glbl.v' from the Vivado software install location into the
|
24 |
|
|
current directory.
|
25 |
|
|
|
26 |
|
|
The 'setup' function is also used for removing the simulator generated data in
|
27 |
|
|
order to reset the current directory to the original state when export_simulation
|
28 |
|
|
was launched from Vivado. This generated data can be removed by specifying the
|
29 |
|
|
'-reset_run' switch to the './axi_uartlite_module_sim.sh' script.
|
30 |
|
|
|
31 |
|
|
./axi_uartlite_module_sim.sh -reset_run
|
32 |
|
|
|
33 |
|
|
To keep the generated data from the previous run but regenerate the setup files and
|
34 |
|
|
library directories, use the '-noclean_files' switch.
|
35 |
|
|
|
36 |
|
|
./axi_uartlite_module_sim.sh -noclean_files
|
37 |
|
|
|
38 |
|
|
For more information on the script, please type './axi_uartlite_module_sim.sh -help'.
|
39 |
|
|
|
40 |
|
|
2. Additional design information files:-
|
41 |
|
|
|
42 |
|
|
export_simulation generates following additional file that can be used for fetching
|
43 |
|
|
the design files information or for integrating with external custom scripts.
|
44 |
|
|
|
45 |
|
|
Name : file_info.txt
|
46 |
|
|
Purpose: This file contains detail design file information based on the compile order
|
47 |
|
|
when export_simulation was executed from Vivado. The file contains information
|
48 |
|
|
about the file type, name, whether it is part of the IP, associated library
|
49 |
|
|
and the file path information.
|