Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

  

Last supported Release

Type or FileVersion
Vivado Design Suite2015.4
Trenz Project Scripts2015.4.01
Trenz board_files.csv1.1
Trenz apps_list.csv

1.3


Directory structure

File or DirectoryTypeDescription
<design_name>/board_files/base directorybase directory with predefined batch files (*.cmd) to generate or open VIVADO-Project
<design_name>/block_design/sourceScript to generate Block Design in Vivado (*_bd.tcl) sourceLocal copy of board part files
<design_name>/Scriptsboard_files/sourceTCL scripts to build and/or create the projectLocal board part files repository and a list of available board part files  (board_files.csv)
<design_name>/Constraintsconstraints/sourceConstraintsProject constrains (*.xdc)
<design_name>/Docdoc/sourceDocumentation
<design_name>/IPip_lib/sourceLocal Vivado IP repository
<design_name>/IPI-BDsmisc/sourceScripts for IPI Block Diagrams(optional) directory with additional sources
<design_name>/prebuilt/prebuiltprebuilt files
<design_name>/prebuiltscripts/hardware sourceTCL scripts to build a projectHDF BIT
<design_name>/prebuilt/software /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/generatedTemporary 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)ELF
<design_name>/vivado/work, generatedWorking 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

Vivado Project File
File NameDescription
clear_project.cmdDelete "<design_name>/v_log/", "<design_name>/vivado/", and "<design_name>/workspace/" directory with related documents.
create_project_firstgui.cmdCreate 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.cmdOpens an existing Project "<design_name>/vivado/<design_name>.xprgenerated". 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 

 

 

Checklist

  1. Are you using exactly the same Vivado version? If not then the scripts will not work, no need to try.
  2. 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.
  3. Ary you using Vivado in Windows PC? Vivado works in Linux also, but the scripts are tested on Windows only.
  4. Is you PC OS Installation English? Vivado may work on national versions also, but there have been known problems,

...