<pepijndevos>
daveshah, I'll be trying to add correct numbers for that in my next Apicula live stream. Last two streams I had ZirconiumX as a guest, but if you enjoy that kind of thing...
<OmniMancer1>
Oooh
OmniMancer1 has quit [Quit: Leaving.]
balrog has quit [Ping timeout: 260 seconds]
balrog has joined ##openfpga
mumptai has joined ##openfpga
X-Scale has joined ##openfpga
jemk has quit [Remote host closed the connection]
jemk has joined ##openfpga
Maya-sama has joined ##openfpga
<azonenberg>
daveshah et al: is anybody here familiar with the fine points of the vivado DCP file format?
<azonenberg>
i know it's a zip containing an xml manifest, an edif, and a bunch of other stuff
<daveshah>
Not really the fine points, but I've accessed it through the RapidWright blob a bit
<daveshah>
All the magic is in the proprietary xdef file
<azonenberg>
i'm wondering more about the multiple constraint files
hackkitten has quit [Ping timeout: 246 seconds]
<daveshah>
Oh, I haven't looked at that side at all
<azonenberg>
whats the difference between them and when do they get parsed?
<azonenberg>
and given a DCP how can i load it and do stuff to it without having a full vivado project?
<azonenberg>
or do i have to make a project and import the dcp as a source file?
<daveshah>
read_checkpoint tcl
<daveshah>
iirc
<azonenberg>
yeah i ran read_checkpoint on it and i got stuff
<azonenberg>
but it wasnt acting like a full design would
<azonenberg>
i feel like there's some other state i need
<daveshah>
No idea
<daveshah>
Pretty much all the DCPs I've used are of RapidWright origin and have no constraints, so I apply any timing constraints in tcl after loading
<azonenberg>
Yeah i'm trying to understand the details of constraint serialization for... reasons...
<azonenberg>
and things like precedence of DCP constraints relative to the project file