• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 1283 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/TMS320F28377D: Problem with common files for 2 CPUs

Aleksey Nevz
Prodigy 210 points
Part Number: TMS320F28377D

Tool/software: Code Composer Studio

Hi. I have two projects (CPU1 and CPU2) for TMS320F28377D. In project for CPU1 I have a source file to work with ePWM (for example). But CPU2 have some functions for that ePWM and thus source file linked to its project.

CPU1-project has predefined symbol "CPU1", CPU2-project has predefined symbol "CPU2_OR_CPU1_ONLY" (in my case).

In CCS Edit perspective I see that predefined symbols work well

Both projects built and work as expected.

But when I try to set a Breakpoint for CPU2-project I have to set it in a source file for CPU1-project because if I try to work with breakpoints in linked source file for CPU2-project I don't see them:

Is it a correct behavior for linked files in two-cores projects or I do something wrong?

Code Composer Studio Version: 7.0.0.00042, Windows 10 Home 1703 build 15063.674.

  • 0
    TI__Guru**** 173310 points

    Aleksey Nevz said:
    Is it a correct behavior for linked files in two-cores projects or I do something wrong?

    When using common source files among multiple projects, the recommended/best practice would be to place those files in a common source folder and link them to all projects, rather than add it to one project (ie place physically within the project folder) and link it to other projects within the same workspace. Keeping it in a common folder outside of the project folders will avoid confusing issues during debugging such as what you are observing. 

    Could you give that a try to see if it helps?

  • 0 in reply to AartiG
    Prodigy 210 points

    Yes, I moved common files to other "empty" project (I created it because I want to open common files via Project Explorer in CCS and see them there - maybe you know better way) and I didn't see any problems during debug session. Thank you.

  • 0 in reply to Aleksey Nevz
    TI__Guru**** 173310 points

    You do not have to create an empty project for the common files. You can place the "common" folder in some directory that is not directly inside a project directory. Then link the folder to both projects. You will still be able to open the files within them via Project Explorer. Any changes made to the files will be saved to that common location and be picked up by both projects.

  • 0 in reply to AartiG
    Prodigy 210 points

    Ok, thanks. I thought I could not open directory with header files via Project Explorer as you can see on the picture below because it includes by Include Options Search Path, but I was wrong (see second picture).