David Biancolin
David Biancolin
We have no foreseeable plans to support zynq because of the complexity of managing cross-builds for ARM-based platforms. This might change in the future.
Thanks for the detailed description, your understanding is correct -- this is a pretty serious timing bug. An immediate workaround is to limit ID reuse to 1 in the target...
I think in the short term the workaround is more useful as it used to be what we did in FireChip before the Chipyard migration. The fact we lost that...
In the UserYanker you can limit maxFlight to some number (specifically by setting it to `Some(1)`). In order to achieve the best system performance you really need to finesse how...
For 1.13.0, add an elaboration-time error if ID reuse is enabled under a model that may reorder across IDs. Longer term fix, limit inflight requests in the transaction scheduler.
I can't open that link, can please attach the tail of the log for that build? I suspect you're running out of resources. You should look at the instance-multithreading optimization...
Are you using FireSim or Chipyard as your top-level repo? This looks like the chipyard submodules are not in sync with each other, or some old scala build artifacts are...
Follow up: this doesn't appear to work on mill because the encoding of the string (i suspect) is wonky in such a way that the json deserializer breaks.
Can you report the address you had to change it to? The right solution here is to invest the time to allow the driver to pass in the base, which...