<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dzu's Blog (Posts about xilinx)</title><link>https://blog.lazy-evaluation.net/</link><description></description><atom:link href="https://blog.lazy-evaluation.net/categories/xilinx.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2025 &lt;a href="mailto:dzu@member.fsf.org"&gt;Detlev Zundel&lt;/a&gt; </copyright><lastBuildDate>Wed, 10 Dec 2025 16:16:35 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>PetaLinux v2019.1 on Ubuntu 18.04 LTS</title><link>https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;p&gt;Although Xilinx &lt;a class="reference external" href="https://www.xilinx.com/products/design-tools/embedded-software/petalinux-sdk.html"&gt;PetaLinux&lt;/a&gt;
officially supports the Ubuntu 18.04 LTS GNU/Linux distribution, there is a small
glitch in the installation procedure.  Following &lt;a class="reference external" href="https://www.xilinx.com/support/documentation/sw_manuals/xilinx2018_2/ug1144-petalinux-tools-reference-guide.pdf"&gt;UG1144&lt;/a&gt;
the installation aborts like this:&lt;/p&gt;
&lt;div class="code"&gt;&lt;pre class="code console"&gt;&lt;a id="rest_code_75165bf29a75454e8390663680a9256c-1" name="rest_code_75165bf29a75454e8390663680a9256c-1" href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html#rest_code_75165bf29a75454e8390663680a9256c-1"&gt;&lt;/a&gt;&lt;span class="gp"&gt;dzu@zarniwoop:~/Downloads$ &lt;/span&gt;bash&lt;span class="w"&gt; &lt;/span&gt;petalinux-v2019.1-final-installer.run
&lt;a id="rest_code_75165bf29a75454e8390663680a9256c-2" name="rest_code_75165bf29a75454e8390663680a9256c-2" href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html#rest_code_75165bf29a75454e8390663680a9256c-2"&gt;&lt;/a&gt;&lt;span class="go"&gt;INFO: Checking installation environment requirements...&lt;/span&gt;
&lt;a id="rest_code_75165bf29a75454e8390663680a9256c-3" name="rest_code_75165bf29a75454e8390663680a9256c-3" href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html#rest_code_75165bf29a75454e8390663680a9256c-3"&gt;&lt;/a&gt;&lt;span class="go"&gt;awk: read error (Bad address)&lt;/span&gt;
&lt;a id="rest_code_75165bf29a75454e8390663680a9256c-4" name="rest_code_75165bf29a75454e8390663680a9256c-4" href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html#rest_code_75165bf29a75454e8390663680a9256c-4"&gt;&lt;/a&gt;
&lt;a id="rest_code_75165bf29a75454e8390663680a9256c-5" name="rest_code_75165bf29a75454e8390663680a9256c-5" href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html#rest_code_75165bf29a75454e8390663680a9256c-5"&gt;&lt;/a&gt;&lt;span class="go"&gt;Please refer to the PetaLinux Tools Installation Guide.&lt;/span&gt;
&lt;a id="rest_code_75165bf29a75454e8390663680a9256c-6" name="rest_code_75165bf29a75454e8390663680a9256c-6" href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html#rest_code_75165bf29a75454e8390663680a9256c-6"&gt;&lt;/a&gt;
&lt;a id="rest_code_75165bf29a75454e8390663680a9256c-7" name="rest_code_75165bf29a75454e8390663680a9256c-7" href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html#rest_code_75165bf29a75454e8390663680a9256c-7"&gt;&lt;/a&gt;&lt;span class="go"&gt;Check the troubleshooting guide at the end of that manual, and if you are&lt;/span&gt;
&lt;a id="rest_code_75165bf29a75454e8390663680a9256c-8" name="rest_code_75165bf29a75454e8390663680a9256c-8" href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html#rest_code_75165bf29a75454e8390663680a9256c-8"&gt;&lt;/a&gt;&lt;span class="go"&gt;unable to resolve the issue please contact customer support with file:&lt;/span&gt;
&lt;a id="rest_code_75165bf29a75454e8390663680a9256c-9" name="rest_code_75165bf29a75454e8390663680a9256c-9" href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html#rest_code_75165bf29a75454e8390663680a9256c-9"&gt;&lt;/a&gt;&lt;span class="go"&gt;   /home/dzu/Downloads/petalinux_installation_log&lt;/span&gt;
&lt;a id="rest_code_75165bf29a75454e8390663680a9256c-10" name="rest_code_75165bf29a75454e8390663680a9256c-10" href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html#rest_code_75165bf29a75454e8390663680a9256c-10"&gt;&lt;/a&gt;
&lt;a id="rest_code_75165bf29a75454e8390663680a9256c-11" name="rest_code_75165bf29a75454e8390663680a9256c-11" href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html#rest_code_75165bf29a75454e8390663680a9256c-11"&gt;&lt;/a&gt;&lt;span class="go"&gt;petalinux-v2019.1-final-installer.run: line 140: /tmp/tmp.rlFbcgKOQZ/petalinux-env-check: No such file or directory&lt;/span&gt;
&lt;a id="rest_code_75165bf29a75454e8390663680a9256c-12" name="rest_code_75165bf29a75454e8390663680a9256c-12" href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html#rest_code_75165bf29a75454e8390663680a9256c-12"&gt;&lt;/a&gt;&lt;span class="go"&gt;ERROR: Failed to extract Petalinux installer...&lt;/span&gt;
&lt;a id="rest_code_75165bf29a75454e8390663680a9256c-13" name="rest_code_75165bf29a75454e8390663680a9256c-13" href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html#rest_code_75165bf29a75454e8390663680a9256c-13"&gt;&lt;/a&gt;&lt;span class="gp"&gt;dzu@zarniwoop:~/Downloads$&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;p&gt;The fix is rather straightforward and easy, but I'll include the
explanation for a better understanding.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html?pk_campaign=feed"&gt;Read more…&lt;/a&gt; (2 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>petalinux</category><category>ubuntu</category><category>xilinx</category><guid>https://blog.lazy-evaluation.net/posts/linux/petalinux-v2019-1-ubuntu-18-04.html</guid><pubDate>Tue, 09 Jul 2019 08:05:51 GMT</pubDate></item><item><title>Vivado 2018.3 and DocNav on Debian 10 (Buster)</title><link>https://blog.lazy-evaluation.net/posts/linux/vivado-2018-3-buster.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;p&gt;Late last year the ageing effects of my old GNU/Linux desktop system
became so severe that ignoring them would soon not be an option
anymore.  One of the hard disks developed problems a while ago and
although I was able to fix it so that finally the extended &lt;a class="reference external" href="https://en.wikipedia.org/wiki/S.M.A.R.T."&gt;SMART&lt;/a&gt; test passed again without
errors, it still continued to report errors in the form of "unreadable
(pending) sectors".  The on-board USB controller also complains about
one of the internal USB ports for a long time and one DDR3 ram module
had to be replaced as diagnosed by the wonderful &lt;a class="reference external" href="https://en.wikipedia.org/wiki/Memtest86"&gt;Memtest86&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;On top of all this, the &lt;a class="reference external" href="https://icecat.biz/en/p/club3d/cgax-hp136/graphics+cards-radeon+x1300pro+256mb-443229.html"&gt;Club 3D Radeon X1300PRO&lt;/a&gt;
dual DVI graphics card started to occasionally hang the whole system a
few seconds after waking up from suspend.  Or at least that is what I
suspect as the system never recorded error messages in the log files.
The display however did visibly degrade and I think I saw some drm
error message flash by at some point.&lt;/p&gt;
&lt;p&gt;Be that as it will, I was glad that I got the chance to replace the
system in time and gradually move stuff off a functioning system
instead of attaching disassembled hard disks to a new system. The &lt;a class="reference external" href="http://www.arlt.com/PC/fluesterleise-Silent-PCs/Whisper-Serie/ARLT-Mr-Whisper-AMD-Ryzen-5-8GB-SSD-Radeon-Vega-11-arlt-1.html"&gt;AMD
Ryzen 5 2400G system&lt;/a&gt;
from ARLT Computer, available without Windows, looked like very good
value for money. Together with an HDMI to DVI adapter it should also
easily power my two DVI monitor setup and so it did not take long
until one of them stood beside my desk for installation.  As the Ryzen
CPU was introduced early in 2018 and the Linux 4.9 kernel at the core
of Debian Stretch was released end of 2016, it was clear that I needed
to go for the yet unreleased Debian Buster based on Linux 4.19.&lt;/p&gt;
&lt;img alt="Buster from Toy Story" class="align-center" src="https://blog.lazy-evaluation.net/images/toy-story-buster.jpg" style="width: 200px;"&gt;
&lt;p&gt;All in all things went smoothly until I turned to the Xilinx tool
chain that already gave me minor problems described in my previous
post &lt;a class="reference external" href="https://blog.lazy-evaluation.net/posts/linux/docnav-2017-04-debian-stretch.html"&gt;Fixing DocNav 2017.04 on Debian Stretch&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/posts/linux/vivado-2018-3-buster.html?pk_campaign=feed"&gt;Read more…&lt;/a&gt; (7 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>debian</category><category>vivado</category><category>xilinx</category><guid>https://blog.lazy-evaluation.net/posts/linux/vivado-2018-3-buster.html</guid><pubDate>Tue, 12 Feb 2019 19:38:15 GMT</pubDate></item><item><title>Fixing DocNav 2017.04 on Debian Stretch</title><link>https://blog.lazy-evaluation.net/posts/linux/docnav-2017-04-debian-stretch.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;p&gt;Having installed &lt;a class="reference external" href="https://www.xilinx.com/products/design-tools/vivado.html"&gt;Vivado 2017.04&lt;/a&gt; on one of
my GNU/Linux machines that run Debian 9.3 (Stretch), I realized that
DocNav fails to start:&lt;/p&gt;
&lt;div class="code"&gt;&lt;pre class="code console"&gt;&lt;a id="rest_code_3868989d18404341ac3cfaa36921ff36-1" name="rest_code_3868989d18404341ac3cfaa36921ff36-1" href="https://blog.lazy-evaluation.net/posts/linux/docnav-2017-04-debian-stretch.html#rest_code_3868989d18404341ac3cfaa36921ff36-1"&gt;&lt;/a&gt;&lt;span class="gp"&gt;dzu@deepthought:~$ &lt;/span&gt;.&lt;span class="w"&gt; &lt;/span&gt;/opt/Xilinx/Vivado/2017.4/settings64.sh
&lt;a id="rest_code_3868989d18404341ac3cfaa36921ff36-2" name="rest_code_3868989d18404341ac3cfaa36921ff36-2" href="https://blog.lazy-evaluation.net/posts/linux/docnav-2017-04-debian-stretch.html#rest_code_3868989d18404341ac3cfaa36921ff36-2"&gt;&lt;/a&gt;&lt;span class="gp"&gt;dzu@deepthought:~$ &lt;/span&gt;docnav
&lt;a id="rest_code_3868989d18404341ac3cfaa36921ff36-3" name="rest_code_3868989d18404341ac3cfaa36921ff36-3" href="https://blog.lazy-evaluation.net/posts/linux/docnav-2017-04-debian-stretch.html#rest_code_3868989d18404341ac3cfaa36921ff36-3"&gt;&lt;/a&gt;&lt;span class="go"&gt;docnav: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory&lt;/span&gt;
&lt;a id="rest_code_3868989d18404341ac3cfaa36921ff36-4" name="rest_code_3868989d18404341ac3cfaa36921ff36-4" href="https://blog.lazy-evaluation.net/posts/linux/docnav-2017-04-debian-stretch.html#rest_code_3868989d18404341ac3cfaa36921ff36-4"&gt;&lt;/a&gt;&lt;span class="gp"&gt;dzu@deepthought:~$&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;img alt="Xilinx Logo" class="align-center" src="https://blog.lazy-evaluation.net/images/xilinx-logo.png" style="width: 150px;"&gt;
&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/posts/linux/docnav-2017-04-debian-stretch.html?pk_campaign=feed"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>debian</category><category>xilinx</category><guid>https://blog.lazy-evaluation.net/posts/linux/docnav-2017-04-debian-stretch.html</guid><pubDate>Sun, 28 Jan 2018 17:38:29 GMT</pubDate></item></channel></rss>