Sourcing hdk_setup.sh fails with patch AR71715 installed on Vivado 2018.2

Question

Since some of the later versions, sourcing hdk_setup.sh checks whether patch AR71715 is installed and if not, installs it.  
  
But: after it is installed, hdk_setup does no longer recognize the installed version as valid, i.e.:

```
INFO: Setting up environment variables
INFO: Base vivado version is Vivado v2018.2_AR71715 (64-bit) ; Checking if patch AR71715 needs to be installed
INFO: Using Vivado v2018.2_AR71715 (64-bit)
ERROR: Vivado v2018.2_AR71715 (64-bit) is not supported by this HDK release.
ERROR: Supported versions are:
Vivado v2017.4 (64-bit)
Vivado v2017.4.op (64-bit)
Vivado v2018.2_AR71275_op (64-bit)
Vivado v2018.2.op (64-bit)
Vivado v2018.2 (64-bit)
```

Note I'm using an on premise version of Vivado and installed the patch using the XILINX_PATH method \[1]  
  
I think hdk_setups hould recognize **v2018.2_AR71715** as valid version. Or am I mistaken?  
  
\[1] https://www.xilinx.com/support/answers/66722.html

Accepted Answer

Hello,  
  
The AR71715 patch is for SDAccel fixes and need not be used for HDK usage.   
  
On our setup flows on the FPGA Developer AMI the scripts try installing it in _/opt/Xilinx/SDx/patches_ path as that is the recommended way by Xilinx. That is why the Xilinx version does not show up as _Vivado v2018.2_AR71715 (64-bit)_ when running the HDK flow.  
  
If you are not using the SDAccel flow, you don't need to use the patch. I believe hdk_setup.sh would try installing it anyways and possibly fail in an on premise setting(I presume this is why you added the patch using the XILINX_PATH method).  
  
We are working on a way to allow for patching for our on-premise customers where you might not have access to the Xilinx install directories, but in the meanwhile you can get around this by either adding _Vivado v2018.2_AR71715 (64-bit)_ to the supported_vivado_versions.txt file or commenting out the setup_patches function in hdk_setup.sh as below and removing the patch from your XILINX_PATH env var:

```
### IN hdk_setup.sh ###
# Install any patches as required
#setup_patches <---- Comment this call out
```

Hope this helps!  
  
-Deep

Answer

"I presume this is why you added the patch using the XILINX_PATH method" - this is correct, I do not have superuser access on the machine I'm using Vivado on.  
  
Thanks for the explanation.

Answer

Hey, I did not apply the patch by copying any files to the Vivado installation directory, as I have no write access to that. I applied it by setting the XILINX_PATH environment variable (this is the recommended way by Xilinx for multi-user environments) - I have no other option than that.

Answer

You most likely did the same that we did which is apply the patch manually to the .../Vivado/2018.2/scripts path instead of the .../SDx/2018.2/scripts/ path.  If you apply the patch to the correct files it will not change the reported version and will not require modifying the AWS scripts.  
  
That said it is annoying that AWS scripts require that an SDx patch be applied to a base Vivado use case.

Sourcing hdk_setup.sh fails with patch AR71715 installed on Vivado 2018.2

Relevant content