• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 500 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.

MSPM0G3505: Building and debugging a DriverLib application in dev container (or WSL)

J.R
Prodigy 60 points
Part Number: MSPM0G3505

Tool/software:

I've been working on an application for MSPM0G3505 MCU using CCS Theia 1.5.1.

My observations are that Theia is OK for tinkering with the platform and to compile the sample applications, but it's not really a tool for long-term application development, which requires for example dev containers to unify the build- and development environments among multiple developers and CI pipelines. It does all the things that matter behind the curtains, so it's hard to resolve the problems when things go wrong. Even the IDE itself freezes quite often, which makes it unusable for real work (the tool just freezes completely, as described here https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1362288/ccstudio-ccs-theia-crashing).

Therefore I would like to migrate the project into a dev container running on WSL. I can find downloads for TI Clang compilers, MSPM0 SDK and even "TI Embedded Debug for VS Code" add-on for VSCode, but it's really hard to find binding instructions for setting up the project that use these tools in any other way than the "recommended way" of using CCS Theia.

So, are there any up-to-date and all-in-one instructions and perhaps project-templates to set up a build- and development environment:
- configure CMake (or similar, standard build system) to use the MSPM0 SDK and TI Clang or GCC compilers (in Linux)
- debug the application using VSCode and for example XDS110 (using WSL or dev container environment, not in native Windows)

  • 0
    TI__Guru**** 463901 points

    Hello,

    We certainly intend CCS to be used for long-term application development also. Note that CCS Theia is our first iteration of the Theia IDE based environment so we admittedly went through some growing pains. We hope to resolve most of them with the upcoming CCS 20 release in a few weeks,

    J.R said:
    Therefore I would like to migrate the project into a dev container running on WSL. I can find downloads for TI Clang compilers, MSPM0 SDK and even "TI Embedded Debug for VS Code" add-on for VSCode, but it's really hard to find binding instructions for setting up the project that use these tools in any other way than the "recommended way" of using CCS Theia.

    WSL is not an officially supported environment for our tools. It is a common one through and many people have successfully used it but we don't have much collateral for it.

    J.R said:
    "TI Embedded Debug for VS Code" add-on for VSCode

    Please note that we are in the early stages of supporting this feature. Basic debug functionality is there but there are a lot of gaps compared to CCS. We really do recommend full CCS for "real" development.

    J.R said:
    So, are there any up-to-date and all-in-one instructions and perhaps project-templates to set up a build- and development environment

    None that I am aware of. I will bring this thread to the device/SDK experts who may have more experiences to share.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 60 points

    Waiting for the next release then.

    - VS Code works well with dev containers
    - TI already provides Linux-versions of compilers and SDK kits that run in WSL (and dev containers)
    - Theia is based on VS Code

    So, the problem might just be the lack of "official support" (by support I mean documentation).

  • 0 in reply to J.R
    TI__Guru**** 463901 points
    J.R said:
    So, the problem might just be the lack of "official support" (by support I mean documentation)

    Besides that, there is no official testing using WSL and containers. At least for host tools as I can't speak for the SDK.

  • 0
    TI__Genius 14892 points

    Hi J.R,
    There are makefiles in the SDK that allow the user to rebuild some libraries, but nothing to the extent that you are looking for. The software team intends that CCS will be used for long-term application development and is working on improving the TI Embedded Debug plugin for VSCode.
    Best Regards,
    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    Prodigy 60 points

    Yes, and I can confirm the application can be at least built in the container using makefile, but the debugger support is still a question.

    At least it's not a problem for competing manufacturer's chips and tools, as I debug those all the time in containerized environments.