Introduction to Embedded Systems

EE319K, Unique: 15955, 15960, 15965
Semester: Spring 2009

Description

Embedded systems; machine language execution; assembly language programming; local variables; input/output synchronization; analog to digital conversion, digital to analog conversion; debugging; and interrupts.
 

Prerequisites

• EE306 and EE312 with a grade of at least C
   

Textbook

Jonathan W. Valvano
Introduction to Embedded Systems: Interface to the Freescale 9S12
HKN notes
(to be published by Cengage in 2009)
 

Objectives

1. Understanding how the computer stores and manipulates data (characters, integers, and fixed-point numbers), the basic arithmetic and logical operations performed by the computer.
2. The understanding of embedded systems (a system with the computer hidden inside) using modular design and abstraction.
3. Assembly language programming: considering both function and style.
4. Understanding how the computer executes instructions (fetch opcode, fetch operand, read data, operate, and write data).
5. The use of a microcontroller (strategic use of RAM, ROM and I/O). Microcontrollers typically have a little RAM and a lot of ROM. Globals, locals and the heap go in RAM. Constants and programs go in ROM.
6. Debugging and verification using a simulator and on the microcontroller (embedded systems typically do not have a print function). Debugging using breakpoints, scanpoints, profiles, monitors, voltmeters, oscilloscopes, logic analyzers.
7. How input/output actually happens (the students wire up analog and digital signals to the 9S12 and measure them with a voltmeter), synchronization, including switches, LEDs, LCDs, DACs, ADCs, and serial ports.
8. The implementation of an I/O driver (a set of programs that perform I/O).
9. Understanding, from an architecture standpoint, how local variables and parameters work (e.g., space on the stack is dynamically created, the local variable is accessed using stack-pointer relative addressing, then the space is deallocated).
10. Analog to digital conversion (ADC), e.g., the students interface a slide potentiometer to the ADC and write software that measures the position of the slide, creating a display like "1.23 cm".
11. Interrupt synchronization, real-time ADC sampling (periodic timer interrupts), introduction to multithreaded programming.
12. Simple motors (e.g., open and closed-loop stepper motor control).
13. Digital to analog conversion (DAC), used to make simple sounds.
14. Design and implementation of elementary data structures, such as linked lists, stacks and queues.

After the successful conclusion of EE319K, students should be able to understand the basic components of a computer, write assembly language programs that perform I/O functions and implement simple data structures, manipulate numbers in multiple formats, and understand how software uses global memory to store permanent information and the stack to store temporary information.
 

Policies

• Grading
  • 10% Homework assignments
  • 25% Lab assignments
  • 15% Test 1
  • 15% Test 2
  • 15% Test 3
  • 20% Final
  
   
• Lab policies

  This is a programming class. Therefore, the quality of the software you write will significantly affect your grade. When you get the program finished, make a printout of your assembly listing, staple a grading sheet to the front, then demonstrate it to a TA. The TA will record the performance and demonstration grades on the assembly listing printout. Labs are due during your scheduled lab period on Thursday. A detailed schedule follows. Late assignments incur a penalty of 10% of the maximum score per day for the first three days and will not be accepted afterwards. Exceptionally "good" programs may be given extra credit. If you do extra functions in your program, point out and demonstrate the extra functions to the TA when you demonstrate your program. Partial credit, not to exceed a maximum of 75% of full credit, may be awarded to a program that does not meet all specifications. Often it is better to demonstrate an incomplete program, rather than incur late penalties while fixing all its bugs. There are five components to the lab grade:

  1. Deliverables 20% (graded later)
  2. Performance 30% (graded by the TA at the time of checkout):
     How well does it work? Does it crash?
     Does it handle correctly all situations as specified?
     How clean is the user interface?
     Possible 5% Bonus, does it do more than specified?
  3. Demonstration 30% (graded by the TA at the time of checkout):
     Can you explain to the TA how your software works?
     Can you explain why you made certain software engineering tradeoffs?
     Both partners if applicable must be present during the demonstration.
  4. Software quality 20% (graded later):
     Clearly describe the data and program structures in the software comments. Simple, well-structured software with descriptive labels is much easier to understand than complex software with voluminous comments. Use either top-down or bottom up structure. Modular programming divides the problem into "natural divisions" with minimal coupling. The interfaces should be simple and natural. The software will be graded on the correctness of the program function, the comments, the interface to the user, the style, and organization. The effort spent to write high quality software will be rewarded both during debugging and when it is time to add features in the future.
  5. Late penalties (-10% per day)

  Lab partners: Most labs must be performed individually, and for others you may work either with a partner or by yourself (Lab 7 is an exception). The lab partnership must be registered with the TA (a simple hand written note or email signed by both students will suffice) 4 calendar days before the assignment is due. Once registered, the partnership will continue. A partnership can be dissolved by either party in writing 4 calendar days before the assignment is due. Both partners must be present during the TA demonstration.
  I strongly encourage you to do the labs solo to maximize your learning/satisfaction from this class.
   

• Homework assignments

  They will be administered over the web (active after 1/20). You may work in groups of any size but each of you MUST submit your individual solution online:

  1. Log into Quest Homework Service at https://quest.cns.utexas.edu/student. Click on the "Get Started" link and login with your EID, Unique #: 15955
  2. Download student's instructions and first homework after Wednesday 1/28.
  3. Work on the homework offline.
  4. Log in any time (possibly multiple times) to submit answers before due time (usually Monday 11:59pm). You can resubmit answers until correct, but you will get reduced or even negative scores for repeated mistakes.
  5. Download solutions after due time.

  The first homework will be due Monday 2/2. Late homework submissions will not be accepted under any circumstances. The lowest homework score will be dropped.
   

• Academic dishonesty

  "Faculty in the ECE Department are committed to detecting and responding to all instances of scholastic dishonesty and will pursue cases of scholastic dishonesty in accordance with university policy. Scholastic dishonesty, in all its forms, is a blight on our entire academic community. All parties in our community -- faculty, staff, and students -- are responsible for creating an environment that educates outstanding engineers, and this goal entails excellence in technical skills, self-giving citizenry, an ethical integrity. Industry wants engineers who are competent and fully trustworthy, and both qualities must be developed day by day throughout an entire lifetime. Scholastic dishonesty includes, but is not limited to, cheating, plagiarism, collusion, falsifying academic records, or any act designed to give an unfair academic advantage to the student. The fact that you are in this class as an engineering student is testament to your abilities. Penalties for scholastic dishonesty are severe and can include, but are not limited to, a written reprimand, a zero on the assignment/exam, re-taking the exam in question, an F in the course, or expulsion from the University. Don't jeopardize your career by an act of scholastic dishonesty. Details about academic integrity and what constitutes scholastic dishonesty can be found at the website for the UT Dean of Students Office and the General Information Catalog, Section 11-802." 

  You are allowed to talk to your classmates about the lab assignments, but you are NOT allowed to look at each other's written work. Oral discussion about an assignment is encouraged and is not considered to be cheating. Copying of any part of a program is cheating without explicit reference to its source. If we find two programs that are copied, there will be a substantial penalty to both students, e.g., failure in the course. Students who cheat on tests or in lab will fail. Prosecution of cases is very traumatic to both the student and instructor. It is appropriate to use software out of the book, class website as long as all copy-pasted software is explicitly referenced. Copy-pasting software from current or past EE319K students is scholastic dishonesty. 

  Policies concerning the use of other people's software in this class:

  • You may use any existing source code that is clearly referenced and categorized:
    original: completely written by you,
    derived: fundamental approach is copied but it is your implementation,
    modified: source code significantly edited to serve your purpose,
    copied: source code includes minor modifications.
  
   
• Add/drop

  The deadline for dropping without possible academic penalty is Monday, February 16, 2009.
   

Students with disabilities

The University of Texas at Austin provides upon request appropriate academic accommodations for qualified students with disabilities. For more information, contact the Office of the Dean of Students at 471-6259, 471-4641 TTY or the College of Engineering Director of Students with Disabilities at 471-4382.