ECSE-4260 PHYSICAL DESIGN IN MICROELECTRONICS

RENSSELAER POLYTECHNIC INSTITUTE

SPRING 2003

Course Hours

Project Time & TA Consultation: M 4:00 pm–5:20 pm Rm: JEC-3332Team Meetings (~1/2-hr time slot): Th 4:00 pm–5:20 pm Rm: JEC-3332

Instructor

Name: Professor Y.L. Le Coz Email: lecozy@rpi.eduOffice: CII-6225Office Hours: M 2pm–3:50pm

Secretary: Melissa ReardonEmail: reardm@rpi.eduOffice: JEC-6049Telephone: x-6313

Course Texts and Software

Title: Inside SPICEAuthor: R.M. Kielkowski (required).

Title: B2 Spice Author: Beige-Bag Software (required, see Instructor before buying).

Title: PSPICE: A TutorialAuthor: L.H. Fenical (Library Reserve).

Title: Musical Applications of MicroprocessorsAuthor: H. Chamberlin (Library Reserve).

Title: Principals of Digital AudioAuthor: K.C. Pohlmann (Library Reserve).

Title: Analog-Digital Conversion HandbookAuthor: D.H. Sheingold, Ed. (Library Reserve).

Title: Tanner Tools L-EDIT

1

Author: Tanner Research, Inc. (optional, for those who own and used it fromECSE-4220 VLSI Design)

Course Library

A collection of relevant Course reference materials, including copies of Course texts listed above, additional primary references, and copies of previous student Proposals, Mid-Term Reports, and Final Reports. This collection is kept under Folsom Library Re-serve, ECSE-4260, Le Coz. (Please be aware that these books are my personal posses-sions, so I would like you to handle them carefully.)

Course Information

Catalog Description:The conversion of circuit schematics to IC chip layouts. Emphasis is on integrated cir-cuits, device design, and the electrical performance of interconnected devices. Projects will involve the use of CAD software for process simulation, electrical analysis, physical placement, and interconnect routing. This is designated as a writing-intensive course. Prerequisites: ECSE-2050 or ECSE-2060, and ECSE-2610. Corequisite: ECSE-2210 and ENGR-4010; ECSE-4220 recommended. Spring term annually. 3 credit hours.

Reference:Four or five introductory lectures covering possible design projects. Lecture notes and project-related handouts. In addition, possibly, a custom reference library (under Folsom Class Reserve).

Goals:The Course goal is to provide practical design experience in microelectronics. Familiarity is gained using a variety of popular CAD tools in the context of a semester-long project design. The ability to convey technical results by means of writing and oral presentation is also stressed. Students are required to furnish three written documents (Proposal, a Mid-Term Report, and a Final Report) and to deliver regular oral presentations.

Prerequisites by Topic: Basic computer skill, circuit modeling.

Topics:Project topics vary year to year depending on individual student interest. General project topics involve MOS device design and determination of SPICE models; MOS circuit lay-out, characterization, circuit extraction, and simulation; interconnect modeling, lumped and distributed interconnect-parasitic extraction, and geometry- and material-dependent (L, W, t, , ) parametric studies; standard-cell implementation of CMOS SSI/MSI cir-cuits; placement and routing, timing, ERC, and DRC of digital ICs. Past projects, to name a few, have included IC implementations of an 8-bit comparator design, a pseudo-random sequence generator, an amusement-park ride controller, IC op-amp design, FPGA design, design of night-vision monocular, simulation of an analog computer, design of a digital-

2

audio system, and design of a high-speed random-walk processor element. Projects have also included algorithmic development of a floating random-walk method, circuit extrac-tion and modeling of multi-layer IC interconnects, and process and device simulation of a high-performance bipolar-junction transistor.

Software & Computer Usage:Students can use the CAD tools PISCES, MEDICI, SPICE, Parade, Magic, QuickCAP, Lazar, Mt Ida, B2 Logic, SUPREM, L-EDIT, Tcl/Tk, and Logic Works to perform their de-signs. These tools operate on IBM PC, Macintosh, RS/6000, VAX, and SUN platforms. In recent years, we have emphasized the Tanner Tools and Cadence IC-design suites, de-pending on the student’s previous experience, and availability.

Grading Percentages:Individual Proposal (10%) = 10%Mid-Term Report (20%), Oral Presentation (5%), Contribution to Team (5%) = 30%Final Report (40%), Oral Presentation (5%), Contribution to Team (5%) = 50%Laboratory Notebook = 10%

Team Size: 3–8 students, preferred.

Note: The Individual Proposal is an individual effort among those who plan on forming a Team. You will then use your Proposal as a basis to coordinate efforts for your Project and subsequent Mid-Term Report, which includes a Team Proposal. Mid-Term Report, Final Report, and Oral Presentations are team efforts, and should be presented and sub-mitted that way appropriately. There is an individual component, however, in your Mid-Term and Final Reports and Presentations, designated “Contribution to Team”.

General Project Description

The electronic synthesis of music presents a broad technical challenge to the integrated-circuit designer. This project entails the design of a high-quality digital-to-analog music-synthesis system. The project breaks down into several components, or electronic “sub-blocks”, which each have to be designed and interfaced to form the “whole”. The basic sub-blocks consist of a parallel FIFO buffer connected to computer mass-storage device, a high-resolution DAC (digital-to-analog converter), a deglitcher and slew eliminator, a sharp low-pass filter, and a stable clock oscillator with digitally programmable frequency. Students are expected to work in teams to design, simulate, and assess. For those students who have used Cadence™ software tools in previous courses; layout, physical placement, and routing of chip circuitry are allowed options. Sub-block teams are also expected to provide each other valuable input and output interface specifications. This permits “com-partmentalization” for simultaneous sub-block design among all teams in the course. Stu-dents, as well, are expected to perform preliminary mathematical calculations to achieve understanding before using design software. This design project is term-long and open-ended. Every student must have a minimum previous-course experience with Logic-

3

Works™ (or an equivalent Boolean simulator) and SPICE™. Students are, in addition, expected to have satisfied listed prerequisites and co-requisites cited in the official RPI Catalog Course Description for ECSE-4260.

4

Policy on Academic Integrity

The design projects are to be performed by the specific group members only. The Instruc-tor defines student groups at the start of the course. The Individual Proposal is to be pre-pared as an individual effort only. Mid-Term and Final Reports and Oral Presentations are to be prepared by the group members only. Copying or paraphrasing previous Propos-als or Reports, or having someone else outside your group directly contribute to the project is not permitted. (Refer to the Rensselaer Handbook regarding Academic Dishon-esty. Written material from sources outside the group (for example, excerpted text) must be properly referenced (author, source, and so forth). See the Instructor before submitting your documents should you have questions concerning proper citation. No grading penalty will be ascribed to those who work in groups relative to those who work alone. You are, nevertheless, required to write the other group-member names on your com-pleted Reports and Oral Presentations. Excuses given for late reports or conflicts with due dates should be truthful. The best chance of having an excuse accepted is the truth. The truth will draw the most “sympathy” from the course Instructor—as honesty has a high value here at Rensselaer.

5

Individual Proposal Format

Cover-Page Memo: To:, From:, Re!, Date:; handwritten initials next to From:; no bot-tom signature. Give name and student number. Keep it short—just a few sentences, maybe a paragraph, at most. Tell me exactly what you are handing in along with any nec-essary comments. Please use the “plain”, “simple”, or “neutral” Memo format available in Microsoft Word’s Project Gallery.

Proposal: 3–4 pages maximum. 10–12pt text; 1in left/right margins; 0.5in top/bottom margins; 1-1/2 spaces/line. Includes a Project Title Page, Introduction or Background, Proposed Work, Professional and Ethical Issues, and Schedule. Compose a Proposal that has a professional narrative feel (check with the Writing Center on this!). (Look at the “Mid-Term Team-Proposal Guidelines” for additional ideas; however, you will not be required to use that exact format until your Mid-Term Report.)

Introduction or Background: As an option, you may describe the nature of your engineer-ing design company/service. Otherwise, keep a strict generic, professional tone. No first-person singular! Go over details presented to you in class or any library/internet re-search. Give a quick overview of proposed semester work. About 1/2 page.

Title Page: Include your tentative project title, Course number, your name, and student number. Center on a single page, and use 16pt font, bold.

Proposed Work: Explain your project goals and objectives. Go over any plans for project teaming and coordination. List out your proposed CAD tools. Think about hard-copy de-sign results to be furnished (plots, graphs, tables, etc.). Also discuss technical specifica-tions and criteria for your design. Point out any key references, including Internet, books, people (profs., students, and so forth), or anything else. About 1 page.

Professional and Ethical Issues:You must in your Proposal indicate how you will incorporate realistic ENGINEERING STANDARDS and REALISTIC CONSTRAINTS that include one or more considera-tions of economics, environment, sustainability, manufacturing, ethics, health and safety, and social and political impact. About 1/2 page.

For example, in this section in your Proposal you could describe a task like researching federal regulations, industry (IEEE) standards, environmental considerations in the choice of fabrication process, patents, and so forth—as related to your Project. You are encouraged to devise other meaningful tasks that address the Professional and Ethical Is-sues above.

Schedule: A list of weekly activities for the remainder of the term. Use a simple Microsoft Table format. The list should describe specific weekly goals. Try not to make the list too aggressive. On the other hand, have something reasonable to do EVERY

6

week. 1 page. Differentiate, as best as possible, between individual and probable team ac-tivities in your Schedule.

Due-Date Draft Version: The DRAFT Individual Proposal is due Th, 1/23, at the be-ginning of your Team meeting. The draft must be passed through the RPI Writing Cen-ter (Sage) and returned with a stamp of approval. (Electronic submission to the Writing Center is ok; just include a copy of the email header as your “stamp”.) You do not need to make all the suggested changes for the draft. The draft will not be handed in; I will just look at it during our Team meeting.

Due Date Final Version: The FINAL Individual Proposal is Th, 1/30, at the beginning of your Team meeting. Make all necessary changes. Include Writing Center suggestions from the draft, if you deem reasonable. (You do NOT have to see the Writing Center again for the final version.) Hand in FINAL and previous DRAFT versions at the same time together. Make a copy of EVERYTHING, BEFORE handing in, for your records!

7

Mid-Term Report Format

Cover-Page Memo: To:, From:, Re:, Date:; handwritten initials next to From:; no bottom signature. Give names and student numbers of ALL the people in your Team. Keep the Memo short, and use the Microsoft Gallery Memo Template, as before. Furnish just a few sentences, maybe a paragraph, at most. Tell me exactly what you are handing in along with any nec-essary comments. No need for specific Report details, at this point.

Team Proposal:Follow, exactly, the “Team Proposal Guidelines”. This second Proposal is, essentially, an integrated version of your individual Proposals submitted earlier, now that you have been working together as a team for a while. Changes from and updates to your initial “plan” are permitted. 3–4 pages, maximum. This part is separate in page count from the Update described below.

Update: Approximately 2 + 2(N – 1) pages word-processed, where N is the number of people in your Team. Times or Times New Roman font; 1-1/2 line spacing; 10–12pt text; 1in left/right margins; 0.5in top/bottom margins. PLUS, put in the Appendix (see below) addi-tional plots, figures, tables, references, and so forth. The Appendix is NOT part of the of-ficial page count. One page per figure, plot, etc. Equations, if any, can go into the normal Update body. There should be at least six basic parts in the Update: Project Title with usual Team member information, Work Completed, Work Remaining, Professional and Ethical Issues, and Individual Team-Member Contribution, Appendix. Additional sec-tions can be generated, as necessary. Compose a Report that has a professional narra-tive feel (check with the Writing Center on this!). What follows, are the specific components of the Update.

Work Completed: Go over your accomplishments. Furnish technical detail and discussion. Mention your CAD tools. Refer to figures, plots, and tables in the Appendix. Also discuss TECHNI-CAL SPECIFICATIONS and PERFORMANCE CRITERIA for your design. Point out any key references, including Internet, books, people (profs., students, etc.), or anything else. Again, do not forget to cite figs, plots, and tables, from your Appendix in the normal Report body.

Work Remaining: Review your PROJECT GOALS and OBJECTIVES. Go over any plans for project team-ing and coordination. List out your proposed CAD tools for the remainder of the term. Think about hard-copy design results to be furnished (plots, graphs, tables, etc.). Also discuss TECHNICAL SPECIFICATIONS and PERFORMANCE CRITERIA for what remains in your design. Point out any key references, including Internet, books, people (profs., students, etc.), or anything else, that might be used as you complete the project.

8

Individual Team-Member Contributions:Please include, as well, short paragraph summaries—one for EACH Team Member—de-scribing his or her contributions since start of semester. Each Member is responsible for writing his or her own summary here. Each summary paragraph should have the Team Member Name clearly identified at the beginning. All the paragraphs should read well, and all possess the same formatted style. (You are free to edit each other’s contributions here, including feedback from the Writing Center; however, each individual is personally responsible for the ultimate content and truthfulness of their paragraph.

Appendix: Include figures, tables, sketches, and plots. Use one page per item. Include also a list of References. You should use a numerical ID when citing the References in the normal Re-port body. Since this is a Mid-Term Report, you are permitted to submit draft-quality ma-terial in the Appendix. For example, plots and tables can be hand-drawn (neatly). Hard-copy print outs can be written on, directly. (For the Final Report, due at the end of term, you will need to “professionalize” the Appendix material.)

Due-Date Draft: The DRAFT Mid-Term Report is due Th, 3/6. The draft must be passed through the RPI Writing Center (Sage) and returned with a stamp of approval (or electronic header). You do not need to make the suggested changes for the draft; use your own judgment. The draft will not be handed in; I will just look at it during our meeting.

Due-Date Final Version: The FINAL Mid-Term Report is due Th, 3/20 at 4pm. (If your Team meeting time is later than 4pm, you must still appear at 4pm.) Make all necessary changes. Include Writing Center suggestions, if you deem them reasonable. (You do not have to see the Writing Center again for this version.) Hand in FINAL and previous DRAFT versions with Cover Memo, in the usual format, on top, draft on bottom. Hand everything in at the same time, all together. Make a copy of EVERYTHING BEFORE handing in, for your records! You will need this material as a basis for the Final Report.

Mid-Term Oral Presentation:Each person within a Team must present for 5 minutes, please follow the “Guidelines for Oral Presentations”. Make sure to include, Project Title, Schematics or Layouts, and Simulation Results (plot), and any additional material listed in the “Guidelines” docu-ment. Strict time keeping will be applied, so practice your talks for efficiency and effec-tiveness! The entire Class will meet for these presentations, and constructive feedback from the entire Class will be encouraged. Oral presentations and final version of the Mid-Term Report are due at the same time! A hard copy submission of the oral pre-sentation is required!

9

Final Report Format

Cover-Page Memo: To:, From:, Re:, Date:; handwritten initials next to From:; no bottom signature. Give names and student numbers of ALL the people in your Team. Keep the Memo short, and use the Microsoft Gallery Memo Template, as before. Furnish just a few sentences, maybe a paragraph, at most. Tell me exactly what you are handing in along with any nec-essary comments. No need for specific Report details, at this point.

Front Matter: Follow “Final Report Guidelines”, exactly.

Final Report: Follow “Final Report Guidelines”, exactly. 7 + 2.5(N – 1) pages word-processed (10–12pt, max. 1-1/2 spaced lines, Times or Times New Roman font), where N is the number of people in your Team. See “Guidelines” about margins, and so forth. Main figures, equations, and tables in the Report should be handled as described in the “Guidelines”. Remember to cite all “borrowed” materials correctly (equations, figures, plots, excerpts, tables, and so forth); see “Guidelines”. Do not use “first person singular”. Avoid the use of personal names, except in the Project Contributions section. Compose a Report that has a professional narrative feel (check with the Writing Center on this!).

Back Matter: Follow “Final Report Guidelines”, exactly. Make sure to include a list of references and an appendix. Put in the appendix any additional plots, figures, tables that you consider supplementary to your Report. (That is, those things that you wish to include for com-pleteness, but which are not presented in detail in your Report body. Check with the In-structor if you are confused on this matter.) The appendix is NOT part of the official page count. Since this is a Final Report, you MUST include “decent-quality” material in the re-port body and appendix. For example, plots and tables should be computer generated. Hard-copy print outs can be NEATLY written on, if necessary. Make sure the Final Re-port has a “professional” feel, both in the body and in the Appendix. Consult with the Writing Center!

Due-Date Final Report: The Final Report is due Tu, 4/29, at 4pm. (If your Team meeting time is later than 4pm, you must still appear at 4pm.) There is no draft submission required. You must submit a draft, though, through the RPI Writing Center (Sage); a stamp or email-header certification is required. Don’t forget the Cover Memo on top of your Final Report. Make a copy of EVERYTHING, BEFORE handing in, for your records!

Final Oral Presentation:Each person within a Team must present for 5 minutes, please follow the “Guidelines for Oral Presentations”. Make sure to include, as well, Project Title, Schematics or

10

Layouts, and Simulation Results (plot). Strict time keeping will be applied, so practice your talks for efficiency and effectiveness! The entire Class will meet for these presenta-tions, and constructive feedback from the entire Class will be encouraged. Oral presen-tations and final version of the Final Report are due at the same time! A hard copy submission of the oral presentation is required!

11

Student Team Information Sheet (Print Clearly!)

TEAM NAME:

Name Phone Email

12

Student Team Self-Rating Sheet, MID-TERM (Print Clearly!)

Please rate, confidentially, your Team Members’ contributions. This includes work per-formed, punctuality and contribution during team meetings, Mid-Term Report prepara-tion, and other relevant factors. Reduce all of this to a single letter grade, with an appro-priate + or –, if necessary. BE ABSOLUTELY FAIR, HONEST, AND IMPARTIAL. ALSO, DON’T FORGET TO RATE YOURSELF!

TEAM NAME:

Stu- dent Team Self-Rat- ing Sheet, FI-NAL (Print

Clearly!)

Name Rating(A+ through F)

(self)

13

Please rate, confidentially, your Team Member’s contributions. This includes work per-formed, punctuality and contribution during team meetings, Mid-Term Report prepara-tion, and other relevant factors. Reduce all of this to a single letter grade, with an appro-priate + or –, if necessary. BE ABSOLUTELY FAIR, HONEST, AND IMPARTIAL. ALSO, DON’T FORGET TO RATE YOURSELF!

TEAM NAME:

Name Rating(A+ through F)

(self)

14