<?xml version="1.0" encoding="UTF-8" ?>
<?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/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ZedBoard Hardware Design - Recent Threads</title><link>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><lastBuildDate>Tue, 24 Jun 2025 14:39:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design" /><item><title>Vivado BRAM Instantiation Issues</title><link>https://community.element14.com/thread/55900?ContentTypeID=0</link><pubDate>Tue, 24 Jun 2025 14:39:07 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:ecfd34c5-740a-4bc5-bfef-2657e1964980</guid><dc:creator>dniemann17</dc:creator><slash:comments>0</slash:comments><comments>https://community.element14.com/thread/55900?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/55900/vivado-bram-instantiation-issues/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello!&lt;/p&gt;
&lt;p&gt;We are currently working on a project which requires us to extend a previously created memory interface on a ZedBoard from being 4k in size to 256k (A 1/4 of a MB).&amp;nbsp;&lt;br /&gt;We had previously created a file, called pocket_core_top_mem.v which instantiated a 4k long memory (4&amp;nbsp;&lt;span&gt;xilinx_tdpram_1024x36&amp;nbsp;modules) that has been working for the longest time.&amp;nbsp;This&amp;nbsp;old interface used only 4 blocks of 140 available Block RAM modules on the zedboard for the project (50 blocks are used elsewhere, leaving 86 remaining).&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&lt;a href="https://community.element14.com/cfs-file/__key/communityserver-discussions-components-files/319/pocket_5F00_core_5F00_top_5F00_mem.v.txt"&gt;community.element14.com/.../pocket_5F00_core_5F00_top_5F00_mem.v.txt&lt;/a&gt;&lt;br /&gt;&lt;/span&gt;While doing this, we simply started by trying to nest multiple memory files (using &lt;span&gt;xilinx_tdpram_1024x36 modules)&lt;/span&gt;, where we would have a .v file and module for 16k ram (4 4k modules), a file for 64k ram (4 16k modules), and finally a top file which consisted of 4 64k modules. (called pocket_core_mem_16k.v, pocket_core_mem_64k.v, and pocket_core_top_mem_nested.v here).&lt;br /&gt;&lt;a href="https://community.element14.com/cfs-file/__key/communityserver-discussions-components-files/319/pocket_5F00_core_5F00_mem_5F00_16k.v.txt"&gt;community.element14.com/.../pocket_5F00_core_5F00_mem_5F00_16k.v.txt&lt;/a&gt;&lt;a href="https://community.element14.com/cfs-file/__key/communityserver-discussions-components-files/319/pocket_5F00_core_5F00_mem_5F00_64k.v.txt"&gt;community.element14.com/.../pocket_5F00_core_5F00_mem_5F00_64k.v.txt&lt;/a&gt;&lt;a href="https://community.element14.com/cfs-file/__key/communityserver-discussions-components-files/319/pocket_5F00_core_5F00_top_5F00_mem_5F00_nested.v.txt"&gt;community.element14.com/.../pocket_5F00_core_5F00_top_5F00_mem_5F00_nested.v.txt&lt;/a&gt;&lt;br /&gt;Unfortunately, when we went to build the project, it ran through with no errors and wrote the bitstream but unfortunately only 2 RAM blocks were instantiated in the implemented design and I was only able to read and write to 0x100 of the memory space I programmed in. In Vivado, it was only reporting that 51 of the 140 RAM blocks were instantiated.&lt;br /&gt;So, I then created and ran a simulation in Icarus Verilog on my files to see if I could indeed read and write to the higher address blocks. This simulation worked and proved my files didn&amp;#39;t have a design error.&lt;br /&gt;&lt;br /&gt;I was dumbstruck and thought it was how Vivado interpreted my file methodology that was making the error occur. So, I then simply made a single file (named pocket_core_top_mem_single.v here) with 64 xilinx_tdpram_1024x36 modules in it.&amp;nbsp;&lt;br /&gt;This STILL only had 2 RAM blocks instantiated when Vivado finished building and writing the bitstream:&lt;br /&gt;&lt;img alt="image" style="max-height:360px;max-width:640px;" src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/pastedimage1750776731868v6.png"  /&gt;&lt;br /&gt;I also ran simulations to confirm if this file worked or not, and they confirmed the file worked.&lt;br /&gt;&lt;a href="https://community.element14.com/cfs-file/__key/communityserver-discussions-components-files/319/pocket_5F00_core_5F00_top_5F00_mem_5F00_single.v.txt"&gt;community.element14.com/.../pocket_5F00_core_5F00_top_5F00_mem_5F00_single.v.txt&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Would there be anything that could be preventing Vivado from instantiating these 64 BRAM blocks that I may have missed?&lt;br /&gt;&lt;br /&gt;Regards,&lt;br /&gt;Daniel&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Configure core0 with petalinux and core1 baremetal on Zedboard 2018.3</title><link>https://community.element14.com/thread/55738?ContentTypeID=0</link><pubDate>Tue, 29 Apr 2025 12:04:18 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:51bec52b-816c-4d16-a0a9-176c93074373</guid><dc:creator>caferba</dc:creator><slash:comments>0</slash:comments><comments>https://community.element14.com/thread/55738?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/55738/configure-core0-with-petalinux-and-core1-baremetal-on-zedboard-2018-3/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;Hello,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;I am working with the Zedboard 2018.3 Rev F and I&amp;#39;m having issues when trying to launch an application on CPU1 from petalinux 2018.3 on CPU0. After loading the firmware and starting&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;strong&gt;&lt;span class="uiOutputText" dir="ltr"&gt;nothing happens&lt;/span&gt;&lt;/strong&gt;&lt;span class="uiOutputText" dir="ltr"&gt;. It seems that the baremetal application on cpu1 is not starting. I have followed the UG1186 documentation for A9-zynq platforms.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;root@avnet-digilent-zedboard-2018_3:/lib/firmware# echo hello-linux.elf &amp;gt; /sys/class/remoteproc/remoteproc0/firmware&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;root@avnet-digilent-zedboard-2018_3:/lib/firmware# echo start &amp;gt; /sys/class/remoteproc/remoteproc0/state&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;remoteproc remoteproc0: powering up remoteproc@0&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;remoteproc remoteproc0: Booting fw image hello-linux.elf, size 2534900&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;remoteproc remoteproc0: registered virtio0 (type 7)&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;remoteproc remoteproc0: remote processor remoteproc@0 is now up&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;root@avnet-digilent-zedboard-2018_3:/lib/firmware# virtio_rpmsg_bus virtio0: rpmsg host is online&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&lt;img alt="image" style="max-height:360px;max-width:640px;"  src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/image.png" /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;system-user.dtsi:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;/include/ &amp;quot;system-conf.dtsi&amp;quot;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;/ {&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;chosen&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;{&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;bootargs = &amp;quot;uio_pdrv_genirq.of_id=generic-uio&amp;quot;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;};&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;};&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;/ {&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;reserved-memory {&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&lt;/span&gt;&lt;span class="cuf-entityLinkId forceChatterEntityLink" data-id="" data-hashtag="address-cells" data-mention="#address-cells"&gt;&lt;span class="uiOutputText" dir="ltr"&gt;#address-cells&lt;/span&gt;&lt;/span&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;= &amp;lt;1&amp;gt;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;span class="cuf-entityLinkId forceChatterEntityLink" data-id="" data-hashtag="size-cells" data-mention="#size-cells"&gt;&lt;span class="uiOutputText" dir="ltr"&gt;#size-cells&lt;/span&gt;&lt;/span&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;= &amp;lt;1&amp;gt;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ranges;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;vdev0vring0: vdev0vring0@3e800000 {&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;no-map;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;compatible = &amp;quot;shared-dma-pool&amp;quot;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;reg = &amp;lt;0x3e800000 0x4000&amp;gt;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;};&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;vdev0vring1: vdev0vring1@3e804000 {&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;no-map;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;compatible = &amp;quot;shared-dma-pool&amp;quot;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;reg = &amp;lt;0x3e804000 0x4000&amp;gt;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;};&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;vdev0buffer: vdev0buffer@3e808000 {&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;no-map;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;compatible = &amp;quot;shared-dma-pool&amp;quot;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;reg = &amp;lt;0x3e808000 0x100000&amp;gt;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;};&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; rproc_0_reserved: rproc@3e000000 {&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; no-map;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; reg =&amp;nbsp;&amp;lt;0x3ed00000 0x00400000&amp;gt;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; };&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;};&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;amba {&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;elf_ddr_0: ddr@0 {&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;compatible = &amp;quot;mmio-sram&amp;quot;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;reg = &amp;lt;0x3e000000 0x400000&amp;gt;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;};&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;};&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;remoteproc0: remoteproc@0 {&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;compatible = &amp;quot;xlnx,zynq_remoteproc&amp;quot;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;firmware = &amp;quot;firmware&amp;quot;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;vring0 = &amp;lt;15&amp;gt;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;vring1 = &amp;lt;14&amp;gt;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;srams = &amp;lt;&amp;amp;elf_ddr_0&amp;gt;;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;};&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;};&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;Thank you&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="uiOutputText" dir="ltr"&gt;Carlos&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Connecting Zedboard to Vivado - Hardware Manager not Detecting</title><link>https://community.element14.com/thread/55641?ContentTypeID=0</link><pubDate>Fri, 21 Mar 2025 19:12:04 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:62e23a6d-4dd8-4926-aa80-523443b807e7</guid><dc:creator>eb_air</dc:creator><slash:comments>4</slash:comments><comments>https://community.element14.com/thread/55641?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/55641/connecting-zedboard-to-vivado---hardware-manager-not-detecting/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I have been struggling to detect my Zedboard on Vivado&amp;#39;s Hardware Manager run in a Linux OS. When I went into the Hardware Manager, I could connect into the local hardware server, but the Zedboard did not show up. I used version 2023.2 and 2022.2, but both versions had the same problem. I tried the JTAG and UART modes with no success. I am confused with the problem here because if I run lsusb, I see &amp;quot;232H Single HS USB-UART/FIFO IC&amp;quot; for the JTAG interface and &amp;quot;Cypress Semiconductor Corp. CDC ACM serial port&amp;quot;, which I assume means the drivers are properly installed.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Is there something I am doing wrong here?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Je1 GPIO - Cant seem to access upper pins</title><link>https://community.element14.com/thread/55622?ContentTypeID=0</link><pubDate>Fri, 14 Mar 2025 11:33:58 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:42241f29-80eb-4e4a-9b59-cf79f3a9d015</guid><dc:creator>PurplePig</dc:creator><slash:comments>2</slash:comments><comments>https://community.element14.com/thread/55622?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/55622/je1-gpio---cant-seem-to-access-upper-pins/rss?ContentTypeId=0</wfw:commentRss><description>&lt;div&gt;&lt;span&gt;# &lt;/span&gt;&lt;span&gt;Xilinx Zedboard (Zynq 7020) GPIO 0&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;I am working with a new Zedboard with the Zynq 7020 processor.&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;I was trying to strobe the pins on the JE1 PMOD port&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;img alt="image" style="max-height:360px;max-width:640px;"  src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/JE1_5F00_PMOD_5F00_MIO.png" /&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;&amp;nbsp;To this end I defined the following pins&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;```&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;File: helloworld.c&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;61: int &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; iPortPins[10];&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;62: &lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;63: #define JE1 &amp;nbsp; &amp;nbsp; 13&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;64: #define JE2 &amp;nbsp; &amp;nbsp; 10&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;65: #define JE3 &amp;nbsp; &amp;nbsp; 11&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;66: #define JE4 &amp;nbsp; &amp;nbsp; 12&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;67: #define JE7 &amp;nbsp; &amp;nbsp; 0&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;68: #define JE8 &amp;nbsp; &amp;nbsp; 9&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;69: #define JE9 &amp;nbsp; &amp;nbsp; 14&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;70: #define JE10 &amp;nbsp; &amp;nbsp;15&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;71: #define LED &amp;nbsp; &amp;nbsp; 7&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;72: &lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;```&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;and configured them as follows&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;img loading="lazy" alt="image" style="max-height:360px;max-width:640px;"  src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/MIO_5F00_CTRL_5F00_unmodified.png" /&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;defined as&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;img loading="lazy" alt="image" style="max-height:360px;max-width:640px;"  src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/MIO_5F00_PIN_5F00_00.png" /&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;what I had observed as that the GPIO_0 DIRM and OEN were not allowing the GPIO 0 pins to&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;drive the PMOD so I explicitly set them&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;What I observed is I was only able to write the lower 8 bits of each of these registers.&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;img loading="lazy" alt="image" style="max-height:360px;max-width:640px;"  src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/iMask.png" /&gt;&lt;/div&gt;
&lt;p&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;### &lt;/span&gt;&lt;span&gt;before&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;img loading="lazy" alt="image" style="max-height:360px;max-width:640px;"  src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/GPIO0_5F00_DIRM_5F00_OEN_5F00_before.png" /&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;code to change &lt;/span&gt;&lt;span&gt;**&lt;/span&gt;&lt;span&gt;DIRM&lt;/span&gt;&lt;span&gt;**&lt;/span&gt;&lt;span&gt; and &lt;/span&gt;&lt;span&gt;**&lt;/span&gt;&lt;span&gt;OEN&lt;/span&gt;&lt;span&gt;**&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;```&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; u32 pGPIO_0_DIRM = 0xE000A204;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Xil_Out32(pGPIO_0_DIRM, (u32)(iMask));&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; u32 pGPIO_0_OEN = 0xE000A208;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Xil_Out32(pGPIO_0_OEN, (u32)(iMask));&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;```&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;### &lt;/span&gt;&lt;span&gt;after&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;img loading="lazy" alt="image" style="max-height:360px;max-width:640px;"  src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/GPIO0_5F00_DIRM_5F00_OEN_5F00_after.png" /&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;Note that bits 8-15 were ignored.&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;This is also the case if I try to modify them from the ide memory window. If I write 0xffffffff only the lower 8 bits are modified.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;(Both DIRM and OEN)&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;Why is this?&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Setting up PLL for use with FPGA fabric</title><link>https://community.element14.com/thread/55452?ContentTypeID=0</link><pubDate>Mon, 06 Jan 2025 20:58:15 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:cfe53d3c-6759-4553-86ba-5b2e85636bf5</guid><dc:creator>hawx2020</dc:creator><slash:comments>3</slash:comments><comments>https://community.element14.com/thread/55452?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/55452/setting-up-pll-for-use-with-fpga-fabric/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m having trouble setting up the 33MHz PLL clock so that I am able to access it from the FPGA fabric. I&amp;#39;ve never used a PLL before and I&amp;#39;ve only ever used the FPGA fabric on the zedboard so I&amp;#39;m not quite sure where to start. If anyone has any advice or an example project, that would be greatly appreciated.&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>audio passthrough using SPI in PL</title><link>https://community.element14.com/thread/55444?ContentTypeID=0</link><pubDate>Sat, 04 Jan 2025 02:26:03 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:11a9a004-1d01-497b-8a62-ae3d0d838a1c</guid><dc:creator>Former Member</dc:creator><slash:comments>7</slash:comments><comments>https://community.element14.com/thread/55444?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/55444/audio-passthrough-using-spi-in-pl/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;I&amp;#39;m new to FPGA and ZedBoard, and for educational purpose, I&amp;#39;m trying to recive signal from microphone(or LINE_IN) and passthrough it to headphones(or LINE_OUT). Eventually I&amp;#39;m going to create a sound recognition system(frequency detection to be precisie), but for now, I want to properly set up audio codec, and check on headphones if I can hear myself. I found interesting project here:&amp;nbsp;&lt;a id="" href="https://www.rtlaudiolab.com/page/4/" rel="noopener noreferrer nofollow" target="_blank" data-e14adj="t"&gt;https://www.rtlaudiolab.com/page/4/&lt;/a&gt;&amp;nbsp;(part1-5) that describes how to passtrough audio using SPI communication. I set up everything, just like on this website, but have a problem with SPI driver(which is the codec audio if I understand that correctly), because the&amp;nbsp;&lt;em&gt;data_in&lt;/em&gt; are going nowhere. I don&amp;#39;t know if that&amp;#39;s how it supossed to be, but common sense tell me that it shouldn&amp;#39;t&amp;nbsp; be that way. Also, I can generate a bitstream and program zedboard, but i can&amp;#39;t hear nothing.&lt;/p&gt;
&lt;p&gt;I would be thankful for any advice and help.&lt;/p&gt;
&lt;p&gt;PS. Acording to website of the project, i should press BTNC before i could hear anything but that doesn;t help either.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Here are screenshots from the vivado:&lt;/p&gt;
&lt;p&gt;&lt;img alt="image" style="max-height:360px;max-width:640px;" src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/screen2.png"  /&gt;&lt;img loading="lazy" alt="image" style="max-height:360px;max-width:640px;" src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/screen1.png"  /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Zedboard troubleshooting : Power LED and DONE LED does not turn ON</title><link>https://community.element14.com/thread/55227?ContentTypeID=0</link><pubDate>Thu, 24 Oct 2024 16:38:53 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:df377d48-aa34-44a5-9061-721ecd7394af</guid><dc:creator>teem-8121</dc:creator><slash:comments>1</slash:comments><comments>https://community.element14.com/thread/55227?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/55227/zedboard-troubleshooting-power-led-and-done-led-does-not-turn-on/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;The zedboard was working all fine.&lt;/p&gt;
&lt;p&gt;But suddenly the Power LED, DONE LED, does not turn ON when 12V adaptor is plugged in with Switch ON, whereas the LD0 to LD7 stays ON in red when the board is powered.&lt;/p&gt;
&lt;p&gt;I checked for the voltage across the following Capacitors with a DMM while the Zedboard is powered: &lt;br /&gt;C328, C329 or C330 ( should be 5V)&lt;br /&gt;C334 or C335 ( should be 3.3V)&lt;br /&gt;C351 or C352 ( should be 1.5V)&lt;br /&gt;C365 or C366 ( should be 1.8V)&lt;br /&gt;C356 or C357 ( should be 1V)&lt;br /&gt;I also verified the fuse voltage F5 and the switch SW8&lt;br /&gt;All of these measured as expected. Not sure what could have went wrong.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Could you suggest some more steps to troubleshoot?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Zedboard Gerber Files</title><link>https://community.element14.com/thread/55079?ContentTypeID=0</link><pubDate>Tue, 10 Sep 2024 21:05:34 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:785c9dc6-3cb0-4690-8820-99960d7eba4e</guid><dc:creator>OliverMcDonald</dc:creator><slash:comments>0</slash:comments><comments>https://community.element14.com/thread/55079?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/55079/zedboard-gerber-files/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Where can I find the Gerber files for the PCB of the Zedboard?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>End of Life of Zedboard</title><link>https://community.element14.com/thread/55078?ContentTypeID=0</link><pubDate>Tue, 10 Sep 2024 20:06:31 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:59b938e2-720a-465b-b3d6-099bfec778d9</guid><dc:creator>OliverMcDonald</dc:creator><slash:comments>0</slash:comments><comments>https://community.element14.com/thread/55078?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/55078/end-of-life-of-zedboard/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Given that the Zedboard is over 10 years old, how much longer does Avnet intend to sell the Zed board?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>ZedBoard</title><link>https://community.element14.com/thread/55077?ContentTypeID=0</link><pubDate>Tue, 10 Sep 2024 18:08:07 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:17015834-3b7d-4a76-9942-a3c7785c8b0a</guid><dc:creator>OliverMcDonald</dc:creator><slash:comments>4</slash:comments><comments>https://community.element14.com/thread/55077?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/55077/zedboard/rss?ContentTypeId=0</wfw:commentRss><description>&lt;div class="x_elementToProof"&gt;I bought a ZedBoard Part number AES-Z7EV-7Z020-G. It was my understanding that support for the board would be located at zedboard.org. However, when I tried going to that site, it appears that the site does not exist anymore. My questions to you are:&lt;/div&gt;
&lt;div class="x_elementToProof"&gt;&lt;/div&gt;
&lt;ol start="1" data-listchain="__List_Chain_62"&gt;
&lt;li&gt;
&lt;div class="x_elementToProof"&gt;How much longer does Avnet plans to manufacture the Zedboard?&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;div class="x_elementToProof"&gt;When does Avnet intend to re-activate the site zedboard.org?&amp;nbsp;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;div class="x_elementToProof"&gt;Are gerber files of the circuit board available?&lt;/div&gt;
&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Issues with Custom Memory Interface</title><link>https://community.element14.com/thread/55029?ContentTypeID=0</link><pubDate>Tue, 27 Aug 2024 15:19:37 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:c965e84f-e5a0-4a0c-84bc-447f477b2145</guid><dc:creator>dniemann17</dc:creator><slash:comments>7</slash:comments><comments>https://community.element14.com/thread/55029?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/55029/issues-with-custom-memory-interface/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We are currently using a Zedboard to create a custom AXI memory and register interface from a verilog file.&lt;/p&gt;
&lt;p&gt;The memory interface is 16K words and uses AXI4 FULL, and the register interface is 32K words and uses AXI Lite&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;As of writing, we are able to do the following with these interfaces using a CLI:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Read custom register interface&lt;/li&gt;
&lt;li&gt;Write to custom register interface&lt;ul&gt;
&lt;li&gt;Confirm data written can be read again&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Read custom memory interface&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;We are having issues trying to write to the custom memory interface.&lt;/p&gt;
&lt;p&gt;All that the software CLI does is parse out an address and use Xil_In/Xil_Out to read/write to ZedBoard memory&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;This feature has been tested extensively on other projects and other sections of memory on the ZedBoard, all of which work perfectly normally&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We believe this is a Verilog error and want advice/help with testing and simulating the AXI bus to try and find the issue.&lt;/p&gt;
&lt;p&gt;We looked for an AXI bus testing solution, but the posts on the Xilinx website were all out of date and unable to be followed (we run 2023.2 and the guides were written for 2019.2).&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Contained below is a list of files associated with a block diagram of our project (I&amp;#39;ve had to rename them to .txt files to upload).&lt;/p&gt;
&lt;p&gt;xilinx_tdpram_1024x36.v&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ====&amp;gt;&amp;nbsp;&amp;nbsp; Base single memory block file&lt;/p&gt;
&lt;p&gt;dig_core_dpram_32.v&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ====&amp;gt;&amp;nbsp;&amp;nbsp; Top memory file (contains 4 rams)&lt;/p&gt;
&lt;p&gt;proto_core_top_regs_ex.v&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ====&amp;gt;&amp;nbsp;&amp;nbsp; Top register file&lt;/p&gt;
&lt;p&gt;pocket_interface_v1_0.v&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ====&amp;gt;&amp;nbsp;&amp;nbsp; Top reg/mem interface file&lt;/p&gt;
&lt;p&gt;pocket_interface_v1_0_S00_AXI.v&amp;nbsp; &amp;nbsp; &amp;nbsp; ====&amp;gt;&amp;nbsp;&amp;nbsp; Register AXI interface file&lt;/p&gt;
&lt;p&gt;pocket_interface_v1_0_S01_AXI.v&amp;nbsp; &amp;nbsp; &amp;nbsp; ====&amp;gt;&amp;nbsp;&amp;nbsp; Memory AXI interface file&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Currently it seems that pocket_interface_v1_0_S01_AXI.v is the main problem with the temporary write address or &amp;quot;axi_awaddr&amp;quot; being the likely cause, but we can&amp;#39;t be fully sure.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Any help with the error or testing methodology would be appreciated.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;--&lt;/p&gt;
&lt;p&gt;Daniel&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;img alt="image" style="max-height:360px;max-width:640px;" src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/PC_5F00_Testing_5F00_Block_5F00_Diagram.png"  /&gt;&lt;a href="https://community.element14.com/cfs-file/__key/communityserver-discussions-components-files/319/xilinx_5F00_tdpram_5F00_1024x36.txt"&gt;community.element14.com/.../xilinx_5F00_tdpram_5F00_1024x36.txt&lt;/a&gt;&lt;a href="https://community.element14.com/cfs-file/__key/communityserver-discussions-components-files/319/pocket_5F00_interface_5F00_v1_5F00_0.txt"&gt;community.element14.com/.../pocket_5F00_interface_5F00_v1_5F00_0.txt&lt;/a&gt;&lt;a href="https://community.element14.com/cfs-file/__key/communityserver-discussions-components-files/319/dig_5F00_core_5F00_dpram_5F00_32.txt"&gt;community.element14.com/.../dig_5F00_core_5F00_dpram_5F00_32.txt&lt;/a&gt;&lt;a href="https://community.element14.com/cfs-file/__key/communityserver-discussions-components-files/319/pocket_5F00_interface_5F00_v1_5F00_0_5F00_S00_5F00_AXI.txt"&gt;community.element14.com/.../pocket_5F00_interface_5F00_v1_5F00_0_5F00_S00_5F00_AXI.txt&lt;/a&gt;&lt;a href="https://community.element14.com/cfs-file/__key/communityserver-discussions-components-files/319/pocket_5F00_interface_5F00_v1_5F00_0_5F00_S01_5F00_AXI.txt"&gt;community.element14.com/.../pocket_5F00_interface_5F00_v1_5F00_0_5F00_S01_5F00_AXI.txt&lt;/a&gt;&lt;a href="https://community.element14.com/cfs-file/__key/communityserver-discussions-components-files/319/proto_5F00_core_5F00_top_5F00_regs_5F00_ex.txt"&gt;community.element14.com/.../proto_5F00_core_5F00_top_5F00_regs_5F00_ex.txt&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Zedboard compatible with Xilinx HW-FMC-105-DEBUG board ?</title><link>https://community.element14.com/thread/54821?ContentTypeID=0</link><pubDate>Mon, 08 Jul 2024 05:57:54 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:9f9125a5-5d29-4af8-bf27-f18bc072e9bb</guid><dc:creator>tintinxyz</dc:creator><slash:comments>1</slash:comments><comments>https://community.element14.com/thread/54821?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/54821/zedboard-compatible-with-xilinx-hw-fmc-105-debug-board/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Can anyone pls tell me how to check if the zedboard is electrically compatible with HW-FMC-105-DEBUG board ?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks in advance !&lt;/p&gt;
&lt;p&gt;Regards.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Viavdo - Zynq7000(Linux - Ubuntu) - PL</title><link>https://community.element14.com/thread/54638?ContentTypeID=0</link><pubDate>Wed, 22 May 2024 13:41:04 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:25946240-dba5-4491-a4a1-ac65850ef823</guid><dc:creator>angerpro</dc:creator><slash:comments>3</slash:comments><comments>https://community.element14.com/thread/54638?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/54638/viavdo---zynq7000-linux---ubuntu---pl/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi guys, I am in a project that I need to boot Linux OS to ARM a9 in Zynq7000(Zedboard). Before my way to design FPGA is Vivado -&amp;gt; .XSA file -&amp;gt; Download XSA file in Vitis -&amp;gt; use Vitis to manage PS and control data path, get result and etc.&lt;br /&gt;Now instead of using Vitis, is there any way that I use Vivado to create block design -&amp;gt; export hardware(include bitstream) .XSA file -&amp;gt; send it to Linux - particularly Ubuntu (inside ARM core a9) -&amp;gt;&amp;nbsp; then use it to implementation PL? and after that I can use directly Linux os to control the peripherals as Leds, Switches, vga??? I saw some tutorials that uses Petalinux, my opinion is that Petalinux is convinient but heaveweight. If I can not use OS like Ubuntu, even simpler Debian, then last choice I will use Petalinux.&lt;br /&gt;&lt;br /&gt;Thansk for reading my question. And also my English is not really good, sorry if there are obscure questions.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>SD card files formatted</title><link>https://community.element14.com/thread/54631?ContentTypeID=0</link><pubDate>Mon, 20 May 2024 17:06:36 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:9e7d2722-801f-49d4-a1a8-a2948f587d94</guid><dc:creator>AWM</dc:creator><slash:comments>1</slash:comments><comments>https://community.element14.com/thread/54631?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/54631/sd-card-files-formatted/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I was trying to configure the zedboard on linux and i was following &lt;a id="" href="https://digilent.com/reference/_media/zedboard_gswel_guide.pdf" rel="noopener noreferrer nofollow" target="_blank" data-e14adj="t"&gt;https://digilent.com/reference/_media/zedboard_gswel_guide.pdf&lt;/a&gt; as a guide. Now, I want to shift on Windows. I was following the steps, It said to format the SD Card, and I formatted SD card. Now, I have to shift it to windows and run it there, I cannot locate SD card files anywhere on internet. Can someone help me resolve this issue, or provide me with the files?&lt;/p&gt;
&lt;p&gt;Any help will be appreciated.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;AWM&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>How can the ADAU1761 ZedBoard be configured in SPI mode for audio pass-through?</title><link>https://community.element14.com/thread/54575?ContentTypeID=0</link><pubDate>Wed, 01 May 2024 22:44:41 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:ae216a63-505d-4dea-b00b-b7b4db6f009e</guid><dc:creator>Adelynul</dc:creator><slash:comments>0</slash:comments><comments>https://community.element14.com/thread/54575?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/54575/how-can-the-adau1761-zedboard-be-configured-in-spi-mode-for-audio-pass-through/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello everyone for some weeks now i try to pass through the zedboard audio codec (ADAU1761) sound, initially i found a very useful tutorial at &lt;a href="https://www.rtlaudiolab.com/001-zedboard-audio-processor/" rel="noopener noreferrer nofollow" target="_blank" data-e14adj="t"&gt;www.rtlaudiolab.com/.../&lt;/a&gt; which i followed but without success. My intention and what i have done is implementing the same logic in VHDL, but something it is not working i tested the SystemVerilog code and it worked. I am not really sure what went wrong and if someone could loom over my code or point me into the right direction because i do not know what to do anymore especially that over the internet it seems that is a lack of resources about this topic(I also found the github repository of Microelectronic Systems Design Research Group, but they implement it over I2C which is not what i need.&lt;/p&gt;
&lt;p&gt;Here is the WeTransfer link with both archives of systemverilog code and vhdl code that i tried, thank you in advance for reading my post and trying to help &lt;a href="https://we.tl/t-4iSOKsY3nF" rel="noopener noreferrer nofollow" target="_blank" data-e14adj="t"&gt;https://we.tl/t-4iSOKsY3nF&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>ZEDBOARD UART-USB connection problem in linux while using matlab</title><link>https://community.element14.com/thread/54506?ContentTypeID=0</link><pubDate>Wed, 03 Apr 2024 15:27:56 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:e0ea4101-a05c-4cb5-9d16-54a4d8c349e7</guid><dc:creator>Rohith_Gopakumar</dc:creator><slash:comments>6</slash:comments><comments>https://community.element14.com/thread/54506?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/54506/zedboard-uart-usb-connection-problem-in-linux-while-using-matlab/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;hello i am new to zedboard and am trying to set up the hardware since the past few weeks so any help would be great. i am trying to connect the board to the development computer&lt;/p&gt;
&lt;p&gt;TOOL VERSIONS:&lt;/p&gt;
&lt;p&gt;matlab version-R2022b&lt;/p&gt;
&lt;p&gt;os-Ubuntu 20.04.3 LTS&lt;/p&gt;
&lt;p&gt;i have used HDL Coder Support Package for Xilinx Zynq Platform&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I keep getting this error and i&amp;#39;m not sure how to resolve it, any and all help would be appreciated thank you&lt;/p&gt;
&lt;p&gt;----------------------------------------------------------------------------------------------------------------------------------------------&lt;/p&gt;
&lt;p&gt;attempts done:&lt;/p&gt;
&lt;p&gt;1)i have tried to setup serial port using s=serialport(&amp;#39;dev/ttyACM0&amp;#39;,115200);&amp;nbsp; fopen(s) then tried the hardware&lt;/p&gt;
&lt;p&gt;2)i have given permissions for dev/ttyACM0 by chmod 666&lt;/p&gt;
&lt;p&gt;3)i have used putty to communicate with the zynq board&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;img alt="image" style="max-height:360px;max-width:640px;"  src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/pastedimage1712158010726v1.png" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Implementing  Vitis C code with Vivaod Verilog code</title><link>https://community.element14.com/thread/54425?ContentTypeID=0</link><pubDate>Tue, 05 Mar 2024 16:09:20 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:4975570d-8412-4b8b-aea9-8c2982425481</guid><dc:creator>CJK15</dc:creator><slash:comments>3</slash:comments><comments>https://community.element14.com/thread/54425?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/54425/implementing-vitis-c-code-with-vivaod-verilog-code/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I am currently using a PmodAD1 with code in Vitis as an ADC. The code reads the digital value obtained by the Pmod and writes it to the serial monitor. I intend to utilize this value to generate a PWM signal, with the duty cycle adjusting according to the input changes. The Pmod is currently operational, and I can generate a PWM signal in Verilog in separate projects. Modifying the duty cycle in the PWM Verilog code requires regenerating a bitstream and reprogramming the device each time. How can I integrate these components to have the PWM automatically update based on the Pmod&amp;#39;s input? I am a student and would appreciate any advice. Thanks&amp;nbsp;&lt;/p&gt;
&lt;p&gt;My block design:&lt;/p&gt;
&lt;p&gt;&lt;img alt="image" style="max-height:360px;max-width:640px;" src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/pastedimage1709654829630v1.png"  /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;My Verilog Code:&lt;br /&gt;&lt;img loading="lazy" alt="image" style="max-height:360px;max-width:640px;" src="https://community.element14.com/resized-image/__size/1280x720/__key/communityserver-discussions-components-files/319/pastedimage1709654926790v5.png"  /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Reading mouse over USB OTG port on Zedboard</title><link>https://community.element14.com/thread/54417?ContentTypeID=0</link><pubDate>Mon, 04 Mar 2024 06:16:13 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:d2f36a75-08f5-49c9-b54b-4ac31dc70491</guid><dc:creator>average_mid</dc:creator><slash:comments>3</slash:comments><comments>https://community.element14.com/thread/54417?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/54417/reading-mouse-over-usb-otg-port-on-zedboard/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I am looking to develop my own custom IP in Vivado to read mouse input from the USB OTG port on a Zedboard (&lt;a href="https://digilent.com/reference/programmable-logic/zedboard/start)." rel="noopener noreferrer nofollow" target="_blank" data-e14adj="t"&gt;digilent.com/.../start).&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve scoured the internet for information but they almost all point to using PS/2 Pmods to achieve this. If I can read a flash drive using the OTG port, I should be able to read mouse signals provided I have the necessary USB A to microUSB adaptor. I&amp;#39;m not even sure where to start as computer mouse are HID devices and I don&amp;#39;t quite know how a mouse&amp;#39;s signal is presented over the OTG port.&lt;/p&gt;
&lt;p&gt;Anyone with insight into this is greatly appreciated!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>ZedBoard not booting, u-boot file is corrupted</title><link>https://community.element14.com/thread/54370?ContentTypeID=0</link><pubDate>Mon, 19 Feb 2024 19:44:34 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:25d3bced-75f9-4310-bd90-6174e4f893cd</guid><dc:creator>CJK15</dc:creator><slash:comments>3</slash:comments><comments>https://community.element14.com/thread/54370?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/54370/zedboard-not-booting-u-boot-file-is-corrupted/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;My ZedBoard will not boot from the SD card. It was able to boot in the past, so I know I have the right jumper configurations. I looked at the SD card, and the U-boot is corrupted. I have tried to install a new u-boot file using the out-of-box demo zip file posted&amp;nbsp;on&amp;nbsp;&lt;a href="https://digilent.com/reference/programmable-logic/zedboard/start" rel="noopener noreferrer nofollow" target="_blank" data-e14adj="t"&gt;Digilent&lt;/a&gt;. It led me &lt;a href="https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18842223/U-boot" rel="noopener noreferrer nofollow" target="_blank" data-e14adj="t"&gt;here&lt;/a&gt;. However, I am still having trouble installing a new U-boot file. Any help would be greatly appreciated.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>New zed board is not booting from SD card despite jumper configuration.</title><link>https://community.element14.com/thread/54296?ContentTypeID=0</link><pubDate>Mon, 29 Jan 2024 18:57:06 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:d505dccd-5ec6-4e1a-98c5-1f7d751d10e6</guid><dc:creator>fluxinduction</dc:creator><slash:comments>11</slash:comments><comments>https://community.element14.com/thread/54296?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/54296/new-zed-board-is-not-booting-from-sd-card-despite-jumper-configuration/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I&amp;#39;ve been following this guide for initial setup of the zedboard:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.avnet.com/wps/wcm/connect/onesite/7ae0f288-1cc5-4283-9e85-300c5401b680/GS-AES-Z7EV-7Z020-G-V7-1.pdf?MOD=AJPERES&amp;amp;CACHEID=ROOTWORKSPACE.Z18_NA5A1I41L0ICD0ABNDMDDG0000-7ae0f288-1cc5-4283-9e85-300c5401b680-nxyWIEs" target="_blank" data-e14adj="t"&gt;GS-AES-Z7EV-7Z020-G-V7-1.pdf (avnet.com)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I cannot get past step 8 of section 5.&amp;nbsp; The zedboard never successfully boots.&amp;nbsp; I do have another SD card, and that doesn&amp;#39;t boot either.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve also been referencing the hardware guide:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="https://digilent.com/reference/_media/zedboard:zedboard_ug.pdf" rel="noopener noreferrer nofollow" target="_blank" data-e14adj="t"&gt;ZedBoard_HW_Users_Guide (digilent.com)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;What is causing this?&amp;nbsp; This board is brand new, just unwrapped.&amp;nbsp;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Zedboard - writing mcs file to flash - can't make that happen</title><link>https://community.element14.com/thread/53899?ContentTypeID=0</link><pubDate>Mon, 30 Oct 2023 16:46:10 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:00ead8c0-4268-4295-be7a-e2b1dfceb985</guid><dc:creator>TorstenS</dc:creator><slash:comments>2</slash:comments><comments>https://community.element14.com/thread/53899?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/53899/zedboard---writing-mcs-file-to-flash---can-t-make-that-happen/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello - I&amp;#39;ve been trying to get the MCS generated in SDK&amp;nbsp; to be written to the flash on the Zedboard. The installed Flash is an S25FL256S Quad SPI.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The board does boot from the flash with the jumpers J7 thourgh J11 set&amp;nbsp; to &amp;#39;00010&amp;#39;. At least this indicates the FLASH is in working order.&lt;/p&gt;
&lt;p&gt;Writing to to the flash:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Generating basic &amp;lsquo;LED on&amp;rsquo; PS/PL in Vivado 2018.3 and SDK 2018.3 (runs fine when just uploading bit file into Zynq from the SDK, and launching the .elf file from the SDK)&lt;/li&gt;
&lt;li&gt;In SDK generating FSBL and .mcs file (files are generated as &amp;lsquo;Release&amp;rsquo;)&lt;/li&gt;
&lt;li&gt;Setting JP7 through JP11 all to logic &amp;lsquo;0&amp;rsquo;&lt;/li&gt;
&lt;li&gt;In SDK run XILINX-&amp;gt;Program Flash&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This&amp;nbsp;is the SDK console output I&amp;#39;ve been getting:&lt;/p&gt;
&lt;p&gt;Connected to hw_server @ TCP:127.0.0.1:3121&lt;/p&gt;
&lt;p&gt;Available targets and devices:&lt;/p&gt;
&lt;p&gt;Target 0 : jsn-DLC10-00001b311f3601&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Device 0: jsn-DLC10-00001b311f3601-4ba00477-0&lt;/p&gt;
&lt;p&gt;Retrieving Flash info...&lt;/p&gt;
&lt;p&gt;Initialization done, programming the memory&lt;/p&gt;
&lt;p&gt;===== mrd-&amp;gt;addr=0xF800025C, data=0x00000000 =====&lt;/p&gt;
&lt;p&gt;BOOT_MODE REG = 0x00000000&lt;/p&gt;
&lt;p&gt;Downloading FSBL...&lt;/p&gt;
&lt;p&gt;===== mrd-&amp;gt;addr=0xF8000110, data=0x00177EA0 =====&lt;/p&gt;
&lt;p&gt;READ: ARM_PLL_CFG (0xF8000110) = 0x00177EA0&lt;/p&gt;
&lt;p&gt;===== mrd-&amp;gt;addr=0xF8000100, data=0x0001A008 =====&lt;/p&gt;
&lt;p&gt;READ: ARM_PLL_CTRL (0xF8000100) = 0x0001A008&lt;/p&gt;
&lt;p&gt;===== mrd-&amp;gt;addr=0xF8000120, data=0x1F000400 =====&lt;/p&gt;
&lt;p&gt;READ: ARM_CLK_CTRL (0xF8000120) = 0x1F000400&lt;/p&gt;
&lt;p&gt;===== mrd-&amp;gt;addr=0xF8000118, data=0x00177EA0 =====&lt;/p&gt;
&lt;p&gt;READ: IO_PLL_CFG (0xF8000118) = 0x00177EA0&lt;/p&gt;
&lt;p&gt;===== mrd-&amp;gt;addr=0xF8000108, data=0x0001A008 =====&lt;/p&gt;
&lt;p&gt;READ: IO_PLL_CTRL (0xF8000108) = 0x0001A008&lt;/p&gt;
&lt;p&gt;Problem in Initializing Hardware&lt;/p&gt;
&lt;p&gt;Flash programming initialization failed.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;ERROR: Flash Operation Failed&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve tried writing to the flash from Vivado instead of the SDK - in VIVADO there is a whole family of S25FL256S flashes available. Out of desperation I tried them all - all resulting in the same message as above.&lt;/p&gt;
&lt;p&gt;Any support and insight into this problem is greatly appreciated.&lt;/p&gt;
&lt;p&gt;Thank you in advance!&lt;/p&gt;
&lt;p&gt;Torsten&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Repair Zedboard</title><link>https://community.element14.com/thread/53367?ContentTypeID=0</link><pubDate>Wed, 26 Jul 2023 20:54:40 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:36f906f6-370d-41a3-8e5a-50110439a6b0</guid><dc:creator>DDina</dc:creator><slash:comments>4</slash:comments><comments>https://community.element14.com/thread/53367?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/53367/repair-zedboard/rss?ContentTypeId=0</wfw:commentRss><description>&lt;div&gt;&lt;span&gt;Hi,&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;
&lt;div&gt;&lt;span style="color:#000000;"&gt;I contacted you to check if you accept to repair the zedboard FPGAs.&amp;nbsp;&lt;span&gt;From past 1 year and 6 months onwards I am working on zedboard, but this&amp;nbsp; week when I turned on the power supply of the zed board and&amp;nbsp;&amp;nbsp;I didn&amp;#39;t do any wrong operations, its not getting turning on, the green LED is not turning on( power status).&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span style="color:#000000;font-family:Roboto, sans-serif;"&gt;I will wait for your answer. Also I have a similar&amp;nbsp;issue with my previous board.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span style="color:#000000;font-family:Roboto, sans-serif;"&gt;Thank you so much.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;&lt;span style="color:#000000;font-family:Roboto, sans-serif;"&gt;regards&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>ZedBoard  Rev f Netlist</title><link>https://community.element14.com/thread/52769?ContentTypeID=0</link><pubDate>Thu, 13 Apr 2023 08:50:04 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:cc65724d-4bd4-43fb-8204-5896dcc673da</guid><dc:creator>darshansm</dc:creator><slash:comments>0</slash:comments><comments>https://community.element14.com/thread/52769?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/52769/zedboard-rev-f-netlist/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;For Boundary scan, required ODB++ files/ Netlist. Where can we get that??&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>AES-Z7EV-7Z020-G
ZedBoard - Zynq SoC Development Board with FMC LPC/JTAG/UART Interface</title><link>https://community.element14.com/thread/52016?ContentTypeID=0</link><pubDate>Wed, 16 Nov 2022 08:21:39 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:28b3449e-6d8b-46c1-80d0-797ead7d73d1</guid><dc:creator>Zero</dc:creator><slash:comments>3</slash:comments><comments>https://community.element14.com/thread/52016?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/52016/aes-z7ev-7z020-g-zedboard---zynq-soc-development-board-with-fmc-lpc-jtag-uart-interface/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;anyone can help me with H.S code and weight of this item&lt;/p&gt;
&lt;p&gt;AES-Z7EV-7Z020-G&lt;br /&gt;ZedBoard - Zynq SoC Development Board with FMC LPC/JTAG/UART Interface&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Zedboard trying to detect and output voltage</title><link>https://community.element14.com/thread/51845?ContentTypeID=0</link><pubDate>Wed, 12 Oct 2022 05:28:25 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:b0d530a5-87b9-4f9f-9808-3c6982aca7fb</guid><dc:creator>JavierToh</dc:creator><slash:comments>6</slash:comments><comments>https://community.element14.com/thread/51845?ContentTypeID=0</comments><wfw:commentRss>https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/zedboard-hardware-design/51845/zedboard-trying-to-detect-and-output-voltage/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I trying to use the Zedboard to detect a voltage level and output another voltage.&lt;/p&gt;
&lt;p&gt;Been trying to find ways to do it but everything seems to be outdated or unable to be used.&lt;/p&gt;
&lt;p&gt;I trying to use XADC or PMOD in order to detect a specific voltage from external circuit before outputing another voltage into another circuit&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>