XGCONF editor not showing.

Steve,

Is this the only project where you cannot view the configuration file properly or are there others as well?
Can you double-check with another RTSC project - either your own or one created using an example template?
Is this a  CCSv4 project imported into CCSv5 or one that was created new with CCSv5?
Has this .cfg come up properly in the XGCONF editor previously or always been blank like this?

There is a related thread on the forums but in that case the user simply deleted the .cfg and copied one over from an example project and that opened up fine. It might help for us to examine your .cfg file. If you can attach it here, I can move the thread to the BIOS forum for the experts there to comment further.

...

"Is this the only project where you cannot view the configuration file properly or are there others as well"

Yes. This seems to be the only project. Though my coworkers have had a similar issue with others.

"Can you double-check with another RTSC project - either your own or one created using an example template"

Sure. Worked fine.

"Is this a  CCSv4 project imported into CCSv5 or one that was created new with CCSv5"

I believe it was imported from CCSV4.

"Has this .cfg come up properly in the XGCONF editor previously or always been blank like this?"

Yes. The cfg has opened in CCS, just the other day. I did get update for the IDE since I last remember viewing the file.

There is a related thread on the forums but in that case the user simply deleted the .cfg and copied one over from an example project and that opened up fine.

This would work per above. But I don't want to have to rebuild our configuration from scratch due to a CCS bug.

It might help for us to examine your .cfg file. If you can attach it here, I can move the thread to the BIOS forum for the experts there to comment further.

Attached.

3443.task.cfg

Steve,

Steve Runion said:

Yes. The cfg has opened in CCS, just the other day. I did get update for the IDE since I last remember viewing the file.

Do you recall what updates you did to CCS? That might help isolate/reproduce the issue.

I copied your .cfg file over to a empty RTSC project and was able to open it fine with XGCONF in both CCS 5.1.0.09000 and 5.1.1.00031, so there must be something in your set up, possibly that changed during the CCS update you did. 

I'll move the thread over to the BIOS forum and see if the folks there have ideas on how to fix this.

Come to think of it the updates I installed were in response to this issue appearing. I was hoping that there was a bug fix in the updates for said problem. I had installed, manually, BIOS 6.3.4.39. So no updates to CCS prior to the issue.

Steve,

Would you be willing to give the latest Beta build of CCS 5.2 a try? It is available for download here. You can install it side-by-side with your current installation (just install in a different folder), so nothing in your current version will be affected. Then you can try importing your project into a new workspace in CCS 5.2 and see if that helps. If something is indeed messed up in your installation that is causing problems with certain projects, this new version should hopefully resolve it. Let us know if this does not help.

I installed the beta CCS5.2: same result.

I poked around some more and by clicking "bios" under the "available products" and was able to view the "system overview" and navigate all the different BIOS modules from there. However, nothing shows in the outline view where I would add resources to the configuration (semaphores, mailboxes, etc). This is the case in both my working CCS install as well as the beta.

Steve,
there are two things you can do to help us with debugging. The first is to open Error Log view. If it's not already open, you can open it with View->Other ...->Error Log. Once you open it, you'll see buttons in the upper right corner of the view. One of the buttons is "Open Log", which will open a text file. Please attach it.

Then, in the shortcut for CCS5 you can add the option -console. It will open a command line window where some additional related messages could show up. Please post the content of that window too.

7624.ccsv5.log log file followed by shell output.

7183.cssv5.txt

8662..config.zip

That indeed fixed it. Let me know if you need any more info to help debug how it got corrupted.