29 lines
1.4 KiB
TeX
29 lines
1.4 KiB
TeX
|
\chapter*{Abstract}
|
||
|
|
|
||
|
|
Embedded real-time multi-core systems must adhere to strict timing requirements
|
||
|
|
in order to guarantee correct execution. Timing requirements are specified to
|
||
|
|
document system execution paths that are safety critical with respect to the
|
||
|
|
timing behavior of an application.
|
||
|
|
|
||
|
|
Via tracing it is possible to validate the fulfillment of timing requirements
|
||
|
|
in the native environment of a microcontroller. However, trace tools produce a
|
||
|
|
trace on hardware or software level, whereas requirements are specified on
|
||
|
|
system level. A transformation of the former to the latter is required to
|
||
|
|
close this gap.
|
||
|
|
|
||
|
|
Additionally, not all trace techniques are capable of producing results
|
||
|
|
suitable for the real-time analysis of embedded applications. Most techniques
|
||
|
|
are not sufficient for one or several reasons: limited trace duration,
|
||
|
|
inadequate number of recordable objects, and limited timing accuracy.
|
||
|
|
|
||
|
|
Therefore, this thesis examines different trace techniques and shows why
|
||
|
|
hardware tracing is the most sufficient for real-time analysis. Next, the
|
||
|
|
coherence between hardware, software, and system level entities is examined.
|
||
|
|
Based on the results a mapping from software level to system level is
|
||
|
|
introduced and validated.
|
||
|
|
|
||
|
|
The thesis concludes that it is possible to record cycle accurate system traces
|
||
|
|
of arbitrary length via hardware tracing. However, this requires detailed
|
||
|
|
knowledge about hardware tracing and the operating system underlying an
|
||
|
|
application.
|