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:
“It was your severed image that grew sweeter,
That floated, wing-stiff, focused in the sun
Along uncertainty and gales of shame
Blown out before I slept. Now you are one
I dare not think alive: only a name
That chimes occasionally, as a belief
Long since embedded in the static past.”
—Philip Larkin (1922–1986)
“Before anything else, we need a new age of Enlightenment. Our present political systems must relinquish their claims on truth, justice and freedom and have to replace them with the search for truth, justice, freedom and reason.”
—Friedrich Dürrenmatt (1921–1990)