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.

Biuld Code Generation Tool error

Other Parts Discussed in Thread: MSP430F2350

I created this code and I build it with the Code Generation tool v3.2.1, but I updated it to CGT v3.3.3, and it is giving me the next error:

How do I solve it?

  • The compiler is getting confused as to which identifiers name function parameters and which ones name functions.  Are you sure absolutely nothing changed but the compiler version?  If you could post the preprocessed code (use -ppo) corresponding to function TXhandler, I would probably be able to tell you quickly what the problem is.  My guess is that, for some reason, the macro USCIAB0TX_ISR expands to something different.

  • Actually de CCS version also changed, from v4.1.1 to v4.1.3

    I reintall the CCS with the Code Generation tool 3.2.1 and it´s still giving me an error:

    "Severity and Description    Path    Resource    Location    Creation Time    Id
    This project was created using a version of Code Generation tools that is not currently installed: 3.2.1 [MSP430]. Please install the Code Generation tools of this version, or migrate the project to one of the supported versions.        nueva version AB4 - AutoTCR    properties    1296064103542    720"

    I do not know how to preprocessed the code with the -ppo corresponding to function TXhandler, I will appreciate if you could let me know how should I do it.

    Thanks.

  • Alfredo Beltran said:
    I do not know how to preprocessed the code with the -ppo corresponding to function TXhandler, I will appreciate if you could let me know how should I do it.

    Information on submitting a test case, including the preprocessing step mentioned here, can be found towards the end of the forum welcome message.

    Thanks and regards,

    -George

  • I found some instructions for the preprocessing, but it wan not quote explicit.

    I already found the problem and this is that in the msp430f2350.h library, the interruption vector was commented for a different vector. Here is the code:

    //USCIAB0TX_ISR(TXhandler)
    //__interrupt void TXhandler (void)
    #pragma vector = USCIAB0TX_VECTOR
    __interrupt void USCIAB0TX_ISR(void)
    {
      if (IFG2 & UCB0TXIFG)
        TI_transmit_callback(&UCB0TXBUF);
      else
        TI_receive_callback(UCB0RXBUF);
    }
    //USCIAB0RX_ISR(RXhandler)
    //__interrupt void RXhandler (void)
    #pragma vector = USCIAB0RX_VECTOR
    __interrupt void USCIAB0RX_ISR(void)
    {
      UCB0STAT &= ~UCSTTIFG;                    // Clear start condition int flag
      TI_start_callback();
    }

    Thanks.

  • Alfredo,

    The MSP430 header files include 2 different syntaxes for interrupt vectors, one that supports the older style used in CCEv2 (which is commented out by default) and the newer "#pragma vector=" style which is compatible with other tools like IAR. As you mentioned, you need to make sure the syntax in your code matches with the header file. The header file itself, as provided, is not different between compiler versions 3.2.x and 3.3.x.