02-19-2020 10:33 PM
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.
02-26-2020 11:40 AM
03-04-2020 03:34 PM
@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.
03-05-2020 07:07 AM
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.
03-18-2020 09:07 AM
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.