Debugging For Embedded Systems
In contrast to the general purpose computer software design environment, a primary characteristic of embedded environments is the sheer number of different platforms available to the developers (CPU architectures, vendors, operating systems and their variants). Embedded systems are, by definition, not general-purpose designs: they are typically developed for a single task (or small range of tasks), and the platform is chosen specifically to optimize that application. Not only does this fact make life tough for embedded system developers, it also makes debugging and testing of these systems harder as well, since different debugging tools are needed in different platforms.er.pdf |title= Plug-in Based Debugging For Embedded Systems |publisher=clarinox |accessdate=2010-09-15 }}
- to identify and fix bugs in the system (e.g. logical or synchronization problems in the code, or a design error in the hardware);
- to collect information about the operating states of the system that may then be used to analyze the system: to find ways to boost its performance or to optimize other important characteristics (e.g. energy consumption, reliability, real-time response etc.).
Read more about this topic: Debugging
Famous quotes containing the words embedded and/or systems:
“The idea of feminine authority is so deeply embedded in the human subconscious that even after all these centuries of father-right the young child instinctively regards the mother as the supreme authority. He looks upon the father as equal with himself, equally subject to the woman’s rule. Children have to be taught to love, honor, and respect the father.”
—Elizabeth Gould Davis (b. 1910)
“Our little systems have their day;
They have their day and cease to be:
They are but broken lights of thee,
And thou, O Lord, art more than they.”
—Alfred Tennyson (1809–1892)