Home ›

Introduction: a Typical Embedded System

Issue 188

From Issue #188
December 2009

Dec 01, 2009  By Johan Thelin
 in
It's not always clear what separates ordinary Linux from embedded Linux. This article takes a look at the parts that make up a typical embedded system, starting with the bootloader and ending with end-user applications.

Resources

Crosstool: www.kegel.com/crosstool

Das U-Boot: www.denx.de/wiki/U-Boot

RedBoot: www.sourceware.org/redboot

uClibc: www.uclibc.org

newlib: www.sourceware.org/newlib

dietlibc: www.fefe.de/dietlibc

Buildroot: buildroot.uclibc.org

Ångström Distribution: www.angstrom-distribution.org

ScratchBox: www.scratchbox.org

BusyBox: www.busybox.net

Boa: www.boa.org

Qt: qt.nokia.com

GTK+: www.gtk.org

Johan Thelin has worked with software development since 1995 and Qt since 2000. Having seen server-side enterprise software, desktop applications and Web solutions, he now works as a consultant focusing on embedded systems. He can be contacted at johan@thelins.se.

______________________

Johan Thelin is a consultant working with Qt, embedded and free software. On-line, he is known as e8johan.

White Paper
More Resources
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
More Resources
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions