• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 551 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 v4.1 EVMC6474 Muti Core: How do you connect projects to each core?

Eddie3909
Guru 10385 points

Hi

I've been reading http://tiexpressdsp.com/index.php/Multi-Core_Debug_with_CCS and it doesn't tell one how to connect a core to a project. I'm trying to do what I could do in CCS v3.x where I could open core 1A and its project proj1A, and then open core 2A and its project proj2A. When I hit the File reload in CCS v3, the correct .out is loaded.

In CCSv4, I created Multi Workbench windows using Window->New Window', and then set the active project in window A to proj1A, and window B to proj2A.

Hitting the reload button in either window wants to load the last loaded .out irregardless of the active project. For example, if hit the load button in the debug perspective for window A, and I select proj1A.out, then I go to window B and select the load button, it wants to load proj1A.out. Shouldn't it default to proj2A.out?

I found Brad Griffis's webinar very helpful for single core debug (http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/3344/11807.aspx#11807), is there a webinar for multicore debug? Maybe you could schedule one?

Anyhow, what I'm missing is how to connect the different cores to different projects. Maybe Multi Workbench windows is not the way to approach this? 

I tried using a single window multi core debug but the console window was shared between the two cores when doing printfs.So I decided to separate the two console by using a new workbench window. Perhaps there is an easy way to do this with a single workbench window?

Thanks

  • 0
    TI__Guru**** 483671 points

    Hi Eddie,

    I think this is what you want to do. Please correct me if I am wrong:

    You opened two workbench windows. The first window has proj1A as the active project and you used the Debug Properties "Connect to Exact CPU" option so that when you select "debug active project", it will load and run to main for core 1A of your 6474 EVM.

    The second window has proj2A as the active project and you used the Debug Properties "Connect to Exact CPU" option so that when you select "debug active project", it will load and run to main for core 2A of your 6474 EVM.

    This should work fine.

    Eddie said:
    Hitting the reload button in either window wants to load the last loaded .out irregardless of the active project. For example, if hit the load button in the debug perspective for window A, and I select proj1A.out, then I go to window B and select the load button, it wants to load proj1A.out. Shouldn't it default to proj2A.out?

    Not always. When you are in a debug session, the reload button will reload the current out file for that debug context. If in window A, you load proj1A.out on core 1A and in window B, you hit "reload", it will load proj2A.out if your have core 2A selected in the Debug view. If you have core 1A selected in your debug view for window B, it will reload proj1A.out for core 1A, even though proj2A is the active project. The debug context is what determines which out file to reload. The active project only impacts which project to build and load when hitting "Debug Active Project".

    ki

  • 0 in reply to Ki
    Guru 10385 points

    Hi Ki

    Thanks for the comments. I think whats happening is the debug context on the main window (proj1A) changes to proj2A on me and I don't realize it.

    Another thing I'd like to understand is the std out for printf. Is there a way to get the proj1A std out to go to the main debug and the proj2A std out to go to proj2A.

    Cheers

  • 0 in reply to Eddie3909
    TI__Guru**** 483671 points

    To avoid confusion of the debug context changing on you, you may want to set the debug scope so that only the core you are interested in shows up in the Debug view. For example you can only have core 2A in scope for your second workbench window.

    Normally, the console will show the std output of the current debug context. So if you have core 2A selected, the console will show the CIO of core 2A. However you can always pin the console to a certain debug context so that it will always show the CIO for a specific core, even if you change the debug context.

  • 0 in reply to Ki
    Guru 10385 points

    Thanks again Ki. You-da-man!

     

    Cheers

    Eddie