![Alpha Data XRM(2)-DAC-D4/1G User Manual Download Page 11](http://html1.mh-extra.com/html/alpha-data/xrm-2-dac-d4-1g/xrm-2-dac-d4-1g_user-manual_2905503011.webp)
XRM(2)-DAC-D4/1G User Guide
V2.2 - Mar 8, 2018
The main Vivado folder contains three files - genxpr.bat, genxpr.tcl, makexpr.tcl plus a folder named after each
supported model of board; currently there are only two models supported, the 7K1 and the 7V1.The model
folders contain TCL files that are specific to the design.
Each model folder contains a ‘vivado-scripts’ folder and an xdc file. The xdc file specifies the XRM(2)-to-admxrc
connections for that model. Each 'design-model-device.tcl' file in the ‘vivado-scripts’ folder corresponds to the
scr file for ISE; the 'design-model.tcl' file in the same folder performs a similar function to the prj file. In this file
the required source files (.vhd and .ngc) and the paths to them relative to the main Vivado folder are defined.
All of these files ( xdc, TCL) are provided as part of the release. Normally only the 'design-model.tcl' file is ever
altered and then that only when path names need to be corrected. Note that additional (standard) xdc files from
the SDK are required in order to build the bit file correctly and these are also referenced in the 'design-model.tcl'
file.
Once the batch file has been run, the main Vivado folder will contain a third folder which is created by Vivado as
part of the script. This folder is named 'vivado' (note that this is at a level below the main Vivado folder) and the
sub-folders within, named from a combination of the valid model-device variables, are used as the location for
working folders when projects are run.
Genxpr.bat accepts command line parameters to allow projects for single boards, single board types or all
supported boards to be generated. The absence of any command line parameters is interpreted as a command
to make all projects. Using the batch file allows parameters to be passed to the script, something that is not
possible when using the standard TCL ‘source’ command from within Vivado (or other TCL interpreters).
The batch file runs genxpr.tcl in Vivado using batch mode; note that any existing xpr file is not overwritten unless
over-write permission is explicitly specified on the command line. Genxpr.tcl subsequently invokes makexpr.tcl
for each required model and device specified via the command line, creating the working folders for each model/
design combination specified.
Genxpr.tcl is based on the file of the same name that can be found in the SDK Vivado projects. In the SDK case,
the script allows all SDK design examples ( simple, uber etc.) to be generated; in the XRM case there is only a
single design, the one for the XRM(2)-dac-d4. Furthermore, in most cases the top-level entity name (reflected in
the vhdl file name) is not the same as the design name so an extra function has been added (gen_design_top)
to handle this.
The folders thus created for each of the model types contains the xpr and a ‘design-model-device_bit_post.tcl’
for that model. The projects are run from the Vivado GUI by opening the required xpr file; any files produced by
Vivado are stored in the same folder to keep things neat. The ‘design-model-device_bit_post.tcl’ specifies some
post-processing of the bit file necessary to produce the bitfile name expected by the SDK application.
Page 7
Introduction
xrm-dac-d4-1g-manual_v2_2.pdf