-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IntersectSphere is locked #2
Comments
I have the same problem. I created the same design from scratch but this time I cannot import the hardware description file to PetaLinux. |
Hi, Fabrizio |
Actually, I've already done it (I can generate bitstream). The problem occurs while importing .hdf (hardware description file) to PetaLinux. In my opinion, PetaLinux should have recognized the AXI DMA core and create the necessary drivers for Linux. What I get is as follows: petalinux-config --get-hw-description -p ~/Desktop/PetaLinux/projects/test_dma/ ****** hsm v2014.2 INFO: [Hsm 55-1698] elapsed time for repository loading 0 seconds *** End of the configuration. [INFO ] generate DTS to /home/abdullah/Desktop/PetaLinux/projects/test_dma/subsystems/linux/configs/device-tree while executing |
Which version of PetaLinux do you use? |
Is it possible that missing constraints cause it? |
We used the linux kernel released by Xilinx at the time we made the project On 9 October 2014 06:02, abdullahyildiz notifications@github.com wrote:
|
-Just to be sure I'm doing the right thing- Did you just run this command? petalinux-config --get-hw-description -p ~/Desktop/PetaLinux/projects/test_dma/ |
I think I've found my mistake. I thought that the connection automation could handle assigning the interrupts. What I've done is to use IRQ_F2P port at the Zynq PS part to connect mm2s_introut and s2mm_introut to the interrupt controller by using Concat IP in the IP Catalog (See http://www.xilinx.com/support/answers/55703.html). Now petalinux-config --get-hw-description -p ~/Desktop/PetaLinux/projects/test_dma/ does not give any error. |
Hi,
I'm trying to rebuild the bitstream with Vivado 2014.2 WebPack, but I get an error stating that there is some locked IP in the system. This appears to be the IntersectSphere block. What is that? Why do we need that? Can I replace it with a simple AXI4-Stream Data FIFO?
Maarten
The text was updated successfully, but these errors were encountered: