-
Notifications
You must be signed in to change notification settings - Fork 450
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
Add feature to "Clock Input" #1341
Comments
Yes. A clock device that output 'n' number of pulses and then stops until triggered again would be nice to have. I tend to often need to manually step through a clocked design and I need to to it in steps of 8 or something like that. Sometimes I want to get deep into the running of an application and I want to quickly get to like 24768 steps into the running and then start single stepping to debug a problem. |
There is a break component. If the circuit contains a break component, the “Run To Break” button is enabled. This button clocks the simulation until the break signal is detected. |
I'm not sure I understood that. You can integrate several break components into the circuit and “fast-forward” the simulation to each of the break components. This gives you full control over the breakpoints. |
You have to disable the clock: The clock control needs to be manual. |
Hmm... Yea. I see now that it says so in the help - I really should learn to read the help files. |
For "Clock Input", add ability to automatically stop after X number of clock cycles.
The text was updated successfully, but these errors were encountered: