EE319K Introduction to Embedded Systems, Spring 2012 (5/3/2012 version)
Course Catalog Description Embedded systems; machine language execution; assembly and C language programming; local variables and subroutines; input/output synchronization; analog to digital conversion and digital to analog conversion; debugging; and interrupts.  
  EE319K will continue the bottom-up educational approach, started in EE302 and EE306. The overall educational objective is to allow students to discover how the computer interacts with its environment. It will provide hands-on experiences of how an embedded system could be used to solve EE problems. The focus will be understanding and analysis rather than design. The analog to digital converter (ADC) and digital to analog converter (DAC) are the chosen mechanism to bridge the CE and EE worlds. EE concepts include Ohms Law, LED voltage/current, resistance measurement, and stepper motor control. CE concepts include I/O device drivers, debugging, stacks, FIFO queues, local variables and interrupts. The hardware construction is performed on a breadboard and debugged using a multimeter (students learn to measure voltage and resistance). Software is developed in Freescale 9S12 assembly and C; 3 out of the 10 labs are simulated-only in TExaS and other 7 are first simulated on TExaS then run on the real 9S12. Software debugging occurs during the simulation stage. Verification occurs in both stages. Labs 1 through 6 are written in 9S12 assembly language. Labs 8 and 9 are written in a combination of assembly and C.  Labs 7 and 10 are written in a C.
Class: ACA 1.104, Tuesday, Thursday 5-6:15pm    Lab: ACA 1.108 (old EE302 room)
Office Hours (change): Tuesday 3:30-4:50pm, Wednesday 1-2pm, Friday 12noon-1

Instructor: Jonathan W. Valvano, ENS627, 471-5141
email  (put "EE319K" in the email title, send no ZIP files)  
Web page 
Lecture notes and lab assignments   Spring 2012 homework 
Data sheets  
Starter files 
Unique Numbers:  16215 Th1-2, 16220 Th2-3, 16225 Th3-4, 16230 Th4-5,  
Text: Introduction to Embedded Systems: Interfacing to the Freescale 9S12, Cengage Publishing 2009, ISBN-10: 049541137X | ISBN-13: 9780495411376, by J. W. Valvano,  Cengage Learning Publisher's Website If you find any mistakes in the book, please let me know. Known errors can be found at list of textbook errors.  We have written a C programming book specific for the Metrowerks compiler and 9S12.

You can download TExaS from the documents section of Blackboard.

Equipment to buy: We are no longer giving microcontroller boards to students. I can tell you the discussions on how to maintain educational excellence in the face of repeated budget cuts has been long and careful. Every group of two students will be required to have one 9S12 board. Either the Technological Arts Adapt9S12DP512 or the Adapt9S12DG128 will suffice.  The first possibility is to buy or borrow a board from a previous EE319K/EE445L student. If you obtain a kit from a previous student, you will need the board, power supply, RS232 cable, and a protoboard. If you do buy a board from another student, I recommend you run the hardware checker to make sure the board is functional. The second possibility is to purchase a new Technological Arts Adapt9S12DG128 kit, which includes a board, power supply, serial cable, and solderless breadboard. The student cost will be $79.00 per kit. The link to pay for this kit is active. The buying process will be:
a) Once you have selected your partner for Labs 3-9, you go to the  web site and pay $79 to TechArts for the kit via PayPal. Please pay for your kit at least 7 days before the demonstration lab period. Our experience is that many credit card companies will add $1 to $3 to the transaction because TechArts is a Canadian company. Neither UT or TechArts sees this added fee. The fee is charged by the credit card company.
b) The department will get an email from TechArts that you have paid.
c) You will go to ENS234 to pickup the kit. There will be specific scheduled hours for the pickup phase, which will be around Feb 8 to 15.
d) There will be a board demonstration lab between labs 2 and 3, the week of Feb 14-18, and you should bring your board to this demonstration. Your TA will show you how to test your board to verify it is operational. If the board does not work during the testing procedure, we will replace it. Our experience with EE319K is if the board works during the initial test, almost all students complete EE319K labs without damaging the board. However, if you do damage your board, then you must purchase another one. Unfortunately we will not be using the board in EE319K in Fall 2012, so you will not have many opportunities to sell it. However, it could be useful for senior lab or other projects. There is no difference to a EE319K student between the Adapt9S12DP512 and Adapt9S12DG128 board. The DG128 board has a little less memory and is a lot less expensive. Every student should own their own voltmeter and their own wire strippers. A voltmeter less than $20 will do, see BG Micro, or Jameco  Harbor Freight has three locations around Austin and usually sells voltmeters for less than $10 Since you will be making only 5 solder joints all semester, all students will be able to share the soldering iron in lab. However, all EE319K students will need their own voltmeter and wire strippers. The NI MyDAC you bought in EE302 can be used for as the voltmeter.

Safety warnings: Due to the lead in most solder, please wash your hands after soldering, before eating or drinking. If you drop the soldering iron, let it fall to the ground. Do not try and catch it. If you are pregnant or think you might be pregnant, have someone else do the soldering.

TAs:    TAs will hold office hours in Lab: ACA 1.106. The office hours will be posted in lab. About 32 students per TA.    Email all professors and TAs (         
Peter Garatoni, 

Manan Kathuria,

Jae Hong Min

Pratyusha Nidamaluri,

Dayo Lawal

Aditya Srikanth

Kurt Fellows,

James Beecham,

Austin Blackstone,

Razik Ahmed,

Brandon Carson,

Kin Hong Mok,

Omar Baca,

Sam Oyetunji,

Zack Lalanne,

Nathan Quang Minh Thai,

Paul Fagen,

Outcomes: After the successful conclusion of EE319K students should be able to understand the basic components of a computer, write assembly and C 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. 

Reference materials: EE319K will have reading assignments from Patt's Introduction to Computing Systems (textbook for EE306 and BME303). Data sheets for most of the devices used in this class are available as pdf files on my web site. Please make sure you have access to the CPU12 instruction manual, either in print (from Freescale) or pdf form. You should download these data sheets and have them available when you are developing code
32 page CPU12 quick reference 
458 page CPU12 programming reference 
page 9S12DP512 datasheet
595 page 9S12DG128 datasheet
Tech arts board information

Short Movies describing TExaS
Web videos of the Example lessons from the book  

Prerequisites: EE306 or BME303 with a grade of at least C-.  There will be no re-tests, make-ups, or incompletes.
Teaching philosophy
I strongly encourage students to take an active role in this class.  Questions are welcome before, during and after class. Please feel free to email, visit or call me if you have questions.

Things you should recall from EE306/BME303

1.      Bits

    1. Numbers - Unsigned and Signed Integer representation in 2’s Complement
    2. True/False - Logical Operations
    3. Characters - ASCII representation

2.      Gates

    2. DeMorgan’s Laws

3.      Computer Components

    1. Central Processing Unit: Arithmetic Logic Unit and Control Unit

                                                              i.      Registers

b.      Memory – ROM and RAM

                                                              i.      Address Space and Addressability

    1. I/O

4.      LC3 Assembly Language

    1. Instruction Set (ISA)

b.      Pseudo-ops

c.       Op-codes and Operands

                                                              i.      Memory operations

                                                            ii.      Arithmetic and Logic operations

                                                          iii.      Control operations – Branches/Jumps

    1. Addressing Modes

5.      Programming

    1. Algorithms

b.      Flow-Charts

c.       Data Types

d.      Arrays

    1. Interrupts

Detailed Objectives of EE319K
0) Understanding how the computer stores and manipulates data (characters, integers, and fixed-point numbers), the basic arithmetic and logical operations performed by the computer,
1) The understanding of embedded systems (a system with the computer hidden inside) using modular design and abstraction,
2) Assembly language and C programming: considering both function and style,
3) Understanding how the computer executes instructions (fetch opcode, fetch operand, read data, operate, and write data)
4) 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.
5) Debugging and verification using a simulator and on the microcontroller (embedded systems typically do not have a print function) debugging techniques such as breakpoints, scanpoints, profiles, monitors, voltmeters, oscilloscopes, logic analyzers
6) 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,
7) The implementation of an I/O driver (a set of programs that perform input/output)
8) Understanding, from an architecture standpoint, how local variables and parameters work (e.g., a space on the stack is dynamically created, the local variable is accessed using stack-pointer relative addressing, then the space is deallocated.)
9) 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”
10) Interrupt synchronization, real-time ADC sampling (periodic timer interrupts), introduction to multithreaded programming
11) Simple motors (e.g., open and closed-loop stepper motor control)
12) Digital to analog conversion (DAC), used to make simple sounds
13) 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.
30% Laboratory assignments, due on Thursday (when performed in groups of  2, one solution turned in)

    10% 2 or 3 in class quizzes, programming practice assignments, and homework assignments   
    15% In class Exam 1, Thursday, February 23, 5-6:15pm, ENS507 (change)
    20% In lab Exam 2, Thursday, March 22, during lab period, ACA 1.106 and ACA 1.108, in regular lab
    25% Final, Thursday, May 10, 7-10pm, PAI 4.42,  regularly scheduled time and place
There will be suggested programming problems to solve, then 3 or 4 times per semester there will be a 10-minute in class quiz, where the problems will be selected from the suggested programming problems. The date of each quiz will be announced in class around 1 week in advance. The specific dates for these quizzes will not be posted in the syllabus or on blackboard. Cutoff scores for the corresponding letter grades will not be determined until after the final exam.  
Attendance: Students are expected to attend lectures. The book covers more information than the class, and we will use lectures to map our way through the book. If you miss class you may find it difficult to catch up.  

Spring 2011 Lab Schedule (labs due on Thursday, and are demonstrated to the TA)






Go to ACA 1.108 for demonstration


Lab 1

Digital Lock I/O, parallel port, direction register and logical function, written in assembly (simulated, groups of two)


Lab 2

LED and switch interface, written in assembly (simulated, groups of two)



Real board demonstration, bring your board to lab


Lab 3

LED and switch interface, written in assembly (board, groups of two)


Lab 4

Debugging Techniques, one switch, one LED, written in assembly (simulated and board, groups of two)


Lab 5 

Traffic Light Controller using the real 9S12, written in assembly (simulated and board, groups of two)



Exam 2 (closed book) in ACA 1.108 Thursday 3/22


Lab 6 

LCD device driver, decimal fixed-point output, local variables, written in assembly (simulated and board, groups of two)



Go to ACA 1.106 for Metrowerks C demonstration


Lab 7a or 7b

Digital Piano or pacemaker using a 4-bit DAC, C (simulated and board, groups of two)


Lab 8

Real-time Position Monitor, ADC, interrupts, LCD, mixture of assembly and C (simulated and board, groups of two)


Lab 9

Distributed DAS, serial port interrupts, FIFO queue, mixture of assembly and C (simulated and board, groups of four)


Lab 10

TRobots programming competition, written in C (simulated, groups of two)

 The following schedule is preliminary, please check the web for the most recent version.





Lecture Schedule

Week 1   1/17  

aLec01, aLec02, aLec03

Lec1.ppt, Lec2.ppt

Chapter 1, Appendix 1.1-1.8.2, Chapter 2 and 3

Introduction Course administration; Embedded systems, development cycle; Flow charts, data flow and call graph

TExaS  - TExaS simulator; Numbers, Hexadecimal

Week 2

aLec03, aLec04,


Lec2.ppt, Lec3.ppt

Chapter 2 and 3, (Patt, Chapters 11 and 12)

Architecture– 9S12 architecture and execution; Simple addressing modes; Memory allocation; C Programming (C Primer) - Introduction to C; Structure of a C program (Cookie Day)

I/O, Execution, stack, subroutines - Parallel ports, direction registers; Logical and shift operations; C Programming – Assignment and Boolean Expressions.

Week 3   1/31

aLec06, aLec07,



Section 4.7 and 5.7, Chapter 3 and 5

Debugging  - Debugging in TExaS

Arithmetic - Arithmetic operations; Condition code bits; C Programming – Functions

Week 4     2/7




Appendix 2, Section 2.6, Section 5.1, 5.2, 6.11

Board- Demo of the board (bring board to class);Switch input and LED output

Modular programming - If-then, loops; Subroutines parameters and the stack; Debugging dump; C Programming – Loops

Week 5




Lec6.ppt, Lec7.ppt

Section 6.1-6.3, 6.11, (Patt, Chapters 14, 16)

Pointers - Indexed addressing; Arrays; Strings

Timers  – Timers; Advanced functional debugging. C Programming – Arrays, Indexing, Pointers.

Week 6   2/21




Chapters 1 – 5

Review for Test 1:

February 23 - Test 1 (closed book), in ENS507

Week 7   2/28


aLec15, aLec16


Section 6.8, 10.1, 7.1-7.5, 9.1

FSMs  - Finite state machines (FSMs); Fixed-point numbers

Locals, parameters  - Local variables; Stack frames and parameter passing; I/O synchronization

Week 8     3/6

aLec16, aLec17


Section 7.1-7.5, 6.8

C Programming – Scope of variables in C (Local/Global); Parameter Passing: Call-by-value and Call-by-reference.

C Programming - Structures and data types; FSMs in C





Spring Break

Week 9   3/20

aLec17, aLec18


Section 8.4, 10.1, 10.5, (Patt, Chapter 17)

LCD interface - LCD programming; Number conversions; Review for Test 2

March 21 - Test 2 (closed book): In lab (during registered lab time), ACA 1.106/108
Chapter 5 and 6

Week 10  3/27

aLec19, aLec20, aLec21


Section 9.2, 9.4, 9.6, 9.10, (Patt, Chapter 17)

Interrupts  -9S12 interrupts and interrupt processing; Timer and periodic (output compare) interrupts

  C programming – Metrowerks; C/assembly interface

Week 11   4/3

aLec28, aLec29,



Section 11.2-11.3, 11.1, 11.4

DAC conversion  - Digital to analog conversion (DAC) on the 9S12; Sound generation

ADC conversion  - Analog to digital conversion (ADC) Lab 8 design methods

Week 12   4/10

aLec23, aLec24, aLec25


Section 10.2, Section 8.1

Numerical calculations - Multiplication and division; Table lookup and interpolation.

Serial I/O - Serial communications interface (SCI); SCI programming and interrupts; Lab 9 introduction

Week 13   4/17

aLec26, aLec27, aLec30


Section 12.1-12.4, 8.7, (Patt, Chapter 19, skip Sections 19.4)

Thread communication  - Producer-consumer problems; FIFO queue; C Programming - FIFO

TRobots  - Stepper motors; TRobots discussion

Week 14   4/24

aLec31, aLec32, aLec33



C structures, abstraction, software design, software testing and TRobots


Week 15    5/1

aLec34, aLec37



TRobots Competition in Class

Review for Final Exam: Chapter 1 - 13


Due Date, Monday 11pm

Homework Schedule, upload to Blackboard


Homework 1: Hand Assembly


Homework 2: Assembly Concepts


Homework 3: Signed/Unsigned numbers Arithmetic/Logic operations (Patt, Chapters 11 and 12)


Homework 4: If-then-else, Loops, and  Functions (Patt, Chapter 13 and 14)


Homework 5: Functions and Arrays (Patt, Chapters 14, 16.3)


Homework 6: Practice Exam 2s


Homework 7: Solve Exam Problem 1 in C, Pointers and testing (Patt, Chapters 15, and 16)


Homework 8: Solve Exam Problem 2 in C, Pointers and testing (Patt, Chapters 15, and 16


Homework 9: Recursion Problem, (Patt, Chapter 17)


Homework 10: Old Final Exam


Computer Usage: Computers in ACA 1.106 and 1.108 are available for your usage. TA's in the laboratory are checking off programs and supervising while on duty, thus you can expect to have only a brief consultations with them. You should learn to develop software while on the computer. This course involves some projects that require extended periods of time to complete and a project cannot be done just overnight. Get started on an assignment early so you can get help if you need it. There are not enough machine hours to give everyone more than enough time to complete each program. We expect most students to have a laptop have access to a machine to run at home. Unfortunately, expect the laboratory to be crowded and machine time to be scarce if you attempt to work in the lab a day or two before an assignment is due. You will be competing with students in other courses for computer time. We need your assistance in the laboratory. Please report any equipment problems to the TA if they are present. If a TA is not present use the form provided in the lab. If you do this we can rapidly get repair service. Please help to keep the lab clean.

Laboratory policies: See the Lab manual at

Lab Partners: See the Lab manual at Lab partners must be selected from the same lab section (registered for the same unique number).

EE319K kit handed out by TAs
and do not need to be returned
1 7406
  6 LEDs (20 mA, 2 red, 2 yellow, and 2 green LEDs)
  6 220 ohm 5%, 0.25 watt resistors
  3 push-button switches
  3 10k ohm 5%, 0.25 watt resistors
  3 1.5k ohm 5%, 0.25 watt resistors
  3 12k ohm 5%, 0.25 watt resistors
  2 feet of 4-Wire 24 gauge solid wire, used to prototyping
  1 0.1 uF ceramic bypass cap
  1 headphone jack
  1 20k ohm slide pot

Item to get from long term checkout
1 LCD display and serial cable (if you check out either of these two and do not return them by 4/29, we will reduce your overall grade in EE319K one letter grade)

Should you buy a computer? Let it be perfectly clear that the following remarks are my personal opinion, and do not reflect an official position of the department, college, or university. I feel very strongly that you should have your own computer on which you develop your software and write your reports. I think both software development and report writing should be done without paper, pencil and erasers. Having a computer at home allows you to organize your information (files, directories etc.) as well as your schedule (allocate your software development time for that the time of day during which you are most creative and energetic.) Physiologically most people are more energetic in the morning. On the other hand, there are fewer distractions late at night. Some students do all their EE319K lab work on campus, but most find it convenient to configure their home computers to work with the EE319K hardware.
Which computer should I buy? To work at home you will need to install TExaS and Metrowerks Codewarrior for the 9S12. For drawing electrical circuit diagrams some students use PCBArtist. All three of these applications run on a PC computer running Windows XP, Vista or Windows 7.  The software development systems will run on any PC with a COM port. If you do  I think the more money you invest, the happier you'll be.
TExaS The hardware/software cosimulator, called Test EXecute And Simulate, is not freeware, so please don’t post it on the net or otherwise send it to others. On the other hand, I grant EE319K students indefinite usage of the software, including installing the application on each of your personal computes. If you know of someone interested in the application have them contact me directly. It is the 14th semester we will be using the application in EE319K, but I will be make an updates to fix bugs or add features. Please work through the tutorials and examples to bring you up to speed on the various aspects of the system. Instructions for installing TExaS was emailed to students. The TExaS application itself runs on Vista/Windows7, but the help system does not run on Vista/Windows7 without a patch. Ask your TA how to get the TExaS help system to run under Vista/Windows7.
Metrowerks Codewarrior for the 9S12. The instructions to download the free (special) version can be found at  The most recent version will run on Windows 7.
PCBArtist. You will be drawing a 5 or 6 circuit diagrams as part of your lab assignments. You are free to draw these diagrams in any manner you wish as long as the information is presented in a complete and professional manner. One option for drawing circuits is PCBArtist, which can be downloaded at or The use of PCBArtist is optional for EE319K students.

Online homework submission 
Most homework will be submitted online through Blackboard. There will be approximately one homework assignment each week

There will be a signup for Lab checkout times. Each student will have a specific checkout time which will be when their lab will be demonstrated to their TA.

  • I strongly advise you work through the Tutorials in the book
  • You can only switch Lab sections using official add/drop procedures.

 TExaS is available in the documents section of Blackboard.

Legal Stuff: The 12th class day is February 1. The drop policy has recently changed. See your academic advisor or the Dean of Students for more information. Course evaluation is conducted on the last class day in accordance with the Measurement and Evaluation Center form. The final exam is at the time and place stated in the course schedule. The University of Texas at Austin provides upon request appropriate academic adjustments for qualified students with disabilities. Students with disabilities may request appropriate academic accommodations from the Division of Diversity and Community Engagement, For more information, contact Services for Students with Disabilities, 471-6259, March 28 is the last day an undergraduate student may, with the dean’s approval, withdraw from the University or drop a class except for urgent and substantiated, nonacademic reasons.
Religious Holy Days By UT Austin policy, you must notify me of your pending absence at least fourteen days prior to the date of observance of a religious holy day. If you must miss a class, an examination, a work assignment, or a project in order to observe a religious holy day, I will give you an opportunity to complete the missed work within a reasonable time after the absence.

Scholastic 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 encouraged to study together and to discuss information and concepts with other students. You can give "consulting" help to or receive "consulting" help from such students in oral form. However, this permissible cooperation should never involve one student having possession of a copy of all or part of work done by someone else, in the form of an email, an email attachment file, a portable storage device, or a hard copy. Copying of any part of a program is cheating without explicit reference to its source. We do enter lab assignments turned in by EE319K students through a plagiarism checker, comparing them to assignments of this and previous semesters. 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:
    · I strongly encourage you to study existing software.
    · All applications and libraries must be legally obtained. E.g.,
        You may use libraries that came when you bought a compiler.
        You may use software obtained from the web.
        You may copy and paste from the existing source code.
    · 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.

The University Honor Code is "The core values of the University of Texas at Austin are learning, discovery, freedom, leadership, individual opportunity, and responsibility. Each member of the University is expected to uphold these values through integrity, honesty, trust, fairness, and respect toward peers and community."

Abet material
Three lecture hours and one laboratory hour a week for one semester.  
Design Assignments: Labs 5, 8, 9 (1 week each)
Laboratory Projects: Labs 1, 2, 3, 4, 6, and 7
SCH Engineering Topics 3 (Including: 1 SCH of Engineering Design)
Relationship of the Course to ABET EC2000 Program Outcomes:


ABET EC2000 Program Outcomes


a.      An ability to apply knowledge of mathematics, science, and engineering


b.   An ability to design and conduct experiments, as well as to analyze and interpret data


c.   an ability to design a system, component, or process to meet desired needs within realistic constraints such as economic, environmental, social, political, ethical, health and safety, manufacturability, and sustainability


d.   An ability to function on multi-disciplinary teams


e.   An ability to identify, formulate, and solve engineering problems


f.    An understanding of professional and ethical responsibility


g.   An ability to communicate effectively


h.   The broad education necessary to understand the impact of engineering solutions in a global, economic, environmental, and societal context


i.    A recognition of the need for, and an ability to engage in life-long learning


j.    A knowledge of contemporary issues


k.   An ability to use the techniques, skills, and modern engineering tools necessary for engineering practice

 ABET Criterion 9:  Program Criteria for Electrical Engineering Curriculum Achieved:




 Programs must demonstrate that graduates have a knowledge of:


1.   Probability and statistics, including applications appropriate to the program name and objectives;


2.   Mathematics through differential and integral calculus, basic sciences, computer science, and engineering sciences necessary to analyze and design complex electrical and electronic devices, software, and systems containing hardware and software components, as appropriate to program objectives.


3.   (Electrical) Advanced mathematics, typically including differential equations, linear algebra, complex variables, and discrete mathematics.



 Curious about my research? See