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.

C28xx: File Loader: Verification failed: Values at address 0x0000000000200000 do not match Please verify target memory and memory map.

Other Parts Discussed in Thread: CONTROLSUITE, MSP430F47187

 

Hello, I'm having an issue with the F28335 on an EZDSP using CCS V6.1

From what I can see I'm attempting to put a bit of code in a memory location that should have been ok on my EZDSP board and I'm getting the dreaded data verification error. had a quick look at other posts and nothing obvious jumped out as being a simple solution to this. Any suggestions would be welcome.

 

regards

Steve

 

 

 

 

 

  • Steve,

    The memory address referenced in this error message maps to external memory on the ezdsp. To use it, did you enable XINTF before trying to load your code?

    The F28335.GEL file has a function that enables it. Check the picture below:

    Hope this helps,

    Rafael

  • Hello Rafael,

    Thanks for your suggestion. I think you are probably on the right track, but I still seem unable to get this working.

    Firstly my version of CCS does not seem to show the GEL functions in the same drop down menu as your image suggests. i.e I don't seem just to be able to click on an XINTF enable. I note that you are in debug mode, but I can't get into debug mode as the code mismatch error bounces it back out. No doubt I'm missing some simple step, but it has me foxed for the time being. 

    Anyway, I tried the old method of removing the comment's in the GEL file to ensure the

    XINTF_Enable();   

    line is active in the OnReset() function in all the F28335.gel files I can see on my system and that didn't work. Nor did copying the gel file into my project area and modifying it there.

    This last method is the one colleagues have used with previous version of CCS. However, there is some talk of there being issues with code that used to work fine with CCS v5.5 but not working with CCSV6 due to memory allocation errors (and no other changes having been made)  such that they use CCS v5.5 for the EZDSP with F28335 and V6 for the F28337D. Now this might be coincidental, but my suspicions are aroused.

    Any further suggestions welcome.......

    regards

    Steve

      

  • Having scoured the department I can't find anyone who has actually managed to successfully run a bit of code on the f28335 EZDSP  that tries to access the on-board external RAM when using CCS V6. We do have code that runs fine on CCS V5.5 but then fails on CCS V6. The solution that has been adopted by others is to stick with CCS V5.5.for the F28335 and use CCS v6.0/6.1 for a few F28337D projects which are under development. Clearly, if there is a version related issue it would be good to sort it.

    It may just be that the compiler tools or standard lib files have been concurrently updated as we find that there is now a section, .esysmem, that appears in the linker files with CCSV6 that never used to be there with the same code in CCS v5.5. This is quite an old project and it doesn't use far_malloc intentionally.  This .esysmem block  prevents the program from compiling due to insufficient memory until you point the .esysmem block to the external memory which is where we already put the .sysmem section. This space is occupied by some data storage arrays.

    I tried the quickly tried XINTF Demo in  controlSUITE and that wouldn't work either. I'm not entirely sure if it is meant to on the EZDSP though.

    Is there a bit of demo code that has definitely been tested by TI on the EZDSP using CCS v6 that you can point me to try on this setup. Also please let me know if there are any specific set ups needed to get it to run (other than uncommenting the line in the gel files).

    Some additional help/suggestions would be welcomed:-)

    regards

    Steve

     

  • Steve,

    Sorry, I was out yesterday.

    A few details that may help you dive into this issue a bit further:

    Steve McDonald said:
    I note that you are in debug mode, but I can't get into debug mode as the code mismatch error bounces it back out.

    In order to have access to the GEL routine before you load code, I launched the debugger without a project, as shown in this short clip below.

    Steve McDonald said:
    I tried the old method of removing the comment's in the GEL file to ensure the XINTF_Enable(); (...) 

    The OnReset() GEL will be called only if the device is reset. In this case, it is possible the device is not resetting before the code is loaded, thus causing this memory segment to be misconfigured. You have two options:

    - Either enable the option Reset the target on a program load or restart - section 3.1 of this page.
    - Add the XINTF_Enable(); call to the GEL function OnTargetConnect().

    You can reproduce the test I did here and shown in the screenshot below. Launch the target manually, open the Memory Browser view and point to the address 0x200000. With XINTF disabled you should see a bunch of zeros. Go to the Scripts menu I sent before to enable XINTF and magically random data should appear on this view.

    With this you are able to verify if the external RAM on your board is working fine.

    The differences in CCS versions may be due to the fact the default options may have changed (or someone changed them on the v5 workspace but forgot to do it on v6).

    I am not 100% sure about the differences in the compiler versions, but keep in mind you can use older compiler releases in newer CCS - check section 4.10 of this page.

    Hope this helps,

    Rafael

  • Hi Rafael,

    That was very helpful. Upon debugging without a program it was obvious that the external memory was still inaccessible. I noticed that the gel file CCS was using was in the ti\CCSv6\ccs_base\emulation subdirectory and I had changed all the ones in the control suite subdirectories thinking that one of them was being used.

    Quite why we need to have as many gel files lying about is a bit of a mystery.

     

    Anyway, upon commenting the line on this file it all began to work properly. Many thanks.

    S

    P.S I see no green button to click on my browser!

     

     


     
      
      
      
      
      
      
      
      
      
      
      
      
     
     
     


  • me too face the same problem,I am begineer for CCS . when I even tried to build the simplest LED_blink code this message is displayd,I tried to enable XINTf as you suggest,but no subscripts found,any suggession pls?

    MSP430: File Loader: Verification failed: Values at address 0x0000000000008000 do not match Please verify target memory and memory map.
    MSP430: GEL: File: D:\DM801\SOFT TEST\Test_1\Debug\Test_1.out: a data verification error occurred, file load failed.
  • Hello,Steve

    The same problem is happened with me in msp430f47187.

    Here the problem with the controller flash.u unable to write the data in flash.

    example like first u dump the any example code using the FET and read the flash u getting the blank data.

  • Hello Ajay,

    My problem was caused by an incorrect setting in the f28335.GEL file to enable/disable the external memory on the board via XINTF.  There are so many copies of the GEL file around the TI subdirectories it is very easy for a default one to reappear and mess things up.

     The offending lines in the f28335.GEL are:

    OnReset(int nErrorCode)
    {
    C28x_Mode();
    Unlock_CSM();
    ADC_Cal();
    // XINTF_Enable(); /* Uncomment to enable XINTF on Reset */
    }

    Not sure if your problem is similar for the msp, but worth a look.