Circuit-Level Modeling, Design, and Optimization for
Digital Systems
Course: ESE370
Units: 1.0 CU
Terms: Fall
Next Offered: Fall 2011
When: MWF 12-1pm
Where: Towne 315
Instructor: DeHon (office Hour: T4:30pm-5:30pm)
TA: Andrew Townley (seas: atownley)
(office hours W1-2pm in Ketterer, R2-3pm in Ketterer)
Prerequisite: ESE170/171, ESE205/215 (roundup of what you should know from ESE215)
URL: <http://www.seas.upenn.edu/~ese370/>
Quick Links:
[Course Objectives]
[Grading]
[Policies]
[Fall
2010 Calendar]
[Reading]
Catalog Level Description:
Circuit-level design and modeling of
gates, storage, and interconnect. Emphasis on understanding physical
aspects which drive energy, delay, area, and noise in digital
circuits. Impact of physical effects on design and achievable performance.
Role and Objectives
The goal of this course is to teach students what they need to know about
the physical aspects (area, delay, energy, noise) of electronic circuits to
support high-speed, low-energy, area-efficient design of robust digital and
computer systems.
Students will learn:
- disciplines for robust digital logic and signaling
(e.g., restoration, clocking, handshaking)
- where delay, energy, area, and noise arises in gates, memory, and
interconnect
- how to model these physical effects both for back-of-the-envelope
design (e.g. RC and Elmore delay) and detailed simulation (e.g., SPICE)
- the nature of tradeoffs in optimization
- how to design and optimize logic, memory, and interconnect structures
at the gate, transistor, and wire level
- how technology scales and its impact on digital circuits and computer
systems
This course comes after a basic introduction to devices and circuits
(ESE205/215) and a course on gate-level digital design (ESE170/171). It
should serve both students who will go on to do circuit-level design and
those who will work primarily at higher levels and need to be able to
reason about technology and fundamental limits to establish capabilities
and understand the circuit-level impact of optimizations they perform
at higher levels of design. This will be the most detailed class on
physical issues required for CMPE BSE students. Students may choose to
continue with more advanced circuit and VLSI courses (e.g., ESE570).
Rough Syllabus (by weeks)
- Review transistor, introduce MOS model
- Gates and restoration, basic gate delay, review transient response
- MOS Transistors (models with physical device parameters
(W,L,Na...)), scaling, variation
- Energy, Delay, Area implications and tradeoffs for MOS circuits
- Clocking, latches, flip-flops (setup, hold, clock skew)
- Other gate models (ratioed, pre/post-charge)
- RC Wire delay and Elmore delay (fanout, transistor sizing)
- Wire Effects (buffering, capacitive coupling/crosstalk)
- RAM design
- Noise: inductive coupling, ground bounce, ionizing particles,
thermal noise
- Transmission lines
- High speed chip-to-chip signaling
- Energy and entropy
See Fall
2010 course calendar for day-by-day calendar with assignments.
Text
- Jan M. Rabaey, Anantha Chandrakasan, and Borivoje Nikolic. Digital Integrated Circuits, A Design Perspective, 2nd edition, Prentice
Hall, 2003.
- Errata for text
Grading
Grading is based on weekly assignments and a longer end-of-term assignment.
- Weekly Assignments [25%]
- Projects [45%]
- Midterm [10%]
- Final [20%]
Projects: Three two-week design/optimization projects: (1)
transistor design and optimization for logic/gates, (2) memory design,
(3) high-speed chip-to-chip or cross-chip signaling.
Policies
Homework Turnin
Writeups must be done in electronic form and submitted through Blackboard
(below). Use CAD or drawing tools where appropriate. Use electric where
required. Handwritten assignments and hand-drawn figures are not
acceptable.
All labs will be turned in electronically through the Penn Blackboard
website. Once logged in, select ESE370 under My Courses, go to Assignments
and click on the assignment you want to submit. Attach all files and click
submit (unless specified otherwise in the assignment, a single file with
your solution is preferred). All file names should have your SEAS login
followed by the assignment
(e.g. bfranklin-hw1.pdf).
Note that some browsers (notable Google's Chrome) are not currently working
with Blackboard. One symptom is that Blackboard will tell you the file
format is invalid when you try to upload. If this happens to you, please
try a different browser. As far as we know Firefox works.
Late Assignments
Assignments must be turned in by the published due date to receive full
credit. We deduct 10% of the assignment grade for each day late.
For Project 3 we deduct 20% of the assignment grade for each day late and
will not accept it at all after the exam.
If assignments or exams fall due on a religious holiday, please make arrangements
with the instructor to accommodate before the posted due date.
A written note from the academic dean or medical doctor will be
required to gain consideration for extenuating circumstances.
Credit Adjustment
Make sure you call any problems with grading to your TA's attention
immediately and not later than the next class meeting after they are
returned
or posted on blackboard. Our TA will be responsible for adjudicating these
problems---the instructors will only be involved as a possible court of last
appeal in case there is some truly difficult decision to make (i.e., in
most cases, we will not be willing to second guess the TA's decisions). To
submit a request to the TA for a review of a credit assignment on a lab
assignment send an email to the TA stating the nature of the problem and
the remedy you desire. We have instructed the TAs not to
consider any requests for grade adjustments that are submitted later than
the one week grace period after the grades are posted on blackboard. You
are responsible for checking your posted grades in a timely manner.
Collaboration
You may help each other understand how to use the CETS computers and course
CAD tools.
Each student is expected to do his/her own work -- including developing the
details, drawing circuits, performing simulations, and writing the
solutions. For the homeworks and projects, you are free to
discuss basic strategies and approaches with your fellow classmates or
others, but detail designs, implementations, analysis, and writeups should
always be the work of the individual. If you get advice or insights from
others that influenced your work in any way, please acknowledge this in
your writeups.
In general, you are expected to abide by Penn's
Code of Academic Integrity. If there is any uncertainty, please ask.
André DeHon