• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 763 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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 behaviour on IAR imported project.

Roberto Romano
Guru 27285 points
Other Parts Discussed in Thread: MSP430G2553

 I decided to migrate away from IAR is win hosted to CCS on Linux only, so I copy'd all files of a working project to workspace new created empty project and migrated incompatible directive but strange error and warning still are unsolvable.

 Compiler CCS  Version: 6.1.0.00104

 target MSP430G2553  32-QFN

 OS Linux Mint Rafaela 17.2 64 bit

 Messages point to lines are correct where no error exists, code was ok. Also warning and messages errors refer to different files. Many files reported there was no new line @ end of file.

  I corrected a lot of compiler related like

//#include "io430.h"
#include <msp430.h>
 but no success and I have no real idea how to point to offending code or trouble, splitting line where warning and error are simply shift the twin Err-warning also hitting comments.

 Can be files have to be converted to unix format than dos one? Code is proprietary and cannot be posted on forum.

after adding new lines and splitting where nonsense error is pointed to location move relative to added lines:

can someone point me how to remove this issue? I can send isolated offending project files with NDA and confidential only to developer team.

 Edit: after compiling one processor core got loaded to 100% by CCS, I was not able to identify process name just don't finish job like a loop somewhere, CCS IDE is not locked and still responsive but processor fan get on and I need shut down CCS and restart. Restarting remove processor core overload for some time.

  • 0
    Guru 27285 points
    First catch from code:
    __monitor
    void setencodersetpoint(long int x);

    this clause get TI compiler messed UP, is some similar primitive present on TI compiler to try migrate code seamless?
    It can be solved and I know how to do it but having this available inform compiler too how code has to be generated and can optimize better than hand coded lock.
  • 0 in reply to Roberto Romano
    TI__Guru**** 173310 points

    Roberto Romano said:
    First catch from code:
    __monitor
    void setencodersetpoint(long int x);

    this clause get TI compiler messed UP, is some similar primitive present on TI compiler to try migrate code seamless?

    There is no keyword equivalent to __monitor supported by the TI compiler, but this post may be helpful. Also the Compiler Users Guide lists all the pragmas supported by the TI compiler.