How is firtool upgraded?

[Øyvind Harboe]

How is firtool upgraded?

I take it https://github.com/ucb-bar/firtool-feedstock is actually maintained by Chipyard?

Some notes from trying to test out elaboration of RISC-V megaboom configuration:

I wanted to try out Chisel elaboration of RISC-V BOOM, so I made a quick and dirty change below and followed the tutorial: https://chipyard.readthedocs.io/en/stable/VLSI/Sky130-OpenROAD-Tutorial.html#building-the-design

However, it looks like Chipyard main(174ebc50b701a03226fd71c32d185727078cceb3 as of writing) is on an older version of the firtool(1.30.0, the latest is 1.54.0 as of writing), which I believe is causing some problems with dontTouch() and the firtool annotations.

I had firtool 1.53.0 locally and I put it first in my path and then re-ran "make syn tutorial=sky130-openroad" with the changes below, however, then I get the following error message:

firtool: Unknown command line argument '--emit-metadata'.  Try: 'firtool --help'
firtool: Did you mean '--emit-bytecode'?
firtool: Unknown command line argument '--repl-seq-mem-circuit=TestHarness'.  Try: 'firtool --help'
firtool: Did you mean '--repl-seq-mem-file=TestHarness'?
make: *** No rule to make target 'syn'.  Stop.

Removing those options, I still get the error message in my crosspost to Chisel group: https://groups.google.com/g/chisel-users/c/Z66x6LXuTe0

I tried adding  --disable-annotation-unknown, but still I get the same error.

diff --git a/vlsi/tutorial.mk b/vlsi/tutorial.mk
index 6b970fcb..eb4edf7e 100644
--- a/vlsi/tutorial.mk
+++ b/vlsi/tutorial.mk
@@ -27,7 +27,7 @@ endif
 
 ifeq ($(tutorial),sky130-openroad)
     tech_name         ?= sky130
-    CONFIG            ?= TinyRocketConfig
+    CONFIG            ?= MegaBoomConfig
     TOOLS_CONF        ?= example-openroad.yml
     TECH_CONF         ?= example-sky130.yml
     DESIGN_CONFS      ?= example-designs/sky130-openroad.yml \

[Jerry Zhao]

We maintain that Conda feedstock. It seems like the command line flags have changed in more recent versions, causing this error.

The firtool invocation is in chipyard/common.mk. You can try updating the command line flags there to work with the newer firtool.
If you do do this, can you post what you changed and/or make a PR? It would help when we get to bumping firtool.

Thanks,
-Jerry Zhao

--
You received this message because you are subscribed to the Google Groups "Chipyard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chipyard+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chipyard/c61516e1-6d41-42a7-86a2-cf0affa70e85n%40googlegroups.com.

[Øyvind Harboe]

I will try. I'm a newbie to Chipyard, but I'm not unfamiliar with  with OpenROAD, OpenROAD-flow-scripts, Verilator and Chisel. With a bit of help from Chisel community and Chipyard, hopefully I can contribute something :-)

What I am looking for now is the simplest way to run elaboration for MegaBoomConfig as a test-case for firtool 1.54.0...

Using https://chipyard.readthedocs.io/en/stable/VLSI/Sky130-OpenROAD-Tutorial.html#building-the-design I would have thought that I could run the command below, but even without upgrading firtool, it fails.

Any advice here? Should this have worked or is there something more that I have to do?

cd vlsi/

make buildfile tutorial=sky130-openroad CONFIG=MegaBoomConfig

[deleted]

/home/oyvind/chipyard/vlsi/generated-src/chipyard.harness.TestHarness.MegaBoomConfig/chipyard.harness.TestHarness.MegaBoomConfig.sfc.fir:2:1: error: Unable to resolve target of annotation: {class = "firrtl.transforms.DontTouchAnnotation", target = "~TestHarness|ChipTop>jtag"}

[deleted]

[Øyvind Harboe]

I have tried to gather some information on the failures with MegaBoomConfig: https://github.com/llvm/circt/issues/6143