Components and Packages Targets

Architecture Overview 15 The process is more automated for evaluation boards supported by eCos, whereas using your own hardware requires more involvement to determine what packages are to be loaded and the value of configuration option settings.

1.3.1.6 Templates

A template is a partial configuration that gives us a valid starting point. Templates are a combi- nation of a hardware target and a group of packages. The group of packages is given a name, as shown in Table 1.2, to describe the functionality included. eCos comes with a small number of default templates. When a new configuration is created, a template is used as a starting point to match the general needs of the application. Configuration options can then be fine-tuned to meet more specific requirements you have. The configuration tools show the specific packages included in the template. Table 1.2 eCos Templates Template Name Description All Provides all packages for a particular hardware target. Cygmon Includes packages necessary to build eCos with Cygmon. Cygmon_No_Kernel Incorporates packages for building Cygmon without eCos kernel support. Default Contains the infrastructure, kernel, C and math libraries, plus necessary support packages. Elix Provides packages for supporting ELIX compatibility. Kernel Includes the HAL, infrastructure, and eCos kernel packages. Minimal Incorporates the HAL and infrastructure packages only. Net Contains necessary support packages for using the OpenBSD networking stack. New_Net Provides support packages for using the FreeBSD networking stack. Posix Provides HAL, infrastructure, eCos kernel, and POSIX packages. RedBoot Used for building the RedBoot ROM monitor image. 16 Chapter 1 • An Introduction to the eCos World

1.4 Summary

This chapter gave us a brief background of eCos and the company behind it. We looked at the compile-time or source-level configuration eCos uses and the advantages it brings to embedded applications. Next, we examined the different mailing lists available for getting support with eCos. Finally, we went through the eCos terminology used in this book and eCos documentation, which gives us a baseline of the elements that compose the eCos system. We are now ready to take an in-depth look at the eCos system, the software components available, and how we use eCos. Stubs Includes packages necessary to build eCos GDB stubs. Uitron Provides full level S standard compliance with version 3.02 of the µITRON standard, plus many level-E extended features. Table 1.2 eCos Templates Continued