<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:media="http://search.yahoo.com/mrss/" 
	>
<channel>
	<title>
	Comments for FPGATEK	</title>
	<atom:link href="https://fpgatek.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>https://fpgatek.com</link>
	<description>Learn how to implement digital circuits with FPGA from scratch</description>
	<lastBuildDate>Wed, 04 Feb 2026 12:07:12 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		Comment on FPGA Design Blueprint by Emanuele Cavaliere		</title>
		<link>https://fpgatek.com/my-courses/fpga-design-blueprint/</link>

		<dc:creator><![CDATA[Emanuele Cavaliere]]></dc:creator>
		<pubDate>Wed, 04 Feb 2026 12:07:12 +0000</pubDate>
		<guid isPermaLink="false">https://fpgatek.com/tva_course_type/384/#comment-1387</guid>

					<description><![CDATA[Should I want to have hardware at hand to work with ISE I found a 60 euro board on aliexpress  Spartan6 LX16 complete with usb blaster JTAG programmer: could it be a reasonable choice?
Regards]]></description>
			<content:encoded><![CDATA[<p>Should I want to have hardware at hand to work with ISE I found a 60 euro board on aliexpress  Spartan6 LX16 complete with usb blaster JTAG programmer: could it be a reasonable choice?<br />
Regards</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Using IP Cores in the ISE Design Suite by Ahmad Saghafi		</title>
		<link>https://fpgatek.com/course/using-ip-cores-in-the-ise-design-suite/#comments/1342</link>

		<dc:creator><![CDATA[Ahmad Saghafi]]></dc:creator>
		<pubDate>Wed, 28 Jan 2026 11:54:57 +0000</pubDate>
		<guid isPermaLink="false">https://fpgatek.com/course/using-ip-cores-in-the-ise-design-suite/#comment-1342</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://fpgatek.com/course/using-ip-cores-in-the-ise-design-suite/#comments/1337&quot;&gt;Malek Mastafa&lt;/a&gt;.

Hi Malek,

What we select in the Wizard window defines how the port contents are interpreted, not the actual VHDL type of the port. As I mentioned, the VHDL type itself is still std_logic_vector, but inside the IP the data carried by that vector is interpreted as a signed value.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://fpgatek.com/course/using-ip-cores-in-the-ise-design-suite/#comments/1337">Malek Mastafa</a>.</p>
<p>Hi Malek,</p>
<p>What we select in the Wizard window defines how the port contents are interpreted, not the actual VHDL type of the port. As I mentioned, the VHDL type itself is still std_logic_vector, but inside the IP the data carried by that vector is interpreted as a signed value.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on An Introduction to VHDL Language by Ahmad Saghafi		</title>
		<link>https://fpgatek.com/course/an-introduction-to-vhdl-language/#comments/1341</link>

		<dc:creator><![CDATA[Ahmad Saghafi]]></dc:creator>
		<pubDate>Wed, 28 Jan 2026 10:56:42 +0000</pubDate>
		<guid isPermaLink="false">https://fpgatek.com/course/an-introduction-to-vhdl-language/#comment-1341</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://fpgatek.com/course/an-introduction-to-vhdl-language/#comments/1340&quot;&gt;Stuart O&#039;Reilly&lt;/a&gt;.

Yes, the type BIT is synthesized and it is not thrown away. A signal of type BIT simply becomes a single wire or register that can only be 0 or 1. 

The real difference between BIT and std_logic is simulation, not hardware. BIT is a two-value type (0 and 1). std_logic is a simulation type with extra values like U, X, and Z. For example, Z is how we model tri-state behavior, which is required to describe and implement bi-directional I/O pins. 

Another practical reason we avoid BIT is ecosystem support. Standard packages such as numeric_std only work with std_logic.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://fpgatek.com/course/an-introduction-to-vhdl-language/#comments/1340">Stuart O&#8217;Reilly</a>.</p>
<p>Yes, the type BIT is synthesized and it is not thrown away. A signal of type BIT simply becomes a single wire or register that can only be 0 or 1. </p>
<p>The real difference between BIT and std_logic is simulation, not hardware. BIT is a two-value type (0 and 1). std_logic is a simulation type with extra values like U, X, and Z. For example, Z is how we model tri-state behavior, which is required to describe and implement bi-directional I/O pins. </p>
<p>Another practical reason we avoid BIT is ecosystem support. Standard packages such as numeric_std only work with std_logic.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on An Introduction to VHDL Language by Stuart O'Reilly		</title>
		<link>https://fpgatek.com/course/an-introduction-to-vhdl-language/#comments/1340</link>

		<dc:creator><![CDATA[Stuart O'Reilly]]></dc:creator>
		<pubDate>Tue, 27 Jan 2026 07:10:47 +0000</pubDate>
		<guid isPermaLink="false">https://fpgatek.com/course/an-introduction-to-vhdl-language/#comment-1340</guid>

					<description><![CDATA[at the end of the video you said the type BIT is only used in simulation. Well, if it is in your code, what happens to it when you synthesize your code and build your bit file?....It can&#039;t just get thrown out as that would break your code. Does it get implemented using a byte in h/w BUT acts as a BIT?]]></description>
			<content:encoded><![CDATA[<p>at the end of the video you said the type BIT is only used in simulation. Well, if it is in your code, what happens to it when you synthesize your code and build your bit file?&#8230;.It can&#8217;t just get thrown out as that would break your code. Does it get implemented using a byte in h/w BUT acts as a BIT?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Using IP Cores in the ISE Design Suite by Malek Mastafa		</title>
		<link>https://fpgatek.com/course/using-ip-cores-in-the-ise-design-suite/#comments/1337</link>

		<dc:creator><![CDATA[Malek Mastafa]]></dc:creator>
		<pubDate>Wed, 14 Jan 2026 21:03:07 +0000</pubDate>
		<guid isPermaLink="false">https://fpgatek.com/course/using-ip-cores-in-the-ise-design-suite/#comment-1337</guid>

					<description><![CDATA[Hi Ahmad,

I have a question regarding the type of the IP inputs. You said that the inputs of the IP have type Std_Logic_Vector. But, the in the window that shows the details of the IP we have chosen that A and B have type signed!!]]></description>
			<content:encoded><![CDATA[<p>Hi Ahmad,</p>
<p>I have a question regarding the type of the IP inputs. You said that the inputs of the IP have type Std_Logic_Vector. But, the in the window that shows the details of the IP we have chosen that A and B have type signed!!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Using Generic Feature for Easier Coding by Ahmad Saghafi		</title>
		<link>https://fpgatek.com/course/using-generic-feature-for-easier-coding/#comments/1336</link>

		<dc:creator><![CDATA[Ahmad Saghafi]]></dc:creator>
		<pubDate>Mon, 05 Jan 2026 11:36:37 +0000</pubDate>
		<guid isPermaLink="false">https://fpgatek.com/course/using-generic-features-for-easier-coding/#comment-1336</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://fpgatek.com/course/using-generic-feature-for-easier-coding/#comments/1335&quot;&gt;Malek Mastafa&lt;/a&gt;.

Yes. You can use it everywhere within the Architecture section.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://fpgatek.com/course/using-generic-feature-for-easier-coding/#comments/1335">Malek Mastafa</a>.</p>
<p>Yes. You can use it everywhere within the Architecture section.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Using Generic Feature for Easier Coding by Malek Mastafa		</title>
		<link>https://fpgatek.com/course/using-generic-feature-for-easier-coding/#comments/1335</link>

		<dc:creator><![CDATA[Malek Mastafa]]></dc:creator>
		<pubDate>Sun, 04 Jan 2026 21:22:45 +0000</pubDate>
		<guid isPermaLink="false">https://fpgatek.com/course/using-generic-features-for-easier-coding/#comment-1335</guid>

					<description><![CDATA[can you you the generic that you define in the entity in the architecture?]]></description>
			<content:encoded><![CDATA[<p>can you you the generic that you define in the entity in the architecture?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Describing Sequential Circuits with VHDL by Ahmad Saghafi		</title>
		<link>https://fpgatek.com/course/describing-sequential-circuits-with-vhdl/#comments/1333</link>

		<dc:creator><![CDATA[Ahmad Saghafi]]></dc:creator>
		<pubDate>Mon, 29 Dec 2025 13:53:58 +0000</pubDate>
		<guid isPermaLink="false">https://fpgatek.com/course/describing-sequential-circuits-with-vhdl/#comment-1333</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://fpgatek.com/course/describing-sequential-circuits-with-vhdl/#comments/1332&quot;&gt;Malek Mastafa&lt;/a&gt;.

Hi Malek,

In VHDL, &#039;length is an integer, so when you do math on it, VHDL uses integer arithmetic and simply truncates the result.

For example, if A&#039;length is 7, then A&#039;length/2 becomes 3. It&#039;s basically rounded down. If you want it to be rounded up instead, you can write:

(A&#039;length + 1)/2]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://fpgatek.com/course/describing-sequential-circuits-with-vhdl/#comments/1332">Malek Mastafa</a>.</p>
<p>Hi Malek,</p>
<p>In VHDL, &#8216;length is an integer, so when you do math on it, VHDL uses integer arithmetic and simply truncates the result.</p>
<p>For example, if A&#8217;length is 7, then A&#8217;length/2 becomes 3. It&#8217;s basically rounded down. If you want it to be rounded up instead, you can write:</p>
<p>(A&#8217;length + 1)/2</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Describing Sequential Circuits with VHDL by Malek Mastafa		</title>
		<link>https://fpgatek.com/course/describing-sequential-circuits-with-vhdl/#comments/1332</link>

		<dc:creator><![CDATA[Malek Mastafa]]></dc:creator>
		<pubDate>Sun, 28 Dec 2025 22:52:37 +0000</pubDate>
		<guid isPermaLink="false">https://fpgatek.com/course/describing-sequential-circuits-with-vhdl/#comment-1332</guid>

					<description><![CDATA[Hi Ahmad. what if &#039;length is odd number. what will happen if i divide it by 2]]></description>
			<content:encoded><![CDATA[<p>Hi Ahmad. what if &#8216;length is odd number. what will happen if i divide it by 2</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on IF-THEN-ELSE Statement in the Process Section by Ahmad Saghafi		</title>
		<link>https://fpgatek.com/course/if-then-else-statement-in-the-process-section/#comments/1324</link>

		<dc:creator><![CDATA[Ahmad Saghafi]]></dc:creator>
		<pubDate>Sat, 06 Dec 2025 07:22:47 +0000</pubDate>
		<guid isPermaLink="false">https://fpgatek.com/course/if-then-else-statement-in-the-process-section/#comment-1324</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://fpgatek.com/course/if-then-else-statement-in-the-process-section/#comments/1323&quot;&gt;Paul Norman&lt;/a&gt;.

Good question. What I explained in this video is about describing combinational circuits inside a process statement. In combinational circuits, any change in an input can cause a change in the output, independent of the other inputs. So the rule is: include all inputs in the sensitivity list.

However, this isn&#039;t what you&#039;ll typically do in practice. Almost all the circuits you describe will be synchronous sequential, meaning they have a clock input and every operation is synchronized with the rising edge of the clock. In that case, the only signal you place in the sensitivity list is the clock itself.

We&#039;ll talk about this in more detail in the upcoming lessons.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://fpgatek.com/course/if-then-else-statement-in-the-process-section/#comments/1323">Paul Norman</a>.</p>
<p>Good question. What I explained in this video is about describing combinational circuits inside a process statement. In combinational circuits, any change in an input can cause a change in the output, independent of the other inputs. So the rule is: include all inputs in the sensitivity list.</p>
<p>However, this isn&#8217;t what you&#8217;ll typically do in practice. Almost all the circuits you describe will be synchronous sequential, meaning they have a clock input and every operation is synchronized with the rising edge of the clock. In that case, the only signal you place in the sensitivity list is the clock itself.</p>
<p>We&#8217;ll talk about this in more detail in the upcoming lessons.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced 

Served from: fpgatek.com @ 2026-04-21 04:41:42 by W3 Total Cache
-->