User Tools

Site Tools


xilinx_upgrading_vivado_project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
xilinx_upgrading_vivado_project [2019/05/16 11:19]
rpjday [Processing 2018.2 project]
— (current)
Line 1: Line 1:
-===== Overview ===== 
  
-Basic steps to upgrade a Vivado project. 
- 
-===== Required ===== 
- 
-  * A current (older) Vivado project. 
-  * Two installed versions of Vivado. 
- 
-===== Project structure ===== 
- 
-Minimally, a Vivado project directory should have a structure something like this: 
- 
-<​code>​ 
-$ tree 
-. 
-├── docs 
-│   └── holder 
-├── loads 
-│   └── holder 
-├── scripts 
-│   ├── bd.tcl 
-│   └── project_all.tcl 
-└── vivado 
-    ├── constraints 
-    │   ├── 00_debug.xdc 
-    │   ├── 10_timing_clock.xdc 
-    │   ├── 11_timing_external.xdc 
-    │   ├── 12_timing_internal.xdc 
-    │   ├── 13_timing_multicycle_path.xdc 
-    │   ├── 14_timing_false_path.xdc 
-    │   ├── 15_timing_others.xdc 
-    │   ├── 20_physical_external.xdc 
-    │   └── 21_physical_internal.xdc 
-    └── projects 
-        └── holder 
-</​code>​ 
-        ​ 
-Additionally,​ you can verify the project version from the ''​bd.tcl''​ file, which should contain a line something like this: 
- 
-<​code>​ 
-set scripts_vivado_version 2018.2 
-</​code>​ 
- 
-For this example, we'll upgrade the project above from 2018.2 to 2018.3. 
- 
-===== Processing 2018.2 project ===== 
- 
-Source 2018.2 Vivado environment,​ ''​cd''​ to project directory: 
- 
-<​code>​ 
-$ source .../​settings64.sh 
-</​code>​ 
- 
-Create the pre-requisite ''​.xpr''​ file with: 
- 
-<​code>​ 
-$ vivado -mode tcl -source scripts/​bd.tcl -notrace 
-</​code>​ 
- 
-You need to ''​exit''​ from Vivado shell when done. 
- 
-Generated artifacts include essential ''​project_1.xpr''​. 
xilinx_upgrading_vivado_project.1558005590.txt.gz · Last modified: 2019/05/16 11:19 by rpjday