When using CCS 6.2.0.00050 and a XDS110 debug probe to use the "Interrupt Profiling" in the Hardware Trace Analysis for a TM4C1294NCPDT program using TI-RTOS Ethernet communication found the trace views were displaying a "CAN1" interrupt name which is confusing as the program isn't using a CAN peripheral. e.g.:
The raw trace viewer has the Data Value 0x38, where 0x38 is the TM4C1294NCPDT interrupt vector for the "Ethernet MAC" yet the CCS trace viewer is naming the interrupt vector as "CAN1".
I think the issue is that the CCS 6.2.0 trace viewer is using the MOD_EXCEPTIONMAP look-up table inside the ccsv6\ccs_base\emulation\analysis\xmldb\trace_config\devices\device_stellaris.xml file for displaying the interrupt names for the TM4C1294NCPDT device, but the interrupt vector numbers in the TM4C129 series devices are different to the TM4C123 / Stellaris series devices.
Inside the ccsv6\ccs_base\emulation\analysis\xmldb\trace_config\devices directory I can't see any device XML file which defines the interrupt vector names for the TM4C129 series devices.
