• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 52 subscribers
  • Views 892 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.

CCS5 system settings

Viktorija Cecil
Genius 17961 points

Team,

When I installed the v5 CCS and imported an existing project, did it carry over the system settings for the project (such as compilation settings) that i had on v4?

Also, does the v5 indicate that the IDE was updated, the compiler or both?

We are cycle testing our new products, and we have a  seemingly random problem where the LM3S315-IQN25-C2T processor faults somehow (tripping the WDT).  It appears to be one of those elusive, random problems that isn’t reproducible.  After compiling a unit with v5, the problem (so far) seems to have gone away?!?

Any thoughts to this?

Thanks

Viktorija

  • 0
    TI__Guru**** 420590 points

    Hi Viktorija

    Viktorija Cecil said:
    When I installed the v5 CCS and imported an existing project, did it carry over the system settings for the project (such as compilation settings) that i had on v4?

    It should carry over all the project settings like build options unless you are moving to a new compiler which does not support some older options (that would be documented in the migration log)

    Viktorija Cecil said:
    Also, does the v5 indicate that the IDE was updated, the compiler or both?

    Are you taking about automatic updates in CCS? CCS will always notify you that an update is available and never automatically silently update it for you.

    Viktorija Cecil said:
    We are cycle testing our new products, and we have a  seemingly random problem where the LM3S315-IQN25-C2T processor faults somehow (tripping the WDT).  It appears to be one of those elusive, random problems that isn’t reproducible.  After compiling a unit with v5, the problem (so far) seems to have gone away?!?

    If you used the newer compiler that comes in v5, it could be that an update in the compiler resolved the problem. If the rest of the build options remained the same, that would be the answer that makes the most sense.

    Thanks

    ki