Build Process Adjustments Required for Bitstreams

[UserNameForGithub03]

Hello, i am new to RoSE. I’ve encountered a few issues with the config_build_recipes_local.yaml file in the RoSE project, particularly with the bitstreams that have the pattern "-with-airsim". It seems there are some missing or mismatched classes.

1. For building the bitstream firesim-rocket-singlecore-fp32gemmini-with-airsim-fast-no-nic-l2-llc4mb-ddr3:

   • Update chipyard.AirSimIOTLFPGemminiRocketConfig to chipyard.config.RoseTLRocketConfig in config_build_recipes_local.yaml.
   • Add the key PLATFORM: xilinx_alveo_u200.
   • Update PLATFORM_CONFIG to BaseXilinxAlveoU200Config.
   • Add platform_config_args with:

     fpga_frequency: 45
     build_strategy: TIMING

2. Adjust buildbitstreams.sh to keep only firesim-rocket-singlecore-fp32gemmini-with-airsim-fast-no-nic-l2-llc4mb-ddr3 and comment out others.

Thanks for your time! Hope for your reply.

[zhuzhurrx]

Hello, I'm also new to RoSE. I am quite confused. Who do you mean by 2. Should I comment out all lines in buildbitstreams.sh file before run it except for "firesim-rocket-singlecore-fp32gemmini-with-airsim-fast-no-nic-l2-llc4mb-ddr3" ?

[iansseijelly]

Hi, thanks for your time and effort in trying out RoSE.

If you wish to use buildbitstream.sh and reproduce the AE results we presented in the ISCA paper, then I would recommend checking out to isca-ae branch and all scripts should work as expected.

If you wish to use the latest branch with many new features like near-sensor computing support, latency injection support, and multi-node firesim support, I have just merged those features into main. You should then not use builtbitstream.sh as they're one-time scripts for ISCA AE, and does not keep up with the updates.I will release updated documentation soon.
In general, you should do all normal FireSim setup steps (buildbitstream, infrasetup, etc.) in FireSim, and then use rose.py to launch the simulation.