• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 2324 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/LAUNCHXL-CC1310: CCS build settings broken on freshly imported project?

Michael Moon
Expert 2050 points
Part Number: LAUNCHXL-CC1310


Tool/software: Code Composer Studio

Hi,

I just checked out a git repository for another project that I need to start work on, but CCS horribly breaks when I try to import it.

I made a brand new workspace, because CCS complains about already-open workspaces and I like to keep my projects organised on separate desktops.

Import seems to go fine, however when I try to Build Project, all that happens is my console says "Nothing to build for project".

If I try to Debug, CCS goes into debug mode, sets up the debugger then chokes, saying "Load program error. Encountered a problem loading file: /path/to/my/project/Debug/project.out Could not open file" - presumably because nothing got built during the build stage.

The Debug directory is notably empty, no makefile or anything.

When I go to build settings, the basic ones look fine but there's a couple of blank tabs in the tree view, and I get java exceptions and mostly blank settings panes when I click on them.

Example projects seem to work fine, and this project works fine on my colleague's computer.

Screenshots:

12345

Project log

Is there a better way to make this work than copying all the files into a new CCS project?

Curiously, it was initially generated from the rfWsnConcentrator example, which is the same example I successfully tried when I noticed that CCS was being stupid again.

PS: Yes, that's CCS's default colour scheme, I didn't deliberately make it look hideous!

  • 0
    TI__Guru**** 173310 points

    Michael,

    This is indeed quite odd. What operating system is your machine running? Is it the same as the OS on your colleague's computer where this same project imports and builds fine?

    And you are importing into CCS 7.1, correct? 

    Michael Moon said:
    PS: Yes, that's CCS's default colour scheme

    The color scheme in your screenshot certainly looks different than what I am used to seeing. My CCS is set up for "Code Composer Studio - Default" theme (under Window->Preferences->General->Appearance), which I believe is the default. Is yours set to the same or something different?

  • 0 in reply to AartiG
    Expert 2050 points

    Hi AartiG,

    I'm running Linux and my colleague uses windows. We're both using CCS7.1 and working on the project via git revision control.

    We managed to fix the issue by freshly importing one of the example projects (rfWSNCollector from memory) and grabbing its .cproject verbatim. This seems to make both our systems happy and allowed us to continue co-development.

    I wasn't able to post earlier since the forum apparently put my post into moderation queue, where I can't access it. It would be great if the forum let me see my own threads and post updates and edits even while in moderation queue, then at least I could post links to others which would be viewable to them after moderation, or post further tests or results on a new issue.

    I'm really not sure what was wrong with the old .cproject, it was also from one of the example projects albeit possibly one a couple of years old. I expected that CCS might complain about the project being old, but having it choke so spectacularly instead was slightly surprising.

    Re. the colour scheme;

    Yes, mine's set to default.

    I think the issue is that CCS only applies its theme to certain elements or attributes, leaving others to be coloured by my system theme.

    I tried setting the dark scheme which makes most things better, but some aspects of it are infuriating - eg when I select a keyword in the editor, it turns into a solid white block and I can't read the text any more (and unlike my preferred editor, pressing esc doesn't clear the highlight), and the console has black writing on dark grey background which is awful for readability. I couldn't find settings in the theme editor which affected either of these specific colourings.

    However since I'm moving away from using CCS as much as possible (I now only use it to generate the makefiles which inexplicably have rules for each individual source file, and for debug mode), the weird colour scheme doesn't bother me so much.

  • 0 in reply to Michael Moon
    TI__Guru**** 173310 points

    Michael Moon said:
    We managed to fix the issue by freshly importing one of the example projects (rfWSNCollector from memory) and grabbing its .cproject verbatim. This seems to make both our systems happy and allowed us to continue co-development.

    Thank you for the update and glad to hear that the issue is fixed.

    Michael Moon said:
    I think the issue is that CCS only applies its theme to certain elements or attributes, leaving others to be coloured by my system theme.

    Yes this is quite likely the case, and I'm sorry about the inconvenience caused due to this.

    I will mark this thread as closed for now since you have been able to move ahead with development. If you encounter issues at a later time, please feel free to start a new post.