01-24-2019 07:19 AM
I have a Vivado 2018.2 block design project with two regular and one HLS custom IP. When exporting hardware in Vivado, the hdf file only holds drivers for one of them, the other two are missing. Of course, when imported in SDK the BSP will only offer the"generic" driver for the other two IPs. To work around it, I manually have to add my IP repo path to the SDK repos.
What is the mechanism that decides which drivers to include in the hdf upon exporting? What tcl commands could I use to debug this? Where is this documented?
01-25-2019 05:14 AM
Not sure about it, I usually recomend the repository usage, need to take a look.
Did you try using advanced tabs within File groups of IP packages?
01-28-2019 04:03 AM
All three IPs have a Software Driver group. Not even the one getting its driver included in the hand-off has "is include" ticked. I don't think it does what you think it does.
Anyway, I tried editing the HLS IP and ticking "is include" for the whole driver group and apart from getting warnings about how some extension can not be an include, nothing changed at hand-off.