• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 144 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.

TMS570LS3137: Memory Verification Log

AARON SPILKER
Prodigy 110 points
Part Number: TMS570LS3137

Code Composer has the following options for debugging:

Verification Options: after the code/data is loaded to the device, sets the level of verification performed on it. This is done by reading back the code/data from the device’s memory and comparing it to the executable in the host. The choices are:

  • Full: reads back the entire program loaded to the device. This is the default option for MSP430.
  • Fast: reads back only the first and last 20 words loaded to the device. This is the default option for all other devices.
  • No verification: no verification is performed

Does CCS produce an artifact for the memory verification? I want evidence that what was loaded matches what I gave the program.

  • 0
    TI__Guru**** 463901 points

    Hello,

    There is no log that is generated during the verification action. If the verification is successful, there will only be a message in the output window indicating so. If there is a failure, it will output a message of the address where the first failure is encountered. Once the first failure is encountered, the verification will be halted. Hence there may be further inconsistencies that is not reported. 

    If a full verification passes with no errors, then that is the evidence that the content loaded to the target matches the program content in the *.out file.

    Thanks

    ki