My sys/bios .cfg file is no longer tagged [SYS/BIOS] in one of my projects. That is, in the Project Explorer window, the cfg filename is NOT followed by "[SYS/BIOS]".
Does anyone know what I did? And more importantly, how do I correct this problem?I'm using Code Composer Studio Version: 5.1.0.09000 with xdctools 3.22.04.46 and sysbios 6.32.5.54
Thanks,
Fred
I'm not sure what tag you are referring to. Do you mean the classification of the project as a RTSC project?
Could you please add a screenshot of what you are referring to? In which earlier version of CCS did you see a "SYS/BIOS" tag?
If a post answers your question please mark it with the "Verify Answer" button
Search the wikis for common questions: CGT, BIOS, CCSv3, CCSv4Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box
Hi AatiG,
No, not the classification, which is correct, rather a [bracketed] attribute:
Note for the 'bios2618' project, the file app.cfg shows the [SYS/BIOS] attribute but the configuration file for the RefBrd2 project, RefBrd2.cfg does not have the [SYS/BIOS] attribute. This is a problem because the XGCONF editor only shows a blank screen.
Regards,
Fred,
It seems like the [SYS/BIOS] attribute appears after the .cfg file has been opened once. When I create a new SYSBIOS project, the .cfg is first shown without the attribute. Once I double-click on the file to open it in the editor, then the attribute appears.
Are you saying that the RefBrd2.cfg opens up to a blank screen? If so, could you check the RTSC tab under project properties and post a screenshot of the versions of XDC and SYSBIOS the project is set to use? Is this the only project where you cannot view the configuration file properly or are there others as well? Was it a CCSv4 project imported into CCSv5 or one that was created new with CCSv5?
I will move this thread to the BIOS forum as the experts there should have a better idea of why this may be happening.
HiAartiG,
> Are you saying that the RefBrd2.cfg opens up to a blank screen?
Yes, with the XGCONF editor.
> Is this the only project where you cannot view the configuration file properly?
Yes. When I created the project the XGCONF editor worked as expected. I slipped on the keyboard (pressed some "random" keys) and all of a sudden XGCONF displayed a blank screen. The file can be displayed with the regular text editor, and has no obvious (to me ;-) defects. The editor still works on other projects. Here is the screen shot you asked for:
It's a mystery.
Can you attach your config file to this thread so we can examine it?
Dave
I think you accidentally checked the "Exclude resource from build" check box from the file's Property page.
1) right-click on your .cfg file and then select "Properties".
A dialog box comes up.
2) click on "CCS Build".
3) verify the "Exclude resource from build" check box is UNCHECKED. (I think yours CHECKED)
4) uncheck the "Exclude resource from build" check box.
5) dismiss the Properties dialog box by pressing the OK button.
6) Try building again.
Alan
Hi Alan,
I verified that the "Exclude resource from build" check box is indeed unchecked. Then I checked it, clicked Apply and clicked ok. No change. I then started the process over again and unclicked "Exclude resource from build". Again no change. Per David Friedland's request, I am attaching the actual config file.
Thanks for the idea,
Hi Dave,
I have placed the config file into "Fred Carter's Files". Due to name restrictions, the file name is RefBrd2.txt rather than RefBrd2.cfg
Hmm, I see there is an icon for Insert file. Lets see what happens:- - - - - - - - - - Start Inserting file
- - - - - - - - - - - End Inserting file
In desperation I deleted the configuration file and copied the msp430 "idle" configuration file from:
C:\ti\bios_6_32_05_54\packages\ti\sysbios\examples\msp430\idle
to my project directory. I then doubled clicked on "idle.cfg" and I'm back in business.
This is still a bug. I have run into it a couple times now and then I fiddle with different "open with" choices and eventually it fixes itself. Or not. I can't seem to get it back again now.