Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Should we be able to poke() implicit resets?
See original GitHub issueWhile I’m aware that the testers have reset(), should we still be able to poke() reset like a normal signal? e.g. poke(c.reset, 1)
If so, it doesn’t seem possible to do that yet since poke() doesn’t recognize chisel3.core.Reset.
If not, then perhaps a more user-friendly error message is in order, since an error message of “no overload for chisel3.core.Reset” isn’t immediately obvious - maybe we should add an explicit poke() method for chisel3.core.Reset and have it print an error message to use reset() instead.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think you’re going to want to be able to poke reset in some way, especially if you have multiple resets.
Looks like poking reset is already in the testers2 test suite: https://github.com/ucb-bar/chisel-testers2/blob/1760d3b134b59fba990c8b91bb2696c542d95dff/src/test/scala/chisel3/experimental/tests/VerilatorBasicTests.scala