• State Resolved
  • Replies 8 replies
  • Subscribers 99 subscribers
  • Views 139 views
  • Users 0 members are here
Support feedback
Options
Options
Related

CCSTUDIO: Link to wrong file for definition if they are the same name in different projects in the same workspace

Wayne Huang
Genius 16325 points
Part Number: CCSTUDIO
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Hi champs,

I am asking this for our customer.

The user reported CCS 20.2 seems to link to wrong file for definition if the files are in the same name in different projects.

Steps to reproduce this issue.

Step 1: Open several examples together in a workspace

Import three ADC example codes from TI C2000ware

C:\ti\c2000\C2000Ware_5_04_00_00\driverlib\f28p55x\examples\adc

Like this, and notice there is a device.c for each project.

Step 2:

Go to a function call like 

Device_init();
 

Go to the definition of Device_init();

You should see it correctly goes to device.c in

~\adc_ex12_burst_mode_oversampling\device\device.c

Step 3:

Repeat the above in another project like adc_ex10_multiple_soc_epwm.c.

Go to its definition of Device_init();

Then, you will see it still links to Device_init(); in the device.c in ex12 rather than that in ex10.

In other words, CCS links to the wrong definition in ex12, and it's supposed to be that in ex10.

Would you please clarify this and see if you can reproduce this on your side?

If yes, this is a critical issue because the user has been troubled by it for some time.

Note that the user tried to put projects in different folders of the workspace, but it did not help.

  • 0
    TI__Genius 10265 points

    Hello,

    I've seen this issue in my projects before as well. The only way I've been able to fix this is by keeping the projects in completely different workspaces.

    Let me loop in the CCS team to comment on how these definition links are resolved.

    Best,

    Matt

  • 0 in reply to Matt Kukucka
    TI__Genius 16325 points

    Hi Matt,

    Would you please elaborate what it means by "keeping the projects in completely different workspaces"?

    So far, we tried to save workspace in a different workspace name, but it failed.

    Use different folders (Multi-Root Workspace) and it failed.

    It seems CCS uses only one workspace which stores the last environment setting no matter that we save it in another name or load another workspace name.

  • 0 in reply to Wayne Huang
    TI__Guru**** 464431 points

    Wayne,

    Wayne Huang said:
    Would you please elaborate what it means by "keeping the projects in completely different workspaces"?

    Based on your first screenshot it looks like the customer once had a multi-root workspace environment and then removed one of the roots (folder) to have a single root workspace save to the workspace file. That single root (20250627_CCS2020_F28P55x_newProject) contains three projects.

    Is that correct?

  • 0 in reply to Ki
    TI__Genius 16325 points

    Hi Ki,

    That's correct.

    The user had two tests independently. One is with MSPM0 using multi-root workspace and the other is with C2000 using single root containing three projects. Both tests have this issue.

  • 0 in reply to Wayne Huang
    TI__Guru**** 464431 points
    Wayne Huang said:
    the other is with C2000 using single root containing three projects. Both tests have this issue.

    Can you try a pure single root workspace environment inside of the environment you currently have where it originally was a multi-root environment with on of the roots removed? Basically use the option to open a folder to the folder containing the three projects. The environments sounds similar but there are actually treated differently by CCS under the hood.

  • 0 in reply to Ki
    TI__Genius 16325 points

    Hi Ki,

    I tried with a pure single root workspace environment by using File->Open Folder and imported two C2000 example projects below.

    The result still failed and is the same as the above.

    Note that the user and I have done three independent tests using MSPM0 and C2000 examples, and we can reproduce it easily.

    It still links to the wrong definition.

    BTW, if I deleted adc_ex10 above and left only one project adc_ex1 above, then the linking could be correct. That is, it seems when more than one project are imported in the same workspace, then this issue can happen.

  • +1 in reply to Wayne Huang
    TI__Guru**** 464431 points

    Thanks for trying. I was able to reproduce the same issue with both CCS 20.2.0 and the CCS 20.3.0 beta. I filed a bug for this. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-12900

    Thanks

    ki

  • +1 in reply to Ki
    TI__Guru**** 464431 points
    Ki said:
    Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-12900

    Note that this was already a known issue: https://sir.ext.ti.com/jira/browse/EXT_EP-12902

    It is currently targeted for the CCS 20.4.0 release at the end of the year.