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.

IAR to CCS migration

 

Hi,

Can you please upload IAR to CCS migration manual?

I saw it a few days ago at one of the posts here and I can't find it now.

Also, please direct me to the CCS user guide data base.

 

Thanks,

Yael

  • Yael,

    The CCS Users Guide for MSP430 includes the topics for migrating from IAR to CCS.

    You search the www.ti.com website and for specific Users Guides thay you're looking for. The Embedded Processors wiki is another great resource for information:
    http://processors.wiki.ti.com/index.php/Main_Page. From here you can access many resources for getting started with CCS.

    A great starting page for compile information is http://processors.wiki.ti.com/index.php/TI_Compiler_Information. This wiki page also has links to the MSP430 Compiler and Assembler/Linker manuals.

  • Hi,

    Is there any CCS User'd Guide for v5?

    The one you supply a link for is for v4.2.

    I tried looking at ti.com or at the wiki but all I find is for v4.

    Thanks,

    Yael

  • Yael,

    That is the latest version of that particular Users Guide. CCS4 and 5 are quite similar, so most of the information in that book should be relevant to CCSv5 as well.

    If you're looking for general information on CCSv5, this wiki is a great resource for getting started:
    http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5

  • The CCS Users Guide for MSP430 (for IAR to CCS migration) does not mention any of the following attributes.

    __interrupt void timera0_isr(void)
    __monitor uint16 my_function(void)
    __noreturn void my_function(void);
    __task void my_function(void)
    __data16 char *my_ptr;
    __data20 char *my_ptr;
    __no_init volatile uint32 my_var @ MY_VAR_ADDR; 

    The guide states "#pragma vector =" is supported, but no mention of __vector.

    __monitor is not mentioned, but I believe the solution is to explicity place _disable_interrupts(); and _enable_interrupts(); calls around the section of code that needs protection.

    __noreturn can be use the "#pragma FUNC_NEVER_RETURNS".  I use "#define __noreturn _Pragma(FUNC_NEVER_RETURNS)

    __task is not mentioned.  Anyone know the equivalent for __task ??

    __noinit is not mentioned.  I put the variable in the linker script along with the fixed memory address

    __data16 and __data20 is not mentioned.  Anyone know how to port these??  Just use uint16 and uint32 types ??

  • Keywords like __monitor are not supported by the TI MSP430 compiler.  There are some pragmas with similar names.  Those pragmas are as close as you'll get to these features in the TI compiler.

    Thanks and regards,

    -George