Presentation is loading. Please wait.

Presentation is loading. Please wait.

1. Hardware: each component on the microcontroller will need to be tested individually using multi-meters, logic analyzers, and circuit probe analysis.

Similar presentations


Presentation on theme: "1. Hardware: each component on the microcontroller will need to be tested individually using multi-meters, logic analyzers, and circuit probe analysis."— Presentation transcript:

1 1. Hardware: each component on the microcontroller will need to be tested individually using multi-meters, logic analyzers, and circuit probe analysis. Next, the components will be tested together in subsystems to ensure compatibility. 2. Software: Ensure that the new software development environment is fully compatible with the hardware system. Test and debug the developed software support libraries. 3. Laboratory Testing and Modification: Update laboratory exercises to ensure proper operation with new hardware/software implementation Metroworks: http://www.metrowerks.com Motorola: http://www.motorola.com CprE 211 Lab Manual C pr E 2 1 1 M icrocontroller E volution Microcontrollers are one of the most prevalent electronic devices in today’s technology dependent society. They can be found in a wide variety of applications from coffee makers to cameras to space shuttles. For this reason, Iowa State University’s Department of Electrical and Computer Engineering has appointed a group of students to research and experiment with new microcontroller technologies to enhance the existing hardware and software used in the Introduction to Microcontrollers (CprE 211) course. A B S T R A C T I N T R O D U C T I O N CprE 211 is a laboratory based course that introduces a variety of essential topics related to computers using the Motorola M68HC11 microcontroller. Although developed in 1978, this basic 8- bit microcontroller is still able to adequately acquaint the students with fundamental computer topics like I/O, interrupts, memory, and assembly language programming. However, as the computer industry continues to progress, so should the educational experience. It is this team’s objective to design and develop a 32-bit prototype board with software support libraries for the CprE 211 laboratories. The hardware solution will retain all of the functionality currently found in the F1-board/M68HC11 combination in addition to exploiting the new features offered by the 32-bit microcontroller. The software development environment will also be enhanced to include a completely integrated visual compiler and debugger. T E a M : D e c 0 1 – 0 4 B U D G E T C L I E N T S / A D V I S O R S R E F E R E N C E S D E S I G N R E Q U I R E M E N T S Design Objectives Interface hardware components with 32-bit microcontroller Design PCB with functionality extended beyond F1-board Write hardware support and interface libraries in C Test compiler, hardware, software compatibility Ensure that the current CprE 211 laboratory projects work with the new hardware implementation Functional Requirements Digital output one: LCD with a minimum of a 2x20 screen Digital output two: 8-16 pin multi-functional output Digital input one: minimum of an 8-bit DIP switch Digital input two: minimum of a 5x8 keypad Analog input: minimum of a one-turn potentiometer Microcontroller: 32-bit, RISC architecture PCB: integrates hardware components M I L E S T O N E S D E S I G N C O N S T R A I N T S E N D – P R O D U C T D E S I G N The 32-bit microcontroller will require a new robust and easy to use software compiler A one month window is necessary to submit/process printed circuit board designs Hardware vendors must be able to support their products for at least five years T E C H N I C A L A P P R O A C H T E S T I N G A P P R O A C H 1.Durability: hardware will be exposed to a high level of use from a variety of students. 2.Reliability: under adverse conditions hardware is expected to last 5-7 years. Hardware and compiler vendor should supply adequate support for replacement products. 3.Ease of use: the software compiler and debugger should provide a straightforward method of use for sophomore level CprE/EE students. 1.Acquisition or creation of prototype board with 32-bit microcontroller 2.Purchase and test robust software development tools 3.Develop and test software C libraries for hardware 4.Upgrade/modify one full semester of CprE 211 laboratory projects 5.Develop designer and end-user documentation A S S U M P T I O N S Figure 1: F1-board / M68HC11 combination currently used in CprE211 Figure 2: End-product design diagram 1. Identify necessary hardware components. Purchase microcontroller and software development package 2. Design prototype board using CAD software. Construct high level software design. 3a. Assemble and test prototype board. Print silicon PCB layout 3b. Develop and test software support libraries in C and assembly language 4. Integrate and test hardware and software. Update CprE 211 laboratory projects. 5. Develop documentation. Present solution to clients. Figure 3: Technical approach diagram Jon Froehlichjonf@iastate.eduCprE295 hrs Brad Hottinger hotti@iastate.eduCprE305 hrs Derek Millerdlmiller@iastate.ed u CprE305 hrs Dan Murrdmurr@iastate.eduCprE280 hrs Total EffortTotal Cost 1185 hours$600.00 Dr. Arun SomaniNicholas Professor Dr. Manimaran Govindarasu Assistant Professor Aaron StriegelGraduate Student CprE 211 Instructor


Download ppt "1. Hardware: each component on the microcontroller will need to be tested individually using multi-meters, logic analyzers, and circuit probe analysis."

Similar presentations


Ads by Google