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

SEQ3 and Timing Standards #106

Open
Nowhk opened this issue Jan 13, 2020 · 1 comment
Open

SEQ3 and Timing Standards #106

Nowhk opened this issue Jan 13, 2020 · 1 comment

Comments

@Nowhk
Copy link

Nowhk commented Jan 13, 2020

It seems that SEQ3 doesn't observe Timing Standards: Therefore, modules with a CLOCK and RESET input, or similar variants, should ignore CLOCK triggers up to 1ms after receiving a RESET trigger.

If I send a reset and a clock 1 sample later, it advance to step 2. i.e. doesn't ignore clocks up to 1 ms after a reset pulse.

@Nowhk
Copy link
Author

Nowhk commented Jan 16, 2020

Here's an example:
seq3 time.zip

Clicking on the button, it should reset and output "step 1", instead it goes directly to "step 2".

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

1 participant