-
Notifications
You must be signed in to change notification settings - Fork 48
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
Adding fst and struct trace support #274
base: pymtl4.0-dev
Are you sure you want to change the base?
Adding fst and struct trace support #274
Conversation
Are there any ways to check if the metadata has changed so we can make Verilator perform a recompile? Now, if I turn the |
I think we write some specific metadata into a comment in the generated verilog so when we regenerate the verilog with different metadata it ends up forcing a recompile? Maybe you can see how we do this for VCD tracing? We have a way where if you turn on VCD tracing it results in forcing Verilator to do a recompile? |
Here's where we do the check: pymtl3/pymtl3/passes/backends/verilog/import_/VerilogVerilatorImportPass.py Lines 340 to 347 in 4b3bc18
|
Is the |
I think it comes from the translated verilog. |
I want to fix that, but it will probably be in another pull request. I will open an issue and ask where to look. |
I have added support for tracing the structure correctly in the waveform
I have also added
fst
format to reduce the trace file size since tracing the structure increases the file size.