Embedded Linux System Design and Development

Posted by Anonymous 0 komentar
The industrial revolution appears as a knife-edge change from a rural selfemployed lifestyle to a clock-punching, whistle-blowing corporate urban way of life. Being in the middle of the current revolution makes it hard to realize that in fifty years most people will consider the messy, dynamic, no-rules embedded product development environment of today as an obvious clean transition caused by technological changes.

The first embedded software project I worked on didn’t use an off-theshelf operating system—there was none. It wasn’t until several years later that WindRiver introduced VxWorks®. In the mid-1990s it appeared that nothing could unseat VxWorks; yet, recently WindRiver announced a Linux-based product. Why the change? Today the most common embedded operating system used in new products is Linux.

For fourteen years I was part of a small army of firmware engineers working on the development of HP LaserJet™ printers. The printer used a homegrown operating system that as I recall was called LaserJet O.S. Usually the very best engineers worked on supporting and extending the operating system. Any LaserJet O.S. documentation that existed, engineers had created. Any test suite was similarly a burden placed on the engineer’s shoulders. The effort and expense of these highly talented engineers seldom led to any features that differentiated the product from the competitors. The most important lesson I learned from the experience was to always put your most talented engineers on the features that make your product unique and outsource the infrastructure. Embedded Linux is often the best choice for the operating system infrastructure for products needing nontrivial connectivity. Download free Embedded Linux System Design and Development.pdf here

0 komentar:

Post a Comment