• Locked Locked
  • Replies 1 reply
  • Subscribers 52 subscribers
  • Views 659 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: Issue with loading program on to CPU2

Ryan47
Prodigy 50 points
Part Number: TMS320F28377D
Other Parts Discussed in Thread: CONTROLSUITE

Tool/software: Code Composer Studio

I am currently using the TMS320F28377D processor on CCS6.1.3. I'm using a Blackhawk BH-USB-200 debugger. I have an intermittent problem after loading the program to CPU2. 

Immediately after using the "Load program option for both CPU1 and CPU2, I open the expression window to watch the various processor variables. The values for all the variables on CPU2 are completely out of the expected range. The program on CPU2 does not then run as expected. It's as if some of the constants being used are out of range.

Sometimes I can reload the same .out file again and it can fix the issue however lately it has become harder to remove the issue. 

It appears to me as if the debug information is somehow out of sync with the program loaded to the processor. I'm not sure how this can happen sometimes but not always.

Any suggestions on what to investigate would be very helpful.

  • TI__Guru**** 173310 points

    Here are some suggestions to help you investigate what may be going on. 

    First I would suggest loading/debugging an example project from ControlSuite to verify functionality. This will help isolate if the issue is within your project settings or somewhere in the hardware environment and/or debug procedure.

    If the example projects work fine, then I would suggest comparing your project's Debug and Flash settings with the example's settings, specifically for CPU2 (Project Properties->Debug).

    If you are using the Debug (bug icon) button to launch your debug sessions, you could instead try a manual launch and perform the sequence of steps manually to reset/load/run code into the two cores. Please refer to this forum post for details.

    If the above suggestions do not help resolve the issue, I would suggest posting to the C2000 forum as well so the experts there can also chime in with their suggestions.