• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 515 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

CC3235SF: Load Program Error during Debugging

CC3235SF: cc3235sf File Loader: Verification failed

? ?
Prodigy 30 points
Part Number: CC3235SF
Other Parts Discussed in Thread: CC3235MODSF, UNIFLASH, LAUNCHCC3235MOD

Hello,

I am facing an error while debugging on our custom boards based on CC3235SF.

I debug the code by jtag in CCS,  when I download the program,  follows this problem.

Cortex_M4_0: File Loader: Verification failed: Values at address 0x01000801 do not match Please verify target memory and memory map.
Cortex_M4_0: GEL: File: xxx\network_terninal_CC3235SF_LAUNCHXL_tirtos7_ccs\Debug\network_terninal_CC3235SF_LAUNCHXL_tirtos7_ccs.out: a data verification error occurred, file load failed

base config:

1: The custom board has exactly the same layout and schematics as the launchpad, use cc3235modSF

2: sop is 010

3: use example project , download from project wizard

4: CC3235SF_tritos7.cmd define flash address 0x01000800

5: the same project is ok on the  launchpad board

  • 0
    Prodigy 30 points

    the device base information: get by uniflash

  • 0
    TI__Mastermind 32620 points

    Hi,

    This document describes how to address this issue. Please read through it in full: https://software-dl.ti.com/ccs/esd/documents/troubleshooting-data_verification_errors.html 

  • 0 in reply to Sabeeh Khan1
    Prodigy 30 points

    hi sabeeh khan1

    first 

    i read the file and record

    I find that memory map , cmd file difine the addr 0x01000800 only read,  why debug need to write this address?

    second

    I  amend the memory map and cmd file. 

       

    then build project and download program,  the error is same

    the other things

    I can flash code by uniflash, but it is not work when power up.

    thanks 

  • 0 in reply to ? ?
    Guru 80285 points

    Hi,

    Just to be sure. Do you use module or QFN? Do you use TI module of module from 3rd party? Are you able run your code at LaunchPad (what exact type of LaunchPad)?

    Yes, I know that you wrote that CC3235MODSF is used? But I want to be sure, because similar symptoms can have issue with pins for powering flash (45, 46, 47 at QFN).

    Jan

  • 0 in reply to Jan D
    Prodigy 30 points

    Hi Jan D

    thanks

    1:  I use the module CC3235MODSF.

    2:  I use example project  "network_terninal_CC3235SF_LAUNCHXL_tirtos7_ccs"

    3:  I use LAUNCHCC3235MOD(PCB REV.A   MCV070A)

    4: CCS version is 11.2.0

    5: uniflash version is 8.0.0

  • 0 in reply to ? ?
    Guru 80285 points

    Hi,

    Hmm... this does not make sense to me. Let me explain. I think similar symptoms can have following issues:

    • issue with XIP (on-chip) flash - JTAG is not able to properly write into XIP flash and ROM bootlaoder is not able copy code for execution into XIP flash. This issue is likely possible with QFN (problem with QFN pins 45, 46, 47) but I can't imagine how it can occur at MOD.
    • problem with JTAG connection. It can explain verification error, but it does not explain why ROM bootloader is not able execute code in XIP flash.
    • maybe some issue linking of your code. Your screenshots above have small resolution, but it seems your linker file is correct. But this will not explain problem with ROM bootloder (especially when you are able execute exact same code at LaunchPad)

    I am not a TI employee and from this reason I don't have access to internal layout of module. But maybe is possible when some VCC pins (VBAT1, VBAT2) or GND pins are not properly connected it can cause issue with powering XIP flash. I can't confirm this due to lack of information from TI side. But if you have easy access to X-ray machine, maybe you can check soldering of your module.

    Jan

  • 0 in reply to Jan D
    Prodigy 30 points

    Hi  Jan D

    I think that you are right,   the XIP(on-chip) flash of module may be not work.  but i can not to test it. 

    I will replace a module to confirm it.

    thanks