• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 81 subscribers
  • Views 93 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.

TMDSCNCD28379D: Renaming multi-cpu project

Ehsan Qiyassi
Prodigy 70 points
Part Number: TMDSCNCD28379D
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi,

I would like to be able to create a project that could be run on two CPUs. There's "sci_ex2_sysconfig" example in the library that is very similar to what I would like to do. I had trouble creating projects from the scratch with all the hooks and configs that could be run similar to this example. Alternatively, I tried to rename the three projects in this folder to re-use them as the basis of my new project and even that failed. I have renamed the "sci_ex2_sysconfig_multi" and "sci_ex2_sysconfig_cpu2" successfully and confirmed that the project could still be built and debugged as the original example. However when I rename the "sci_ex2_sysconfig_cop1", the links to target configuration file breaks and manually pointing to it does not result in the same simple debugging experience from the project "sci_ex2_sysconfig_multi". Any advice on how to do this? If you believe this should be simple, please provide the step by step instructions.

I am using CCS 12.8.1 on Windows 11.

Thank you in advance.

  • 0
    Prodigy 70 points

    I should add what I mean by the 'simple debugging experience':

    I could use: Debug As -> 1 Code Composer Debug Session, from 'sci_ex2_sysconfig_multi', which builds and loads both project 'sci_ex2_sysconfig_cpu1 and _cpu2'. They would appear as two separate projects that could be rung/debugged.

  • 0
    Prodigy 70 points

    After fourth attempt I was finally able to rename the project. I didn't do anything out of ordinary but it seemed like the steps that CCS was taking to rename and update the project were affected by some environmental variables and therefore inconsistent. So I started using new workspaces and rename each part of the project one by one until everything was finally renamed.