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.

CCS V4.2, SYSBIOS, OMAP-L138 link error "Data Verification Failure"

Other Parts Discussed in Thread: OMAP-L138, SYSBIOS, OMAPL138, TMS320C6748

Hello,

I'm trying to build an initial 6.30 SYSBIOS project for my OMAP-L138 6748 DSP, using CCS V4.2.  I followed the steps in the "Sys/BIOS 6.30 Getting Started Guide".  And I can build the example SWI project using the procedure documented there.  However, when going to load the resulting output file to the DSP on the OMP-L138, I get the following error:

"C674X_0: File Loader: Data verification failed at address 0xC1010430 Please verify target memory and memory map.
Error found during data verification.
Ensure the linker command file matches the memory map."

I've tried a few things to resolve this, but with no luck.  Any pointers would be greatly appreciated.

I haven't added any linker command file to the project, but am wondering if I should.

Regards,

Robert

  • 0640.swi_OMAPL138.zip

    Hi Robert,

    I've attached a swi.out program to this post (I had to zip it up in order to attach).  Please unzip the .out file and try to load/run the program on your OMAP-L138 board and let me know if it works on your setup. 

    I have a few quick questions as well:

    What is the the full version of CCSv4.2 that you are using?  You can find this under the "Help-->About Code Composer Studio" menu.  Also, are you using the defaults versions of SYS/BIOS, IPC and XDCtools that shipped with the CCSv4.2 that you have. 

    What is your connection to your OMAP-L138 board, i.e, XDS560, usb, etc?

    I think I can help you get up and running.

    -Jon

     

  • Hi Jon,

    Sorry for the delay in replying back, since I wasn't able to access the OMAP system the past 2 days.

    I tried to load your swi.out to my OMAP-L138, and received the same error.

    I'm using CCS 4.2.0.10017.

    I updated everything that was allowed, and am building the  example SWI project with the following: 6.30.03.46 SYS/BIOS, 1.21.02.23 IPC and 3.20.04.68 XDCTools.

    Connection to the OMAP-L138 is via XDS100.

    Thanks,

    Robert

  • Have you successfully downloaded any program using CCS and the XDS100? See this wiki article for details:

    http://processors.wiki.ti.com/index.php/How_to_connect_to_the_OMAP-L138/C6748_EVM_board_using_CCS%3F

    Mark

     

  • Hi Robert,

    The link Mark provided should help make sure you have the correct setup.  Can you confirm that you were configured with the correct OMAPL138 gel files when you were trying to connect and load the BIOS program.  Here is another link for the xds100 that may be of use to you.  

    http://processors.wiki.ti.com/index.php/XDS100

    -Jon

     

  • I have loaded and run with the XDS100, on OMAP-L138 before, and confirmed again today.  It’s an example, non-bios “led_pb” program that came with an original CCS 3.3 install.  I did run into some initial problems with loading, via XDS100, related to the EEPROM programming, which was resolved here:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/74005/271512.aspx#27151

    But as mentioned, no problems loading and running that LED example now.  So I think we’re ok with XDS100, and that may not the source of the problem this time.

    I did look into GEL files, and noticed I didn’t have one.  So I’ve updated to use one now, and have attached it, which has also resulted in an update of the Memory Map (to something other than one line).  But still, the program load fails with the same/similar error message.

    If of any use, I’ve also attached a picture of some of my program settings, for review.

    A question that remains is a command (.cmd) file required with building projects under CCS 4.2?  I’ve left that field as none, simply because a suitable wasn't found in any of the project directories that came with the install.  I don’t think this is the problem, because I also get the same load error with Jon’s output file, which is assumed to have been built with the required command file (or lack of one, if that's right).

    Thanks,

    Robert

     3731.OMAPL138_DSP.gel.txt

     

      

      


  • Robert said:

    A question that remains is a command (.cmd) file required with building projects under CCS 4.2?  I’ve left that field as none, simply because a suitable wasn't found in any of the project directories that came with the install.  I don’t think this is the problem, because I also get the same load error with Jon’s output file, which is assumed to have been built with the required command file (or lack of one, if that's right).

    Hi Robert --

    You do not need a .cmd file.  SYS/BIOS configuration will generate a command file.

    Which example are you building?   If it is just a basic BIOS app (like Task or Clock or Hello sample), can you try using 'ti.platforms.evmOMAPL138' instead of the RTSC Platform you show above to see if that helps? 

    Can you zip up and attach the problematic .out file and we can try to load it here?

    Thanks,
    -Karl-

     

  • Karl,

    I'm building the SWI example.  I changed to ti.platforms.evemOMAPL138, but still get the same load error, after a clean rebuild.

    Attached is my resulting .out file.

    Thanks,

    Robert

     

    3443.swi0.zip

     

     

     

     

     

     

     

     

  • Hi Robert,

    I am able to load and run your swi0.out program when I use an XDS560 to connect to the board but when I switch to the XDS100 I get the same erorr as you.  I'm looking into it so stay tuned.

    -Jon

     

  • Robert,

    Can you confirm one thing? Do you get this error using XDS100v1 or v2 as the configuration in CCSv4? Unless something changed, the built-in emulator in the OMAPL138 EVM board is XDS100v1, not v2. The configuration must be XDS100v1 and the device must be TMS320C6748 (not OMAPL138, as XDS100v1 does not support ARM).

    The reason of my question is that I can load the code to the target without problems when using XDS100v1 connection.

    Hope this helps,

    Rafael

  • Robert,

    Another detail just ocurred to me: which GEL file are you using? LogicPD has two sets of GEL files, one for OMAPL138 (DSP and ARM) and one for C6748 (just DSP, obviously). I could not load your .out file if my target configuration had the <omapl138_dsp.gel>, as it assumes the ARM side performed the mDDR initialization. If you use the <C6748.gel>, the initialization is done properly, as shown in the GEL output screen below:

    Console said:

    C674X_0: Output:  Memory Map Cleared.
    C674X_0: Output:  ---------------------------------------------
    C674X_0: Output:  Memory Map Setup Complete.
    C674X_0: Output:  ---------------------------------------------
    C674X_0: Output:  Enabling Experimenter PSCs...
    C674X_0: Output:  PSC Enable Complete.
    C674X_0: Output:  ---------------------------------------------
    C674X_0: Output:  PLL0 init done for Core:300MHz, EMIF:25MHz
    C674X_0: Output:  mDDR initialization is in progress....
    C674X_0: Output:  PLL1 init done for DDR:132MHz
    C674X_0: Output:  mDDR init for 132 MHz is done
    C674X_0: Output:  ---------------------------------------------

    Hope this helps,

    Rafael

  • Rafael,

    Yes, that helped, as I can now download my .out file, after switching from omapl138_dsp.gel to c6748.gel.  Thanks :)

    Robert