[Discuss OpenCPI] [UK OFFICIAL] Multiple Constraints files for a HdlConfig
Classification: UK OFFICIAL
Hello again,
Is it possible for a HdlConfig file to specify multiple constraints files to be used?
I have a platform atm that has grown to 4 possible configurations, each requiring a complete Constraints file.
These configs are largely very similar (GPIO and RAM pins and iostandards are identical, clocks are set up the same way) with a section of FMC related iostandard constraints and associated input delays that differ.
Currently my HdlConfig looks like this:
<hdlconfig constraints="<file-name>">
......
</hdlconfig>
I tried a comma separated list of constraint files, but that doesn't seem to be supported and I struggled to find the section of ocpigen that parses this.
The way I've gotten around this at the moment is by editing vivado-impl.tcl:
_at_ -52,7 +54,7 @@link_design -mode $mode -part $part
puts "Loading XDC: $constraints"
- read_xdc $constraints
+ read_xdc -unmanaged $constraints
}
This allows the constraints file to be read as pure .tcl, so the .xdc file itself is then allowed use the whole syntax of .tcl, such as:
Ø read_xdc <second_constraints_file>.xdc
Without this change vivado complains, saying that "read_xdc can't be used in a .xdc file".
Is adding "-unmanaged" here okay?
You turn off managed design flows in vivado-synth.tcl, although I'm not sure if that is related to this -unmanaged flag.
Thanks,
Dominic Walters
"This e-mail and any attachment(s) is intended for the recipient only. Its unauthorised use,
disclosure, storage or copying is not permitted. Communications with Dstl are monitored and/or
recorded for system efficiency and other lawful purposes, including business intelligence, business
metrics and training. Any views or opinions expressed in this e-mail do not necessarily reflect Dstl policy."
"If you are not the intended recipient, please remove it from your system and notify the author of
the email and centralenq_at_dstl.gov.uk"
Received on Mon Jan 27 2020 - 14:45:45 CST
This archive was generated by hypermail 2.3.0
: Fri Jun 05 2026 - 08:45:25 CDT