User Tools
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
labs:sp20_uar [2020/06/10 16:58] nelson [Exercise #3 - Test It in hardware] |
labs:sp20_uar [2020/06/10 17:08] (current) nelson [Exercise #3 - Test It in hardware] |
||
|---|---|---|---|
| Line 155: | Line 155: | ||
| Synthesize, implement, and generate a bitstream for your design. Test it in hardware with putty. In putty, anything you type will be sent down the line (make sure you have the baudrate, parity, etc all done correctly). It will NOT be mirrored to the putty screen but will go down the serial line where your receiver will receive it and display it on the LED's. Once your receiver has received a byte it should light up the Receive output to tell you that a new character has arrived. The handshaking will be that you assert the Received input (from a button) and your state machine will lower Receive and that is the end of the handshake. The received byte should be reflected on the LED's along with the parity error signal. | Synthesize, implement, and generate a bitstream for your design. Test it in hardware with putty. In putty, anything you type will be sent down the line (make sure you have the baudrate, parity, etc all done correctly). It will NOT be mirrored to the putty screen but will go down the serial line where your receiver will receive it and display it on the LED's. Once your receiver has received a byte it should light up the Receive output to tell you that a new character has arrived. The handshaking will be that you assert the Received input (from a button) and your state machine will lower Receive and that is the end of the handshake. The received byte should be reflected on the LED's along with the parity error signal. | ||
| - | As you test your design, remember a few things: (a) upon startup when your shift register has all 0's in it, what would you expect the value of your parityErr signal to be? Check it to be sure. (b) Remember that after each character is received you must acknowledge it via handshaking using the Received button. | + | ===Some Thoughts on Testing=== |
| + | * Upon startup when your shift register has all 0's in it, what would you expect the value of your parityErr signal to be? Check it to be sure. | ||
| + | * Remember that after each character is received you must acknowledge it via handshaking using the Received button. | ||
| + | * This can be a difficult design to debug if it is not working. For example, if you set up putty and push a character and absolutely nothing happens, then what do you do? One common strategy would be to bring your state machine bits out to output pins and wire them to LED's. That way, if you FSM is just stuck in some state you will have a hint. | ||
| + | * The .xdc file for this design has been left wide open - it is easy to get confused about the role of Receive vs. Received and other signals. Carefully think through them until you are sure you understand what they are to do. | ||
| <color red>Include a copy of your top-level module in your laboratory | <color red>Include a copy of your top-level module in your laboratory | ||
