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.

UniFlash Image Verification

Other Parts Discussed in Thread: UNIFLASH, TM4C123FH6PM

I am using UniFlash V7.2, the XDS200 Debug Probe, and a TIVA TM4C123FH6PM.

I tried verifying a .OUT file against one loaded onto my target that was different by just a few lines of code. UniFlash reported that verification was successful while I was expecting an error.

Does UniFlash V7.2 use full verification or fast verification?

In other words, does UniFlash only check portions of memory or does it check all memory. Since my two images were only different by a couple lines of code, I am suspecting that UniFlash missed the differences.

Can this be verification type (fast and full) be set by the user?

  • This is not a direct answer your questions but...

    It could be that your changed code is in an unreferenced section and so is never part of the output binary. Try to make a hex file of the before and after programs and use a text compare to verify, beyond doubt, that you have two different images.

  • Hello

    Does UniFlash V7.2 use full verification or fast verification?

    UniFlash defaults to fast verification with the exception of MSP430 (which defaults to full).

    Fast verification would only check a few sections vs Full (which checks everything).

    Can this be verification type (fast and full) be set by the user?

    For the UniFlash GUI: It depends on the device. For example, there is an option to specify the flash verification type on Hercules. But not for Tiva.

    However, you can set the verification setting if using UniFlash via the command line.(-s VerifyAfterProgramLoad="Full verification")

    Thanks

    ki

  • Hi, 

    I verified that the files are different using WinMerge. Thank you for the suggestion though, I didn't know CCS will sometimes removed unreferenced/unused code.