• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 351 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.

are the debugging commands simultaneously applied to each core in multi-core debug mode?

juan jimenez
Intellectual 670 points

Hi all,

I am developing a project with two concerto controllers where both processors must be synchronized.  I use the SYNCI and SYNCO signals provide by the ePWM modules to achieve such goal. Once the sync between processors has been carried out, I continue my debugging process in the Debug View, grouping the two synchronized CPUs to run debugging commands simultaneously in both cores. However, when I pause the debugging session  and watch the value of the register TBCTR for each device, I find it is not the same for both. So, I wonder if:

Is the debugger receiving/applying the commands simultaneously?

Is the expected behavior for the debugger in multi-core session?

How dependable are the values showed in the expression window?

I attach a screenshot obtained from my scope to show the correct synchronization between the two processors. The capture shows the SYNCO output signal in each device.

Regards, Juan.

  • 0
    TI__Guru* 93800 points

    juan jimenez said:
    I am developing a project with two concerto controllers where both processors must be synchronized.  I use the SYNCI and SYNCO signals provide by the ePWM modules to achieve such goal. Once the sync between processors has been carried out, I continue my debugging process in the Debug View, grouping the two synchronized CPUs to run debugging commands simultaneously in both cores. However, when I pause the debugging session  and watch the value of the register TBCTR for each device, I find it is not the same for both

    Hi Juan,

    There is an advisory against the F28M35x where global run does not work properly - instead each CPU is started individually:  www.ti.com/lit/SPRZ357