<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Altera on Sigasi</title><link>https://www.sigasi.com/tags/altera/</link><description>Recent content in Altera on Sigasi</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 21 Nov 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sigasi.com/tags/altera/index.xml" rel="self" type="application/rss+xml"/><item><title>Importing a Quartus project in Sigasi Visual HDL</title><link>https://www.sigasi.com/knowledge/how_tos/importing-quartus-project-sigasi/</link><pubDate>Fri, 30 Mar 2018 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/knowledge/how_tos/importing-quartus-project-sigasi/</guid><description>&lt;p&gt;For some time it has been possible to &lt;a
 style="white-space: nowrap;"
 href="https://www.sigasi.com/legacy/eclipse/tools/#altera-quartus-ii-integration"
 
 &gt;integrate Sigasi Visual HDL (SVH) in Altera Quartus&lt;/a&gt;.
Through feedback from our users, we have seen that this approach is good when starting a project or taking off with SVH on an existing Altera Quartus project.
However, as a project grows and when more of the development work happens in SVH, keeping the link to the Altera Quartus project often gets in the way.
Switching to a separate SVH project is more flexible. For example, this allows to show the source files in a hierarchical way in the Project Explorer.&lt;/p&gt;</description></item><item><title>Opening VHDL files in Sigasi, using Quartus</title><link>https://www.sigasi.com/legacy/tech/opening-vhdl-files-sigasi-using-quartus/</link><pubDate>Wed, 19 Dec 2012 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/legacy/tech/opening-vhdl-files-sigasi-using-quartus/</guid><description>&lt;p&gt;This page deals with step three of using the Quartus integration plugin for Sigasi. We assume have already set up Sigasi as default editor in &lt;a
 style="white-space: nowrap;"
 href="https://www.sigasi.com/legacy/eclipse/opening/#intel-quartus"
 
 &gt;Intel Quartus&lt;/a&gt;.&lt;/p&gt;
&lt;h2 
 class="uk-heading-large" 
 id="how-to-open-an-hdl-file-in-quartus"&gt;
 &lt;a
 href="https://www.sigasi.com/legacy/tech/opening-vhdl-files-sigasi-using-quartus/#how-to-open-an-hdl-file-in-quartus"
 class="uk-link-reset"
 aria-label="Link to this section: How to open an HDL file in Quartus"&gt;
 How to open an HDL file in Quartus
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Step three happens when you open a VHDL file in Quartus, and Sigasi kicks in to show you the file. There are several ways to open an HDL file in Quartus. The most common ways are: you can double-click a file in the Quartus project navigator, or double-click an error in the console log.&lt;/p&gt;</description></item><item><title>VHDL Physical Type is not Synthesizable, or is it? (part 2)</title><link>https://www.sigasi.com/legacy/tech/vhdl-physical-type-not-synthesizable-or-it-part-2/</link><pubDate>Mon, 15 Oct 2012 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/legacy/tech/vhdl-physical-type-not-synthesizable-or-it-part-2/</guid><description>&lt;p&gt;In a previous post, &lt;a href="https://www.sigasi.com/legacy/tech/vhdl-physical-type-not-synthesizable-or-it/"&gt;VHDL Physical Type is not Synthesizable, or is it?&lt;/a&gt;, I pointed out that VHDL synthesis tools can indeed synthesize VHDL physical types. In the example I gave, all computations with physical types were done at elaboration time, so that the synthesis tool does not really have to deal with physical types at all.&lt;/p&gt;</description></item><item><title>VHDL Physical Type is not Synthesizable, or is it?</title><link>https://www.sigasi.com/legacy/tech/vhdl-physical-type-not-synthesizable-or-it/</link><pubDate>Thu, 11 Oct 2012 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/legacy/tech/vhdl-physical-type-not-synthesizable-or-it/</guid><description>&lt;p&gt;Everybody who has been taught VHDL in college or in a company with senior colleagues has heard the following &lt;em&gt;&amp;ldquo;wisdom&amp;rdquo;&lt;/em&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Pysical types are for simulation only. They cannot be synthesized.&lt;/em&gt;
[commonly heard claim – debunked in this article]&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></channel></rss>