Goal: Your objective is to control the red LEDs in the lower right corner of the board $($the corner opposite the USB connector$).$ Use this to design a state machine to turn on an LED when a user types ON into the console and to turn off the LED when a user types OFF, using only one byte of RAM. Remember, you receive only one character at a time from the UART and it is not buffered. Then you will code the state machine you created.

Prompt

Begin your work by accessing the Milestone Two UART GPIO Lab Guide PDF document. While this document was written for a Windows interface, the tools can be used on Mac or Linux as well. Note that to accomplish the work outlined in the guide, you will need the following:

TI CC$3220$x LAUNCHXL

TI Code Composer Studio $($installed$)$

USB connection between the PC and board

Specifically, you must address the following rubric criteria:

Develop code for all of the specified functionality. The goal of this criterion is for the code to result in the expected functionality $($note how this is different from the state machine functionality$).$ Both ON and OFF should operate as expected. In your video, show the terminal window and LED to make this clear.

Create code that reads characters from the UART. This must use only one byte at a time with no multi$-$byte buffering of the serial input. The characters are encoded back.

Create code that controls the LED on and off from the state machine. Note that this involves use of the GPIO peripheral. Partial credit may be awarded if the code does not work but you are able to successfully determine how to turn the LED on and off, then include it in the comments.

Implement $($in code$)$ the state machine functionality described by your documentation. The goal of this criterion is for the code to accurately reflect the state machine documentation, rather than for it to have perfect functionality.

Create state machine documentation to describe the operation that matches the technical specifications. This should be completed as a draw.io file and saved as a PDF$.$

Discuss the questions from the lab. Address all the questions thoroughly and thoughtfully, with supporting evidence from your work.

Apply coding best practices in formatting, commenting, and functional logic.