UPGRADE YOUR BROWSER
We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!
How do I use the MYVIVADO environment variable to apply a tactical patch for either a Vivado or PlanAhead install?
Note: In Vivado 2016.1, a new variable named XILINX_PATH is introduced and replaces the MYVIVADO variable.
For Vivado 2016.1 and later versions, please see (Xilinx Answer 66722).
The MYXILINX equivalent in Vivado is a variable called MYVIVADO that can contain one or more paths (delimited by a ':' on Linux, ';' on Windows) to other patches.
The $MYVIVADO area allows you to use Xilinx software patches without affecting your original install area.
In a shared environment, this allows individual users to apply any patch they need without affecting other users.
The $MYVIVADO directory structure should match that of the Vivado or PlanAhead install area.
Note: If a certain patch is desirable for use by all engineers at a site, In Vivado 2014.4 and later, the patches can be installed in the $XILIINX_VIVADO install directory under a user-created "patches" directory.
It is important to use patches only with the software for which they were built.
For example, if you have a patch in the $MYVIVADO area that was built for 2014.3, you must not use this patch with the 2014.4 version of Vivado tools.
Patches that are built for a certain build of software are included in the next full release of the software.
When the Vivado software loads a data file (for example, a speed file), it first checks to see if the required file exists in the $MYVIVADO area.
If so, it uses it and prints a message notifying the user that a $MYVIVADO data file is overriding the default VIVADO data file.
Next, Vivado will look in the $XILINX_VIVADO/patches directory.
If the file does not exist in the $MYVIIVADO or patches directories then Vivado uses the original data file within the $XILINX_VIVADO tree.
The following is an example of how to change from a standard environment to an environment that accesses a patch using the $MYVIVADO variable on Linux:
setenv MYVIVADO /home/user/patches/Vivado/2012_3_ar50123_patch
On Windows, the appropriate commands would be:
set MYVIVADO=C:\patches\Vivado\2012_3_ar50123_patch
The paths contained in MYVIVADO will take precedence going from left to right.
This means that if patches contain the same files, the files first patch listed in MYVIVADO will be used.
Using Multiple Vivado Patches:
Example 1:
/opt/Vivado_AR12344 <-- Patch for AR12344
/opt/Vivado_AR12345 <-- Patch for AR12345
/opt/Xilinx/2012.4/
Vivado/
bin/
vivado
data/
baseline.txt <-- points to /opt/Xilinx/ISE_DS/14.4/PlanAhead
ISE_DS/
14.4/
PlanAhead/
bin/
...
...
These are the options for using multiple patches:
For Vivado 2014.4 and later, we have the following support for multiple patches:
Answer Number | Answer Title | Version Found | Version Resolved |
---|---|---|---|
54206 | PlanAhead - MYXILINX enviroment variable is not loaded by the PlanAhead tool | N/A | N/A |
62520 | LogiCORE IP SMPTE2022-5/6 Video Over IP Transmitter v4.0 - Why is the Primary MAC address stuck at 0? | N/A | N/A |
63014 | LogiCORE IP DisplayPort v5.0 - This answer record contains patch updates for the LogiCORE IP DisplayPort v5.0 | N/A | N/A |
64817 | 2014.4 PetaLinux - --get-hw-description errors out. | N/A | N/A |
AR# 53821 | |
---|---|
Date | 12/15/2017 |
Status | Active |
Type | General Article |
Tools |
|