<?xml-stylesheet type="text/xsl" href="https://community.element14.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Learning Xilinx Zynq: Interrupt ARM from FPGA fabric</title><link>/technologies/fpga-group/b/blog/posts/learning-xilinx-zynq-interrupt-arm-from-fpga-fabric</link><description>You can interrupt the Zynq ARM side with a signal coming out of the FPGA part of the chip. In this post, I test this.
The FPGA part has a few blocks that will generate interrupts. In a Jupyter notebook, I&amp;#39;ll try to show that they are detected by the </description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Learning Xilinx Zynq: Interrupt ARM from FPGA fabric</title><link>https://community.element14.com/technologies/fpga-group/b/blog/posts/learning-xilinx-zynq-interrupt-arm-from-fpga-fabric</link><pubDate>Fri, 19 Nov 2021 20:43:10 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:26ffcfbd-6aab-4f8c-ae94-cdff52d585cd</guid><dc:creator>Jan Cumps</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;Works! The interrupt now nicely waits the correct time, each time.&lt;/p&gt;&lt;p&gt;Communities for the win. It was resolved by another Pynq user.&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=21928&amp;AppID=19&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Learning Xilinx Zynq: Interrupt ARM from FPGA fabric</title><link>https://community.element14.com/technologies/fpga-group/b/blog/posts/learning-xilinx-zynq-interrupt-arm-from-fpga-fabric</link><pubDate>Fri, 19 Nov 2021 20:06:57 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:26ffcfbd-6aab-4f8c-ae94-cdff52d585cd</guid><dc:creator>Jan Cumps</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;In the post, I reported this issue:&lt;/p&gt;&lt;blockquote class="jive-quote"&gt;&lt;p&gt;&lt;span&gt;In the version of Pynq that I&amp;#39;m using (2.6), there is a practical issue: the interrupt fires twice from FPGA before the Python code in the Jupyter notebook resets it. &lt;/span&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;I logged this on the Pynq support forum and got several replies.&lt;/p&gt;&lt;p&gt;There&amp;#39;s a possible solution:&lt;/p&gt;&lt;p&gt;&lt;a class="jive-link-external-small" href="https://discuss.pynq.io/t/zynq-ps7-interrupts/198/10" rel="nofollow ugc noopener" target="_blank" title="https://discuss.pynq.io/t/zynq-ps7-interrupts/198/10"&gt;https://discuss.pynq.io/t/zynq-ps7-interrupts/198/10&lt;/a&gt;&lt;/p&gt;&lt;p&gt;I&amp;#39;m testing that now ...&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span&gt;[View:/resized-image/__size/620x428/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-26ffcfbd-6aab-4f8c-ae94-cdff52d585cd/contentimage_5F00_217706.png:620:428]&lt;/span&gt;&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=21928&amp;AppID=19&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>