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

Timing in simulation needs investigating #218

Closed
xross opened this issue Jul 5, 2021 · 3 comments
Closed

Timing in simulation needs investigating #218

xross opened this issue Jul 5, 2021 · 3 comments
Assignees
Labels
testing Issue with testing
Milestone

Comments

@xross
Copy link
Contributor

xross commented Jul 5, 2021

In GTKwave the clock is shown as 100MHz (should be 60MHz)

The TB currently also allow for time slipping, however fixing this doesn't resolve the frequency issue.

@xross xross added the testing Issue with testing label Jul 5, 2021
@xross xross added this to the 2.0.0 milestone Jul 5, 2021
@xross
Copy link
Contributor Author

xross commented Jul 5, 2021

Added @DaveAtkinsonXMOS since he has been modding xsim

@xross
Copy link
Contributor Author

xross commented Jul 5, 2021

My current theory is that xsim's time units are "ticks" (rather than ns) but the TB is interpreting each tick as 1ns.

So at 600MHz each tick is 1.66ns. Multiplying the 10ns period we observe on the clock port by 1.66 gives us 16.66 -60MHz as expected.

This is quite a big bug with the TB.. suggest Pyxsims wait_until() is renamed wait_until_ticks() we can also add wait_until_ns() since we know the core freq in the tb

This was referenced Jul 5, 2021
@xross
Copy link
Contributor Author

xross commented Jul 6, 2021

Fixed in #220

@xross xross closed this as completed Jul 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Issue with testing
Projects
None yet
Development

No branches or pull requests

3 participants