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

No testbench generated #135

Closed
ggreif opened this issue Mar 18, 2016 · 2 comments
Closed

No testbench generated #135

ggreif opened this issue Mar 18, 2016 · 2 comments

Comments

@ggreif
Copy link
Contributor

ggreif commented Mar 18, 2016

With a somewhat older clash, namely

$ ~/.cabal/bin/clash --version
CAES Language for Synchronous Hardware, version 0.6.8 (using clash-lib, version: 0.6.8)

I observed that a topEntity with a non-function signature

topEntity :: Signal (SFixed 2 10)

will not get a testbench generated even if I have

expectedOutput :: Signal (SFixed 2 10) -> Signal Bool
expectedOutput = outputVerifier $(v ...)

available. I tricked it into submission by giving topEntity a dummy input signal, but ignoring it:

topEntity :: Signal Bool -> Signal (SFixed 2 10)
topEntity _ = ... as before ...

For

CAES Language for Synchronous Hardware, version 0.6.15 (using clash-lib, version
: 0.6.13)

this trick does not work any more. What can I do?

@ggreif
Copy link
Contributor Author

ggreif commented Mar 18, 2016

I ended up always inputting a False signal and using mux. But this is not very satisfactory :-(

@christiaanb
Copy link
Member

Test benches will now also be generated for circuits that have no inputs. I'll release a new version of clash containing this feature today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants