Lecture 9 - Program Design

Lecture 9 - Program Design - ECE 265 – LECTURE 9 PROGRAM...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: ECE 265 – LECTURE 9 PROGRAM DESIGN 11/5/2010 1 ECE265 © Joanne E. DeGroat, OSU Lecture Overview ¡ Program Design ¡ General Overview ¡ Program Design Methodology ¡ Assembler Language ¡ Assembler Directives ¡ REF: Chapter 4 11/5/2010 2 ECE265 © Joanne E. DeGroat, OSU Program Design ¡ General Overview ¡ From the text page 89: “The design of an embedded microcontroller system requires an integrated use of hardware and software.” ¡ Hardware and software provide a natural division of the view of the system. Embedded systems require well designed interaction between these two divisions. ¡ The software design needs to follow established methodologies. 11/5/2010 ECE265 3 © Joanne E. DeGroat, OSU Software Design Methodology ¡ The software of the system is typically called a Software Program. ¡ A software program is software compiled and assembled into executable code for the target machine. ¡ Window7 is a program designed as the operating system for general purpose PCs and will run on hardware structured to support that OS. 11/5/2010 ECE265 4 © Joanne E. DeGroat, OSU Top-down design methodology ¡ A popular design methodology for software is Top-Down design and Bottom-up coding. ¡ It starts with a specification of the system at the top level. ¡ This top-level is then broken down into major tasks and subtasks. ¡ Each major task (and subtask) is broken down into smaller subtasks as appropriate. 11/5/2010 ECE265 5 © Joanne E. DeGroat, OSU Top-Down Design ¡ Graphical illustration of the Top-down design methodology. ¡ The number of levels continues until the subtask is one that can be directly coded. 11/5/2010 ECE265 6 © Joanne E. DeGroat, OSU Benefits of the top-down method ¡ Each subtask is independent of other subtasks, allowing the programmer to design, write and test each module independently. ¡ Errors can be detected and corrected in a logical manner. ¡ Mentally, the programmer only has to grasp one subtask at a time....
View Full Document

This note was uploaded on 04/01/2012 for the course ECE 265 taught by Professor N /a during the Fall '08 term at Ohio State.

Page1 / 27

Lecture 9 - Program Design - ECE 265 – LECTURE 9 PROGRAM...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online