Open bgottschall opened 3 years ago
Thanks Bjorn, i'm looking into it.
@bgottschall, i'm sorry i never got around to fixing this.
The links are dead now -- did you workaround the problem?
For my purpose I did work around this problem by just not using any triggers and tracing every cycle. I just linked my target application into a address range that was unique so I could identify the data of interest.
But it would be great to attach to the tracerV trigger to selectively trace. I give you new links, my university decided to put this server behind a firewall ;) https://bgottschall.de/smallboom.fir.xz https://bgottschall.de/anno.json.xz
I created a new tracing interface which allows me to pipe out additional informations out of the simulation. I've created this interface exactly like TracerV, but a little bit simpler as it is just tracing out a bit vector. The interface works exactly as expected and I retrieve so far in the Verilator simulation exactly the data from my Bridge that I want. Now I wanted to reuse the TracerV trigger to enable tracing between certain trigger points. The documentation talks about the TriggerSource and TriggerSink annotation and the trigger is annotated as far as I can see like that in the TracerV Bridge.
So I tried to do the following:
However it gives me during the FIRRTL transformation the following error:
For reference here is the link to the mailing list discussion about that issue: https://groups.google.com/g/firesim/c/YQHhnuGdHMI
FireSim Version: 1.11.0
I've also uploaded the FIRRTL and annotation file (links will be valid until issue is resolved) Annotation JSON: https://bgottschall.de/anno.json.xz FIRRTL: https://bgottschall.de/smallboom.fir.xz