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

Jump to bottom

verilator does not produce waveform for 512-bit value #319

Closed
veripoolbot opened this issue Jan 26, 2011 · 3 comments
Closed

verilator does not produce waveform for 512-bit value #319

veripoolbot opened this issue Jan 26, 2011 · 3 comments
Assignees
@wsnyder
Labels
resolution: fixed Closed; fixed type: feature-IEEE Request to add new feature, described in IEEE 1800

Comments

@veripoolbot
Copy link
Contributor

Author Name: Alex Solomatnikov
Original Redmine Issue: 319 from https://www.veripool.org
Original Date: 2011-01-26
Original Assignee: Wilson Snyder (@wsnyder)

commands to reproduce:

verilator --cc hashBlockTest.v --trace --exe sim_main.cpp
cd obj_dir/
make -j -f VhashBlockTest.mk
VhashBlockTest

vlt_dump.vcd (attached) is missing "data" value.

It does work correctly if width of data is reduced to 256 bits.
@veripoolbot
Copy link
Contributor Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2011-01-26T20:28:58Z

That's expected. Tracing something so wide is very slow.

If you look in the generated __Trace source file, there will be a comment that says:

// Ignored: > 256 bits.

I probably could add an option to override this, just realize it will slow tracing down.

@veripoolbot
Copy link
Contributor Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2011-02-24T02:58:35Z

Added --trace-max-width and --trace-max-array.

In git for 3.812+.

@veripoolbot
Copy link
Contributor Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2011-04-06T11:40:18Z

In 3.812.

@veripoolbot veripoolbot added resolution: fixed Closed; fixed type: feature-IEEE Request to add new feature, described in IEEE 1800 labels Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wsnyder wsnyder

Labels
resolution: fixed Closed; fixed type: feature-IEEE Request to add new feature, described in IEEE 1800
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wsnyder @veripoolbot