Part Number: EVMK2H
Other Parts Discussed in Thread: TCI6638K2K, 66AK2H14, 66AK2H12
Tool/software: Code Composer Studio
Was using CCS 7.2.0.00013 under Windows 10, with TI Emulators 7.0.48.0 and Keystone2 1.1.9 to attempt to use the Memory Throughput Analysis Hardware Trace Analyser, when a program was running on the C66xx_0 core of a EVMK2H accessing DDR memory. Used the XDS200 Onboard Debug Probe on the EVMK2H, with the boot mode set to "DSP No-Boot" and the ..\..\emulation\boards\xtcievmk2x\gel\xtcievmk2x.gel GEL script used to perform the device configuration.
The Memory Throughput Analysis was started using the default values. The "Memory Throughput - CSSTM_0" graph wasn't displaying any data:
Looking at the "Trace Viewer - C66xx_0" table shows that the CFG and SPI_ROM_EMIF16 domains have been captured rather than the expected DDR3A and DDR3B domains for the Memory Throughput Analysis:
Checking the Analysis Properties from the "Trace Viewer - C66xx_0" shows that DDR3A and DDR3B have been set as the Transaction Monitors:
If the same test is repeated using CCS 7.1.0.00016 with TI Emulators 6.0.628.1 and Keystone2 device support 1.1.9 then the Memory Throughput Analysis captures data for the DDR3A and DDR3B domains:
Therefore, in the change from CCS 7.1.0.00016 / TI Emulators 6.0.628.1 to CCS 7.2.0.00013 / with TI Emulators 7.0.48.0 something has caused the Memory Throughput Analysis to capture data from the incorrect transaction monitors.
The example project used is attached 66AK2H14_C66_system_trace_TCI6638K2K_device_file.zip
[In the Target Configuration the device has been set to a TCI6638K2K rather than 66AK2H12 since the 66AK2H12 device file is missing some entries for trace - see https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/511744]
