This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

verify trace analyzer of CCSV5.3

after installed CCSV5.3, i tried to verify the "trace analyzer" functionality by using the "streaming.tdf" and "streaming.out" as mentioned in the HELP document.

but there is nothing appeared to show the trace, and i found one new line of log in "Error Log" view; it shows that some java class can't found.

it seems that other functionality of CCS is working. could you help to give hints on this issue? thanks.

  • Hi,

    I just tried this with my CCSv5.3.0 and it worked fine; I wonder if there is something else going on with the debug session. I am using a C64x+ CPU Cycle Accurate simulator (little endian) and all the components are the defaults (I did not add any updates). I tried that on both Win7/64 and WinXP/32

    I wonder if doing a small cleanup would help anything. Typically the steps shown at the sections General IDE and Debugger at the CCSv5 Troubleshooting page.

    Hope this helps,

    Rafael

  • thanks for the reply.

    some information about my computer: PC is win7/64bit and JRE7 already installed and no errors with it before or after i install CCSv5.3; i also have Eclipse c/c++ tool installed and works fine.the install of CSSV5.3 was after uninstall CCSV5.0.

    i have tried to delete ".TI", ".metadata" dir to make it a clean run; when i try the trace analyzer, i didn't start a debug session but just open the .tdf and .out file(do i need to start the debug session then open the trace file? actually i have a workable debug configuration(c64+) and able to run a simple helloworld program)

    i suppose there is no need to change anything for Windows environment varaible setting.

  • Hi,

    The JRE7 does not influence CCS, as it installs and runs a known good compatible version inside the directory ccsv5/eclipse/jre. Also, there is no need to set any environment variable or have a debug session running to open the Trace Viewer.

    One additional detail: some releases of CCSv5 (I think 5.3 is one of them) create a directory in the C:\Users\<username> called .TI-trace. Can you try to locate this directory and move or delete it and restart CCS?

    Apart from this I really am not sure what may be happening. The Trace file viewer is something ingrained into CCSv5 (part of a larger component called DVT) and therefore if this issue is blocking I would either uninstall/reinstall or install in a separate directory.

    I apologize for the inconvenience,

    Rafael