• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 84 subscribers
  • Views 1407 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.

Code Composer not connecting to CPU2 - TMS320F28377D

Avinassh Bhavananthi
Intellectual 315 points

Other Parts Discussed in Thread: TMS320F28377D

I am trying to connect to CPU2 on TMS320F28377D MCU using TI debugger (XDS100v2). I am able to connect it to CPU1, erase and perform Blank Check. However, if I try to connect to CPU2 by changing the Core Selection to CPU2(slave), then it still is connecting to CPU1 and overwrites my setting as well. Please see attachment.

  • 0
    TI__Guru* 93800 points
    Avinassh,

    I've asked someone familiar with the plug-in to look into your question. You should hear back soon.

    Regards
    Lori
  • 0
    TI__Guru** 116591 points

    Avinassh,

    In the console it is showing CPU1 only and not CPU2. Please double check the core you have selected. If you are indeed selecting the CPU2 but console is showing  CPU1 then it could be possible that your workspace is corrupted. In that case I would suggest to switch to new workspace and try it again.

    Also what CCS version you are using?

    Regards,

    Vivek Singh

  • 0
    TI__Genius 13125 points

    Avinassh,

    The Core Selection option you are modifying ("CPU1 (Master)" and "CPU2 (Slave)") is an On-Chip Flash option to help the flashing code determine which core it is writing to. But this option does not control which core you are connecting to if debugging a project in CCS.

    Please view the following YouTube tutorial video to get more information on how to set up your project for multi-core debugging.

    Please let me know if you have any questions on this.


    Thanks,

    Ricky

  • 0 in reply to Ricky Lau
    TI__Guru** 116591 points
    Avinassh, Were you able to get this working?

    Vivek Singh
  • 0 in reply to Vivek Singh
    Intellectual 315 points

    Hi Vivek,

    No. The issue is still not resolved. I had no time to try the procedure you propsed.

    Since we were running out of time, we implemented in such a way that CPU1 needs to be programmed first with proper application before programming CPU2.

    Regards,

    Avinassh.