Refreshing Embedded Software

Now that we understand that software is "out there" for long periods of time, we need to confront the problem of how to refresh it. This is a particularly perplexing problem for embedded software. In the remainder of this chapter, I address the pesky problem of upgrading software in a certain class of device: those that are handheld, mobile, wireless, and fairly lightweight. In this class, we find cell phones, personal organizers, GPS receivers, digital cameras, and various combinations thereof. They all have embedded software, some programmable memory, and batteries. They may or may not communicate with other devices.

This class of device is increasingly important, and its members are proliferating, for at least two reasons. In the first place, every product that is designed for personal portability tends to get smaller over time; and as the benefits of their functions (for instance, the transferability of digital photographs) become widely understood in the marketplace, their decreasing size makes them more attractive as well. In the second place, we are constantly seeking ways to free ourselves from detestable tethers. Wireless communication does that nicely because there's no landline to fuss with, and batteries do away with the other tether, the power cord.

My notion is that upgrading software for these devices should be made as simple as possible. The proposed solution is speculative, but I believe it merits further discussion.