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/TMS570LS3137: Verification of the running executable

Expert 1995 points
Part Number: TMS570LS3137
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

Hello,

Which method do CCS and Uniflash (supposing the same for both) use to verify that the running executable is actually the pointed .out ?

Are there other methods you can suggest me to confirm that ? (e.g. downloading the memory in a particular format and performing some comparison)

Thanks ahead.

  • _MM_ said:
    Which method do CCS and Uniflash (supposing the same for both) use to verify that the running executable is actually the pointed .out ?

    When a program is loaded, CCS (and UniFlash) usually does some verification of the loaded program, to see if it matches the expected results based on the contents of the *.out file. The type of verification done can be specified in the debugger options:

    The default verification done is "Fast verification", which is a partial check (like a quick sanity check). This verification is usually enough in most cases. However, "Full verification" can be enabled. This is a thorough (full) check of everything.

    If verification fails, then a Data Verification Error will occur.

    Note that you can also manually do a verification via 'Run -> Load -> Verify Program'

    Thanks

    ki