part :1OverviewIn this lab, you will use TI Code Composer Studio (CCS) to program the TC CC3220x LAUNCHXL to control an LED from the serial port using a state machine. This work will build on the concepts you learned during your activities in the zyBook this week.
During this milestone you will use CCS to edit, compile, and load code into the CC32xx board. You will then proceed to use it for debugging. Throughout this process, you explore the components of a CCS project and the CCS code generator (system config). You will also be able to learn more about the UART and GPIO drivers.
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.
PromptBegin 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 CC3220x 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.
Guidelines for SubmissionYou will have four different file submissions for this milestone. Once you have completed your lab work, first zip your workspace and submit the zipped file for grading. Second, submit a 10-second video of the LEDs blinking on your board. If you encounter any difficulties filming the lights on your hardware component, reach out to your instructor. Third, submit a document containing your answers to the questions from the Milestone Two UART GPIO Lab Guide. Finally, submit a state machine diagram completed using draw.io and exported in PDF format.
part 2:
OverviewIn this module, you have been learning about peripherals. You have learned how to analyze the software requirements and resources required for peripherals, explain common peripherals for connecting to external sensors and actuators, and describe design considerations when selecting a particular peripheral for IO. For this assignment, we will focus on comparing peripheral interfaces in embedded systems.
PromptEmbedded systems communicate with the outside world via their peripherals. In this journal assignment, you will compare and contrast various interfaces and explain why you would use one over another. Research various interfaces to learn about the differences between communications protocols in embedded technologies, their uses, strengths and weaknesses. Describe the differences between any three: GPIO, PWM, A2D, SPI, I2C, and UART. Why would you use one interface over another? Address the following criteria:
Identify three of the following interfaces to compare and contrast:GPIO
PWM
A2D
SPI
I2C
UART
Explain the differences between the three interfaces chosen.
Explain why you would use one interface over another.
Guidelines for SubmissionSubmit your assignment as a 1- to 2-page Word document with double spacing, 12-point Times New Roman font, and one-inch margins.
