ECE 6110 - Microprocessor Systems - Spring 2009

Dragon12 Special-Purpose System 2009

Revision History:

• 2/06/09 Official release
• 3/20/09 Delayed Progress Report 2 and Final Report at student request.
• 4/08/09 Delayed Final Report at student request.

Table of Contents

• Summary
• Schedule
• Requirements and Constraints
• Project Specs Report
• Progress Report 1
• Progress Report 2 and Demo
• Final Report and Demo
• Related Documents

Summary

Design and construct (if necessary) a special-purpose hardware/software system based on the Dragon12 microcomputer board.

Schedule

Requirements and Constraints

• General Rules
  • Students work in teams of two.
  • Grade = Degree of project functionality + quality of documentation at each stage.
  • 5 points per day late will be deducted after due dates.
  • Submit printed copy of each Report.
  • Submit all documentation and code to your ClassDrop folder at \\athena.pclab.tntech.edu\classdrops\ECE\ECE6110-Haggard\your-teamname\report-title\.
  • It may be written in C or assembly code. Use logical, organized program structure, including subroutines. Use good comments.
  • It may use all available library code.
  • It must work correctly and reliably.
  • It must run in EVB mode with D-Bug12 monitor, thus must fit in 11KB ram plus 3KB of EEPROM for code and constant data. Nothing special is required to assemble and load your assembly language code/data into EEPROM, other than using ORG to set the start address in the EEPROM range (0400 - 0FFF). The EEPROM cannot be used with the C compiler.

• Required Tasks
  • Each team must propose and develop a unique project that will utilize ALL of the I/O devices on the Dragon12 board.
  • You must use the I/O devices for a useful, meaningful, integrated purpose. These include specifically: keypad, DIP switches, LEDs, pushbuttons, analog potentiometer, 7-segment digits, LCD, infrared transceiver (source and sensor), audio speaker, and serial port to PC (for program download, execution, and text/numeric entry/display).
  • It should be creative and interesting. It may be fun or serious in nature.
  • It must be more interesting and more complex than the textbook examples and homework.
  • You must also use the HCS12 internal timer subsystem.
  • You must use interrupt-driven I/O wherever possible to allow multi-tasking and the multi-tasking must be obvious to the user.
  • The program should run continuously.
  • It must be user friendly in every way.
  • Detect and report all possible error conditions and recover from them gracefully.
  • Evaluate your system in terms of accuracy, speed, and limitations. Explain all the sources of error.
  • You must NOT damage the Dragon12 board, or you may have to pay for its replacement.

• Optional (extra credit)
  • A pair of Dragon12 boards may be used together with some form of inter-board communication.
  • Additional hardware devices may be interconnected to the Dragon12 board. You may borrow or purchase these devices.
  • You may use any other HCS12 subsystems, such as the communication ports.

Project Specifications Report

The project specs report should contain the following, in this order. The report must be all typed and computer-drawn; no hand-written material is allowed.

• Title page
• Table of contents
• Project Goals. What are the overall objectives of this project?
• Overview of functions and features that will be implemented. What can it do?
• Detailed operation manual for the user. Exactly how does the user activate, utilize, and interpret all the functions and features? What can the user do at each point in time and what results are expected? Give a clear step-by-step description.
• Mechanical system drawings of anything that will be built or used beyond the  basic Dragon12 board and PC

Progress Report 1

The first progress report should contain the following, in this order. The report must be all typed and computer-drawn.

• Title page
• Table of contents
• Project Specifications (revision 1): Goals, Features, Operation Manual, Drawings
• First draft description of system hardware/software operation details, beyond the Specifications. For example, describe any extra hardware added; describe multi-tasking, timer, interrupts, and other major subsystem operations.
• First draft of software pseudocode, following our documentation standards.
• Work completed and tasks remaining.

Progress Report 2 and Demo

The second progress report should contain the following, in this order. The report must be all typed and computer-drawn.

• Title page
• Table of contents
• Project Specifications (revision 2): Goals, Features, Operation Manual, Drawings
• Second draft description of system hardware/software operation details.
• Second draft of software pseudocode.
• Work completed and tasks remaining.
• Version 1 of C source code and/or HCS12 assembly code listings, following all our documentation standards. At least half of the specs should be operational at this point.

Demonstrate partial system operation to the professor.

Final Report and Demo

The final report should contain the following, in this order. The report must be all typed and computer-drawn.

• Title page
• Table of contents
• Final Project Specifications: Goals, Features, Operation Manual, Drawings
• Final Description of system hardware/software operation details
• Final software pseudocode.
• Evaluation, Results, and Conclusions
• Final C source code and/or HCS12 assembly code listing, following all our documentation standards. The project should be fully operational per the specs at this point.

Demonstrate complete system operation to the professor.

Related Documents

• TBD

Home • Course Information • HW Assignments • References • Project • Old Tests • Student Pictures • Table of Contents