The IRMA Community
Newsletters
Research IRM
Click a keyword to search titles using our InfoSci-OnDemand powered search:
|
Framework-Based Debugging for Embedded Systems
|
|
Author(s): Gokhan Tanyeri (Clarinox Technologies Pty Ltd, Australia), Trish Messiter (Clarinox Technologies Pty Ltd, Australia)and Paul Beckett (RMIT University, Australia)
Copyright: 2014
Pages: 31
Source title:
Handbook of Research on Embedded Systems Design
Source Author(s)/Editor(s): Alessandra Bagnato (Softeam R&D, France), Leandro Soares Indrusiak (University of York, UK), Imran Rafiq Quadri (Softeam R&D, France)and Matteo Rossi (Politecnico di Milano, Italy)
DOI: 10.4018/978-1-4666-6194-3.ch018
Purchase
|
Abstract
Debugging embedded systems is almost guaranteed to cause headaches. Embedded systems, and especially portable embedded systems, are becoming increasingly complex and have unique constraints that make them hard to debug. Traditional static debugging tools provided by the embedded development tool chains are important but are only part of the story. Time-dependant issues cannot be debugged by such tools. Embedded environments have to provide efficient mechanisms for managing a range of issues such as thread interaction, control of timers, semaphores and mutexes, IPC message passing, event handling, and finite-state machine organizations. This chapter looks at issues of escalating complexity in modern heterogeneous embedded systems and their impact on debugging techniques and advocates a framework approach to manage this complexity. Using the ClarinoxSoftFrame® Suite framework as an illustrative example, this chapter describes how a modular and open approach to debugging can aid the rapid development of robust wireless-enabled embedded systems that employ a variety of operating systems and platforms. The overall objective in this type of approach is to leverage prebuilt code infrastructure plus existing development skills as much as possible, thereby avoiding the need for engineering staff to learn and re-learn a range of compilers, operating systems, and the like. Overall, debug time can be greatly reduced by improved visibility into the complex interactions between cooperating processes within the code. Collateral benefits can include a reduction in the size of the necessary development team with a reduction in skills specialization.
Related Content
|
Subrata Tikadar, Kaushik Paul, Abhishek Mukhopadhyay.
© 2026.
26 pages.
|
|
Devanshi Shrivastava, Debanshi Chakraborty, Manjusha Pandey, Siddharth Swarup Rautray.
© 2026.
32 pages.
|
|
Harshita Gupta, Suman Suman Majumder.
© 2026.
12 pages.
|
|
Subhajit Ghosh.
© 2026.
38 pages.
|
|
Sanjib Kundu, Sourav Kayal.
© 2026.
40 pages.
|
|
Sudip Chatterjee, Pronaya Bhattacharya, Subrata Tikadar.
© 2026.
14 pages.
|
|
Chandan Kumar Singh.
© 2026.
40 pages.
|
|
|