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

CCS/TMS320F28379D: Loading different code into each CPU

Jake Gareau
Prodigy 140 points
Part Number: TMS320F28379D


Tool/software: Code Composer Studio

Hello,

I have a question regarding the dual CPUs, I am looking at the "adc_epwm" example under the dual_cpus folder in control suite. This has 2 projects one for each CPU, and I am just curious can I run 2 separate projects at the same time and do I even need to? I ran both codes individually and they appeared to work but I have done some dual CPU in the past on another platform  and I was required to specify each code to be loaded onto the specific CPU, and from what I can see here I only have the option to load the same code onto each CPU.

Any info is much appreciated, also I have already looked at  and it didnt appear to offer any insight.

  • 0
    Prodigy 140 points
    I have found the solution,

    Step 1: First I clicked on the target configuration that I was using for both projects, next I hit the green bug button to launch a projectless sessions

    step 2: The debug window that pops up has a list of the CPUs, I right click on the CPU I want to use and click "connect to the target" this establishes connection

    step3: Next you need to go to the top menu and click the run tab which opens a menu , here you want 'Load' next you find 'load program'

    step4: select the .out file associated with the program you want to run. (you may need to browse for it, but it should be in the same project folder)

    step5: repeat steps 2 through 4 for each additional core/cpu
  • 0 in reply to Jake Gareau
    TI__Guru**** 473961 points
    Hi Jake,
    Yes that is the recommended way. To be able to use 2 different executables from different projects, you need to use a project-less debug session launch.

    ki