11-07-2013 03:17 PM - edited 11-07-2013 03:19 PM
I'm having a little trouble understanding how the Manage IP/Package IP tools organize things in Vivado, and I was hoping for some clarification.
I have a couple custom EDK IP stored in a pcores folder, like this:
pcores | |---core1_v1_00_a | | | |--data | |--devl | |--hdl | | |---core2_v1_00_a | |--data |--devl |--hdl . . .
In EDK, I can add a peripheral repository by pointing to the pcores folder, and then the cores show up in the EDK IP Navigator. Now, I'm trying to migrate them to Vivado using the Manage IP and IP Packager tools. What I would like to accomplish is to create a Vivado repository that works the same way, where I can point to the "pcores" folder as a repository in Vivado and each core will be accessible from the Vivado IP Catalog.
My confusion is how I tell Vivado this. What I've done so far is to specify the "pcores" folder in Vivado as the New Customized IP Location after first clicking on Manage IP, then point the IP Packager to "core1_v1_00_a" to package that core, and then by pointing the IP Catalog to look for a repository at "pcores" I was able to use the core in a Vivado design. Now, I would like to reopen the same Customized IP Location to add the second core to it, but when I click on Manage IP the option for recent locations is grayed out and I am forced to create a new location.
So my questions are:
1. Is the New Customized IP Location that I specified when I first clicked on the Manage IP tool the "repository" location for the Vivado cores, or do I need to essentially just package each IP separately and point Vivado to the "pcores" folder?
2. If the latter, what are the Customized IP Location and "empty_name.data" folder created there used for?
3. Why might I not be able to open the Customized IP Location I specified originally?
Let me know if I need to clarify anything. Thanks!
01-30-2015 07:09 PM - edited 01-30-2015 07:09 PM
01-30-2015 11:08 PM
For Vivado 2014.3 and later, see: UG1115: Packaging Custom IP Tutorial