UNIFLASH: Does Uniflash GUI do verification when programming?

Part Number: UNIFLASH
Other Parts Discussed in Thread: TMDSCNCD263P

Tool/software:

Using Uniflash 9.2.0.5300 with TMDSCNCD263P Rev B, onboard XDS110 over JTAG with BOOTMODE=OSPI(8s).

When programming FLASH using Uniflash GUI, the console would say it all chunks are programmed and is complete.

But we have noticed that sometimes (hard to replicate) after successful loading and power cycling the board it stops part way during the boot.  Almost as if the image was corrupt.

In one instance we programmed SBL, appimage and appimage_xip.  On success and reboot, we can see the output stopped part way booting SBL.

The same images were loaded again with success.  Another power cycle and the SBL booted and handed control to application where it crashed.

The same images were loaded again with success for a 3rd time.  Another power cycle and now SBL and appimages booted up properly.

It was almost as each programming sequence programmed the images further.

I have 3 questions:

  1. Does Uniflash GUI do verification while it does programming?
    1. If so, how can we explain the behavior I saw?
  2. Is there a way or tool that can only verify images against what is programmed in flash?
  3. When using dslite from the standalone command line, the arguments seem conflicting.  -s says no verification, but -v says verify after programming.   
    1. -s VerifyAfterProgramLoad="No verification"
    2. -v
    3. It does seem to be doing verification though.

Thanks for the support.

  • Hello,

    Does Uniflash GUI do verification while it does programming?

    Yes. Please see:  RE: UNIFLASH: About the "verify image" function of Uniflash 

    For non-MSP it would be a "fast" verification which only checks in a few areas.

    Is there a way or tool that can only verify images against what is programmed in flash?

    CCS can be configured to run a full verification without loading/flashing with the "verify program" option.

    When using dslite from the standalone command line, the arguments seem conflicting.  -s says no verification, but -v says verify after programming.   
    1. -s VerifyAfterProgramLoad="No verification"
    2. -v
    3. It does seem to be doing verification though.

    Yes they do seem to contradict each other. I assume you are working with a standalone CLI package generated by UniFlash. I assume the it would use the option specified last (-v in this case). I would need to confirm with engineering.

  • The "verify image" link returned "access denied".

    Is there a CLI tool? or some hidden feature with dslite / uniflash that we can use?  We do not develop in CCS hence it would be very inconvenient to program using uniflash, close, open CCS, connect, load image, verify.  Then switch back to uniflash to program image again.

    Thanks for looking into this.

  • The "verify image" link returned "access denied".

    Sorry, that link is restricted. Here is the relevant portion:

    Yes... kind of. That is the intent but there are different kinds of verification that can be done. UniFlash defaults to a "fast" verification option which only checks some of the download program (first and last 20 bytes). This is true for all devices expect MSP430, which always does a "full" verification (check the whole program).

    For more details, see: https://software-dl.ti.com/ccs/esd/documents/users_guide_12.8.0/ccs_debug-main.html#program-memory-load-options. Check the part called "Verification Options".

    Is there a CLI tool? or some hidden feature with dslite / uniflash that we can use?

    I will look into this.