• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 852 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.2.3 workspace issues

Rhonda Liang
Prodigy 80 points

I am new to ccs v4.2.3 and have the following issues with its workspace. Hope the future version would address them.
1. I would like to save the workspace when I felt the settings and displays are convenient for my work. After that, I may do some other things and may want to save the workspace for another working condition, or may want to discard the changes. At this point, my early saved workspace is already lost (instead of being saved). Closing CCS v4 at this point only confirms that the saved workspace is not what I save.
2. The graphical displays are not considered as part of workspace by CCS v4. Therefore, they are not saved at all. Even I export, I can only export the data settings for the graphs, but not the display.
3. Extended from issue 2, I cannot put the graphs behind other tabs or windows. If I minimize the graphs, then there is no way torestore them to the sizes and location I like. This makes the work really time consuming when I make minor modifications of the code and would like to verify the same waveforms.
4. Extended from issue 1, the same thing happens when I tried to save the perspectives. Even I save each perspective with a different name, they all get overridden as soon as I make any change on screen.
5. The "Reset" button plays hide-and-seek game. Sometimes it is on the tool bar, sometimes it is not.
6. The "Go Main" function is doing what? Not just go through initializations and stop at the main, but also keeps going.
7. Why at the end of code compiling, the message only says it is finished without explicitely saying if it is successful or not?

  • 0
    TI__Guru**** 483141 points

    Hello,

    Rhonda Liang said:
    1. I would like to save the workspace when I felt the settings and displays are convenient for my work. After that, I may do some other things and may want to save the workspace for another working condition, or may want to discard the changes. At this point, my early saved workspace is already lost (instead of being saved). Closing CCS v4 at this point only confirms that the saved workspace is not what I save.

    This is currently not supported. However, there may be some Eclipse plugins that you can drop into your CCS install that will add this functionality.

    Rhonda Liang said:
    2. The graphical displays are not considered as part of workspace by CCS v4. Therefore, they are not saved at all. Even I export, I can only export the data settings for the graphs, but not the display.

    This is not supported in CCSv4, but it is supported in CCSV5

    Rhonda Liang said:
    3. Extended from issue 2, I cannot put the graphs behind other tabs or windows. If I minimize the graphs, then there is no way torestore them to the sizes and location I like. This makes the work really time consuming when I make minor modifications of the code and would like to verify the same waveforms.

    You can move the graphs around by dragging the tabs of the graph view. You can also right-click on the tab and select 'Detached'. This will detach the Graph so that it will be in its own floating window that you can resize however you wish.

    Rhonda Liang said:
    4. Extended from issue 1, the same thing happens when I tried to save the perspectives. Even I save each perspective with a different name, they all get overridden as soon as I make any change on screen.

    Yes, CCS will always keep track of any changes made to that perspective while that perspective is active on CCS shutdown.

    Rhonda Liang said:
    5. The "Reset" button plays hide-and-seek game. Sometimes it is on the tool bar, sometimes it is not.

    You have to keep track of which perspective you are in. It is available in the 'Debug' perspective but not the 'C/C++' one.

    Rhonda Liang said:
    6. The "Go Main" function is doing what? Not just go through initializations and stop at the main, but also keeps going.

    It should set a breakpoint at 'main' and then run to it. If there is no 'main' in the application, it will just keep executing. It is possible to change the option so that it will run to a different label than main. But the Function will still be called "Go Main".

    Rhonda Liang said:
    7. Why at the end of code compiling, the message only says it is finished without explicitely saying if it is successful or not?

    If the build failed, it will explicitly tell you it failed. Otherwise it will tell you that the executable was created. If you are doing an incremental build and nothing changed (no changes since the last build), then you will see the behavior you described (nothing happens and a message that the build finished).

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 80 points

    Ki: "This is not supported in CCSv4, but it is supported in CCSV5"

    Well, CCS v5 does not support F283xx development kits, yet. I have to wait.

    Ki: "You can move the graphs around by dragging the tabs of the graph view. You can also right-click on the tab and select 'Detached'. This will detach the Graph so that it will be in its own floating window that you can resize however you wish."

    I have been floating the graphs around, but can not put them behind other windows.

    [[quote user="Rhonda Liang"]5. The "Reset" button plays hide-and-seek game. Sometimes it is on the tool bar, sometimes it is not.[/quote]

    Ki: "You have to keep track of which perspective you are in. It is available in the 'Debug' perspective but not the 'C/C++' one."

    But even in Debug perspective, the REST button plays hide-and-seek game.

    Ki: "If the build failed, it will explicitly tell you it failed. Otherwise it will tell you that the executable was created"

    It does not explicitly tell that the build failed. What It does is NOT TELL the executable was not created.

     

    One more question: if the souce code gets modified from other method, how do I update/referesh the source code in the opened project inside the CCS v4? So far I have to close and then open the project again. In old CCS v3.3, it prompts me to refresh the file inside the opened project.

  • 0 in reply to Rhonda Liang
    TI__Guru**** 483141 points

    Rhonda Liang said:
    Well, CCS v5 does not support F283xx development kits, yet. I have to wait.

    CCSv5.1 does. It is currently a Beta build but you are welcome to try it.

    http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5

    Rhonda Liang said:
    I have been floating the graphs around, but can not put them behind other windows.

    You're right. Floating windows are always on top. If docked, you can put the graph tab behind another tab

    Rhonda Liang said:
    But even in Debug perspective, the REST button plays hide-and-seek game.

    It should always be in the toolbar in the 'Debug' view. Unless you closed the 'Debug' view, it should be there. Do you see it disappear from the 'Debug' view?

    Rhonda Liang said:
    It does not explicitly tell that the build failed. What It does is NOT TELL the executable was not created.

    You should see a message like:

    gmake: Target `all' not remade because of errors.

    Rhonda Liang said:
    One more question: if the souce code gets modified from other method, how do I update/referesh the source code in the opened project inside the CCS v4? So far I have to close and then open the project again. In old CCS v3.3, it prompts me to refresh the file inside the opened project.

    Is the file open in the editor? CCSv4 should detect the change and prompt you to refresh the file like in v3.

  • 0 in reply to Ki
    Prodigy 80 points

    Thanks.

    I will try CCS v5.1 for next project.

    The RESET button really disappears sometimes from the toolbar in DEBUG perspective.

     

  • 0 in reply to Rhonda Liang
    TI__Guru**** 483141 points

    Rhonda Liang said:
    The RESET button really disappears sometimes from the toolbar in DEBUG perspective.

    If you can take a screenshot of that and post it here, that'd be good.

    But I think what is happening is that the Debug view is being closed, hence the RESET button will disappear because it is attached to the Debug view