CCS 4.2.3.00004 unable to open source file during compilation

Hi,

I wonder if there is a problem with the original project itself... Could you point me to where you downloaded this project so I can try it out here?

Regards,

Rafael

Project files attached. Other people in the workshop were able to get the projects to compile without issue. I ended up going through the workshop using my partners build. I did have a previous version of CCS installed (4.1.???)  when I installed the 30 day trial of 4.2.3 Platinum. Perhaps the two versions didn't play nice together?

Hi,

I managed to build the project straight from what you sent (I built all of the Lab2 projects, including the 915MHz Unrestricted configuration you used), therefore I suspect that something is strange with the workspace you are using. Can you either import your projects into a new workspace or "clean" the existing one? Check the section General IDE section of the troubleshooting page below:

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

Hope this helps,

Rafael

Hello,

have you 

- tried the latest version of the examples?

- where did you unzip the example projects?  Sometimes with SimpliciTI projects you need to unzip them in the SimpliciTI folders and you may also find you need to set the DEV_ROOT etc in CCS.   I will have a look at the zip file you sent, but I would also like to know what DEV_ROOT and settings you use.

Hopefully we can figure this out!

Best Regards,
Lisa 

Hi Rafael,

I tried the cleanup methods you mentioned, but it did not solve the problem. Thanks for pointing me to the Wiki. I've attached the debug files I should have included originally.

Hi Lisa,

I'm not aware of any more-recent examples. As noted above, these example have compiled successfully for several other people.

I am using a fresh install of CCS v4.2.3.00004. I have not modified the DEV_ROOT or anything else in the project files, and am unsure of how to check this in CCS.

Please let me know if there are other debug files or information I can gather to help solve this.

Hi John,

I tried to import and build the examples from the zip file you sent.  I was able to do this without issue.

Please try the following

1) Open a fresh workspace

2) Project -> Import Existing CCE/CCS Project

3) Browse to the folder where the lab2 files are.  For me this happened to be as below (Will be different for you )

C:\Users\a0406096\Desktop\Stellaris\Avnet_RF_Speedway_Files\Lab2 files\Lab2ab_Chronos2Chronos

4) CCS should find one project which will automatically be ticked

5) Select "Copy project into workspace"

Try the build again.

Please let me know whether this works.   

You actually should not have to worry about SimpliciTI or DEV_ROOT ... the examples are well enough self contained from what I see :  )

Best Regards,

Lisa

I have been doing this from the start without success. I have tried several fresh workspaces to no avail. Could I have gotten to the point of compiling the project if I didn't have it successfully imported into the workspace?

I suspect the problem stems from the fact I had an older version of CCS installed on my machine when I first installed CCS v4.2.3.00004. I have since uninstalled the old version and reinstalled CCS v4.2.3.00004 with the temporary 30 day platnium license and the MSP430 components but that has not resolved the issue. Are there any Windows environment variables that I can check or other things that would be related to my installation of the IDE?

Hi John,

Ok, it sounds like you are doing things correctly and I have not been able to reproduce the issue with that project. 

One thing I am wondering is if you have chosen the wrong version of project to make active my selecting the Unrestricted version of the 915MHz project.  What happens if you select the Core version of the project as active and build that?   I found that when I select the Core Version I get errors ... almost identical .. when I select Unrestricted I do not.

It is relatively hard unfortunately not being able to reproduce the issue.   

Please let me know if this could be the issue.  I am wondering whether it is a silly licensing thing.

Best Regards,
Lisa 

Hi Lisa,

Thanks for all your help with this and for your prompt responses. With the Core build configuration I receive the same initial error as I get with the Unrestricted version:

Fatal error: could not open source file "../main.c"
1 fatal error detected in the compilation of "../main.c".
Compilation terminated.

I've attached a screenshot of my licensing info from CCS.

I believe the earlier version I originally had installed was also a trial version that had expired (from a previous workshop). Perhaps having the older version installed initially, or my multiple uninstall/reinstall of 4.2.3 messed up the licensing. Is there any way to completely clear out my current license data so that I can do a fresh install of the evaluation version?

Hi John,

let me see if I can look into this for you.  Unfortunately it is fewer and fewer programs that like to do clean uninstalls.

What license options did you select?  Did you find remnants of CCS after you uninstalled the previous version you had?

Cheers,
Lisa 

I selected the 30 day evaluation license. The only remnants from my previous installation were empty folders that I had not deleted via the final step of the uninstaller. If it is licensing, the problem is probably lurking in the registry somewhere. Let me know if it would be helpful to identify the problem, I can save off a copy of my registry contents.

Any idea when there will be a new version of CCS available for download? I can wait for that and give it a try with a fresh install and the evaluation license if the newer version will reset my license.

One thing i noticed: the download Wiki (http://processors.wiki.ti.com/index.php/Download_CCS) says the latest version is 4.2.4.00033, but when I download and install the production DVD image (http://software-dl.ti.com/dsps/forms/self_cert_export.html?prod_no=setup_CCS_4_Platinum.zip&ref_url=http://software-dl.ti.com/dsps/dsps_public_sw/sdo_ccstudio/CCSv4/latest/) the version is actually the same 4.2.3.00004 that I have been working with.

Hi John,

I am wondering less and less now if it has to do with the licenses.  

Have you run updates in CCS? 

It almost seems like in your case the MSP430 code generation tools are not included.  I assume you can create a blank MSP430 project and see a Code Generation Tool version in the CCS Build option.

I would assume if you imported and built the project that this is the case.  I attached two screenshots.  How do these compare with yours?

Best Regards,

Lisa

Quick question. If you double click on main.c in the "C/C++ Projects" View does it open ok in the editor?

Hi John,

Yes I can open, edit and save the main.c file in the project.

Hi Lisa,

After running the updates, I captured the same screenshots and noticed one small difference: My "Effective Code Generation tools:" for CCS Build show as TI v3.3.2.

I can create a blank CCS MSP430 project. I also created a new MSP430 project using the "Hello World" example and received a similar compilation error:

Fatal error: could not open source file "../hello.c"
1 fatal error detected in the compilation of "../hello.c".
Compilation terminated.

Thanks and have a great weekend!

Hi John,

I am thinking this is likely due to the MSP430 code generation tools. 

I have experienced the following

CCS 4.2.3 - version 3.3.3 is ok, 3.3.2 generates errors.

CCA 4.2.4 (what you actually seem to have) - I do not have 3.3.2 at all.  Once again 3.3.3 works.

I would suggest the following and please keep me informed.

1) If you can select 3.3.3 or 3.3.1 please give one of these a try.

2) Run an update .. Help -> Software Updates -> Find and Install.   Hopefully that will include the newer 3.3.3 version of MSP430 code generation tools.

Hopefully this will get you going.

Best Regards,
Lisa

Hi Lisa,

1) I am not able to select version 3.3.3. It is not an available option. I can only select 3.3.1 or 3.3.2. When 3.3.1 is selected, the Effective Version still shows as 3.3.2 per my earlier picture. Neither version compiles.

2) I've tried running Software Updates, but it always says "No updates for currently installed features found".  I've tried both the "Search for updates of the currently installed features" and "Search for new features to install" options.

Is there a file that i can manually download from somewhere to get the 3.3.3 code generation tools for MSP430?

Hi Lisa,

I just found a related thread that sounds like it may be the same issue:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/91810/318950.aspx#318950

What do you think?

Here are my options under the new features:

When I select the MSP430 and click Finish I get: "No features found on selected site, choose a different site or site category"

Any idea what site I should choose?

Thanks!

Hi John,

yes there seems to be something going on with the MSP430 code generation tools ... odd.

I would wait to see if you can get a way to update to 3.3.3 through a colleague of mine via that other thread.  I will also see if I can follow through on my end.

As I think that is the next step, there is not much to be done until you are able to try 3.3.3

The only in between option would be to give CCSv5.1 a go.

Best Regards,

Lisa

Hi John,

can you send me a friend or conversation request/start ... I can send you the 3.3.3 installer but only offline.

Cheers,
Lisa

Hi Lisa,

Still no luck with the 3.3.3 code generation tools. I'm wondering about where the compiler is looking for the files from the relative directory: "../"

For example in the output below, the compiler says: 'Building file: ../hello.c'

How can I find out the full path that is referenced with the "../hello.c"?

I've looked at the project Macros and the ProjDirPath shows C:\NewWorkspace2\asdfaw, which looks to be correct, except for maybe it should be using / instead of \ ?

**** Build of configuration Debug for project asdfaw ****

C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake -k all
'Building file: ../hello.c'
'Invoking: Compiler'
"C:/Program Files/Texas Instruments/MSP430 Code Generation Tools 3.3.3/bin/cl430" -vmspx -g --define=__CC430F6137__ --include_path="C:/Program Files/Texas Instruments/ccsv4/msp430/include" --include_path="C:/Program Files/Texas Instruments/MSP430 Code Generation Tools 3.3.3/include" --diag_warning=225 --silicon_errata=CPU22 --silicon_errata=CPU21 --silicon_errata=CPU23 --silicon_errata=CPU18 --silicon_errata=CPU40 --printf_support=minimal --preproc_with_compile --preproc_dependency="hello.pp"  "../hello.c"
Fatal error: could not open source file "../hello.c"
1 fatal error detected in the compilation of "../hello.c".
Compilation terminated.

>> Compilation failure
gmake: *** [hello.obj] Error 1
gmake: Target `all' not remade because of errors.
Build complete for project asdfaw

Hi John,

ok this is hard as I am not able to reproduce it but it could be a path or a slight syntax error somewhere. 

Do you feel it is worth setting up a WebEx might be useful?  Have you tried the Chronos project again may I assume?

The slashes should have no impact.  

Do you see this error with all projects then? 

Best Regards,
Lisa

Hi John,

thought I would check for an update. 

I am at a bit of a loss as at least three of us here simply do not have any issues at all with the project you are trying/sent.

The fact at the beginning you mentioned being next to the only one with issue in the workshop makes me suspect it may be related to your setup?  Have you been running everything as an administrator?  Do you have access to another PC to try?

Best Regards,
Lisa

Hi Lisa,

I've been out of the loop as my computer crashed (registry hive file corruption). There was definitely something wrong with my setup before, but unfortunately we will not be able to get to the root cause now as the computer has been wiped out.

I'm now set up with a clean install on a fresh PC and everything works fine for this project!

Thank you and your crew for all the time and effort. The support has been great, even if we weren't able to get to the root cause. This is reassuring as I may be using CCS soon for a project at work.

Thanks!

John