Skip to content
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

Open
maartenbrock opened this issue Aug 26, 2014 · 8 comments
Open

IntersectSphere is locked #2

maartenbrock opened this issue Aug 26, 2014 · 8 comments

Comments

@maartenbrock
Copy link

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

@abdullahyildiz
Copy link

I have the same problem. I created the same design from scratch but this time I cannot import the hardware description file to PetaLinux.

@fspada
Copy link
Collaborator

fspada commented Oct 1, 2014

Hi,
IntersectSphere is a private core hw created with Vivado HLS in order to test the system. Obviously you don't need it, just replace IntersectSphere with anything that has a AXI4 Stream interface. If you want to test only the DMA you can connect MM2S and S2MM interfaces in loop.

Fabrizio

@abdullahyildiz
Copy link

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/
INFO: Checking component...
INFO: Getting hardware description...
INFO: Rename zed_wrapper.hdf to system.hdf

****** hsm v2014.2
**** SW Build 928826 on Thu Jun 5 17:59:37 MDT 2014
** Copyright 1986-2014 Xilinx, Inc. All Rights Reserved.

INFO: [Hsm 55-1698] elapsed time for repository loading 0 seconds
source /home/abdullah/Desktop/PetaLinux/projects/test_dma/build/linux/hw-description/hw-description.tcl -notrace
INFO: [Common 17-206] Exiting hsm at Wed Oct 1 10:39:22 2014...
INFO: Config linux
[INFO ] config linux
configuration written to /home/abdullah/Desktop/PetaLinux/projects/test_dma/subsystems/linux/config

*** End of the configuration.

[INFO ] generate DTS to /home/abdullah/Desktop/PetaLinux/projects/test_dma/subsystems/linux/configs/device-tree
INFO: [Hsm 55-1698] elapsed time for repository loading 0 seconds
INFO: [Common 17-206] Exiting hsm at Wed Oct 1 10:39:34 2014...
ERROR: Failed to post config linux
ERROR: Failed to config subsystem linux.
ERROR: [Common 17-55] 'get_property' expects at least one object.
ERROR: [Hsm 55-1545] Problem running tcl command ::sw_axidma::generate : ERROR: [Common 17-55] 'get_property' expects at least one object.

while executing
"get_property IP_NAME $intc "
(procedure "hsm::utils::get_dtg_interrupt_type" line 12)
invoked from within
"hsm::utils::get_dtg_interrupt_type $intc $ip $intr_port_name"
(procedure "get_intr_id" line 8)
invoked from within
"get_intr_id $dma_ip "mm2s_introut" "
(procedure "::sw_axidma::generate" line 24)
invoked from within
"::sw_axidma::generate axi_dma_0"
ERROR: [Hsm 55-1442] Error(s) while running TCL procedure generate()
ERROR: [Hsm 55-1450] Error: running generate_bsp.
make[1]: *** [autogen-dts] Error 1
make: *** [post-config-auto-dts] Error 255

@abdullahyildiz
Copy link

Which version of PetaLinux do you use?

@abdullahyildiz
Copy link

Is it possible that missing constraints cause it?

@durellinux
Copy link
Owner

We used the linux kernel released by Xilinx at the time we made the project
available.
Unfortunately I do not have Xilinx tool with me now to test it with the
latest Xilinx release.

On 9 October 2014 06:02, abdullahyildiz notifications@github.com wrote:

Can it be because of missing constraints?


Reply to this email directly or view it on GitHub
#2 (comment)
.

@abdullahyildiz
Copy link

-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/

@abdullahyildiz
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants