Simple XC project can't find xc.h and timer.h include files

[leon_heller]

I've created a simple XC project for the startKIT which builds and runs OK, but xs1.h and timer.h are flagged as unresolved. I can't find out how to get the necessary includes folder containing the missing header files into the project. All the projects I've downloaded include it. I'd have thought that they would be added when I created the project, I'm sure that used to be the case with earlier versions of the tools.

[AJB2K3]

Do the demo startkit programs complain about it?

[leon_heller]

No, they are OK as their projects include the necessary folder.

[sethu_jangala]

Can you send your work space as attachment to see whats causing issue in your case?

Sethu.

[leon_heller]

It's attached.

[sethu_jangala]

Hello leon_heller,

I tried building the application which you have sent to me using xTIMEcomposer 13.0.1 without any issues. the application does show as warning next to the code:

Unresolved inclusion: <xs1.h>
Unresolved inclusion: <timer.h>

But the application builds and runs fine. This looks like settings file not being included properly. I exported the paths and symbols settings file from the working project (project in which these errors do not occur) and imported into this application workspace and I am able to remove the errors with this. not sure whats causing the issue in this case that corrupts the paths and symbols settings. We are investigating the issue and will update you once we have more information on this.

Sethu.

[leon_heller]

Thanks. I'll try your solution.

Importing the settings from another project fixed the problem.

I see from a previous post that someone else had the same problem, but closing Composer Studio and restarting it fixed it. I tried that, but it didn't work.

Leon

[leon_heller]

Has anyone else experienced this problem? I haven't heard anything from XMOS about it, so I suppose I will have to raise a customer support ticket to make sure that it is fixed.

[sethu_jangala]

I filed this as a bug in the internal bug tracking system and we are facing difficulty replicating the issue from our end as we are not sure whats causing this. This will be fixed once we can replicate and see whats causing the problem.

Sethu.

[leon_heller]

Thanks, Sethu.

Leon