Page History
...
| Type or File | Version |
|---|---|
| Vivado Design Suite | 2016.4 |
| Trenz Project Scripts | 2016.4.0506 |
| Trenz <board_series>_board_files.csv | 1.2 |
| Trenz apps_list.csv | 1.9 |
| Trenz zip_ignore_list.csv | 1.0 |
Currently limitations of functionality
- No limitations are known
- for modules with dual parallel QSPI implementation only:
Configure Flash with TE::pr_program_flash_binfile does not work. Reason: Select FSBL file is not implemented. Workaround: Use Vivado or SDK GUI and select FSBL manually.
- for modules with dual parallel QSPI implementation only:
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). (optional) Some board part designs used subfolder <board_file_shortname> with Board Part specific Block Design (*_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>/board_files/carrier_extension | source | (Optional) Additional TCL-Scripts to extend Board Part PS-Preset with carrier board specific settings. |
| <design_name>/console | source | folder with different console command files. Use _create_win_setup.cmd to generate files on top folder. Linux version currently not available. |
| <design_name>/constraints/ | source | Project constrains (*.xdc). Some board part designs used subfolder <board_file_shortname> with additional constrains (*.xdc) |
| <design_name>/doc/ | source | Documentation |
| <design_name>/hdl/ | source | HDL-File and XCI-Files. Advanced usage only! |
| <design_name>/firmware/ | source | ELF-File Location for MicroBlaze Firmware. Additional sub folder is used for MicroBlaze identification. |
| <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 prebuilt boot images (*.bin) and configuration files (*.bif) for zynq and configured hardware files (*.bit and *.mcs) for micoblaze included in sub-folders: default or <board_file_shortname>/<app_name> |
| <design_name>/prebuilt/hardware/ | prebuilt | Directory with prebuilt hardware sources (*.bit, *hdf, *.mcs) and reports included in subfolders: default or <board_file_shortname> |
| <design_name>/prebuilt/software/ | prebuilt | (Optional) Directory with prebuilt software sources (*.elf) included in subfolders: default or <board_file_shortname>/<app_name> |
| <design_name>/prebuilt/os/ | prebuilt | (Optional) Directory with predefined OS images included in subfolders <os_name>/<board_file_shortname> or <os_name>/default |
| <design_name>/scripts/ | source | TCL scripts to build a project |
| <design_name>/settings/ | source | (Optional) Additional design settings: zip_ignore_list.csv, vivado project settings, SDSOC settings |
| <design_name>/software/ | source | (Optional) Directory with additional software |
| <design_name>/os/ | source | (Optional) Directory with additional os sources in in subfolders <os_name> |
| <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 | (Temporary) Working directory where Vivado project is created. Vivado project file is <design_name>.xpr |
| <design_name>/vivado_lab/ | work, generated | (Optional/Temporary) Working directory where Vivado LabTools is created. LabTools project file is <design_name>.lpr |
| <design_name>/workspace/hsi | work, generated | (Optional/Temporary) Directory where hsi project is created |
| <design_name>/workspace/sdk | work, generated | (Optional) Directory where sdk project is created |
| <design_name>/sdsoc | work, generated | (Optional) Directory where SDSOC project is created |
| <design_name>/backup/ | generated | (Optional) Directory for project backups |
...
HDL files can be saved in the subfolder "<design_name>/hdl/" or "<design_name>/hdl/<shortname>" and all subfolders of "<design_name>/hdl/<shortname>". They will be loaded automatically on project creation. Available formats are *.vhd, *.v and *.sv. A own top-file must be specified with the name "<design_name>_top.v" or "<design_name>_top.vhd".
...
Overview
Content Tools