This session reviews in detail all the facets of the make vs. buy an operating system selection decisions - both technical and commercial - for an operating system on an embedded design. Most modern embedded systems employ an operating system [OS] of some kind, and this necessitates some critical design decisions. Should you obtain a commercially available OS or develop one in-house. If the acquisition of a commercial OS is planned, how do you make the selection?

1. Selecting an Embedded OS
Colin Walls
colin_walls@mentor.com
mentor.com/embedded
Android is a trademark of Google Inc. Use of this trademark is subject to Google Permissions.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

2. Agenda
Introduction
In-house vs "Free" vs Commercial OS
OS Selection Criteria
Multicore
Conclusions
2
mentor.com/embedded

3. Introduction

Rarely no operating system
—

Need to be sure
Making the choice
—
Wide range of options
–
–
RTOS
–
"Free" OS
–
—
Linux, Windows CE etc.
In-house
Selection flowchart?
–
3
Too many parameters
mentor.com/embedded

4. Software Architecture & OS
32-bit
RTOS or full OS
16-bit
High-end, simple SW
8-bit
CPU Architecture (complexity)
Simple kernel
High-end, complex SW
Low-end, simple SW
Low-end, complex SW
(no OS)
Simple kernel
Software Architecture (complexity)
4
mentor.com/embedded

5. Introduction

Rarely no operating system
—

Need to be sure
Making the choice
—
Wide range of options
–
RTOS
–
"Free" OS
–
—
Linux, Windows CE etc.
–
?
In-house
Selection flowchart?
–
Too many parameters
?
?
?
5
mentor.com/embedded

6. 
6
To view the rest of this free presentation, including OS
selection criteria and in-house vs ―free‖ vs commercial OS,
visit Mentor Embedded.
mentor.com/embedded