TimingProfiler helps you identify application parts that cause unsatisfactory execution times. It delivers results as soon as there is compiled code, and thus can be used very early in the development process, when measurements on physical hardware are costly or plain impossible.
This makes TimingProfiler ideally suited for constantly monitoring timing behavior during software development and in model-based development environments.
Call graph with timing information
Usage of variables
TimingProfiler has been specifically developed to apply static-analysis techniques at early development stages, providing quick feedback about the timing behavior. It takes executable code as input and explores the timing of all potential execution paths of each task on a generic processor with the target instruction set, e.g. PowerPC.
The goal is not to give precise worst-case guarantees, but to enable development of applications in a timing-conscious way without cumbersome measurements on physical hardware. In fact, the analysis is applicable when no hardware is available yet, or the application is not mature enough for measurements.
No user interaction is required; information not statically available is filled in by specialized heuristics. Hence, the resulting execution time is a realistic worst-case scenario, albeit not a guarantee as provided by aiT.
TimingProfiler is currently available for ARM, LEON2, LEON3, PowerPC, TriCore (incl. AURIX), and V850/RH850. Preliminary versions are available for over a dozen more processor families. Support for more processors still is underway.
TimingProfiler is also available as an integral part of the SCADE Suite, the market-leading mission and safety-critical embedded software development environment from Esterel. Within the Suite, the tool is called Timing and Stack Optimizer.
We also offer a plugin for automatic integration of TimingProfiler in Jenkins, the leading open-source automation server.
Request your free trial package today.