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.

CC2652R: Uniflash programmer (4.2.2.1692) image verification fail

Part Number: CC2652R
Other Parts Discussed in Thread: UNIFLASH

Hi,

I am using cc2652R1 development kit. I build the host test application and when ever i flash the image i found , writing image is successful, but if i use verify then i get error.

Here is the log what i receive when i write the image in flash

[6/19/2018, 7:44:20 PM] [INFO] Cortex_M4_0: GEL Output: Memory Map Initialization Complete.
[6/19/2018, 7:44:23 PM] [INFO] Cortex_M4_0: GEL Output: Memory Map Initialization Complete.
[6/19/2018, 7:44:27 PM] [INFO] Cortex_M4_0: GEL Output: Board Reset Complete.
[6/19/2018, 7:44:41 PM] [SUCCESS] Program Load completed successfully.

Here is the log what i receive when i verify

[6/19/2018, 7:45:33 PM] [INFO] Cortex_M4_0: GEL Output: Memory Map Initialization Complete.
[6/19/2018, 7:45:35 PM] [INFO] Cortex_M4_0: GEL Output: Memory Map Initialization Complete.
[6/19/2018, 7:45:47 PM] [ERROR] Cortex_M4_0: File Loader: Verification failed: Values at address 0x0003A002 do not match Please verify target memory and memory map.

May i know why this error is getting generated? why flash contain is not same?
I attached the hex file i generated, which i want to flash in cc2652R1

Thank you.
With Regards,https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/538/5518.ble5_5F00_host_5F00_test_5F00_cc26x2r1lp_5F00_app.7z

  • Hello,

    Thanks for reporting the issue and apologies for any inconvenience. I was able to reproduce this behavior with the Cloud and the Standalone versions, we are looking into this and trying to understand the reason behind this.

    In the meantime, you could use CCS to upload this image as I confirmed that the image is being uploaded correctly.

    Best regards,

    David
  • Hello,

    It looks like this has been reported before - e2e.ti.com/.../2521965

    And that bug has already been fixed and should be in the next Uniflash release 4.4.

    Best regards,

    David
  • Hi David,

    After i downloaded and use uniflash [4.3.0.1802], i thought this issue is resolved. But i found the issue still there, like below. issue is not resolved

    1) if we use builtin hex file [ble5_host_test_cc26x2r1lp_app_FlashROM_Release.hex] from the location C:\ti\simplelink_cc26x2_sdk_2_10_00_44\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack\hexfiles\cc26x2r1

    The verification pass after writing the firmware

    2) if we use builtin hex file [ble5_host_test_cc26x2r1lp_app_FlashROM_Release.hex] from the location C:\ti\simplelink_cc26x2_sdk_1_60_00_43\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack\hexfiles\cc26x2r1

    The verification FAIL after writing the firmware

    3) If i build the host_test project from simplelink_cc26x2_sdk_1_60_00_43 SDK or simplelink_cc26x2_sdk_2_10_00_44 SDK the generated hex file, write in flash is pass, but verification FAIL.

    Can you Please confirm the same.

    Thank you.
    With Regards,
    Kaushik