Skip to content
This repository has been archived by the owner on Aug 21, 2024. It is now read-only.

More than two clocks at top level of dut issues warning #358

Open
chick opened this issue Sep 10, 2021 · 1 comment
Open

More than two clocks at top level of dut issues warning #358

chick opened this issue Sep 10, 2021 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@chick
Copy link
Collaborator

chick commented Sep 10, 2021

In TreadleTester.scala:88
Maybe this should be >= 2 instead of >2

@chick chick added the bug Something isn't working label Sep 10, 2021
@chick chick self-assigned this Sep 10, 2021
@ekiwi
Copy link
Collaborator

ekiwi commented Sep 17, 2021

I think the problem is the implementation of findTopLevelClocks. The function should ideally only consider input ports. Currently it considers a lot of derived clock signals to be independent clocks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants