Last supported Release
| Type or File | Version |
|---|---|
| Vivado Design Suite | 2015.4 |
| Trenz Project Scripts | 2015.4.02 |
| Trenz board_files.csv | 1.2 |
| Trenz apps_list.csv | 1.3 |
Directory structure
| File or Directory | Type | Description |
|---|---|---|
| <design_name> | base directory | Base directory with predefined batch files (*.cmd) to generate or open VIVADO-Project |
| <design_name>/block_design/ | source | Script to generate Block Design in Vivado (*_bd.tcl) |
| <design_name>/board_files/ | source | Local board part files repository and a list of available board part files (<board_series>_board_files.csv) |
| <design_name>/constraints/ | source | Project constrains (*.xdc) |
| <design_name>/doc/ | source | Documentation |
| <design_name>/ip_lib/ | source | Local Vivado IP repository |
| <design_name>/misc/ | source | (optional) Directory with additional sources |
| <design_name>/prebuilt/boot_images/ | prebuilt | Directory with prebuild boot images (*.bin, *.mcs) and configuration files (*.bif) included in subfolders: default or <board_file_shortname>/<app_name> |
| <design_name>/prebuilt/hardware/ | prebuilt | Directory with prebuild hardware sources (*.bit, *hdf) and reports included in subfolders: default or <board_file_shortname> |
| <design_name>/prebuilt/software/ | prebuilt | (optional) Directory with prebuild software sources (*.elf) included in subfolders: default or <board_file_shortname>/<app_name> |
| <design_name>/prebuilt/os/ | prebuilt | (optional) Directory with supported OS sources |
| <design_name>/scripts/ | source | TCL scripts to build a project |
| <design_name>/sw_lib/ | source | (optional) Directory with local SDK/HSI software IP repository and a list of available software (apps_list.csv) |
| <design_name>/v_log/ | generated | Temporary directory with vivado log files (used only when vivado is started with predefined command files (*.cmd) from base folder otherwise this logs will be writen into the vivado working directory) |
| <design_name>/vivado/ | work, generated | Working directory where Vivado project is created. Vivado project file is <design_name>.xpr |
| <design_name>/workspace/ | work, generated | (optional) Directory where hsi project is created |
Windows Command Files
| File Name | Description |
|---|---|
| clear_project.cmd | Delete "<design_name>/v_log/", "<design_name>/vivado/", and "<design_name>/workspace/" directory with related documents. |
| create_project_firstgui.cmd | Create Project with setting from "start_settings.cmd" and source folders. Vivado GUI will be opened during the process. Delete "<design_name>/v_log/", "<design_name>/vivado/", and "<design_name>/workspace/" directory with related documents before Projekt will created. |
| create_project_nogui.cmd | Create Project with setting from "start_settings.cmd" and source folders. Delete "<design_name>/v_log/", "<design_name>/vivado/", and "<design_name>/workspace/" directory with related documents before Projekt will created. |
| open_project_gui.cmd | Opens an existing Project "<design_name>/vivado/<design_name>.xpr". Delete old "<design_name>/v_log/" before Projekt will opend. |
| run_prebuild_all.cmd | Create Project with setting from "start_settings.cmd" and source folders. Build all Vivado hardware and software files if the sources are available. Delete "<design_name>/v_log/", "<design_name>/vivado/", and "<design_name>/workspace/" directory with related documents before Projekt will created. This will be done for all available Board Parts from the |
| run_project_nogui.cmd | Create Project with setting from "start_settings.cmd" and source folders. Build all Vivado hardware and software files if the sources are available. Delete "<design_name>/v_log/", "<design_name>/vivado/", and "<design_name>/workspace/" directory with related documents before Projekt will created. |
| start_settings.cmd | Set Vivado Version for all other .cmd files and used board part number for create_*.cmd and run_*.cmd files (avaliable IDs found in <design_name>/board_files/board_files.csv) Don't change Vivado Version. Change only required board part number. |
Checklist
- Are you using exactly the same Vivado version? If not then the scripts will not work, no need to try.
- Do you run the script from Vivado console? They may work from Vivado GUI TCL prompt also, but they are tested only from pure Vivado TCL console prompt.
- Ary you using Vivado in Windows PC? Vivado works in Linux also, but the scripts are tested on Windows only.
- Is you PC OS Installation English? Vivado may work on national versions also, but there have been known problems,
References
- Xilinx User Guide UG949
- Revision Control use guide from Vivado User Club 2015 Stuttgart
- SDSoC platform builder file structure
Overview
Content Tools