• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 298 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCSTUDIO: .dat, .cache and .cache.valid files located in the AppData folder

Ceyhun Deniz
Prodigy 40 points

Part Number: CCSTUDIO
Other Parts Discussed in Thread: UNIFLASH

Hello,

When I upload code to the processor through the CLI, I noticed that .dat, .cache, and .cache.valid files remain in the AppData folder as temporary or leftover files. Is there a way to make them clean up automatically instead of deleting them manually, or to prevent them from being generated at all? If they aren’t created, would the programming process still work properly?

Thanks

  • 0
    TI__Guru**** 480331 points

    Hello,

    Can you provide more details:

    • What CLI command are you using to load code?
    • What exact CCS version is being used?
    • Why is there interest in removing these generated files?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 40 points

    Hello,

    I am using CCS 12.4.0 and Uniflash 8.7.0. When I create a standalone package through Uniflash, I directly use the dslite.bat file. If I don’t run dslite.bat, I perform the operation using commands similar to those in the dslite.bat file, such as:

    "dslite --mode flash -c example.ccxml -l example.ufsettings -s VerifyAfterProgramLoad="No verification" -e -f -v example.hex"

    In all cases, these files are generated. Because of the contents of these files, I would like to prevent them from being created if possible, or automatically have them cleaned up if that’s not possible.

    Thanks

  • 0 in reply to Ceyhun Deniz
    TI__Guru**** 480331 points
    Ceyhun Deniz said:
    I would like to prevent them from being created if possible

    Those files are used during the debug (or in this case the flashing) process. It is not possible to prevent generation as they are needed. It is ok to delete these files afterwards if desired. They will just get generated again on the next debug/flash session. There is no automatic way to delete this after usage.

    Thanks

    ki