embedded design lifecycle n.
Download
Skip this Video
Download Presentation
Embedded Design Lifecycle

Loading in 2 Seconds...

play fullscreen
1 / 13

Embedded Design Lifecycle - PowerPoint PPT Presentation


  • 79 Views
  • Uploaded on

Embedded Design Lifecycle. Seven Phases. Product Specification Partition Design into Hardware/Software Iteratively refine Partitioning of Hardware/Software components Independent hardware and software design Usually in parallel Hardware and software integration Product Testing & Release

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Embedded Design Lifecycle' - keith-cherry


Download Now An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
seven phases
Seven Phases
  • Product Specification
  • Partition Design into Hardware/Software
  • Iteratively refine Partitioning of Hardware/Software components
  • Independent hardware and software design

Usually in parallel

  • Hardware and software integration
  • Product Testing & Release
  • Maintenance & Upgrades

Instructor: G. Rudolph, Summer 2006

focus in this course
Focus in this course
  • Software Design
  • Software/Hardware integration at the application level
  • We use the light sensor, but we don’t focus on how to build one

Instructor: G. Rudolph, Summer 2006

it s alive or is it
It’s Alive!!…or IS IT?
  • Design Correct Hardware the first time through
    • No dead wires, problems
  • Design perfect, bug-free software the first time
  • Throw it all together, and it works!

Instructor: G. Rudolph, Summer 2006

why not
Why Not?
  • Complex behavior only analyzable as it occurs
  • Accurate simulations aren’t worth the effort
  • Modeling tools continue to improve

Instructor: G. Rudolph, Summer 2006

before we get into software
Before we get into Software…
  • Selecting a microprocessor
  • The JSTamp microntroller vs the RCX
    • http://graphics.stanford.edu/~kekoa/rcx/#Overview
    • http://jstamp.systronix.com/Resource/jstamp_datasheet.pdf

Instructor: G. Rudolph, Summer 2006

selecting a microprocessor
Selecting a Microprocessor
  • Embedded Systems usually task-specific
  • Designs can be highly optimized
  • You want “the right” CPU for the job
  • Final selection must pass 5 critical tests

Instructor: G. Rudolph, Summer 2006

five tests
Five Tests
  • Available in a suitable implementation
  • Capable of sufficient performance
  • Supported by a suitable OS
  • Supported by adequate tools
  • Non-technical issues

Instructor: G. Rudolph, Summer 2006

suitable implementation
Suitable Implementation
  • Cost
    • Off-the-shelf-parts
    • highly integrated
  • High Performance
    • Specialized gates
    • Specialized circuits

Instructor: G. Rudolph, Summer 2006

sufficient performance
“Sufficient” Performance
  • Difficult to quantify as things get more complex
  • Has less to do with computational power
  • More to do with
    • Hardware architecture vs.
    • the more demanding tasks

Instructor: G. Rudolph, Summer 2006

suitable rtos
Suitable RTOS
  • You might prefer one OS over another
  • Porting is not an easy task
  • Hardware issues
  • Software issues

Instructor: G. Rudolph, Summer 2006

adequate tools
Adequate Tools
  • Critical to success
  • Specific toolset often depends on the nature of the task
  • Minimum Needs
    • Good cross-compiler
    • Good debugging support
  • Often have
    • Host-based tools, IDEs
    • Specialized tools such as an ICE

Instructor: G. Rudolph, Summer 2006

other issues
Other Issues
  • Prior commitment to a processor family
  • Prior restrictions on languages
  • Prior experience of team members
  • Time-to-market factors

Instructor: G. Rudolph, Summer 2006

ad