• State Resolved
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 82 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

TMS320F28375D: Dual Core Sysconfig Project Setup

Scott Weaver
Prodigy 10 points
Part Number: TMS320F28375D
Other Parts Discussed in Thread: C2000WARE, SYSCONFIG

Tool/software:

Hello!

Device: F28375D

C2000Ware version: 5.01

CCS version: 12.6.0.00008

I have an existing single core (cpu1 only) project with Sysconfig generating various files. This project uses .project +.cproject files, NOT .projectspec.

I am trying now to now split this project into two cores. I have created two different .syscfg files, one with --context "CPU1" and the other with --context "CPU2". I tried two methods:

1) creating a single project with two different build configurations. CPU1 configuration excludes the CPU2 syscfg. CPU2 configuration excludes CPU1 syscfg.

2) creating two projects, one for CPU1 and one for CPU2, each with their corresponding syscfg files.

In both cases, I'm having the following issues:

a) clocktree.h doesn't get generated by the CPU2's syscfg, the CPU2 project does not have access to clock constants.

b) ipc / interrupt settings show warnings, indicating that the settings cannot be checked correctly without the context of the other CPU.

c) I cannot see the CPU1 and CPU2 tabs to allow editing multi-core syscfg mode. I see many online resources referencing these tabs.

These problems all seem to be caused because the 2 syscfg files do not seem to be aware of each other.

I noticed that in all of the dual core example projects I have seen, .projectspec files are used to define two separate projects (CPU1 and CPU2) in the same .projectspec file.

Are we required to use the .projectspec file, with two separate projects for each CPU, in order to use syscfg in dual-core mode? Or can we use the .project + .cproject files (either 1 project with 2 configurations, or 2 separate projects)?

  • +1
    TI__Mastermind 34685 points

    Hi, 

    For a multi-core project, it has to be a system project with two projects for each core. 

    Pls refer this link

    https://software-dl.ti.com/ccs/esd/documents/application_notes/appnote-system_project_debug_launch.html

    Best Regards

    Siddharth

  • 0 in reply to Siddharth Deshpande
    Prodigy 10 points

    Thank you, this is exactly what I was looking for!

    This works fine when I set CPU1 and CPU2 to use different projects.

    However, whenever I set CPU1 and CPU2 to use the same project (but two separate cpu-specific build configurations), I encounter the following issue:

    Whenever I attempt to build CPU1's build configuration, it works fine. When I attempt to build CPU2's build configuration, it automatically switches to CPU1's build configuration and builds that. Therefore, when I try to debug, it attempts to build CPU1&2 build configurations, but in reality only builds CPU1 build configuration, and thus the CPU2 binary does not exist.

    When I close the system project, then this behavior stops (I can build cpu1 and cpu2 build configurations separately). But then I am back at the same issue as before (where CPU2 build configuration has no context of the CPU1 autogenerated code).

    Should I expect to be able to use the same project with two separate build configurations for each CPU? Or am I required to use separate projects for each core?

    Thanks you!