MichelleNicholes

No, we never did. And I ran out of desire to solve it. Now that I am retired. Good Luck in your search for the answer.

I dont think lonel answered my question. I already know how to generate the sdk so that I can use the vitis tool. Interrupts caught and handled in bare bones is way different than how you catch and handle them in linux. So far, in all the tutorials, they show us how we can see that an interrupt is being caught by the kernal by looking at a file /proc/interrupts and seeing a number increase for a certain interrupt number but they never teach how we get our code to see it and handle it. Also, for turning on LEDs the tutorials had you do devmem to set the direction and to set the value for on or off. However, in Vitis, you had to create a memory block associated with the gpio and in that block set the direction and values. So how you do it in linux itself and how you do it in code are different. Now I will say I saw a tutorial where someone actually polling the /proc/interrupts file and parsed out the number change to tell if an interrupt happened but surely that is not how its properly done. On a side note, I have seen as of today that in linux c code you can use the linux/interrupt.h to register your interrupt but that example seemed to use gpio as a module so I am not sure I am on the right track or not and I have no idea if linux/interrupt.h is included in vitis or not. Still looking What I am looking for is an actually tutorial on how to do interrupts in vitis for petalinux.

@JColvin All the examples you provided are using the standalone version. I have the standalone version working. The linux version works completely different and that is what I am trying to learn. Do you know of any linux interrupt examples? I have been searching and have not found any as of yet. I see lots of tutorials who get the leds to blink but none reading from a switch or button triggering an interrupt. Interesting enough, there are tutorials saying switch led but they do not implement the switch and interrupt in the example.

I have been learning GPIO in Petalinux and outside of Vitis I used UIO0 for the GPIO however when I tried to code using the GPIO in Vitis it was quite different. Basically you create a memory map and link it to the GPIO and then write to the memory. But now I want to implement Interrupts. So far I have seen how you can do it by hand in the linux terminal but I have not found any tutorials or examples on how to use it in a Vitis application. Any recommendations would be appreciated.

I am doing a tutorial on Petalinux and was asked to change the DTG settings to zedboard but I changed it to zybo instead. However, my build failed saying I didnt have a zybo.dtsi file. I was looking at the petalinux user guide and it shows a list of acceptable values so evidently xilinx has installed of of their board files with the dtsi settings for that board. Is there one for the Zybo -20 board?

Turns out iperf3 does not work. Once I installed iperf2 it connected and began transferring data.

So I built a basic Zynq with Ethernet 0 enabled in PL. I created the platform in Vitis 2020.1. I created the LwIP UDP Perf Server and Built it and ran it. It asked me to run the perf client using the ip address 192.168.1.10 and port 5001. I downloaded iperf3 to my windows 10 computer which was configured to 192.168.1.20. I ran the command suggested but with iperf3. In wireshark it says it was using TCP protocol and the request is in red. I get a reply that the connection was rejected. I had already closed everything down and so I do not have the actual message. Hopefully what I am typing right now is enough. Have not found any tutorials on how to use UDP Perf so I have no idea what I am doing right or wrong. I did notice the command suggested did not include the -u option so I did run it again with -u for UDP but it also rejected the connection and still said TCP in wireshark. Any help would be awesome. The ip address was changed because something on my system was forcing me to use 169.254.x.x ips for my network to communicate. Dont know enough about TCP IP to know what or why so I had changed my ips back for my network. So that is why the ips are different. But I had tried using both. Both being 192.168.1.x and 169.254.x.x

Where can I find documentation for the Digilent Dynamic Clock Generator IP core? 2019.1 uses version 1.2.

Yes I am aware that the demo was created in 2020.1 and it does work with 2020.1. I am not a big fan of Vitis just yet and so I wanted to get it to work in 2019.1. I literally created the demo in 2020.1 and then wrote the project to tcl then modified the tcl file for 2019.1 so I know the design is exactly the same. I played around with different combinations of the libraries provided in the demo vs the master library. First I noticed that the vivado library uses dynamic clock 1.2 but gives errors that its Zybo Z7-10 not -20 [IP_Flow 19-4965] IP ila_pixclk was packaged with board value 'digilentinc.com:zybo-z7-10:part0:1.0'. Current project's board value is 'digilentinc.com:zybo-z7-20:part0:1.1'. Please update the project settings to match the packaged IP. I know its the dynamic clock because when I use the dynamic clock that comes with the demo for 2020.1 the message changes to -20 1.0 which mine is -20 1.1. I also noticed that the TC in 2020.1 is 6.2 which 2019.1 uses 6.1. There is another person who asked a question before about the com port not working which I get the same thing when running in 2019.1 HDMI demo not working - FPGA - Digilent Forum I get the color pattern but the com port becomes unresponsive and it never tells me the HDMI input connects. Now, I am leaning towards the TC being the difference given its 6.2 in 2020.1 and not 6.1 which is in 2019.1. Not really willing to copy 2020.1 xilinx stuff over to 2019.1 I did install 2018.2 and I was able to get the 2018 version to work. Anyways, any other ideas as to why I am not getting the same results in 2019.1 Same design and same code minus using TC 6.2 in 2020.1? I have attached the 2019.1 tcl script with files needed in case someone wants to help figure this out. Oh I just realized I have the script pointing to my vivado libraries so you will need to edit the script for your locations. test.zip

So the tutorial "How to create Zybo-z7-20 Hardware Vitis Platform - YouTube" teaches how to create a Vitis Platform using Petalinux. It uses a Linux VM to create the hardware in block design in Vivado create the software using petalinux using the .xsa file this is much more in-depth than I had realized. this can take several hours and I am not sure its all inclusive, could not see ethernet support ultimately you will partition a SD card and add the files needed to boot up in linux create a platform for Vitis which given I was using 2020.1 and he was using 2020.2 this is where my lack of knowledge of Vitis failed me. But the point is that this tutorial did work and I was able to boot my FPGA with petalinux. btw the user is petalinux. There is also root and I guessed that the password was root. I ended up changing the password for petalinux so not sure what happens if you only try to login as petalinux. Dont forget to poweroff.

I am new to vivado 2020.1 and vitis. I have been using 2019 but with no os at all. I wanted to learn Petalinux so I created a virtual with Ubuntu 18.04.4 and installed 2020.1 and got the hello world proj working. even on my Zybo. Great. I installed Petalinux. however, the download BSP is for a different version. I tried to use the Petalinux Demo but what a mess. Wish it stepped you through it using 2020.1 given that each version seems to be different. Tried watching the only video out there and she seems to be just as lost. Anyone willing to step me though how to do this for 2020.1? Update: So I figured out to create a petalinux project and then run the config pointing it to my .xsa file. which contains my FPGA PL portion of the design and it looks like if that was all I needed I could build it and package it and put it on an SDCard and boot it. But what about the PS side of stuff? Where do I put that stuff? Also, Does the 2019 SDK build this? Or the Vitis 2020.1? I saw that you can select linux as your os in Vitis so does it build the petalinux or is it somehow related to the petalinux stuff. Do I add petelinux to the Vitis solutions and build something. It just shows you at this point I have no clue yet. Finally found a good tutorial: How to create Zybo-z7-20 Hardware Vitis Platform - YouTube

I am using Vitis 2020.2 just like the demo requires. I have my Blue Ray DVD player plugged into the Rx Port and my TV plugged into the Tx port. I have my usb and jtag usb plugged in. The power LED is lit and the Done led is lit and so is the hpd led. I have teraterm up and I do see the text when I run the project. When it first runs, the color bars display but then within a moment the screen goes dark. It shows that the HDMI is Unplugged. Though it is plugged in and the DVD player is turned on and running. I tested it with the TV first. If I change the resolution to 720P I get a green rectangle in the middle of my screen and if I select 3 or 4 it flashes and goes away in the upper right corner. WOW, my DVD player turned off and now it all works minus the stream stuff. I am getting the patterns and can change the resolution. Turned the DVD player back on and it quit displaying. Turned my DVD player back off and was able to display the color bars again. I got a power adapter and it still didnt work. I switched out the DVD player to my laptop and I got an image. The frame capture didnt work but at least I had an image. Wonder why the DVD player didnt work.