Ctools Use Case Library
Program Counter Trace (PC Trace)

PC Trace use case APIs provide the ability to debug and profile applications in real time. Data is captured either by seperate hardware units (Embedded Trace Buffers, called as ETB) and then decoded offline or captured using external emulators (XDS560PRO or XDS560T) and decoded using CCS.

PC trace is useful to debug and profile only on a single core. There is no visibility to what is going on at the same time in the other cores. The PC trace setup can be done either via CCS or via 'C' code using the ctools use case library. This page describes the instructions for implementing PC trace features via 'C' functions. The library provides the following PC Trace use cases:

Please note: Only one PC trace use case can be implemented at any point of time. It is not possible to implement multiple PC trace use cases at the same time.

PC Trace - ETB drain via CPU during Exception or App SW fault

The following sequence needs to be executed for this use case:

PC Trace - ETB drain via CPU (capture only 4 KB of PC trace)

The following sequence needs to be executed for this use case:

PC Trace - ETB drain via EDMA (ETB extension to capture more than 4KB)

The following sequence needs to be executed for this use case:

PC Trace - No ETB drain (The emulator like XDS560T or XDS560PRO is used to export PC Trace)

The following sequence needs to be executed for this use case: