ESE 519: Real–Time & Embedded Systems

University of Pennsylvania


  • L2 due on October 3

  • Venue for lectures: 401B - Active Learning Center, 3401 Walnut St (Above CVS and Starbucks)

  • Sign up for Piazza for discussions and real-time announcements


Lecture: Tuesdays & Thursdays, 12 - 1:20 pm @ 401B Active Learning Center, 3401 Walnut St
Lab: Detkin Lab is reserved on Fridays 4 - 7 pm
There will be 24x7 access to Detkin Lab except during other reservations. Please check Detkin calendar.
Click here
to request for PennCard access to Detkin Lab.

About the course

The course will span a variety of topics ranging from microcontroller basics, computer architecture through the eyes of an embedded developer, peripherals interfacing and device drivers, real-time concepts like scheduling, concurrency, synchronization and real-time controls. There will be intensive hands-on lab assignments that will complement the lectures.


Programming in C/C++, ESE 350 or equivalent and senior or graduate standing. Prior hands-on experience with operating systems and circuits is beneficial.


There will be six lab assignments and two mid-term exams.

  • Lab assignments: 60%

  • Mid-terms: 40%

Lab assignments will be performed in groups of two. Late submissions are not permitted and there are no grace periods. However, the rule may be relaxed for only one of the assignments and you may submit any one of the assignments any time before the late lab deadline with 15% penalty. If you opt to do so, make sure you notify the teaching assistants before the assignment due date and receive an acknowledgement for the same. It is highly advised that you do not push your responsibilities that far as the pressure only increases during finals week.

Integrity Policy

It is expected that the students taking the course have the integrity not to cheat. Finding or trying to find solutions online only defeats the purpose of learning. University's policies on cheating will be strictly enforced and violators will be punished according to university regulations as determined by the Office of Student Conduct. If one student shares code with another on a different team, both the donor and the recipient are in violation of the integrity policy.

Computer Failures

Computer failures (e.g. server failures, network failures, power outages, etc.) are a fact of life. Plan your project to be able to cope with this degree of uncertainty. Short failures will be considered to be part of the normal course of events. In the case of catastrophic failures (which last more than 12 hours), notify your teaching assistants.