• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 5 replies
  • Subscribers 55 subscribers
  • Views 1719 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CSS Theia IDE support for C2000 DSPs

Tery Shen
Prodigy 20 points

Hi.

I would like to ask when will be added support for C2000 and other MCUs in CCS Theia IDE based on VSCode?


Thanks.

  • +1
    TI__Genius 16490 points

    Hi Tery,

    CCS Theia support for C2000 is not yet feature complete. We are working to add missing features that are specific to the various device families. Each family will be officially supported as it reaches feature completeness. This will happen throughout 2024 with most activity in the first half.

  • 0 in reply to AndyW
    Intellectual 902 points

    Is there any where we can follow this progress? webPage/Wiki/twiter/youtube/maillist/newsletter/...

    Also I would like see some kind of road-map. Like what is going to be just like in old CCS? What is changed to do in a new way? What will not be available in Theia? What will be new?

    What is coming first and last  A.S.O.

    What are the major design thinking behind the change?

    Practical changes, like can we reuse existing .projectspec files?

    Conceptual changes, like will we get rid of the strange import of projects that you inherited from Eclipse?

    Will it only be supported as a complete package (including some version of vscode) or will it also be supported as a plugin to my own version of vscode?

  • +1 in reply to Martin Otzen
    TI__Guru**** 464611 points

    Official support for C2000 in CCS Theia is be available starting with version 1.3.0 (January). However, we do have special versions that have support for C2000 (and other) devices. If you wish to be an early adopter and experiment with these versions, please start a private E2E conversation with me.

    Martin Otzen said:
    Like what is going to be just like in old CCS?

    The IDE update is the biggest change as we are based off a new IDE. Hence the look and feel will be quite different. However much of the underlying functionality will remain the same.

    Martin Otzen said:
    What are the major design thinking behind the change?

    The Eclipse IDE framework that CCS Eclipse is based off is getting dated. The Theia IDE framework the CCS Theia is based on is a much more modern IDE. It is also based off VS Code, which is very popular.

    Martin Otzen said:
    Practical changes, like can we reuse existing .projectspec files?

    Yes. All your current CCS Eclipse projects can be imported into CCS Theia (assuming that the device the project is based on is supported in CCS Theia). The project format has not changed much between CCS Eclipse and CCS Theia, making for a smooth project migration experience.

    Martin Otzen said:
    Conceptual changes, like will we get rid of the strange import of projects that you inherited from Eclipse?

    Not sure what exactly you are referring to here but the project system between the two versions remain mostly the same.

    Martin Otzen said:
    Will it only be supported as a complete package (including some version of vscode)

    Note that we are not based directly off VS Code. We are based off Theia (which in turn is based of VS Code).

    Martin Otzen said:
    will it also be supported as a plugin to my own version of vscode?

    This is on the roadmap for some time in the second half of 2024.

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 902 points
    Ki said:
    If you wish to be an early adopter and experiment with these versions, please start a private E2E conversation with me.

    Done  :-)

    Ki said:
    Yes. All your current CCS Eclipse projects can be imported into CCS Theia (assuming that the device the project is based on is supported in CCS Theia). The project format has not changed much between CCS Eclipse and CCS Theia, making for a smooth project migration experience.

    Please note that I pointed to the .projectspec format.

    I sincerely do not hope that the .cproject format (inherited from the eclipse.cdt) is preserved, it is horrible. Looks like cdt developers have just dumped entire dialog classes into the xml, leading to huge amount of unneeded information, triggering changes because you did something in the GUI entirely unrelated to the project, creating wastefull noise in the version system a.s.o.

    The messy .cproject files was a major reason for us to shift to the .projectspec format.

    Ki said:
    Martin Otzen said:
    Conceptual changes, like will we get rid of the strange import of projects that you inherited from Eclipse?

    Not sure what exactly you are referring to here but the project system between the two versions remain mostly the same.

    On almost all other IDE's you "open" a project. While i do like Eclipse, the import project into workspace has been a nuisance the whole time.

    Combined with the fact that you cannot have two projects of same name in a workspace, has lead to the practice of having a workspace for each task reflecting the branch in git for that task. That again means that settings stored in one workspace do not always survive to the next.

    Also the historically (as in eclipse history) mess of  some settings is in the workspace others in the project, but with no clear definition of what goes where. Example I did once setup the error parser to parse error messages from doxygen, worked like a charm until I realized that the settings was split between the workspace and the project, so if imported into a new workspace it would break :-(

  • +1 in reply to Martin Otzen
    TI__Guru**** 464611 points
    Martin Otzen said:

    Please note that I pointed to the .projectspec format.

    I sincerely do not hope that the .cproject format (inherited from the eclipse.cdt) is preserved, it is horrible. Looks like cdt developers have just dumped entire dialog classes into the xml, leading to huge amount of unneeded information, triggering changes because you did something in the GUI entirely unrelated to the project, creating wastefull noise in the version system a.s.o.

    The messy .cproject files was a major reason for us to shift to the .projectspec format.

    Nothing has changed in this respect. Note that a .projectspec file is simply a template that is used on first import to CCS. Once imported, a full CCS project is created (including a .cproject file)

    Martin Otzen said:
    On almost all other IDE's you "open" a project. While i do like Eclipse, the import project into workspace has been a nuisance the whole time.
    Martin Otzen said:
    Combined with the fact that you cannot have two projects of same name in a workspace

    Nothing has changed here either with CCS Theia.

    Martin Otzen said:
    Also the historically (as in eclipse history) mess of  some settings is in the workspace others in the project, but with no clear definition of what goes where.

    Much of this remains also, though the workspace functionality did get quite an overhaul.

    https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs_theia/ccs_ide.html#settings-tabs

    https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs_theia/ccs_project-management.html#workspaces