VLSI Testing / VLSI Senior Project
ECEn 455/490
Winter 2001
Instructor: Prof. Doran Wilde, wilde@ee.byu.edu,
449 CB, (801)378-8749
| Class Meetings:
Mon, 3:00-3:50 PM 393 CB Tue, 12:2:50 PM 254 CB (490 Students only) Consultation:
Summary:
ECEn 490 is a 4 credit hour course to build and test an application of your VLSI chip. Prerequisites:
Text:
|
|
| Date | Subject |
|---|---|
| Jan 8 | Make Groups; Data Sheets |
| Jan 15 | (Holiday) |
| Jan 22 | Data Sheet Due; VLSI Testing |
| Jan 29 | Project Proposal Due; VLSI Testing |
| Feb 5 | Hand back Project Proposal; OSI Model |
| Feb 12 | Project Proposal Rev 2 Due; Parallel Ports (Nathan) |
| Feb 19 | (Holiday)Class held Tuesday |
| Feb 20 | FPGA Card (Spencer) |
| Feb 26 | Phase Locked Loops |
| Mar 5 | Trip to Micron, car pool, leave at 3:00, return by 6:00 |
| Mar 12 | Design Reviews; 5 min/group to present schedule & progress |
| Mar 19 | (Chips tentatively due back) |
| Mar 26 | |
| Apr 2 | Plan for Oral Reports |
| Apr 9 | |
| Apr 16 | Oral Reports |
MOSIS reports are required by MOSIS who funds your project. A one page report is not a high price for you to pay in exchange for $800 worth of services! MOSIS uses the information that it collects to create statistics for quality control.
You must submit a MOSIS report to pass the class (455 or 490).
| Grade |
|
|
|
Data sheet was turned in, and
Chip was demonstrated and works as it was designed to work, and The MOSIS report has been turned in. |
|
|
Data sheet was turned in, and
Chip was demonstrated, and worked partially, but not entirely. The cause of the problem was traced back to the design and has been described, and The MOSIS report has been turned in. |
|
|
Data sheet was turned in, and
Chip was demonstrated and worked parially, but not entirely. The cause of the problem is not known, or, Chip was totally dead and could not be demonstrated, and The MOSIS report has been turned in. |
|
|
Data sheet was not turned in, or
The chip was not tested or demonstrated, or The MOSIS report was not turned in. |
Below are some suggestions for your oral and written reports:
What should I put into my report?
You may want to include some of the following as part of your report.
These are only some suggestions. You probably won't have room to
do all of it.
- Background of what you designed. Its history, purpose, uses,
and importance. What is it? How do you use it?
- Description of your design. Functional description.
How does it work? How was the circuit broken down into functional
blocks? What are its main components? What do they do?
Are there any innovative aspects to your design? What challenges
did you have in designing your chip? Warning: Don't go into
too much detail here about your design, unless it illustrates a point.
Stay at a relatively high, functional level.
- Description of your design methodology. How did you do the
design? What tools did you use? What processes, procedures,
and methods did you use? How did you verify and validate your design?
- Description of the layout of your integrated circuit. Show
the floorplan. Why did you organize the chip in that way? What
constraints did you have to meet in laying out the chip? What technology
did you use? How many transistors are on your chip?
- Description of the test bed. Show a schematic of your test
circuitry. What does the test circuitry do? How does it demonstrate
the operation of your chip? How do you operate the test bed?
- Description of the test. How did you test your integrated circuit?
What tests did you perform? What is your test coverage? What
were the results of the test? Did you find any problems? If
so, did you figure out what caused the problem? Did you find a solution?
- Summary of your integrated circuit design experience. What
did you learn from this project? What do you consider significant
from your experience?
- Bibliography. List the sources you got your information from.
- Your data sheet should be included as an appendix.
Who is my audiance? At what level should should I describe
my project?
- Write to a technical audiance: engineers with a training similar
to yours. Explain to them what you did. with enough detail that they
understand without putting them to sleep.
- Write to yourself to be read five years from now. You will
have forgotten the details of what you have done. Tell yourself what
you did and how it worked.
This is not a great amount of time to speak. If you use transparencies, you should only prepare about 8-10 transparencies for a group of two, and 14-17 transparencies for a group of four (excluding title slide, outline, etc.) Practice your presentation and time it.
When giving your presentation, do not stand at the projector. Stand to the side of the screen, facing the audience, so everyone can see both you and the screen. If you need to point, point to the screen, not to the tranparency.
Come prepared to demonstrate your application, and have it set up and tested
before hand. It doesn't need to be the thorough demenstration that
you did to pass off your demonstration requirement for the class, just
a quick demo to impress the audiance. It should only last a few minutes.
Electrical and Computer Engineering || College of Engineering || Brigham Young University
Last Updated: Jan 2000 by Doran Wilde