Versions Compared


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


There are two options for installing the Board Part files

  • Option1: Use Trenz Electronic Reference Design with local board part file
  • Option2: Install into a User Repository
  • Option2Option3: Install into the Vivado installation

Attention: The board part files of our reference designs are for the corresponding Vivado version of the project delivery. It's possible to use them with other versions, but maybe it's not working correctly with other Vivado versions.

Option1: Use Trenz Electronic Reference Design with local board part file

The board part file will be set for the local project, if the project is generated with the provided scripts from the project delivery. More information on: Project Delivery

Option2: Install into a User Repository

This Option allows you to install the Vivado Board Part files to any location of your choosing. The disadvantage is that it required an additional command to point the tools to your repository.


Setting this parameter in the Vivado TCL Console is shown below. Set the following parameter as the first command after the Vivado integrated design environment (IDE) opens. Notice the direction of the ‘/’ forward slash. A backward slash will be accepted, but the path will not be registered correctly. To use this method you will need issue the command each time you launch Vivado.

For the Vivado 2014.4 please use the command:

set_param project.boardPartRepoPaths C:/TE 

For the vivado 2015.1 please use the command:


If you finish to create the init.tcl file, place this file in the software installation:


Attention: This description s for Vivado 2015.1 and higher. Older Vivado versions used other variable names, so some changes are necessary.

  1. Copy the  init.tcl from this Website to your Vivado Script location: <installdir>/vivado/<version>/scripts/. If this file exists on your installation path, copy only the content into the existing tcl-file.
  2. Copy the Board part files folder from the reference project (<reference_design>/board_files/) into the folder C:/TE (the folder location can be changed in the init.tcl script). The *.csv file from <reference_design>/board_files/ is not necessary for this way.
  3. Start your Vivado Version and the TCL-console printout should be the following:
    Image Added

    Image Added

    Please make sure you use plain ASCII text editor when creating the init.tcl file, any non ASCII character in the file will make Vivado to freeze on startup.

    A working init.tcl file is provided in the archive with this tutorial. With this method you can set up a permanent initialization TCL that is read by Vivado each time it launches. Details about the init.tcl file are included in UG835 Vivado Design Suite Tcl Command Reference Guide. UG835 describes where to put the init.tcl file. 



Option3: Install into the Vivado installation

This is the quickest option, but it is not recommended by Xilinx. Use at your own risk.

  1. Extract the archive to the following location. 
    Now browse to the following location. The screenshot below shows the contents of this directory after the installation of the TEboards.
    installdir\Vivado\2014.2\data\boards\board_parts\ artix7
    Image Removed
    Copy the Board part files folder from the reference project (<reference_design>/board_files/) into the folder <installdir>/vivado/<version>/data/boards/board_files/. The *.csv file from <reference_design>/board_files/ is not necessary for this way.

Test in Vivado

Regardless of which method you choose, the new boards should now be visible in Vivado 20142015.4 1 or higher for vendor . To test this out, do the following.

  1. Launch Vivado 2014.4.
  2. Select Create New Project.
  3. Click Next>  to get started.
  4. Set the project name and location. Press Next>.
  5. Select project type Click Next>.
  6. At the Default Part screen,
    a, Click Boards under Specify.
    b, Click under Vendor.


Software Requirements

The software used is

  • Windows-7 64-bit
  • Xilinx Vivado 2014Xilinx Vivado  2015.4 or 2015.1higher