cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Adventurer
Adventurer
441 Views
Registered: ‎11-23-2018

set permanent XPM library for custom IP

Hello

I had the same issue as mentioned in given thread https://forums.xilinx.com/t5/Implementation/XPM-FIFO-SYNC-in-custom-IP-Could-not-resolve-non-primitive-black/td-p/824918

Is there any solution for permanent property setting for XPM library while packaging the Custome IP?

For every new design, I need to set this library for custom IP. 

 

0 Kudos
5 Replies
Highlighted
Scholar
Scholar
362 Views
Registered: ‎03-28-2016

I have the same issue as well.  A permanent solution would be greatly appreciated!

Ted Booth | Tech. Lead FPGA Design Engineer | DesignLinx Solutions
https://www.designlinxhs.com
0 Kudos
Highlighted
Xilinx Employee
Xilinx Employee
338 Views
Registered: ‎10-01-2007

Thanks for the feedback, unfortunately too late for 2020.1 but I will look at getting this supported for 2020.2.

0 Kudos
Highlighted
Xilinx Employee
Xilinx Employee
285 Views
Registered: ‎10-01-2007

@tedbooth I have been trying different combinations of packaged IP with XPMs in them and not having any issues.  No need to pass any parameters to make it work.  I might need a test case from you as I have nothing to show engineering that XPM is not working with packaged IP.  I am using 2019.2 for my testing.

0 Kudos
Highlighted
Scholar
Scholar
261 Views
Registered: ‎03-28-2016

@cdunlap,

Is there a flag that should be set when the IP is packaged?

The particular XPM Library that I'm having issues with the XPM_FIFO.  In my Vivado 2019.2 design, it listed XPM_CDC and XPM_MEMORY when I ran "get_property xpm_libraries ...".  I had to add XPM_FIFO with the "set_propery xpm_libaries..." command.

I can share with you the IP that I packaged, but I can't post it to the forums.

Ted Booth | Tech. Lead FPGA Design Engineer | DesignLinx Solutions
https://www.designlinxhs.com
0 Kudos
Highlighted
Xilinx Employee
Xilinx Employee
211 Views
Registered: ‎10-01-2007

OK we found the problem.  If you create a project with XPMs in it and then package it, it works fine in the packager.

If you create an IP from a directory, it dosen't add the XPM params.  This is because there is no project infrastructure that the session can grab this information from.

If you create an IP from a project without XPM initially, it won't add the XPM params in future builds.  We will fix the release to support this flow.