03-22-2020 07:41 AM
04-08-2020 11:59 PM
Most of the documents now have an option to get a previous version of the same document included, however it seems that it is not available for UG1137. I will report the issue internally to check whether we could provide the same feature in this particular document.
06-03-2020 11:25 AM
I am using Xilinx SDK 2019.1 so I need ug1137 v10.0
ug1137 v11.0 is for 2019.2 which refers to Vitis.
Please provide a link to download ug1137 v10.0
06-09-2020 07:10 AM
I am looking for this particular version:
ug1137 version 2018.2
Do you know how can I find it? This is not available on xilinx 'older version' links.
06-09-2020 08:26 AM
These User Guides are versioned by "number" (v8, v9, v10, and v11). Version 11 is when they replaced SDK with Vitis so if you're using SDK (and you are), any of the older versions should be useful. I don't know which version of this doc is specifically tied to 2018.2, but I suspect it would be v8.0 ... see attached.
06-09-2020 08:31 AM
... Also. When you installed Vivado, you probably installed DocNav by default. If you never went back and updated those documents, you might have the file you're looking for on your hard drive already. Browse to a folder called "XilinxDocs", and drill into the sub-folders to see what version of User Guide you have. Something like C:/.../XilinxDocs/Zynq_UltraScale+MPSoC/documentation/user_guides.
06-09-2020 10:55 AM
Gotcha. My DocNav has been updated regularly. It would be great if we could navigate all versions of any particular docs from DocNav. Even better if the DocNav could tell if any docs or a set of docs have been combined to a different doc in later Xilinx version. For example, I have found that several Petalinux docs (ug97x and ug98x) are now in ug1144. It was not obvious to me until I found this info in forum search.
06-09-2020 06:37 PM
06-10-2020 03:18 AM
I have already reported the issue internally and I do agree with you that "See All Version" should be available to all the documents. The latest update I got internally is that they were looking to it but I don't have more information. Anyway thanks everybody for reporting the issue, this gives more visibility to the issue