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/TMS320F28022: Log file(s) for loading program to target

Part Number: TMS320F28022

Tool/software: Code Composer Studio

Win7 SP1 (32bit). CCS 6.1.3. F28022.

Hi CCSrs:

Is there a log file that details what CCS is doing when I change into debug? If so, where is it (are they)?

I have begun to suspect an issue related to erasing the target FLASH, loading the FLASH, and loading the RAM.

Normally, when I click the little spider, a series of windows pops up mentioning stuff about "loading program", "erasing FLASH sector A, B, C..." then "Loading an address range" etc.

The info goes by pretty fast, and I would like to verify these steps in detail.

Any help is appreciated,

Thanks, Mark.

  • Hi Mark,

    You could enable debug server logging. But this log is very heavy and a lot of the messages may be cryptic for anyone outside the CCS debugger engineering team. There is also quite a bit noise to sort through. You can always send us the log for analysis.

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv7#Debug_Server_Logging

    If you actually automate the steps via DSS script, you can enable a verbose DSS log. But that would require you to use DSS

    http://software-dl.ti.com/ccs/esd/documents/users_guide/sdto_dss_handbook.html#logging

    Thanks

    ki

  • Cool Javelin said:
    Normally, when I click the little spider, a series of windows pops up mentioning stuff about "loading program", "erasing FLASH sector A, B, C..." then "Loading an address range" etc.

    Under the project properties -> Debug -> F28022 Flash Settings at the bottom there is a "Enable Verbose Output" option:

    If that option is ticked, I think the CCS console will show the flash erase/program operations as they are performed on the sectors.

    [Don't have a device to test this]

  • Ki:
    I did try to enable the "debug server logging, and you are right, it was over 500K lines. Very heavy indeed.

    I have looked into using the DSS before, and I do want to get into it as we will be making production runs of our product, I just haven't made the mind set yet to learn that.

    Chester:
    I did the "Enable Verbose Output" as you suggested, and got results I expected, (sort of). One interesting thing is the order of the flash sectors written isn't as expected. Not sure yet if that is an issue, but I doubt it.

    I got a little more info from MatthewPate on a different post of mine, he suggested using the hex2000 util to see the .out file.

    I am also using the abs2000 util but haven't gotten it to work properly yet.

    Thanks to both of you.
    Mark.