The Simon State Machine Part 1

Transcription

1 The Simon State Machine Part 1 Lab Summary This lab is the first part to a two-part lab where you will be combining all the components you created throughout the semester into one functioning state machine. You will first modify your Random Number Generator from your previous lab. You will then replace the Sound Decoder with the TEST_Controller VHDL block provided to, and make the necessary connections. Once the design works with the proper hardware connections, the TEST_Controller should be replaced by the System Controller VHDL file that will also be provided to you. The System Controller is the state machine that performs the function of the Simon game by controlling all of the output signals to all other hardware based on the input signal status. Once your hardware connections are verified as correct with the Test Code, you will need to replace it and edit the code in the System Controller VHDL file to get the Simon game to work. Lab Preparation Supplies: DE2 Board USB Blaster Cable (already on your lab bench) Simon Game Box Speaker

2 Part 1: Modified Random Counter and TEST_Controller Watch the Lab6&7 video. Modify the Random Counter by removing the SevenSegment block and adding the counter megafunction block as seen in the video and schematic below. Figure 1. Modified Random Counter You will also be renaming some of the pins. Don t forget to remove the not gate that was present in the old version. Also ensure that your RandomCounter has a count enable pin and not a clock enable pin. Once the Random Counter has been modified, update the symbol file and delete and replace the old Random Generator at the top level on the CODEC. You will also replace the SoundDecoder block you created in the previous lab with a TEST_Controller block. Download the TEST_Controller vhdl file from the website, paste and add it to your project. Once added, create a symbol file from your vhdl file and it to the top-level like in the schematic below.

3 Figure 2. Top-Level with Test Controller DO NOT MODIFY the VHDL code inside the TEST_Controller VHDL file. Make sure that all connections to the TEST_Controller are correct. Recompile your project with your modified random number generator and TEST_Controller. Program the DE2 board with your modified project and make sure that it works. If everything was done right, you should be able to observe the LEDs cycle like an arcade game. When you press Key[0] a random sequence will play on the Simon board. You can also press the pushbuttons at this instance to check to see if the LEDs and audio are responding. The Test block ensures that all your components are working right. Checkpoint 1: Demonstrate your working project to a lab monitor or TA. After Checkpoint 1, archive your project so that you don t lose any of your changes.

4 Part 2: System Controller Code Download and replace the TEST_Controller with the System_Controller VHDL file. Make a block and replace the TEST_Controller. Be advised that your hardware will not work until you have fully edited the System_Controller. Finally, you will begin writing the code for the system controller to get everything to work. Note that the code seen in the VHDL file is slightly different than what you saw in the video. More code has been added to make it easier for you to complete the project. You will NOT need to uncomment or remove any code. Figure 3. Top-Level with System Controller

5 Wait State For the Wait state, the only code you need to add is below the if and elsif statements seen in the figure below. Note that the correct format is elsif and NOT else if. Figure 4. Code to be modified for Wait State You should be familiar with how to turn LEDs on and off from the previous labs. Remember, the LEDs are low true. In order to reset ticks, simply set the value of ticks to zero. Unlike the Boolean values used for the LEDs, ticks is an integer, hence when setting the value for ticks, you will not use any quotes ( ). Checkpoint 2: Show your Wait state VHDL code to a lab monitor or TA. Autodisplay State For the Autodisplay state you will need to add code below the if and elsif statements seen in the figure below. The variable auto_counter is an integer. To increment its value simply add 1 to itself. Figure 5. Code to be modified for Autodisplay State Checkpoint 3: Show your Autodisplay state VHDL code to a lab monitor or TA.

6 Game State For the Game state you will need to write if statements for two cases. One case for when a button is pressed and another case for comparing the pressed button with the generated sequence. When a button is pressed, you will need to add these four statements: 1. Turn on the corresponding LED 2. Load the corresponding audio value 3. Save the corresponding color value in button 4. Reset the timer (ticks) Figure 6. Code to be modified for Game State (Part 1) Next, you will be comparing the pressed button value with the generated sequence. You will need to write the same three statements for each case as seen in the figure below. Figure 7. Code to be modified for Game State (Part 2) Checkpoint 4: Show your Game state VHDL code to a lab monitor or TA.

7 Win State For the Win state, turn the LEDs and sound on in a specific sequence.: in order of their frequency. The code you will need to add is very simple and seen in the figure below. Lose State Figure 8. Code to be modified for Win State For the Lose state we want to play the Wrong audio for one second. After one second, you want to reset ticks, set the value of button back to no_button and go back to the Wait state. Figure 9. Code to be modified for Lose State Checkpoint 5: Show your Win state and Lose state VHDL code to a lab monitor or TA. Compile your project. If you get any errors, they re most likely syntax errors. After fixing any errors that you might have had. Program your code and play the Simon game! Check to make sure your Simon game works as intended. Checkpoint 6: Demonstrate your working Simon Game to a lab monitor or TA

8 Checkpoint 7: Clean up and show your workbench to the lab monitor or TA. Discussion Questions 1. Name the 5 states and describe the function of each in one sentence. 2. For each state, indicate which hardware blocks in CODEC.bdf are used. 3. How would you change the code to increase the number of game states from 5 to 8? 4. How would you have to change the hardware to increase the number of game states from 8 to 16?