User Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
labs:sp20_debounce [2020/05/28 10:39]
nelson [Exercise #2 - Debounce Simulation]
labs:sp20_debounce [2020/05/28 18:42] (current)
nelson [Debounce State Machine]
Line 1: Line 1:
  
-====== Debounce State Machine ======+====== ​Sp20 Debounce State Machine ======
  
 You will create a debounce state machine and use this state machine to debounce the button on the NEXYS4 board to reliably count the number of times the button is pressed. You will create a debounce state machine and use this state machine to debounce the button on the NEXYS4 board to reliably count the number of times the button is pressed.
Line 180: Line 180:
 After completing your top-level module, create a TCL script to simulate at least three "​noisy"​ button presses on your top-level design. Verify that your design counts properly in these noisy button press situations. After completing your top-level module, create a TCL script to simulate at least three "​noisy"​ button presses on your top-level design. Verify that your design counts properly in these noisy button press situations.
  
-<color red>​Attach ​your code and your Tcl script to the Lab Writeup page (there are locations to do so). Your simulation must show the expected behavior of your debounce module. ​+<color red>​Attach your Tcl script to the Lab Writeup page. Your simulation must show the expected behavior of your debounce module. ​
 </​color>​ </​color>​
 +
 +<color red>​Attach PDF of your **debounce** SystemVerilog module. ​  </​color>​
 +
 +<color red>​Attach PDF of your **debounce_top** SystemVerilog module. ​  </​color>​
  
 **Exercise #3 Pass-Off:** Nothing to be passed off in person. \\ \\ **Exercise #3 Pass-Off:** Nothing to be passed off in person. \\ \\