Embedded Testing decompiled by Target Communication Framework
When compared with normal stand alone applications or web applications, debugging Embedded Applications are relatively tough primarily due to the inherent complexity of real time computing. There are several factors that make the embedded applications complex:
- the platform chosen specifically to optimise the target application,
- embedded application are typically selected for small tasks and
- in embedded system; memory, speed and tools are always time sensitive.
Generally, embedded applications are debugged and tested for
- logical or synchronisation problems in code,
- design error in hardware and
- information on operating states to boost performance and optimise.
For debugging and testing different tools are carefully chosen based on the target platforms. Some of the available methods / tools are:
- In-circuit emulators
- JTAG/BDM debuggers
- Customed hardware
- LEDs and switches
- Serial or other communication ports
The concern with the traditional methodologies are:
- Most embedded systems cannot host a development environment, many cannot have host debugger
- Development occurs on PCs and remote debugging is usually provided by the IDE / debugger to trouble shoot the target
- Each software development tool has its own method of communication with targets
- Communication methods conflict with each other, require individual setup, configuration and maintenance.
- Most of the embedded system communication doesn't follow same protocols
The above factors is amplified when an organisation works into automotive safety critical applications.
Thanks to TCF from eclipse, which helps teams to address this complex challenge by providing the key to unlock the aforementioned issues.
This session will provide a practical understanding of Target Communication Framework and will provide key inputs for the engineers working on real time systems.