• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 56 subscribers
  • Views 1608 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.

MSP430 GEL errors

Calum Mackinnon
Genius 4155 points

Hi,

I have 4 pieces of firmware that were developed by a client, the original developer is not available, and the client knows very little about the firmware. I have the source code and can compile OK. I'm using CCS5 and have teh 90 day trial licence.

3 of the pieces are for the part: MSP430F5436AIPZ

1 of them if for part: MSP430G2553IPW20R

I am using the TI launch-pad (spi-by-wire) for the smaller uPro and I am using the Jtag interface on the MSP430 USB-debug-interface for the other three

1 piece of software for the MSP430F5436AIPZ has no problem programing to the target.  The other three result in the following errors: - regarldess of the order in which I progtram teh devices I get teh same errors.

For MSP430F5436AIPZ:

MSP430: File Loader: Data verification failed at address 0x00000200 Please verify target memory and memory map.

MSP430: GEL: File: C:\Texas Instruments\Latest SW\API radio for rower 3-26-2012 5436a\Debug\API radio for rower 3-26-2012 5436a.out: a data verification error occurred, file load failed. 

For MSP430F5436AIPZ:

MSP430: Trouble Writing Memory Block at 0x200 on Page 0 of Length 0x3502: Could not write device memory

MSP430: GEL: File: P:\Clients\Pocock\4_Discovery\From Pocock\Software\Latest SW\Copy of Rower broadcast 1-9-2013\Debug\Copy of Rower broadcast 1-9-2013.out: Load failed.

For MSP430G2553IPW20R

MSP430: Trouble Writing Memory Block at 0x200 on Page 0 of Length 0x818: Could not write device memory

MSP430: GEL: File: P:\Clients\Pocock\4_Discovery\From Pocock\Software\Latest SW\Copy of 2553 sensor with sleep 8-15-2012\Debug\Copy of 2553 sensor with sleep 8-15-2012.out: Load failed.

The errors all seem very similar, but I am not a firmware guy and I cannot seem to figure out how to solve this.

 Can you offer any advice?

  • 0
    TI__Guru*** 130875 points

    Hi Calum,

    some things to check

    - verify there are no build errors

    - are these on mapped drives?  Try locally instead of mapped.

    Are there any further details you can provide?  This may be one for the msp forum but information would help.

    Best Regards,

    Lisa

  • 0
    TI__Guru**** 171044 points

    Hi,

    Did you check the original projects these files were created? Basically all error messages (Data verification failed at address 0x00000200) indicate problems in writing to address 0x200, which does not map to any valid memory on the MSP430 devices you are using.

    A few details are shown in the wiki page below, but my guess is that you do not have a linker CMD file included in the projects you are building - thus everything tries to be allocated starting from address 0x0.

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS_-_Data_Verification_Errors

    Hope this helps,

    Rafael

  • 0 in reply to Lisa TI
    Intellectual 320 points

    Calum posted this issue on my behalf.

    -there are no build errors, but a few warnings.

    -the projects were on a mapped drive, moved them to C: issue is persistent.

    thank you for the suggestions.

  • 0 in reply to desouza
    Intellectual 320 points

    I think i have the proper linker file set.  is this what you mean?

    I do have the original source

  • 0
    Guru 92251 points

    Calum Mackinnon said:
    I have the source code and can compile OK

    When the code is compiled, are there any warnings of the form "creating output section "<section_name>" without a SECTIONS specification".

    The reason for asking is that if the compiler version is updated, sometimes the compiler generates new section names which if not in the linker command file causes the linker to place code or data at an incorrect address leading to verification (or runtime) failures.

  • 0 in reply to Chester Gillon
    Intellectual 320 points

    one of the pieces gives this warning:

    Description Resource Path Location Type
    This project was created using a version of compiler that is not currently installed: 4.0.0 [MSP430]. Another version of the compiler will be used during build: 4.2.3. Please install the compiler of the required version, or migrate the project to one of the available compiler versions by adjusting project properties. 

  • 0 in reply to David Iverson
    Intellectual 320 points

    the other two have the following warnings:

    Description Resource Path Location Type
    #10247-D creating output section ".stack" without a SECTIONS 

    Description Resource Path Location Type
    #10247-D creating output section ".stack" without a SECTIONS 

    #69-D integer conversion resulted in a change of sign cpu.c 

    This project was created using a version of compiler that is not currently installed: 4.0.0 [MSP430]. Another version of the compiler will be used during build: 4.2.3. Please install the compiler of the required version, or migrate the project to one of the available compiler versions by adjusting project properties.

  • 0 in reply to David Iverson
    Guru 92251 points

    David Iverson said:
    Description Resource Path Location Type
    #10247-D creating output section ".stack" without a SECTIONS 

    That might be causing the verification failures.

    David Iverson said:
    This project was created using a version of compiler that is not currently installed: 4.0.0 [MSP430]. Another version of the compiler will be used during build: 4.2.3. Please install the compiler of the required version, or migrate the project to one of the available compiler versions by adjusting project properties.

    Since the project was created using an earlier version of the compile, probably best to install MSP430 compiler 4.0.0, and then re-build with MSP430 compiler 4.0.0 and see if that removes the "#10247-D creating output section ".stack" without a SECTIONS" warnings and prevents the verification failures. See http://processors.wiki.ti.com/index.php/Compiler_Releases for help on installing a specific compiler version.

  • 0 in reply to Chester Gillon
    Intellectual 320 points

    thank you for the suggestion, but i do not see a download for the 4.0.0 compiler 

  • 0 in reply to David Iverson
    Guru 92251 points

    David Iverson said:
    but i do not see a download for the 4.0.0 compiler 

    Using CCSv6 looking at "Help -> Install New Software" agree that MSP430 compiler v4.0.0 wasn't shown, but the closest compiler version shown was v4.0.1.

    Is CCSv5 showing a download for MSP430 compiler v4.0.1? If so can you try using that version at it should generate compatible section names with the v4.0.0 compiler.

  • 0 in reply to Chester Gillon
    Intellectual 320 points

    i was able to find 4.0.2

    installing now.  will update

    However, i found an original linker file in the clients original folder structure and targeted that instead of the new versions CC5 is offering for my device.  and now 3 out of the 4 projects are working!

    still one to go, but we have made major progress today!