Closed da-steve101 closed 8 years ago
It turns out some of the peeks are generated internally by the Tester and the simplest way to silence them is by toggling the isTrace
member variable.
As a new Tester interface is under development for Chisel3, we'd like to hold off adding new features/complexity to the existing Tester interface.
fixes #588 which requests fine grained control over printing peek and pokes Unfortunately scala does not allow overrided methods with default arguments: http://stackoverflow.com/questions/4652095/why-does-the-scala-compiler-disallow-overloaded-methods-with-default-arguments But what I have done instead is make new methods with an argument "silent". Ie) peek() -> peekSlt( silent), poke() -> pokeSlt(, silent) etc ... the original behaviour for peek and poke is maintained so that it doesn't break anything