This chapter explains TriCore specific configuration for Trace including Templates, Aurora Trace Port, Profiler and Coverage analysis. For general analyzer information refer to general Analyzer chapter.

 

Trace

Per default, TriCore target processors don’t provide trace functionality, which is often necessary during the development and test process. As an alternative, Infineon offers a dedicated pin compatible Emulation Device (ED), which features Nexus compliant on-chip trace (MCDS) in conjunction with the standard OCDS debug module, which is controlled by the external tool through the JTAG or DAP debug interface.

 

Emulation device can feature either:

•Aurora trace port, where Nexus trace information is pushed immediately off-chip to the external debug tool

•On-Chip Trace Buffer, where Nexus trace information is stored in a dedicated trace buffer until it’s full and then read through debug interface and uploaded to the PC for further analysis.

 

Devices may support one or both of these two trace technologies. Availability depends on the specific TriCore ED.

 

 

Operation mode

Before using trace for the first time please refer to the Analyzer chapter to learn more about trace technologies and possibilities. A selection between trace Analyzer Operation modes is done in the CPU Options dialog. Refer to Analyzer Configuration for more information.

 

 

Trace Configuration

Configuration windows may differ slightly from the screenshots presented in the following chapters, as different TriCore devices provide different functionalities. Record with Default Trace Configuration.

 

 

More resources: