CODECOMPOSER: Task (tasks.json or .theia-workspace) support in CCS Theia

Hello Eugene,

This feature is currently disabled in CCS Theia/20. However, it is something we can look to enable if it is of interest. Thank you for your feedback.

ki

Hi Ki,

That unfortunate.  Why would you disable builtin Theia functionality? Should probably re-enabled.

Meanwhile,  I have company wide build system and need to integrate its makefiles and source structure into CCS to simplify debugging set up. I can easily bring build system files into standard Theia or VS Code but not CCS.

How would you suggest I do that without tasks and workspace files in CCS?

Regards,

Eugene

Eugene K said:

Why would you disable builtin Theia functionality?

There was some debate about simplifying the user interface to hide/disable functionality that were not commonly used.

Eugene K said:

Should probably re-enabled.

Yes, we looking into doing this in a future release.

Thanks

ki

Hi Ki,

Looking forward for restoration of standard Theia functionality. Which release this is planned for?

Meanwhile there is still the question for CCS 20.01:

I have company-wide build system and need to integrate its makefiles and source structure into CCS to simplify debugging set up so developers can use source files to set BPs. So far, with .theia-workspace file and launch.json for manual project-less debug I had no success at all. How would you suggest doing that?

Regards,

Eugene

Eugene K said:

I have company-wide build system and need to integrate its makefiles and source structure into CCS to simplify debugging set up so developers can use source files to set BPs.

If I understand correctly, you have a external makefile build environment (outside CCS) and you wish to set up an environment to debug the generated executables using CCS. You would need source debug visibility where the source file correlation is set up to set source level BP, etc. Is this correct?  

Yes, and more

1. External makefile is "first level" correct.
2. The target board might have multiple heterogenous TI MCUs (F28, F29, TMS570, MSPM0 etc.) meaning that ccxml file would be custom

How all of this comes into CCS?

Regards,

Eugene

Eugene K said:

The target board might have multiple heterogenous TI MCUs (F28, F29, TMS570, MSPM0 etc.) meaning that ccxml file would be custom

Yes, you would need to create a custom target configuration using the target configuration editor:

https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs/ccs_debug-main.html#advanced-target-configuration-options

The editor is similar to what was available in CCS Eclipse and similar steps apply regarding adding connections and devices:

https://dev.ti.com/tirex/explore/node?node=A__AFwYJhmnwlJWUElGChKuxg__ccs_devtools__FUz-xrs__LATEST

However, the tool in CCS 20 is more limited in that you can only add connections and devices while in CCS 20 had more customizable options of adding routers and cpus instead of devices.

Note that if that ccxml files between CCS 12.x and CCS 20.x are compatible as long as the devices are supported between the two environments.

As for:

Eugene K said:

I have company-wide build system and need to integrate its makefiles and source structure into CCS to simplify debugging set up so developers can use source files to set BPs. So far, with .theia-workspace file and launch.json for manual project-less debug I had no success at all. How would you suggest doing that?

Once you have your ccxml file created. You can launch a project-less debug session for it so that the launch for it is created in the launch.json file. You can also add the source search paths (Run -> Edit Source Paths...) to specify to the debugger where to look for source files when debugging (the debugger will search recursively). This will also be stored in the launch for the ccxml in the launch.json file (in addition to any other debug property settings).

Then the ccxml and launch.json can be shared to other users.