Hasan Genc

If you're on the `dev` branch, then there should be a file called `SPIKE.hash` that gives you the correct Spike commit that you need to be on. Afterwards, run these...

We've lost the original images, unfortunately. They were randomly selected from the ImageNet validation dataset. The numbers correspond to ImageNet1k classes. You could look into the ImageNet dataset to find...

I think that the original four images first passed through the standard preprocessing steps (which you've apparently already run). Afterwards, the pixel values where multiplied by a constant scaling factor....

The mvins are explained over here: https://github.com/ucb-bar/gemmini#mvin-move-data-from-main-memory-to-scratchpad

Your error implies that your Verilator installation may be out-of-date. Can you check: 1. Which Gemmini commit you are on. 2. Which Chipyard commit you are on. 3. Which Verilator...

This probably means that one of these two commands failed: ``` ./scripts/init-submodules-no-riscv-tools.sh ./scripts/build-toolchains.sh esp-tools ``` Could you share the output of these commands in a Gist?

The second instruction is to configure Gemmini's "im2col-on-the-fly" module. The module's configuration parameters have not been documented though, and the module seems to have bugs on the latest version of...

I think I know what this issue might be. Whenever you build Spike using the `./build-spike.sh` script, you generate a new file called `gemmini_params.h`, which you can find in the...

Just ignore that "error". It seems to be an issue with Chipyard, but it doesn't affect any of the simulations.

@fPecc This PR is out-of-date. Fortunately, we already have an improved depthwise conv which was added to Gemmini's `master` branch. We use it for our hand-written Mobilenet implementation (as shown...