-
Notifications
You must be signed in to change notification settings - Fork 250
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
Check _Next for more than 1 clock #576
Comments
I think the continuously asserted start event has been described already "check_next passes if expr = '1' num_cks active (according to active_clock_edge) and enabled (en = '1') clock edges after a start event. The start event is defined by an active and enabled clock edge for which start_event = '1'." So if you have many start events in a row there will be many clock cycles with expr = '1' in a row. I can add your figure for allow_missing_start. Can you provide the .json? |
Ok I will make a pull request for this item. Do you mind if i also change "check_next passes if expr = '1' num_cks active..." to "check_next passes if expr = '1' for the num_cks active..."? |
…ure (see VUnit#576). Indicates in the timing diagram when the options 'allow_overlapping' and 'allow_missing_start' add no influence regarding the given example.
…ure (see #576). Indicates in the timing diagram when the options 'allow_overlapping' and 'allow_missing_start' add no influence regarding the given example.
I think it is missing a section to describe that if Start_Event is asserted for X cycles, that it will also check that expression will also need to be asserted for X cycles.
And to maybe to put a decription where the description of allowing for overlaps
What do you think?
The text was updated successfully, but these errors were encountered: