we are using CCS5.1.1 on C6657, sysBios 6.34.4.22 with XDS100V2 from BH. A related post about this setup is under (http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/264951.aspx). I reported this problem under that thread, but as it is marked as answered, I am reposting it.
I setup the trace start and trace stop all at ti_sysbios_family_c64p_Hwi_int1 as in the attached ppt file. (I even set up a break point there to prevent it from moving forward with sysBios system calls)
I purposely setup a call which access null pointer, which is called by uart task, as the following
int crash_trigger(void)
{
memset(0,0x12,10);
}
I would expect that I could find this in my trace buffer. But I only saw the sysbios acitivities. I am attaching the trace log, in which I can not find anything related to memset or crash_trigger. I would expect that the tracing would stop at the time of exception. Is there anything I missed in the setup/configuration?
I am attaching one of the trace data exported in spreadsheet format
thanks
Weichun