02-20-2016 10:20 PM
I have a need to, based on combination of parameters that user has selected for the IP in his BD, decide which .xdc file(s) to include in the IP build process, such as:
if (based-on-user-selected-IP-GUI-option) then
Any ARs, AppNotes or examples on how to go about that?
02-20-2016 10:24 PM
I think this AR should help you:
02-20-2016 11:43 PM
Is your query resolved? If you need any further help, please let us know.
02-21-2016 12:00 AM
That AR is very interesting, but it unfortunatelly does not address what I'm trying to do, which is:
1) keep the IP reconfigurable in user BD
2) but have it pick up proper subset of .XDC and .V files for the combination of options that user has selected through the IPI GUI
Note that the user may put down multiple instances of this IP on his BD canvas, and have different parameter selection for each, hence the IP would need to get built with different set of .XDC and .V files for each instance. And, given the rather large number of parameter combinations, I really need to support that with only one component.xml file.
By googling around, I ran into the following link:
which comes with the kind of construct I'm looking for:
02-21-2016 01:40 AM
@chili.chips As far as i know there arent any examples like this. We wont recommend customers to modify/update xml files which are in install area. I havent tried this myself but i think unmanaged constraint may help you here, check this thread
02-21-2016 10:41 PM
unmanaged constraints are indeed helpful to know about and I believe they could be drawn upon to crack this problem open.
Ultimately however, what I'm looking for is ability to define *Enablement Dependency* in the File Groups section of IP-XACT GUI in the similar way as that can already be done for Ports and Interfaces
Also, is there a way to propagate configuration parameters from the IPI GUI into this "unmanaged constraints TCL"?
I know they get propagated from GUI to Verilog parameters / VHDL generics, but am not sure how to pick them within TCL to so make the constraints sensitive to the combinaton of IP settings that the user has entered within IPI GUI.
Alternatively, is there a way to embed contraints' TCL in RTL, in which case I could use Verilog conditionals to pass the GUI settings into constraints, such as:
if (GUI-ENTERED-PARAMETER-VALUE == XYZ) then
I believe that Synopsys DC can take constraints which are embedded in RTL...
02-25-2016 11:56 PM
here is an interesting lead on How-to-Propagate-Parameters-from-Verilog-to-TCL, but unfortunatelly does not solve the problem: