<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Xilinx on Sigasi</title><link>https://www.sigasi.com/tags/xilinx/</link><description>Recent content in Xilinx on Sigasi</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 22 Aug 2011 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sigasi.com/tags/xilinx/index.xml" rel="self" type="application/rss+xml"/><item><title>You can't write VHDL code without an intelligent editor!</title><link>https://www.sigasi.com/opinion/you-cant-write-vhdl-code-without-intelligent-editor/</link><pubDate>Mon, 22 Aug 2011 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/opinion/you-cant-write-vhdl-code-without-intelligent-editor/</guid><description>&lt;p&gt;Yesterday evening I was reading the &lt;a
 style="white-space: nowrap;"
 href="https://issuu.com/xcelljournal/docs/xcell_journal_issue_76?viewMode=magazine&amp;amp;mode=embed"
 
 target="_blank"
 
 &gt;latest edition of the Xilinx Xcell journal&amp;nbsp;&lt;span uk-icon="icon: sign-out; ratio: 0.7"&gt;&lt;/span&gt;&lt;/a&gt; and encountered an interesting article about &lt;strong&gt;&amp;ldquo;How Do I Reset My FPGA&amp;rdquo;&lt;/strong&gt;. This article gives some valuable tips and best practices on how to implement reset structures in FPGAs. The author also gives a VHDL code example on how to infer the reset structure of your choice.
To my surprise the author &amp;ndash;without doubt an &lt;strong&gt;experienced designer&lt;/strong&gt;&amp;ndash; made &lt;strong&gt;multiple VHDL errors in a simple code snippet&lt;/strong&gt;:&lt;/p&gt;</description></item><item><title>List of known VHDL metacomment pragma's</title><link>https://www.sigasi.com/tech/list-known-vhdl-metacomment-pragmas/</link><pubDate>Thu, 28 Apr 2011 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/tech/list-known-vhdl-metacomment-pragmas/</guid><description>&lt;p&gt;Following up on a previous post, &lt;a href="https://www.sigasi.com/tech/vhdl-pragmas/"&gt;VHDL Pragmas&lt;/a&gt;, this is an incomplete list of supported VHDL pragmas, organized by vendor.&lt;/p&gt;
&lt;p&gt;As an introduction, most pragmas have the following structure:&lt;/p&gt;
&lt;div class="code-block-container"&gt;
 &lt;div class="code-block-header"&gt;
 &lt;span class="code-block-lang"&gt;VHDL&lt;/span&gt;
 &lt;button class="code-block-copy" aria-label="Copy code to clipboard"&gt;
 &lt;i data-lucide="copy" style="width: 1rem; height: 1rem;"&gt;&lt;/i&gt;
 &lt;/button&gt;
 &lt;/div&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-vhdl" data-lang="vhdl"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;-- trigger directive&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;where &lt;code&gt;trigger&lt;/code&gt; is a keyword such as &lt;code&gt;pragma&lt;/code&gt; or &lt;code&gt;synthesis&lt;/code&gt;, and the &lt;code&gt;directive&lt;/code&gt; is a special compiler directive.
Many tools support several triggers, each with identical meaning.&lt;/p&gt;</description></item><item><title>Is Xilinx slowly dumping Modelsim?</title><link>https://www.sigasi.com/opinion/xilinx-slowly-dumping-modelsim/</link><pubDate>Fri, 14 May 2010 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/opinion/xilinx-slowly-dumping-modelsim/</guid><description>&lt;p&gt;For years, both Xilinx and Altera have provided a free version of Mentor Graphics&amp;rsquo; Modelsim. This was a nice symbioses, since FPGA customers need a simulator in order to create designs. Xilinx and Altera have always provided EDA tools at a very low cost, and made their money on silicon rather than EDA software. Teams that create large hardware designs would still need an expensive full version of Modelsim, rather than the free version that comes with their FPGA tools.&lt;/p&gt;</description></item></channel></rss>