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

Three newbie CCS 5.2 questions

Robert Smith
Intellectual 640 points

I have a few newbie questions about CCS 5.2:

1. CCS 5.2 separates compiler and linker output by projects. For example if I have 2 projects in workspace(ProjectA and ProjectB, A depends on B), and rebuild project A. To see compiler and linker output for ProjectB I have to select manually ProjectB in Project Explorer, the same for ProjectA. My question is it possible to consolidate compiler and linker output from all projects to console, so I don't have to select each time project in Project Explorer tab.

2. Let say I have a few projects in workspace and several files from different projects are opened in editor. If I click on some file in editor, the project explorer automaticaly sets the project which contains this file as active in project explorer. Is there any way to prevent this? I don't want selection one or another file in editor influence which project is currently active in project explorer.

3. In order to debug my app I have to perform the following steps discovered by try and error:

 - Click on Beatle icon, this initialize JTAG and connect CCS to board.
   (In Debug window I see "Blackhawk ...C55xx(Running)" )


 - Click on Suspend icon. (In Debug window I see "Blackhawk ...C55xx(Suspended)" )

 - Click on menu Run -> Load -> Load Program and click on OK button on Load Program dialog.

- Click on Resume icon

 - Now in Debug Window I see
                 Blackhawk ...C55xx(Suspended - SW Breakpoint)
                |- main() ...
                |- _args_main() ...

From this point I can set breakpoints and debug my app. It seems to me that I missed something or didn't configure CCS Debuger properly. I assume that I should be able to set breakpoints and debug my app right after clicking Beatle icon without all these intermediate steps.

Could someone comment?

Thanks

  • 0
    TI__Guru**** 171519 points

    Hi,

    1. You can select a global build console that holds the output for all projects in the workspace. However, by default CCS erases the contents of the console view before building the project. In this case you can achieve what you want by doing the following:

    • Go to menu Window --> Preferences --> C/C++ --> Build --> Console and de-select the option Always clear console before building
    • Then open the console view. In the top bar there is a small blue monitor icon. Click on the small black triangle close to it and select CDT Global Build Console.

    With this, you must manually clear the console output by right-clicking on the view and selecting Clear...

    2. Unfortunately I couldn't find a way to customize the IDE to do what you intend...

    3. I see this behaviour if my project is not in focus when I click on the green bug button, or if the project does not have a target configuration assigned to it. In this case you can either:

    • Link an existing target configuration to your project. Open the menu View --> Target Configurations. Right-click on the desired target configuration file (.cxxml) and select Link file to Project. Select the project. An entry with the name of the target configuration file should appear in your project (the icon will have a small shortcut arrow, indicating it is linked). Select the project and click on the green bug button. 
    • Create a target configuration file (.ccxml) embedded to your project. Select the desired project in the Project Explorer view. Right-click on it and select New --> Target Configuration File. Configure the emulator/device appropriately and save the file. An entry with the name of the target configuration file should appear in your project. Select the project and click on the green bug button.

    For details about what happens "under the hood" when a debug session is launched, please check slide 40 and on of the CCSv5 Tips & Tricks presentation available at the page below:

    http://processors.wiki.ti.com/index.php/Tips_and_Tricks_for_CCStudio_IDE

    Hope this helps,

    Rafael