Compilers are generally thought of as being tools that convert a high level language, like C or C++, into assembler or machine code. Of course, they do perform this function, but have the potential to do much more. Code may be generated by a compiler, or be extracted from its run-time library, which adds to the functionality of the user-written code in order to detect run-time errors and take appropriate action. This is useful in any software development context, but for embedded systems, where a fail-safe error control system is often required, this compiler functionality is essential. This paper reviews a number of the error detecting and trapping techniques that are available and discusses how these techniques are implemented in modern compilers. The availability of such functionality in embedded compilers on the market today is also reviewed.

During the last decade, embedded software’s nature in devices has changed radically. As devices have taken on increasingly more functionality, the complexity of higher level software has grown accordingly. Today’s devices employ high-performance hardware such as accelerators and multi-core architectures, which in turn, enable more sophisticated software applications to cater to growing customer demands and using hardware drivers that come out-of-the-box. This quantum leap in software complexity, combined with ever tightening development schedules, requires more advanced software development tools and a new approach to embedded software development.

In this paper, the differences between three different types simulators are examined. All three simulation approaches are viable and the decision to choose one over the other depends not only on the requirements burdened upon the software, but also on the needs embedded device manufacturers are facing today.

In today’s increasingly competitive consumer device markets, multimedia-enabled products must offer a user interface (UI) that is both visually compelling and easy to use. But changing an embedded UI can often require a lot of time and work. By taking a new approach to the UI problem as a whole, software developers can seriously reduce the amount of effort involved in making changes to a device’s interface throughout the product development life cycle, without adversely impacting time to market

The success of any consumer electronic device depends to a large extent on the appeal of the user interface (UI) and how easy the device is to use. Studies show that a good cosmetic design can encourage users to explore the full range of features and often engenders the perception that a product is easier to use. So if the benefits of great looking, easy-to-use UI are so clear, why are so many products still falling short of customer expectations?

The solution lies in taking a fresh new approach to the role the UI plays. By identifying common UI functionality and implementing it in a reusable and customizable manner, we can make it far easier for embedded engineers to deliver visually engaging and easy-to-use products.

The selection of a real-time operating system for an embedded application is always important, but, for certain applications - notably the implementation of a medical device - it is critical. This white paper considers the RTOS functionality and specification that influence the selection process, addressing performance, reliability, device usability, and compliance with standards and regulations and illustrates the benefits gained by using the Nucleus® OS approach when developing today's medical devices.

Embedded system developers are typically very skilled and knowledgeable in their field. They may be an expert in secure authentication, routing, wireless applications, etc. – whatever is needed for their application. But typically their understanding of JTAG is minimal. This is a technology that is vital for debugging and testing an embedded application. With an appreciation of how JTAG works, the number of setup details may be minimized, which leads to an easier and faster transition to the goal of designing, developing, and differentiating a product. This paper explains the issues and concepts that require a JTAG connection and how it provides much needed visibility and control of a modern processor core-based system.