Hasan Genc

Well, I think the dog image might just be failing because the first node in your ONNX graph expects `int8` inputs, while the dog image is `float`. Perhaps you can...

It should be included for you by Firesim. Can you share which Gemmini commit and which Chipyard commit you're on?

Do you mean you can't clone all of Chipyard at once? We don't really support "partial cloning", unfortunately. I'm sure it's possible, but I just haven't tried it out myself....

Thanks for checking that! That's surprising to me

I'm not sure, unfortunately. We just haven't tried cloning the modules individually before, so I don't know what path or dependency issues might result from that

Pointer errors are usually caused by `gemmini_params.h` files which don't match each other. Can you make sure that your `systolic_params_fp32.h` file matches the `gemmini_params.h` which was created by your dummy...

1. While we don't explicitly support int32 in ONNX-Runtime, I _believe_ that if you just replace `systolic_params_int8.h` with the int32 `gemmini_params.h` and rebuild, then it _should_ work. I haven't tested...

We've built a 32-by-32 design on Firesim a while back, but I don't remember us pushing above that. Did 64-by-64 work for you? Also, I believe Firesim gives multiple options...

Unfortunately, in your example, increasing `dma_buswidth` only increased the bus-width on Gemmini's side, but didn't actually increase the system bus-width connecting to Gemmini from other components on the SoC. So...

For Gemmini 0.6.4, you should be using Chipyard's `117624d8eea27bafd613eec09e9b9b3e31239e08` commit (as in the `CHIPYARD.hash` file) Was there as specific reason why you wanted Chipyard 1.8.0? If so, one easy way...