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

Implemented "legacy" 5x clock divider. #4

Merged
merged 1 commit into from
Apr 2, 2018

Conversation

awygle
Copy link
Contributor

@awygle awygle commented Apr 2, 2018

Also allowed adjusting testbench clock divider.

@whitequark
Copy link
Member

Hmm it's kind of annoying to have it enabled by default in toolchain tests because that slows them all down and clutters up waveforms. How about driving that signal to 0 early in the testbench, and reverting that in the test for it?

@awygle
Copy link
Contributor Author

awygle commented Apr 2, 2018

This sounds reasonable but I'm not sure where/how to do that. If I understand right, I don't think I can just .eq() the signal from the testbench because it's set by NextValue in the actual module, and I can't send the command with yield from tb.write in setUp or the constructor either (because those aren't supposed to be generators, maybe?)

@whitequark whitequark merged commit 1e48626 into GlasgowEmbedded:master Apr 2, 2018
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

Successfully merging this pull request may close these issues.

None yet

2 participants