0
\$\begingroup\$

enter image description here

Instead of toggling, this circuit throws this error. What does this mean and how do I fix it?

\$\endgroup\$
13
  • \$\begingroup\$ It is level-triggered. So your clock period is probably too long so it is changing the state several times during one period. \$\endgroup\$
    – Eugene Sh.
    Dec 23, 2019 at 19:33
  • \$\begingroup\$ @EugeneSh. I changed the clock's frequency to the maximum available value and I still get this error \$\endgroup\$ Dec 23, 2019 at 19:37
  • \$\begingroup\$ I am not sure how this thing is simulating. Do the gates have propagation delay simulated? Also it is indeed expected to oscillate. So maybe just follow the advise and single-step it? \$\endgroup\$
    – Eugene Sh.
    Dec 23, 2019 at 19:38
  • \$\begingroup\$ @EugeneSh. I looked it up and on the github page it said to run it in single step mode to figure out the case of oscillations and so I did, and it toggled normally like it should. \$\endgroup\$ Dec 23, 2019 at 19:43
  • \$\begingroup\$ @EugeneSh. I don't get the error right away when I set the J and K inputs to 1 at the start, I only get the error when the first toggle is supposed to happen \$\endgroup\$ Dec 23, 2019 at 19:45

1 Answer 1

1
\$\begingroup\$

Try this instead

Notice there are 2 stages of latches to make the clock edge sensitive.
enter image description here

\$\endgroup\$
1
  • \$\begingroup\$ Thanks, I will take a look \$\endgroup\$ Dec 23, 2019 at 22:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.