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.

430BOOST-SHARP96_OutOfBox build errors

Other Parts Discussed in Thread: MSP-EXP430FR5969, MSP430WARE

Hi,

After importing from C:\ti\msp430\MSP430ware_1_80_01_03\examples\boards\MSP-EXP430FR5969\Software\430BOOST-SHARP96_OutOfBox and trying to build with CCS v6.0.0.00190 I have errors

>> Compilation failure

undefined first referenced

symbol in file

--------- ----------------

HighScore ./UpdateDisplay.obj

error #10234-D: unresolved symbols remain

error #10010: errors encountered during linking; "430BOOST-SHARP96_OutOfBox.out" not built

gmake: *** [430BOOST-SHARP96_OutOfBox.out] Error 1

gmake: Target `all' not remade because of errors.

  • attached is full console output

    6813.Console.txt

  • The big bunch of warnings you can ignore (they are not nice from TI!).

    Your only problem is HighScore becomes not defined. It should be defined at the begin of the source file ‘Game.c’. Try if it works when you add these two lines to the end;

    #else

    unsigned long HighScore;

    In total it will be then;

    #pragma location = 0xF004
    #if defined(__IAR_SYSTEMS_ICC__)
    __no_init unsigned long HighScore;
    #elif defined(__TI_COMPILER_VERSION___)
    #pragma NOINIT(HighScore)
    unsigned long HighScore;
    #elif defined(__GNUC__)
    unsigned long HighScore __attribute((section ("HIGHSCORE_DATA")));
    #else
    unsigned long HighScore;
    #endif
    

     

  • I spotted the same issue and have already reported it to TI.

    The problem is in the line "#elif defined(__TI_COMPILER_VERSION___)", which has an extra underscore at the end. Instead it should read "#elif defined(__TI_COMPILER_VERSION__)".

  • Sharp eyes!

    And for me strange was that CCSv5 doesn’t have a problem with it.

  • my errors were different but for a 30$ investment I'm not willing to spend 3 hours figuring it out. I guess I will start from the blink example (which worked) an build from there cause the code composer package is so huge that someone with plain old C experience could get lost in the environment forever. My experience tells me its much wiser to crawl successfully then attempt to run on your first trial out of the gates!

    Thanks anyway

  • The double underscore problem mentioned is not my problem cause changing it to a single just created more errors

  • DENIS LEBEL1 said:
    The double underscore problem mentioned is not my problem cause changing it to a single just created more errors

    Maybe because it was a triple underscore that needs to be changed to a double, and not a double changed to single?

**Attention** This is a public forum