
High-speed Serial Trace Interface
Lauterbach is supporting high-speed serial trace interfaces since mid 2008.
Parallel trace data is coded 8b/10B and converted to a bit stream by the target device. This bit stream is sent via differential lanes to the TRACE32 preprocessor which recovers the original parallel data.
The max. supported speed for the serial trace interface depends on the number of data lanes.
- 6.250 Gbit/s per lane (up to three lanes)
- 3.125 Gbit/s per lane (at four lanes)
High-speed serial trace interfaces require PowerTrace III / PowerTrace II LITE as trace port analyzer.
The connection to the target is done by standardized adapters defined by manufacturer.
TRACE32 offers a comprehensive trace display and analysis.
TRACE32 offers full access to all NEXUS settings.
|
- BTM, HTM, DTM, OTM, WTM, DQM, PTCM: Selection of Trace method(s).
- TimeStamps: Enable NEXUS client generated timestamps.
- PODT, PTMARK, DTMARK: Special core trace options.
- STALL: Stall cores to prevent overflow of on-chip NEXUS message FIFO.
- Spen<message>: Enable suppression of certain trace messages depending on NEXUS message FIFO fill level.
- PortSize, PortMode: Configuration of Aurora trace port.
- RefClock: Enable reference clock source ofAurora preprocessor.
- CLIENT1/2: Enable and configure additional trace clients, e.g. DMA, FlexRay, SRAM port sniffer.
|
The basic filter and trigger features are easy to use.
|
- TraceEnable: Sample only the specified event.
- TraceData: Sample the complete program flow and the specified data event.
- TraceON: Switch the sampling to the trace buffer on after the specified event occurred.
- TraceOFF: Switch the sampling to the trace buffer off after the specified event occurred.
- TraceTrigger: Stop the sampling to the trace buffer at the specified event. A trigger delay is possible.
|
Profiling and Code Coverage
|
- Detailed analysis of function run-times
- Detailed analysis of task run-times and state
- Graphical analysis of variable values over the time
- Analysis of the time interval of a single event (e.g. Interrupt)
- Analysis of the time interval between 2 defined events
|
 | |
|
- Real-time, non-intrusive display of RTOS system resources
- Task stack coverage
- Task related breakpoints
- Task context display
- SMP support
- Task related performance measurement
- Statistic evaluation and graphic display of task run times
- Task related evaluation of function run times
- PRACTICE functions for OS data
- Easy access via RTOS specific pull-down menus
- Support for all major RTOSes
|
 | |
|
- Established part of AUTOSAR Classic timing tool chain
- Support for ORTI and ARTI
- Excellent co-operation with vendors in the AUTOSAR Classic ecosystem
- Extensive TRACE32 profiling features
- Trace export to timing verification tools
|
 | |
|
- Provides all metrics for functional safety
- For standard trace protocols TRACE32 Code Coverage gets by with no or very little instrumentation, full instrumentation as fallback
- Suitable for long-term testing
- Automated report generation in multiple exchange formats
- TRACE32 Trace-Based Code Coverage is included in the scope of delivery of all TRACE32 Debug & Trace Tools at no additional cost
|
 | |
|
- Extensive C++ Support
- Flash Programming
- Sophisticated Cache Debugging
- Full Support for MMU and MPU
- Many RTOS supported
- AUTOSAR-aware debugging
- Support for VLE (Variable Length Encoding)
- eTPU, GTM and SPT debuggers included
|
 | |
|