• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 831 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.

nowECC support and roadmap

Jiri Janacek
Genius 3315 points
Other Parts Discussed in Thread: NOWECC, CODECOMPOSER

Dear support,

in this forum post there is mentioned: " But use of nowECC has been replaced by compiler generated ECC... "

Does it mean that TI do not intend to support nowECC as a stand-alone tool for next years? Well, the mentioned forum thread also states: "the next release planned for end of this month (03/2014)" - but will this release not be the last one?

Please may you clarify a situation about nowECC tool? Obviously that is important for customers who do not use CodeComposer. For this kind of users there is another possibility to flash a program with ECC:

- apply the flash API function Fapi_issueProgrammingCommand() which can calculates (auto-generates) an appropriate ECC pattern (if called with the argument Fapi_AutoGeneration) upon given data itself, am I right?

Thanks for your comments in advance,

Best regards, Jiri

  • 0
    TI__Genius 11645 points

    Hi Jiri,

    I will touchbase with our tools team and get back to you on this.

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    TI__Genius 11645 points

    Jiri,

    At the moment nowECC is purely in a maintenance only mode to support critical bug fixes, that too for a very short duration of 3-6 more months which can be confirmed with the tool folks, but certainly  with no plan for enhancements.

    TI  recommends users to move towards using codegen based compiler suite.

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    Genius 3315 points

    Dear KARTHIKEYAN,

    so the nowECC support and maintenance will be definitely terminated in a few months (3 - 6), right? Afterwards newly revealed bugs will not be fixed - what a pity, it is really bad message for users who do not utilize CCS toolchain. Did you mean CodeComposer Studio by your sentence "using codegen based compiler suite.", did not?

    In other words, customers using other compilers cannot fulfill some requirements of the safety manual. TMS570 is certified for up to SIL3 applications - of course, the safety manual instructions must be applied in this case.

    May you suggest another option for users of the different compilers? Possible in-house solution of your customers is not the right way, I guess.

    As mentioned in the previous post "- apply the flash API function Fapi_issueProgrammingCommand() which can calculates (auto-generates) an appropriate ECC pattern (if called with the argument Fapi_AutoGeneration) upon given data itself, am I right?"

    Please may you clarify this point?

    Thanks in advance,

    Best regards, Jiri

  • 0 in reply to Jiri Janacek
    TI__Genius 11645 points

    Hello jiri,

    I would like to stand corrected as we got confirmation from tools team that support will continue for nowECC mainly to cater the customers who are not using CCS.

    In the meanwhile we will also continue to support the CCS based tool chain moving forward.