Post B8IT8gX4Peei5RqgrI by mntmn@mastodon.social
 (DIR) More posts by mntmn@mastodon.social
 (DIR) Post #B8I4O9bk60H9khJVlA by mntmn@mastodon.social
       0 likes, 0 repeats
       
       someone has a recipe for running vivado p+r in CI? :D or what's the status of the foss toolchain for zynq?
       
 (DIR) Post #B8I4jbz7mlF3qMTxr6 by mntmn@mastodon.social
       0 likes, 0 repeats
       
       asking for my amigas
       
 (DIR) Post #B8I5MhbAqcNkY1v43k by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @rafaelmartins hehe, unfortunately ISE didn't support zynq7020 yet iirc
       
 (DIR) Post #B8I5kXBlCeFtDDOde4 by redsakana@infosec.exchange
       0 likes, 0 repeats
       
       @mntmn I think maybe @lethalbit was fighting with that a few weeks ago, but could have been someone else on my timeline
       
 (DIR) Post #B8IClamw0LsMLREgsa by seanwbruno@infosec.exchange
       0 likes, 0 repeats
       
       @mntmn Every project I've hacked on starts with "export project to TCL".  Then there some faffing about with removing DCP files and paths.Once that hackery works to build with the command line invocation of vivado, I'll wrap that in a shorter TCL file to "do that and then spit out an XSA".This seems to be the design pattern that worked for me with gitlab-ci and friends.
       
 (DIR) Post #B8IT6E5VCMHvHvmWmm by whitequark@social.treehouse.systems
       0 likes, 0 repeats
       
       @mntmn the meta is to strace a run then extract just the files it accesses
       
 (DIR) Post #B8IT6EIGQuUpvVkig4 by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @whitequark that's... refined
       
 (DIR) Post #B8IT8gX4Peei5RqgrI by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @seanwbruno thanks, good to hear it can work! i do have the tcl already
       
 (DIR) Post #B8IUXKOdwzracxDoXo by poleguy@mastodon.social
       0 likes, 0 repeats
       
       @mntmn We run vivado in CI and have full scripting for it. I have already had my wrist slapped for leaving a copy of all this up in a public github repo, so it's currently not publicly accessible. I intend to get it put back up eventually, but there are a bunch of corporate policies I'll have to navigate now. Is your question about scripting, or dealing with the size of the vivado install files?We run CI on our own on-prem machines so vivado on-disk size is not a worry.
       
 (DIR) Post #B8IfK6Ic9SDwdXITnE by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @poleguy yeah the question was mostly about the shape of the script (but i guess i can also dig in LiteX sources for that) and also if this is something that people successfully do
       
 (DIR) Post #B8Im63u6xXwopi5Za4 by poleguy@mastodon.social
       0 likes, 0 repeats
       
       @mntmn I can help significantly with this. We do some magic to make simulation and builds easier accross multiple tools by using an explicit list of files that we want compiled and parsing it into vcom and/or vivado tcl commands to include those files.But then the basic approach is to run in batch mode:time vivado -mode batch -source "build.tcl" -notrace || status=$?The build.tcl is a set of steps to do the non-project flow. This is pretty mundane.I could post examples if you need.