<?xml version="1.0" encoding="utf-8"?><!-- generator="b2evolution/7.2.4-stable" -->
<rss version="0.92">
	<channel>
		<title>Technology Blogs - Latest Comments</title>
		<link>https://blog.abbey1.org.uk/index.php/technology/?disp=comments</link>
		<description></description>
		<language>en-GB</language>
		<docs>http://backend.userland.com/rss092</docs>
				<item>
			<title>In response to: Script to compile Xilinx Primitives with Intel's FPGA Starter edition QuestaSim</title>
			<description>&lt;p&gt;Vivado IP is the next level of abstraction up. You would need to generate the FIR filter and then figure out which files you needed to include in your broader compile script. For example:&lt;/p&gt;
&lt;p&gt;PLL:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;pll\pll_sim_netlist.vhdl&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;AXI IP:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;axis_broadcaster\gen\axis_broadcaster_sim_netlist.vhdl&lt;/li&gt;
&lt;li&gt;axis_combiner\gen\axis_combiner_sim_netlist.vhdl&lt;/li&gt;
&lt;li&gt;axis_register_slice\gen\axis_register_slice_sim_netlist.vhdl&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;DFX Controller: You will need something more elaborate like &lt;a href=&quot;https://github.com/philipabbey/fpga/blob/main/VHDL/DFX_PS/modelsim_compile.cmd&quot; rel=&quot;nofollow ugc&quot;&gt;https://github.com/philipabbey/fpga/blob/main/VHDL/DFX_PS/modelsim_compile.cmd&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;There&amp;#8217;s no simple answer here, you have to do the hard work to figure it out. Good Luck!&lt;/p&gt;</description>
			<link>https://blog.abbey1.org.uk/index.php/technology/script-to-compile-xilinx-primitives-with-intel-s#c16</link>
		</item>
				<item>
			<title>In response to: Script to compile Xilinx Primitives with Intel's FPGA Starter edition QuestaSim</title>
			<description>&lt;p&gt;Hey!&lt;/p&gt;

&lt;p&gt;how can I compile xilinx IP like for example FIR compiler with this?&lt;/p&gt;</description>
			<link>https://blog.abbey1.org.uk/index.php/technology/script-to-compile-xilinx-primitives-with-intel-s#c15</link>
		</item>
				<item>
			<title>In response to: Script to compile Xilinx Primitives with Intel's FPGA Starter edition QuestaSim</title>
			<description>&lt;p&gt;Thank you for taking the time to post your appreciation. I think you have spotted a mistake and I need to re-test with your correction.&lt;/p&gt;

&lt;p&gt;The AMD/Xilinx question states &amp;#8220;This question is closed&quot;, so I can&amp;#8217;t add anything new to it. Perhaps one day I will get a reddit account and post there, but feel free to make the link yourself.&lt;/p&gt;

&lt;p&gt;Best wishes,&lt;/p&gt;

&lt;p&gt;Philip&lt;/p&gt;</description>
			<link>https://blog.abbey1.org.uk/index.php/technology/script-to-compile-xilinx-primitives-with-intel-s#c14</link>
		</item>
				<item>
			<title>In response to: Script to compile Xilinx Primitives with Intel's FPGA Starter edition QuestaSim</title>
			<description>&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;I want to thank you for this post, I don&amp;#8217;t have deep knowledge of TCL and without this post I don&amp;#8217;t think I would have been able to use the Vivado libraries in QuestaSim.&lt;/p&gt;

&lt;p&gt;I think this post is much more useful than the two posts you quote from the AMD forum and Reddit so I encourage you to write an entry in that Reddit post with the link to this website, as it appears much higher than this website in Google searches.&lt;/p&gt;

&lt;p&gt;Just a comment: when you compile the XPM library on lines 142-145 I think the correct path to the FIFOs package is &lt;br /&gt;
&lt;code&gt;&lt;br /&gt;
&quot;%xpm%\xpm_fifo\hdl\xpm_fifo.sv&quot; ^&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
instead of &lt;br /&gt;
&lt;code&gt;&lt;br /&gt;
&quot;%xpm%\xpm_fifo\simulation\xpm_fifo_tb.sv&quot; ^&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
Or at least that&amp;#8217;s how it worked for me.&lt;/p&gt;

&lt;p&gt;Regards,&lt;/p&gt;

&lt;p&gt;Pablo&lt;/p&gt;</description>
			<link>https://blog.abbey1.org.uk/index.php/technology/script-to-compile-xilinx-primitives-with-intel-s#c13</link>
		</item>
				<item>
			<title>In response to: Low Speed Serial I/O Variable Delay Monitoring</title>
			<description>&lt;p&gt;Xilinx would appear to have already written an IP core for their FPGAs according to this document: &lt;a href=&quot;https://docs.amd.com/v/u/en-US/pb052-ldpc&quot; rel=&quot;nofollow ugc&quot;&gt;LDPC Encoder Decoder v1.0 Product Brief (PB052)&lt;/a&gt;&lt;/p&gt;</description>
			<link>https://blog.abbey1.org.uk/index.php/technology/low-speed-serial-i-o-variable-delay-monitoring#c12</link>
		</item>
				<item>
			<title>In response to: Low Speed Serial I/O Variable Delay Monitoring</title>
			<description>&lt;p&gt;No! I&amp;#8217;m afraid I had to look &lt;a href=&quot;https://en.wikipedia.org/wiki/Low-density_parity-check_code&quot; rel=&quot;nofollow ugc&quot;&gt;Low-density parity-check code&lt;/a&gt; up on Wikipedia. I will have to consider that, thanks for the pointer. I did find the 01 signal sampling was superior to these methods. BTW I am currently double checking my work here as it happens.&lt;/p&gt;</description>
			<link>https://blog.abbey1.org.uk/index.php/technology/low-speed-serial-i-o-variable-delay-monitoring#c11</link>
		</item>
				<item>
			<title>In response to: Working With AXI Streaming Data</title>
			<description>&lt;p&gt;Hi Erik,&lt;/p&gt;
&lt;p&gt;The line of code you point to is a pure signal (wire) assignment outside a clocked process and hence there&amp;#8217;s no register on that line. The ready signal takes the output from the register on line 68. It then inverts it before it leaves the component. Strictly speaking that&amp;#8217;s not purely registered, but for most cases it is good enough. If you want a fully registered solution take a look at the &lt;a title=&quot;AXI Register Slice&quot; href=&quot;https://www.amd.com/en/products/adaptive-socs-and-fpgas/intellectual-property/axi-register-slice.html&quot; target=&quot;_blank&quot; rel=&quot;noopener nofollow ugc&quot;&gt;AXI Register Slice from Xilinx&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I&amp;#8217;ve referred to the ITDev blog post many times when working with AXI-S. I use their non-registered solution all the time as it is so simple. I&amp;#8217;m glad to have been of use, but I can&amp;#8217;t take credit for the &lt;a title=&quot;Register ready signals in low latency, zero bubble pipeline&quot; href=&quot;https://www.itdev.co.uk/blog/pipelining-axi-buses-registered-ready-signals&quot; target=&quot;_blank&quot; rel=&quot;noopener nofollow ugc&quot;&gt;original article&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Philip&lt;/p&gt;</description>
			<link>https://blog.abbey1.org.uk/index.php/technology/working-with-axi-streaming-data#c9</link>
		</item>
				<item>
			<title>In response to: Working With AXI Streaming Data</title>
			<description>&lt;p&gt;Hi Philip,&lt;/p&gt;

&lt;p&gt;Let me thank you for such a wonderful post. I&amp;#8217;m starting to battle with managing upstream and downstream axi connections and I felt like missing something, and this post has just nailed it. &lt;/p&gt;

&lt;p&gt;Just a quick question: In the pipelined solution, you say you&amp;#8217;re registering the &lt;code&gt;ready&lt;/code&gt; signal. Does that occur in line 82 where &lt;code&gt;us_ready &amp;lt;= not expansion_valid_reg;&lt;/code&gt; , because &lt;code&gt;expansion_valid_reg &lt;/code&gt; is assigned synchronously?&lt;/p&gt;</description>
			<link>https://blog.abbey1.org.uk/index.php/technology/working-with-axi-streaming-data#c8</link>
		</item>
		  </channel>
</rss>
