I have an application which occasionally causes one of the cores on a C6472 to crash. Using the trace control functionality available in CCS I can see that the program is exiting due to an HWI_NMI interrupt which causes the EXC_exceptionHandler() and EXC_internal() functions to run, eventually ending up in UTL_halt(). Several of these functions print out useful looking debug info using LOG_error(), however I cannot seem to find any of this log info from within the debug session in CCS. I can view other BIOS related log output in CCS in RTOS Object View (ROV)->LOG->LOG_system. However I cannot find anything logged using LOG_error(), how may I get access to this output? I have seen on another post that messages will be written to the symbol SYS_PUTCBEG, however this area of memory appears to be all zero when viewed in the memory browser when I hit a breakpoint in UTL_halt.
Device: TMS320C6472
Emulator: xds560v2stm
DSP/BIOS version: 5.41.13.42
CCS version: CCSv5.2.0.00069
Incidentally I seem to be able to trigger a core trash much more readily when Trace Control is enabled (trace breakpoint set, trace receiver set to 'ETB'). This despite reassurance on the wiki that trace does not impact system execution. Are there circumstances under which trace could be making the system more unstable? I'm concerned that trace may be causing the core to crash for a separate unrelated issue.
