CCS/RM46L852: Launch (debug) configuration portability

dduncan said:

• The launch configuration does not connect.
• Target Configuration in the Launch Configuration is "${project_loc:[project_name]}\targetConfigs\RM46L852_XDS200.ccxml"

This seems to indicate that the target configuration file is actually physically inside the project folder. Is that the case here, or was the target configuration file linked to the original project?

The idea behind the steps described in that page is to convert the absolute path of a linked target configuration file to a path relative to a variable. I see that following those steps converts the path to be relative to the variable TI_PRODUCTS_DIR. This should allow the path to get resolved properly even if the project were imported to another workspace. 

If you could provide more details on your set up, how exactly you configured the target configuration and debug launch configurations in the original project and what they look like after moving to another workspace, it would help us better understand and possibly reproduce your issue.

The target configuration file was inside the project folder, and then linked per the instructions.

I tried moving the target configuration outside of the project folder. Then after converting to relative, under 'Linked Resources' I can see RM46L852_XDS200.ccxml with a location of "PROJECT_LOC\..\targetConfigs\RM46L852_XDS200.ccxml". This move appears to be insignificant, in that under Debug Configurations, on the Main tab the project referenced by ${project_loc:[project_name]} is still recognized, just adding an extra "\.." to the linked-resource relative path.

The problem appears to occur under the Program tab, that when the project is selected (which sets the Program field to ${build_artifact:[project_name]}), this adds a few lines with absolute paths. Or at least after this is checked out into a new location, even after re-importing the Project and Program fields under the Program tab are blank.

Sorry about the delayed reply. I was out of the office for a few days.

dduncan said:

The problem appears to occur under the Program tab, that when the project is selected (which sets the Program field to ${build_artifact:[project_name]}), this adds a few lines with absolute paths. Or at least after this is checked out into a new location, even after re-importing the Project and Program fields under the Program tab are blank.

I am still unable to reproduce this. I tried recreating it by creating a simple project with a linked target configuration file. The Main and Program tabs in the debug configuration look like below.

If I then import the project into a different workspace, launch a debug session and check the Debug Configuration, the Main and Program tabs contain the same information as shown above.

dduncan said:

Or at least after this is checked out into a new location, even after re-importing the Project and Program fields under the Program tab are blank.

Is it possible that the Device field got inadvertently set to IcePick or Dap? If so the Project and Program fields are expected to be blank. For the CortexR4 device it should have preserved the original values.