Hunting and gathering embedded systems resources -

Hunting and gathering embedded systems resources

At least one bird species uses a twig to dig insects out of holes in trees. Some primates open hard shells with branches used as clubs. The Attini ant is quite literally a farmer, cultivating patches of fungus and exchanging fungi species with other ant colonies. Clearly Homo sapiens is not the only species that uses tools to manipulate the environment. Four billion years of evolution has produced creatures whose fitness for their place in an ecological niche must be augmented by using and building things.

Tools are surely one of the defining marks of our species. In 10,000 years, we've gone from the wheel to the microprocessor, each invention a means to improve our lot in life.

We engineers are today's inventors, the creators of many of the products that improve and change the life of billions of our fellow Earth-dwellers. Most of the planet's population must now be aware of the microprocessor; surely billions of lives have been touched by embedded products in one form or another. Just last week, I talked with a company building tiny 5 kW microprocessor-controlled generators for use in the smallest villages in Nepal. Spacecraft beam TV and other communications products to all but the most remote African communities. Cheap datacomm is propelling Third World nations into the global exchange of trade and lifting some from abject poverty. Remoteness no longer isolates societies from the computer age.

In our rush to build products, we forget to look on the impact of our creations. Do you make routers? That project might seem to be just a very sophisticated way of shoving packets around, but in fact it's much more. As a primary component of the Internet, it quite literally puts food in hungry bellies. Save the Children ( and a hundred other aid groups solicit donations online and help current and potential donors see in near real time how a few dollars quite literally saves lives.

Your company's webcam lets distant grandparents connect with their descendants, the numerically controlled milling machine reduces the cost of all sort of consumer products, a DVD player substitutes a tiny hunk of plastic for hundreds of feet of videotape built from the most toxic of chemicals. The amount of good done by our products far exceeds what we imagine, especially when we're caught up in the drama and frustration of getting the silly thing to market on schedule.

And yet there are only a half-million of us producing these smart products. A mere handful of engineers whose impact has been quite profound. Perhaps this has always been true of the engineering profession. When Roebling designed the Brooklyn Bridge, cars didn't exist; could he have dreamed of the vast numbers of people who would use his concrete and steel edifice to earn a living, feed their children, and pay the mortgage? Could De Lesseps foresee the vast impact of his Suez Canal? Did Jack Kilby and Robert Noyce anticipate how integrating a few transistors onto a single chip meant devices could be smart, energy requirements reduced, emissions curtailed, and, of course, good jobs created for the 500,000 of us?

We're an odd and almost invisible breed. Mention computer and the average person thinks of a PC. Yet of the six billion processors made every year, only 250 million go to the desktop market. The rest are for embedded systems. Tell your neighbor you're a computer designer, and he'll immediately target you forever for answers about his problems with spreadsheet macros and sporadic system crashes. Embedded? Hey, is that why my car goes 100,000 miles between tune-ups? Ah, my new refrigerator uses half the energy of the older one . . . you mean there's a computer in there that manages temperature control, cuts my expensive electrical bill, and so helps me send the kids through college?

Resource hunters
We embedded systems folks include quite a disparate range of people, with skill sets that range widely. In the early days of the business, all developers were EEs, who both designed the hardware and wrote all of the code. Most worked in isolation; few projects required more than a couple of people. The high cost of memory at the time had a self-limiting effect on program size: 4 kbytes of code could easily be written by a single engineer in very little time.

Moore's Law drove, and continues to drive, the price of transistors practically to zero, so the limits to program size have largely disappeared. Systems with over a million lines of code are not uncommon today. This technological change has created a corresponding one in us; now more and more developers have little to do with the hardware. Quite a few EEs leave college and embark in careers in firmware.

Computer engineers, who have less exposure to the intricacies of electronic design, and pure computer scientists both bring more of a software-centric focus to projects. Although embedded systems are the last place where hardware and software intertwine to form a unified whole, there's quite a gulf between the people developing each component. The circuit design of systems in many cases is becoming more complex despite an ever-increasing suite of tools and off-the-shelf chips. In many cases, hardware engineering now looks a lot like software development as the EEs struggle with VHDL equations and even SystemC code that compiles to a hardware description language.

But one characteristic that both disciplines combine is a continuous search for new tools to accelerate development, new ideas, time-saving products, and canned solutions to common problems. Wise developers are resource hunters.

Engineering is the art of solving problems, not producing products. Products result from our problem-solving. Engineering doesn't demand we invent everything. The most efficient engineers are those who seek out and use solutions that already exist, saving their employers money and speeding the product to market.

In print
Many EEs get a dozen magazines a month, most free, all containing valuable information. No one can consistently, month after month, read all that material, so the typical engineer flips through the publications, perhaps noting an article or two of interest to read later. The ads get as much attention as editorial content. “Hey, check out this cool DSP from TI!” Although you may not need that today, you're building a wetware database, a file in your brain that's every bit as useful and important as the most extensive link site on the 'net. A year later, when a colleague asks about available DSPs, you may respond, “Gee, I dunno, but something makes me think TI does this. Check them out.”

Even as far back as 1890, The Electrical Engineer was a weekly publication engineers read to stay on top of the latest technology. Obviously, the headlines didn't scream about cool new FPGAs; “breaking news” back then included exciting coverage of new forms of wire insulation. But for 100+ years, there's been an EE tradition of keeping up, noting resources, and finding useful commercial products.

This tradition is much less common in the software world, particularly for firmware. After all, this is a very new business. The one publication targeted specifically at the industry–Embedded Systems Design –is but two decades old. Its subscribers include only 10% of the engineers working in the field, so clearly a lot of people aren't tuned into new developments.

It's our responsibility to keep up and to pursue new sources of information as aggressively as we build products. This publication and its online version are the world's most complete collection of embedded systems resources extant, both in the ads and in the editorial. Need an RTOS? A compiler? An embedded Cobol compiler? Keil ran an ad in these pages for just that product a couple of years ago. On April Fools Day.

Once engineers strove to acquire and save all relevant knowledge. In fact, a system called the “EEM File” helped catalog the data in file cabinets. This is no longer possible due to the sheer proliferation of information and the move to electronic repositories. But plenty of other venues, in print and online, exist.

It's hard to remember life before Google. Maybe it's the old fart in me, but I feel Internet searches have one huge problem: they lack serendipity. Put a magazine in my hands, and I have to flip through the pages, looking for interesting stuff. Paging through an initially uninteresting article, maybe an odd graph claims one's attention, revealing a pretty intriguing facet of the field never previously considered.

Then there are the ads. BigDogFirmware just went from their usual quarter-pager to a full color, full page spread? They must be doing well; maybe their product is worth a little deeper examination. Only by reading the ads can we keep up with commercial product offerings that may help or even save a future project.

Magazines are a push technology; they place unexpected contents in your hands. The Internet is much more a pull venue that delivers exactly what you're looking for. That's incredibly useful but terribly narrow. I was recently building a control circuit and found a number of useful high-power drive chips online. None quite fit my application. Then a friend sent a scan of an old article that gave me a canned solution.

Yet print publishing has been in decline for a number of years. Even newspapers, a cultural part of the landscape for centuries, struggle in the face of electronic competition. That's a shame. Regardless, there are still a lot of valuable print resources for embedded systems developers, which I've covered before (see my 2005 Breakpoints column “The Fourth Estate,”


Although I prefer a hardcopy magazine over an e-version, there are a lot of fabulous resources on the 'net for developers who wish to stay connected to this field. I'm thankful to Dave Kellogg for finding many of them. He's a big believer in using podcasts while driving and exercising for self-improvement. Here are some recommended podcasts and webinars:

Agile Toolkit–

Developer Works (IBM)–

Manager Tools (highly recommended)–

Lean Enterprise Institute–

IEEE Spectrum Radio Online–

Software Quality Engineering–

Agile Project Management– http://community.feature

IT Measurement and Productivity Institute–

Although there are a number of embedded blogs, these two seem the most interesting and are regularly updated:

Embedded Gurus, a collection of blogs from Mike Barr, Niall Murphy, Larry Mittag, and others–

Atomic Object–

USENET and other groups continue to provide useful forums for us. Some of the better ones include:

Lean Software Development– /leandevelopment

Lean Software Development and Scrum–

Agile Embedded–



As professionals we have a responsibility to both our employers and our careers to be on top of the latest thinking about embedded systems and the latest resources that are available. We have to be like doctors, who spend more than a little time reading professional journals to stay current. After all, stasis is death.

Jack Ganssle () is a lecturer and consultant specializing in embedded systems' development issues. For more information about Jack .

1 thought on “Hunting and gathering embedded systems resources

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.