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.

F29H85X-SOM-EVM: CCSv20 Theia vs CCS Theia 1.5.1: What version to use for F29H85X-SOM-EVM?

Part Number: F29H85X-SOM-EVM

Tool/software:

Team,
Apparently both CCSv20 and CCS Theia are based on the Theia framework. CCSv12.8.x is based on Eclipse.
-What version should be used moving forward for F29H85 development?
-Will the C29 compiler, C29 device support and C29 feature metadata available available on the three CCS versions mentioned above?

The CCSv20 release notes is not available online so it is difficult to understand the difference with CCS Theia 1.5.x:
https://www.ti.com/tool/CCSTUDIO

-Regarding admin rights for SDKs installation:
Must every SDK (like MCU-SDK-F29H85x_1.00.00.00_EA2) be installed using the installer?
Or can the different components be recognized by CCS automatically (if they are copied over from another machine and assuming that the CCS version has support for the given device family)?

Thanks in advance,
Anthony

  • Hi AnBer,

    Great questions, I hope this answer will serve as a reference for you and future E2Ers, specifically in regard to F29H85x Slight smile

    -What version should be used moving forward for F29H85 development?

    Moving forward, CCS 20 should be used for F29H85x development as well as other devices (including F28x and future C2000 devices). CCS Theia was created to intermediately support F29H85x between CCS Eclipse and CCS 20 during these earlier milestones and will eventually be removed. 

    -Will the C29 compiler, C29 device support and C29 feature metadata available available on the three CCS versions mentioned above?

    These features are available only with CCS 20 and CCS Theia, but CCS 20 is the only CCS that will have continual support and updates done in regard to F29x.

    The CCSv20 release notes is not available online so it is difficult to understand the difference with CCS Theia 1.5.x:
    https://www.ti.com/tool/CCSTUDIO

    See above. CCS 20 is "CCS Theia-based", so the appearance and basic functionality is very similar, if not the same. 

    Must every SDK (like MCU-SDK-F29H85x_1.00.00.00_EA2) be installed using the installer?
    Or can the different components be recognized by CCS automatically (if they are copied over from another machine and assuming that the CCS version has support for the given device family)?

    The SDKs should be installed using the installer to ensure all the updates to software examples, libraries, etc. are reflected in your system. CCS specifically provides device support to actually work with various devices in the IDE. This the F29x SDK release notes where you can find what is/is not supported, device support, tool dependencies, etc: F29H85x-SDK: Release Notes 1.00.00.00

    Best Regards,

    Aishwarya

  • Hi Aishwarya,

    AnBer question was raised following a question from my side (he is our FAE).

    Regarding your last point, is the installer doing anything else than uncompressing data and putting it in the right place ?

    In the past (some years ago), you used to provide these things as zip files, which was a good thing.

    I am in a big company and we have strict IT rules and installing something is not a simple process obviously. We have to go through a set of decision boards. Such a process for "just" a set of libraries and examples is clearly a burden. Especially when you provide regular releases.

    As far as possible, you should provide an archive link for those among us that don't have the flexibility of click/install.

    Clément

  • Clement,

    As of now, we are planning to only have installers for the SDK, but this is good feed back and I will relay it to the team.

    Best Regards,

    Aishwarya 

  • Clement,

    Apart from the installers, the SDK will be hosted on dev.ti.com where you can download it as a zip file. 

    Also, we are working on setting up a GitHub repo where this SDK will be available . There will be few components like EtherCat stack which will not be available on GitHub since it uses a commercial lioense.

    Best Regards

    Siddharth

  • Hello,

    Thank you for the feedbacks, that's giving us a set of acceptable options to get access.

    Clément

  • Anthony,

    Here is the complete list of installation options across three platforms (including zip file download option), hope this helps:

    Aishwarya