February 2016
31
T
ools
& S
oftware
HyperText Markup Language (HTML) is used
as the standard output format. The formatting
can easily, and without too much effort, be
adapted to customer-specific requirements
via a style sheet.
Availability of the debugger functionality via
a general-purpose software interface is a pre-
condition for the automated method already
described. With PLS Universal Debug Engine
(UDE), Microsoft Component Object Model
(COM) is used here as the basic technology.
COM has established itself over a long period
of time as the de facto standard in the Win-
dows world. Even Windows itself provides a
large share of its newly added functions via
COM interfaces. The object model of the UDE
includes nearly all functions of the debug-
ger such as flash programming, run-control,
reading and writing of target memory in
symbolic form, trace data capture and analy-
sis, and much more. One great advantage of a
COM-based application programming inter-
face (API) is that it can be used by a very large
number of various languages. This includes C,
C++, C# and other .NET languages together
with scripting languages such as JavaScript,
Python, Perl and VB Script or Windows own
PowerShell, because they can all handle COM
components. Table 1 shows a general descrip-
tion of the UDE API on the basis of interface
description language (IDL) and their use with
various languages.
The functionality of the debugger can be used
in three different ways. Firstly, scripts can be
executed within the graphical user interface.
At the same time, a link with menu points or
toolbar buttons is possible for quick access. In
addition, the built-in script debugger supports
testing with line-by-line processing, variable
display and the possibility to set breakpoints.
The second possibility of using the debugger
functionality is user-specific windows that
can be added to the user interface. At the
same time, the appearance is defined with the
description language HTML; the complete
COM-based API can be accessed for the dis-
play logic. Finally, the debugger can also be
started, configured and controlled completely
externally. Thus, access for third-party pro-
vider tools is ensured. A good example of this
is the availability of an application written in
PERL, which provides almost all functional-
ity of the Universal Debug Engine (UDE) in a
command shell and can be a very useful tem-
plate for own test scripts.
n
Figure 1. Extract from an HTML-based code coverage report
Figure 2. The object model of the UDE includes nearly all functions of the debugger.
Table 1. Use of a method of the UDE object model in various languages
Embedded World
News
Hall-Stand 4-432
LDRA extends TÜV certifi-
cation of compliance tools
LDRA has been awarded TÜV certifica-
tion for all major safety-critical standards,
further securing LDRA’s leadership in the
software compliance and certification space.
The TÜV certificate assures LDRA custom-
ers and partners that the LDRA tools fulfil
the requirements for support tools and are
qualified to be used in safety-related soft-
ware development. This TÜV certification
confirms LDRA’s compliance to indus-
trial safety (IEC 61508), automotive (ISO
26262), and rail transportation (EN 50128)
for LDRAunit, LDRAcover, and LDRArules
and adds compliance for medical devices
(IEC 62304) and nuclear (IEC 60880) for
these LDRA products as well as the LDRA
tool suite.
