Thursday, February 23rd, 2012

EB tresos Debug & Trace

AUTOSAR debugging at runtime

Integrating and configuring AUTOSAR basic software is a complex task. The AUTOSAR standard defines more than 50 basic software modules with more than 6000 configuration parameters. Practical experience has shown that an error-free module configuration is not enough and that configuration tools are not able to detect every type of error. Conflicts regarding the runtime behavior surface only in the integration phase. EB tresos Debug & Trace helps you to detect problems during early stages of integration and allows you to debug and trace an AUTOSAR stack, the EB tresos AutoCore, during runtime.

Benefits

Provides you with a quick overview of the system status

Allows you to identify problems without requiring detailed AUTOSAR module expertise

Makes comparing measured data with design and configuration data easy

Real-time debugging and tracing without having to stop your ECU

Features

Debug and trace an AUTOSAR software stack’s (EB tresos AutoCore) behavior during runtime

Transmit the debug and trace data via standardized bus interfaces (CAN, FlexRay, Ethernet)

Transmit the debug and trace data via a Lauterbach debugger interface (for example JTAG or Nexus)

Buffer the debug and trace data in the ECU memory

Switch the tracing of specific data on and off during runtime

Define online triggers in your ECU

Trace runtime environment (RTE) signals

Trace operating system (OS) tasks

Trace the development error tracer (DET)

Export debug and trace data to a csv-file for further analysis in third party tools

Features beyond the AUTOSAR standard

Generic function tracing (extension to the AUTOSAR specification)

Generic state machine tracing (extension to the AUTOSAR specification)