User Tools
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
labs:debounce [2019/10/29 15:32] jgoeders [Exercise #3 - Top-Level Push Button Counter] |
labs:debounce [2020/04/30 09:44] (current) nelson old revision restored (2020/03/11 14:27) |
||
|---|---|---|---|
| Line 82: | Line 82: | ||
| {{ :labs:debounce:debounce_sm.png?600 |}} | {{ :labs:debounce:debounce_sm.png?600 |}} | ||
| + | |||
| + | The diagram above shows a ''clr'' signal that resets/initializes your state machine. You should use your ''reset'' input to set your state machine to S0. | ||
| ** Debounce Timer ** | ** Debounce Timer ** | ||
| Line 98: | Line 100: | ||
| Determine the size of this signal using the //clogb2// function and declare the counter signal by using the results of the //clogb2// function. | Determine the size of this signal using the //clogb2// function and declare the counter signal by using the results of the //clogb2// function. | ||
| */ | */ | ||
| - | The description of the debounce timer is found at the end of section 26.1. For this design, however, you will be required to wait precisely 5ms instead of whatever the maximum value for your timer is. At 5ms your timer should assert "timerDone" and then reset to 0. Your counter must also be cleared when clrTimer is asserted. | + | The description of the debounce timer is found at the end of section 26.1. For this design, however, you will be required to wait precisely 5ms instead of whatever the maximum value for your timer is. At 5ms your timer should assert "timerDone". Your counter should be cleared when clrTimer is asserted by the state machine. |
| + | |||
| + | By the way, if you have a parameterized counter from a previous lab, go ahead and use it - no need to re-invent the wheel. If not, you may choose to create a counter module parameterized for both maximum count value as well as bit-width (you will be needing such a counter in essentially every lab you complete moving forward). | ||
| **Exercise 1 Pass-off:** Show a TA your debounce module. Explain how you implemented the state machine and how the state machine should behave when it receives a noisy input.\\ \\ | **Exercise 1 Pass-off:** Show a TA your debounce module. Explain how you implemented the state machine and how the state machine should behave when it receives a noisy input.\\ \\ | ||
| Line 116: | Line 120: | ||
| {{ :labs:tb_debounce.v |}} | {{ :labs:tb_debounce.v |}} | ||
| + | <color red>Include a copy of your testbench output in your lab report</color> | ||
| - | **Exercise 2 Pass-off:** Make sure the output of the testbench has no errors. You don't need to get a TA to pass this off.\\ \\ | + | **Exercise 2 Pass-off:** No passoff, just make sure that you passed the testbench with zero errors.\\ \\ |
