Syllabus - ESET 369 Embedded Systems Software, Fall 2016 Contact Information: Professor: Dr. Byul Hur Office: 008A Fermier Telephone: (979) 845-5195 Facsimile: E-mail: byulmail@tamu.edu Web: www.tamuresearch.com Student Assistant: TBD Office: Telephone: Facsimile: E-mail: Web: Class Period and Location: Monday, Wednesday, and Friday, 9:10 am - 10:00 am, Thompson Hall 122 Lab Period and Location: Friday 3:50 pm - 6:30 pm, Thompson Hall 101A (Section 501) Tuesday 1:50 pm - 4:30 pm, Thompson Hall 101A (Section 502) Office Hours: Monday, Wednesday, and Friday, 10:10 am - 11:00am, 008A Fermier, Student Assistant: TBD and/or by appointment. Course Description: A study of the technical aspects of embedded computer software systems, with emphasis on embedded real-time systems, programming techniques and development methodologies. Course Sequence Goals: Develop understanding of the technical aspects of embedded systems including Hardware and Software methodologies, Advanced C and Assembly programming techniques, and Embedded operating system concepts. Prerequisite: ESET 349 with a grade of C or better; completion of ENGL 104, MATH 151, MATH 152, CHEM 107 and CHEM 117, and PHYS 218 with a grade of C or better; junior or senior classification in electronic systems engineering technology. Corequisite: ENTC 350. Textbook: (Recommended) Simon, D. E., An Embedded Software Primer, Addison-Wesley, Boston, 1999. (Reference) C Primer Plus, Fifth Edition, Stephen Prata, 2005, Davies, John H., MSP430 Microcontroller Basics, Elsevier, 2008 Hohl, W., ARM Assembly Language - Fundamentals and Techniques, CRC Press, 2009 Exam Dates: There will be one mid-term exams and one final exam given in the semester. Midterm Exam: Tentatively, October 7 th, 2016 (Friday) Final Exam: Tentatively, December 9 th, 2016 (Friday) Term Project Due (if it is given): Tentatively, December 5 th, 2016 (Monday) Term Project: The term project is your opportunity to demonstrate your skills learned in this course. You can form a team of two or three students. In this course, it is recommended to deliver the term project in a team or a group. However, you can choose to deliver the project without a team or group but by only your induvial contribution. I will evaluate overall performance based on what you did either a team or only individual contribution. Students who worked on a team need to report the evaluation of their team members contribution as percentage (Total: 100%), which will be included in the grading.
Make-Up Exams/Quizzes Policy: If an emergency arises and you cannot take the test or quiz on the right dates, please contact me before the exam date. If not, please contact me within 24 hours with a documented excuse. According to the University policy, for illness confirmation I require you to fill out the Texas A&M University Explanatory Statement for Absence from Class (form available at http://attendance.tamu.edu). Attendance: Regular lecture and laboratory attendance is required. Attendance during all regularly scheduled examinations is required. Students who are absent from a lecture or examination must submit medical or other appropriate documentation in order to classify the absence as excused. A student who is absent from an examination without submitting medical documentation or other appropriate documentation that substantiates an emergency will receive a zero for the examination grade and there will be no make-up examination. Each student is responsible for all material presented during regularly scheduled lecture and laboratory sessions. Preliminary Grading Policy: Your course grade will be based on the following points: Midterm Exam 20% Final Exam 20% Homework 15% Laboratory 25% Term Project 10% Quizzes, Attendance, and Participation 10% Total 100% A: 90%-100%, B: 80%-89%, C: 70%-79%, D: 60%-69%, F: <60%, incomplete Lab, or an F score in Lab. (*Round to the Nearest One) One middle-term exam and a final exam will be given. Since the course content builds on prior material, all exams are to some extent cumulative. No make-up exams will be given unless circumstances are exceptional. The term project is your opportunity to demonstrate your skills learned in this course. The term project can be done in groups of up to three students. At the end of the semester, students will be asked to evaluate your project which will be included in the grading. Laboratory Requirements: All laboratory work must be completed to meet the minimum requirements for a passing grade in the course. Laboratory work may include exercises, assignments and a final project. Each student is required to maintain an engineering journal. In this journal you will record the progress of your work, questions, references, contact information, web addresses, etc. Each student is expected to prepare for laboratory work. When you work with the professor you may be asked to review your journal entries. In preparation for laboratory work sessions each student should read related reference material, conduct appropriate research and work related problems. All laboratory work must be completed to meet the minimum requirements for a passing grade in the course. You should not miss any labs and you must have all pre-labs and lab reports completed.
The following procedures will help us maintain a safe and clean lab. Please no cell phone calls or text messaging while working on your laboratory assignment. The lab requires your concentration and most of the time you need to troubleshoot your network setup. The use of cell phones and text messaging is a big distraction and will not be allowed. Keep a journal (on-line or in a notebook) of the common procedures and commands to configure network equipment. Before leaving the lab, make sure to demonstrate to the laboratory instructor that you completed the laboratory experiment, and he/she will sign you out. Clean your workstation after each lab period, and return all equipment and materials to appropriate stations before leaving the lab. No eating or drinking in the laboratory. Prepare for a lab in advance by reading up the required theory and pre-labs. Follow the lab instructions clearly and demo the checkpoints to the TA. Always reach the lab on time and always inform in case you are not able to make it, make sure you complete it at another time. For group submissions the entire group is responsible for on time submission. Each and every part of the lab report should be according to the rubric description 1) Introduction: Describe the objective of the lab, an overview of the main task, and describe how it is going to be achieved. 2) Flowchart 3) Source code: C or assembly code should be included, with comments throughout the code. 4) Make sure the report is well formatted and grammatically correct. Always use a cover page. 5) Q&A: Always answer any question in the lab report in a question-answer format. State the question with the number and highlight the answer. 6) Conclusion/Discussion (Optional): The conclusion/discussion should state the lessons learned from the lab and its practical applications. Academic Integrity: The Aggie Honor Code states, An Aggie does not lie, cheat, or steal or tolerate those who do. Academic Integrity is essential for the university environment of academic inquiry and learning and the accurate recognition of each student s achievement in that endeavor. Collaboration and information sharing are characteristics of a university education; however, academic integrity is violated when student conduct involves dishonesty or ways that give a student an unfair advantage. Academic dishonesty includes the commission of any of the following acts: cheating, fabrication, falsification, multiple submissions, plagiarism, complicity, abuse and misuse of access and unauthorized access, violation of departmental or college rules and university rules on research. (This listing is not exhaustive.) Clarification of these terms is at: www.tamu.edu/aggiehonor/definitions.php
Students may report violations of the honor code to the Aggie Honor System Office (AHSO), www.tamu.edu/aggiehonor or to the instructor. The report procedure is described at: www.aggiehonor/reporting.php Self-reporting is encouraged and may be considered a mitigating circumstance in the sanctioning phase of a particular case. The honor code process is described at: www.tamu.edu/aggiehonor/process.php and www.tamu.edu/aggiehonor. The following is an overview of some of the student responsibilities: You are responsible to be fully acquainted with and to comply with the Aggie Honor Code, Honor Code Rules and Procedures. You are responsible to seek clarification from the instructor if you are in doubt whether an action constitutes academic dishonesty. You are to actively promote academic integrity. Apathy or acquiescence in the presence of academic dishonesty is not a neutral act failure to confront and deter it will reinforce, perpetuate and enlarge the scope of such misconduct. Software Use All faculty, staff and student of the University are required and expected to obey the laws and legal agreements governing software use. Failure to do so can lead to monetary damages and/or criminal penalties for the individual violator. Because such violations are also against University policies and rules, disciplinary action will be taken as appropriate. We, the members of the University of Florida community, pledge to uphold ourselves and our peers to the highest standards of honesty and integrity Americans with disabilities act policy statement: The Americans with Disabilities Act (ADA) is a Federal anti-discrimination statute that provides comprehensive civil rights protection for persons with disabilities. Among other things, this legislation requires that all students with disabilities be guaranteed a learning environment that provides for reasonable accommodation of their disabilities. If you believe that you have disability requiring accommodation, please contact the Department of Student Life, Services for Students with Disabilities, in Cain Hall, Room B118 or call (979)845-1637. See www.tamu.edu for details. Tentative Schedule of Topics: Weekly Date, (No. of Classes) 8/28 (3) Topics: Embedded Systems, and C and MSP430 Assembly Programing Lab 0: H/W and S/W prep. 9/5 (2) Engineering Career Fair (6~7) and Sciences Career Fair (8) Tentatively No class on 9/7 (Wed.), No labs, and make-up class and/or labs if necessary later with the majority of students consent and request
Topics: MSP430 General Purpose I/O Programing, and Ch. 2 (Textbook) 9/12 (3) Topics: MSP430 Assembly Programing, MSP430 General Purpose I/O Programing, and Timers Lab 1: LEDs and Push Buttons 9/19 (3) Topics: Timers, and S/W PWM, and Ch. 3 (Textbook) Lab 2: 4 x 4 Matrix Keypad and 7 segment display 9/26 (3) Topics: LCD, Timers, S/W PWM, and Programming techniques, and Ch. 4 (Textbook) Lab 3: Timer and Buzzer 10/3 (3) Midterm exam, October 7, 2016 (Tentative) Topics: ADC theory, Programming techniques, review, and Ch. 4 (Textbook) Review for Midterm Exam No Lab 10/10 (3) Topics: ADC, MSP430 ADC modules, and Exam 1 solution Lab 4: LCD module (character) 10/17 (3) Topics: H/W PWM, DC motor, H-bridge driver, and Ch. 5 (Textbook) Lab 5: ADC lab 10/24 (3) Topics: Servo motor, Serial Communications Bit banging, and Ch. 6 (Textbook) Lab 6: DC motor lab 10/31 (3) Topics: Serial Communications UART & RS232, and Ch. 6 and 7 (Textbook) Lab 6: DC motor lab (part 2) 11/7 (3) Topics: Serial Communications UART, I2C and SPI, Real-Time Operating Systems (RTOS) and Basic Design, and Ch. 7 (Textbook) Lab 7: Servo motor lab 11/14 (3) Topics: Topics: I2C, Timers (Capture), IR sensor & decoding, Real-Time Operating Systems (RTOS) and Basic Design, TI RTOS examples, and Ch. 7 (Textbook) Lab 8: UART lab
11/21 (1) Topics: TI RTOS examples and Ch. 7 and 8 (Textbook) No class, Reading day (23) No class, Thanksgiving Holiday (24-25) No Lab 11/28 (3) Topics: TI RTOS examples, Arduino/Energia Kernel, More embedded system examples, and Ch. 8 (Textbook) Review for Final Exam Lab: Q/A session for Term Project 12/5 (3) Final Exam, December 12, 2016 (Tentative) Term Project Presentation on December 5, 2016 (Tentative) No Lab