CE121L - Microprocessor System Design
General Laboratory Information

Laboratory Project

In the 121L laboratory sessions, you will build a Motorola HC11 microprocessor system. The basic system will include the HC11, FLASH EEPROM (electronically-erasable programmable read-only memory), RAM (random access memory), RS-232C drivers and receivers (a communication standard), and a DAC (digital to analog converter). The HC11 microcontroller chip includes a serial port (for use with the RS-232C drivers), many parallel ports (great for debugging - just hook up a few LEDs with resistors from the vending machines), a timer, and an ADC.

After building this basic system, the last weeks of the course will be devoted to building a digital synthesizer. Sample wave forms will be stored in the RAM and read out at varying rates to produce notes. Each group will write programs for sampling and sending out these waveforms through the DAC to an audio amplifier and speaker. The synthesizer will be playable from the lab PC's keyboard. A complete specification of this product will be distributed latter, as well as a list of enhancements that you may wish to consider.

All labs must be demonstrated to the TA before the start of the next lab. The final project will include an informal demonstration to the TA, instructor, and class, to be scheduled latter. In addition to the scheduled lab periods, you will be able to use AS104 whenever you want using its combination lock.

Evaluation for 121L will be based on lab performance and lab notebook (40%), lab final (40%), and final project report (20%).

Laboratory Notebooks

You must each get a bound graph-paper notebook in which to record your lab procedures, observations, and results. The lab notebook will help you recall thoughts from previous weeks and be invaluable in the preparation of lab reports. At the start of each lab, the previous lab's writeup will be evaluated by the TA. You will be able to use your lab notebook during the lab section of the final as well. In the corporate world, lab notebooks enable others to carry on your work, document that you have been doing your job, and can be critical in patent litigation.

For each lab session, include as appropriate: the date, title and object of work, diagrams of circuits and equipment setups, listings of parts and equipment used, explanation of procedures, records of observations taken and resulting data, analysis of data, and thoughts, ideas, and conclusions that occur during or after the session. Your first action on entering lab should be to open the notebook and date the first empty page.

You lab notebook must at all times contain a neat and up-to-date wiring diagram -- do not expect any assistance from me, the TA, or the lab tutors without such a diagram.

Also:

1. Number the pages and provide a table of contents.
2. Only the right-hand pages count. Use the left-hand pages for scribbles, doodles, and the like. Exception: inserts (e.g., lab instructions, program listings, and data sheets) may be affixed to left-hand pages if desired. Note that data recording does not fall in this category -- data, such as that in the temperature lab, should be recorded directly onto a right-hand page.
3. Work must be in pen. Do not ``white-out'' or scribble over mistakes. Instead, put a single horizontal line through the incorrect text, or a single diagonal line through a diagram or page. When appropriate, write in an explanation of the mistake. Being able to review past mistakes is an important feature of a lab notebook, especially when they may turn out not to be mistakes.

Preparation for the labs is required. Initial prelab may be on left-hand pages, but final designs must be copied to the right before the start of the lab. The TA will check your prelab at the start of the lab session.

In the past, several students have received lower-than-expected lab grades for not completing prelabs or maintaining a good laboratory notebook, which forms 40% of the 121L grading

Laboratory Reports

For the initial labs, your lab notebooks will be used in lieu of lab reports.

The final project will include a formal report. The report should have an overview product description, a user's guide, and a technical description (8-12 pages). Block diagrams will be part of the technical description but wiring diagrams and code, unless particularly relevant to the discussion, should be relegated to the appendices. The report should be suitable for publication as a technical report or for requesting the go-ahead from management to build your product.

The final report will be due on March 17th.

If a piece of equipment does not work, immediately tell the TA.