
Identical features like the debug cable for Qorivva MPC5xxx/SPC5xxx (e200 cores).
|
- 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
|
 | |
|
- Full support of eTPUs
- "Step" and "Go" commands
- Supports all eTPU Breakpoints
- Disassembler for Microinstructions
- Monitor all eTPU Registers during stepping
- Modify eTPU internal Registers
- Display of Entry Points
- Peripheral View of eTPU Registers
|
 | |
Operation Modes
- 2 - 16 MDOs with 1 or 2 MSEOs
- MCKO trace clock up to 100 MHz
- Full/reduced port mode supported
- DDR Mode support
Supported Trace features
- Program trace (full branch trace and history trace messaging)
- Data trace (read / write / read+write and instruction fetch trace)
- Ownership trace messaging (e.g. for tracing task scitches)
- Watchpoint tracing (e.g. event counting, frequency measurement)
- Data aquisition messaging
- Tracing all cores of multicore processors (multicore license required)
- Data trace if additional trace clients (e.g. DMA, FlexRAY, SRAM port sniffers)
- Program/Data trace support for eTPUs and CDC
Advanced trigger sequencer
- Application examples:
- Program break on data value (for cores without DVC)
- Filtering trace messages for longer recording time
- Check time span between events, e.g. to verify max. task execution times
- Feature set:
- 4 Trigger Levels (Goto, Continue)
- Trace Control (Enable, On, Off, Break)
- 3 Counters (Enable, On, Off, Restart)
- 2 Flags (On, Off, Toggle)
- 2 Markers
- Break (Program, Trigger Bus)
- 2 Trigger Outputs
Trigger Delay
External Trigger
- Input from PODBUS
- Output to PODBUS
Performance Analyzer
|
- Allows re-debuggging of a traced program section
- Provides forward and backward debugging capabilities
- High-level language trace display including all local variables
- Timing and function nesting display
- Has the ability to fill most trace gaps caused by the limited bandwidth of trace port
|
 | |
|
- 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
|
 | |
|
- 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
|
 | |
|