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.

AM2632: uart_uniflash.py does not report verification failure

Part Number: AM2632
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

I am using uart_uniflash.py to program my board.  I can successfully program and power cycle and boot.  The problem is, when I tell the script to 'verify' with known different code, it does not report a failure.  I have confirmed that it does not program the new/different code because if I reboot, the old code is still there.

I have sdk mcu_plus_sdk_am263x_10_00_00_35 and I launch uart_uniflash as follows:

python C:\ti\mcu_plus_sdk_am263x_10_00_00_35\tools\boot\uart_uniflash.py -p COM7 --cfg verify_flash.cfg

The contents of the config file are below.  The two files I am attempting to verify are different, but neither reports an error.  What am I missing?

#-----------------------------------------------------------------------------#
#                                                                             #
#      DEFAULT CONFIGURATION FILE TO BE USED WITH THE FLASHWRITER SCRIPT      #
#                                                                             #
#-----------------------------------------------------------------------------#
#
#  We took this from C:\ti\mcu_plus_sdk_am263x_09_02_00_56\tools\boot\sbl_prebuilt\am263x-cc
#  and modified  it accordingly to work for our code. The configurations below still point
#  relevant files in the SDK installation directory (C:\ti\mcu_plus_sdk_am263x_09_02_00_56\).
#  Those files could be copied to here to make the flahing process independent of having
#  the SDK installed.  Bu that is left for another time.
#
# By default this config file,
# - points to pre-built flash writer, bootloader for this EVM
# - The application image points to relative path of the ipc echo application image for this EVM
#   - Make sure this application is built before running this script
# - You can customized this config file to point to your own bootloader and/or application images
# - You can use --operation=flashverify if you just want to verify the flash contents and not flash the file.
#C:\ti\mcu_plus_sdk_am263x_09_02_00_56\tools\boot\sbl_prebuilt\am263x-cc

# First point to sbl_uart_uniflash binary, which function's as a server to flash one or more files
#--flash-writer=sbl_prebuilt/am263x-cc/sbl_uart_uniflash.release.tiimage
#--flash-writer=C:/ti/mcu_plus_sdk_am263x_09_02_00_56/tools/boot/sbl_prebuilt/am263x-cc/sbl_uart_uniflash.release.tiimage

--flash-writer=sbl_uart_uniflash.tiimage

# Now send one or more files to flash or flashverify as needed. The order of sending files does not matter

# When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0
--file=bootloader-leave.tiimage --operation=flashverify --flash-offset=0x0

# When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0
--file=bootloader-stay.tiimage --operation=flashverify --flash-offset=0x0

The output from running the script is below:

Enter COM Port [COM7]:
Using COMPORT COM7

Parsing config file ...
Parsing config file ... SUCCESS. Found 3 command(s) !!!

Executing command 1 of 3 ...
Found flash writer ... sending sbl_uart_uniflash.tiimage

Sent flashwriter sbl_uart_uniflash.tiimage of size 43705 bytes in 5.74s.

Executing command 2 of 3 ...
Command arguments : --file=bootloader-leave.tiimage --operation=flashverify --flash-offset=0x0
Sent bootloader-leave.tiimage of size 301197 bytes in 30.28s.
[STATUS] SUCCESS !!!

Executing command 3 of 3 ...
Command arguments : --file=bootloader-stay.tiimage --operation=flashverify --flash-offset=0x0
Sent bootloader-stay.tiimage of size 301197 bytes in 29.79s.
[STATUS] SUCCESS !!!

All commands from config file are executed !!!