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.

CCS/TCI6638K2K: Crash dump analysis using Datasnapshot viewer

Part Number: TCI6638K2K
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

Hello TI,

We are using TI CCS Datasnapshot viewer to debug and analyse crash dumps. We, in some cases, need the entire DDR3A, DDR3B contents to conclude the issues. 

The issue we are facing is the loading time of dumps in CCS. It takes more than an hour to load the complete 2.5GB dump (txt files) into CCS  which is a little too long. Is there a way to optimize and reduce the loading time of dumps? As I can see, snapshot viewer loads the memory contents byte by byte based on architecture. Is there a way we can load one word (4bytes) at once, or some other method, to achieve reduction in load time of dumps?

Regards, Yunas

  • Yunas,

    If you set the environment variable TI_DS_ENABLE_DSV_WRITES to 1 before launching CCS or running a DSS script, then you can use any method you like to write to the memory.  Both CCS and DSS have ways of loading binary data to memory, which should be noticeably faster than using the text format. 

    Darian

  • Thank you Darian for the assistance. I need some more info please.

    I checked your method. I can see the environ variable TI_DS_ENABLE_DSV_WRITES set to 1 from preference->CCS->build->variables->systemVariables. But on trying to load a binary data file into memory using memoryBrowser->loadMemory i see driver error from DSV:

    Trouble Writing Memory Block at 0x80000000 on Page 0 of Length 0x7ff0: This operation is not supported by this driver

    Is this feature available in CCS 6.1.3 or I need to update to some later version?

    PS: I checked with CCS v7 on Linux machine but I couldnt find the variable. I will check further.

    Regards, Yunas
  • Yunas,

    I went back to 6.1.3, and even chose the TCI6638K2K target.  Everything worked fine for me.

    Could you try setting the flag in a dos console, and then running ccstudio.exe in that console?  My fear is that preference->CCS->build->variables->systemVariables is picking up what new global settings will be passed to the compiler in a new process, but not what the current settings are for the currently running process.  Either that, or you have a typeo in the spelling of the environment variable name.

    Darian

  • Darian, thanks for your help. Setting the environ variable from console worked.

    Regards, Yunas