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.

  • Resolved

CCS/TMS320F28377D: CCS Flash error with data verification failed.

Intellectual 420 points

Replies: 17

Views: 551

Part Number: TMS320F28377D

Tool/software: Code Composer Studio

Hi All,

I am using a Black hawk 560v2 USB terrace debug probe to program TMS320F28377D micro. I have flashed many times before and it ran successfully.

But after flashing one of the projects today morning it is suddenly giving out the following error and unable to flash anything.

I even tried using Uniflash but was not successful.

C28xx_CPU1: Error initializing flash programming: Interface returned from dll, but flash is not available on this device.
C28xx_CPU1: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map.
C28xx_CPU1: File Loader: Verification failed: Values at address 0x80002@Program do not match Please verify target memory and memory map.
C28xx_CPU1: GEL: File: C:\Users\.....\Merged_Mana_Bala_ControlBoard_PS_CPU1.out: a data verification error occurred, file load failed.
C28xx_CPU1: GEL Output:
Memory Map Initialization Complete
C28xx_CPU2: GEL Output:
Memory Map Initialization Complete
C28xx_CPU2: Error initializing flash programming: Interface returned from dll, but flash is not available on this device.

Any help would be appreciated.

Thanks,

Bala.

  • Bala,

    Few debug tips that may help: 

    1) Did you check if XRSn is toggling on your board? May be the application programmed in the Flash is causing resets as it executes.  

    2) What boot mode GPIO config are using when you try to reprogram the device? Hope it is wait boot or serial boot - It will stop device from executing the application so that the device remains in a known state to take over Flash programming.

    3) Did you program any DCSM settings in the OTP as part of your latest project? If the device is locked, you need to provide password to unlock the device before you can reprogram (using Flash tools).

    Which version of UniFlash are you using?

    Thanks and regards,
    Vamsi

  • In reply to Vamsi Gudivada:

    Hi Vamsi ,

    Thanks for the reply.

    1. I will check and let you know.

    2. I believe I am in Emulation boot mode

    3. I didn't program any DCSM settings. How to check whether it is locked? If it is locked then how to unlock it.

    I have used uniflash 3.4 version as the latest 5.1 version doesnt have Blackhawk probe support.

    Thanks,
    Bala.
  • In reply to Bala Grandhi:

    Hi Vamsi,

    I have checked the XRSn pin and it is high all the time.
    Also, boot mode GPIO config is in Get Mode.

    Thanks,
    Bala.
  • In reply to Bala Grandhi:

    Bala,

    Regarding #3: Please go through "3.13 Dual Code Security Module (DCSM)" section in TRM at http://www.ti.com/lit/ug/spruhm8h/spruhm8h.pdf

    "Figure 3-22. Location of Zone-Select Block Based on Link-Pointer" shows the address for password locations (Zx-CSMPSWD0/1/2/3). See if you programmed anything in those locations by connecting to the debugger.

    UniFlash 3.4 was released 6 years ago. See if you can use latest versions. You can try latest CCS as well.

    Thanks and regards,
    Vamsi

  • In reply to Vamsi Gudivada:

    Vamsi,

    I have connected the debugger and saw the password locations and they are all 1's at both Zone1 and Zone2.
    Also, I have installed the latest Uniflash and getting the same data verification error as before.

    I am not sure how to proceed further without being able to erase the flash and then programming it.

    Thanks,
    Bala.
  • In reply to Bala Grandhi:

    Bala,

    Did you change anything in your linker command file or the board when it started failing for you?

    Can you generate the logs for us to debug this further: processors.wiki.ti.com/.../UniFlash_v4_Quick_Guide

    Thanks and regards,
    Vamsi
  • In reply to Vamsi Gudivada:

    Bala,

    Also, which device did you select when you created the target config file?

    Thanks and regards,
    Vamsi
  • In reply to Vamsi Gudivada:

    6204.ds.logVamsi,

    Thanks for the quick responses.I didn't change anything in the command file .

    I am selecting the TMS320F28377D device in the target config file which is on our custom made board.

    Also for generating the log time ,if I use the Uniflash verison 5.0 then it is not responding as soon as I give the command to Erase/Program Flash.

    If I use the version 3.4  then it is giving an error on erase/flash but generating a log file .

    I am including the log file from the version 3.4.

    Also,I am wondering if this is something because of depletion? If so, how to recover from that?

    Thanks,

    Bala.

  • In reply to Bala Grandhi:

    Bala,

    Thank you for the log file.
    Will get back to you early next week.

    Thanks and regards,
    Vamsi
  • In reply to Vamsi Gudivada:

    Thanks, I will be waiting for your response.

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.