NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.
Common Platform Tracer Examples
Introduction[edit]
The Common Platform Tracer (CPT) provides slave bus profiling, event logging and debug support for the Keystone family of devices. For details on CP Tracer capabilities and device specific information see CP Tracer Details. For instructions and downloads see the examples below.
Requirements[edit]
- CCSv5.1.x Installed
- CP Tracers are provided with Keystone devices that include the following:
- TMS320C667x
- TMS320TCI6616
- TMS320TCI6614/2
- TMS320C6657
- CP Tracer Data is exported via the System Trace Module (STM). STM data can be collected with:
- On-chip ETB using any XDS to configure or cTools Libraries for embedded application support.
- Pin export to an XDS560v2 or in the case of Keystone EVMs, the Blackhawk XDS560v2 Mezzanine Emulator.
- For pin export the target card requires a TI 20-pin CTI or MIPI 60-pin trace header. See SPRU655 for trace header requirements.
Examples[edit]
A CPT Module can be setup and enabled through CCS or using the CTPLib from your application. The following links provide detailed CPT profiling examples:
- CP Tracer profiling from CCS setup - data collection with XDS560v2 System Trace
- CP Tracer profiling from CCS setup - data collection with ETB
- CP Tracer profiling using CPTLib - data collection with on-chip Embedded Trace Buffer(ETB)
- CP Tracer profiling using CPTLib - data collection with XDS560v2 System trace
- CP Tracer DDR Profiling Example
Debugging With Common Platform Tracer provides CPT debug information.
See Common Platform Tracer Errata for known silicon and software problems.
Results[edit]
For profiling cases CCS can be used to display CPT Data in a graphical form: