Adding xilinx IP dcp files for packaging custom IP to speed up synthesis

[a.lisitsyn]

Hello!

I am new to a Vivado dcp concept and have some (maybe simple) question.

How can I add dcp (or netlist) of an IP to my own custom IP to speed up synthesis and generation of my IP?

For now, I have several ILAs in my own IP, that are added as .xci files to "Verilog synthesis" folder in "Package IP" wizard. However, when I add custom IP to a block design and start to generate block design it advanced very slowly, because it sequentially generates all ILAs from .xci files. Removing ILAs from custom IP incredibly speed up block design generation process. Another problem is that any modification in custom IP hdl sources (ILAs remains unmodified) makes Vivado regenerate custom IP core completely.

[balkris]

IP Packager does not accept DCP files as a source for a custom IP.

In Vivado 2013.3 and later an Error will be issued if a DCP is given as a source to the IP Packager.

[a.lisitsyn]

Any workaround for speeding up?

[vemulad]

Hi,

In vivado 2015.1 we have option "IP Cache", see if this helps.

Refer to page-25 of http://www.xilinx.com/support/documentation/sw_manuals/xilinx2015_1/ug896-vivado-ip.pdf for more details.

Thanks,

Deepika.

[swolf]

You can add an edif and associated constraints files instead of the DCP.  When adding xdc files with the edif, be sure to set the scope to cell and scope to ref properties appropriately to get the xdc to apply to the edif module.

While a DCP is definately more convenent, the vivado frontend is a bit limited with nesting DCPs.  Packager stops you from adding since the reset of the system wouldn't work with it.

[a.lisitsyn]

How can I convert dcp files that I get by OOC compile to edif files? I tried read_checkpoint your_design.dcp
write_edif -force your_design.edn but it does not work.

[vemulad · Accepted solution]

Hi,

Open the checkpoint using File-->open checkpoint command and run the write_edif command from the tcl console.

Thanks,

Deepika.

[a.lisitsyn]

Thank you, it works. But can I automate it by some sort of tcl script?

[sgustafsson]

IP packager (Vivado 2017.4) seems to accept DCP files as sub blocks when packaging IP. Adding a sub block in the dcp format becomes part of the hierarchy.  However, the module becomes a black box in implementation. Adding the DCP file to the project does not make a difference. Reopening the ip packager shows that dcp file is no longer in the project. Is there any way to make implementation use the DCP?