Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport T1Rocket and T1Rocket testbench #745

Closed
wants to merge 5 commits into from
Closed

Conversation

sequencer
Copy link
Member

  • [build system] add t1-rocketv in build system for link t1 with rocket
  • [t1rocket] implement T1RocketTile
  • [t1rocket] implement t1rocket Testbench
  • [build system] add elaborator to T1RocketTestbench

Avimitin and others added 5 commits August 26, 2024 16:26
It is incovenient for users to always input strings like
".#t1.blastoise.ip.cases.mlir.hello.emu-result". So here is an env to
help improve the current situation. With the "dev-mode" shell, users
will have many bash function to help them set the current development "mode".

For example, if users want to test "intrinsic.linear_optimisation" with VCS emulator,
and compare the result with verilator-emulator,
they will have to write "nix build
.#t1.blastoise.ip.vcs-emu.cases.intrinsic.linear_optimisation",
then ".#t1.blastoise.ip.verilator-emu.cases.intrinsic.linear_optimisation"

With the new script, the test flow is separate into different phrases:

* Firstly, get into the dev-mode shell: `nix develop .#dev-mode`
* Then, set the config: `set_config blastoise`
* Users can inspect RTL with simple command too: `build vcs-emu-rtl`
* To switch between verilator and VCS, they can use: `set_emulator
  vcs-emu` or `set_emulator verilator-emu`
* Finally, run the case: `test intrinsic.linear_optimisation`

Signed-off-by: Avimitin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants