CCSv5 EALLOW and EDIS

What is the code within the EALLOW/EDIS construct? Is it a warning from the compiler that says EALLOW/EDIS has no effect? Can you show a screenshot of the warning?

The code inside is:

EALLOW;
PieCtrlRegs.PIEIER9.bit.INTx2=1;        // Enable SCITXINTA
IER |= M_INT9;                                           // Enable CPU Interrupt group 9
EDIS;

And the warnings are: Statement has no effect 'EALLOW'. Statement has no effect 'EDIS'

I can't recreate this warning. I am using CCS 5.1M6. Which version of CCSv5 are you using? It may help if you could attach your project here, so we can try to reproduce it locally with your project.

I started this morning to work again with the project. Now I have same kind of problem but this time it's for all files complaining about:
Symbol 'IER' could not be resolved    EPwm.c     line 76    Semantic Error.

And the code line is: IER |= M_INT3;                                     // Enable CPU Interrupt 3

There was some update to CCSv5 when I started, so it might be related to that. I can compile the code and it will produce .out but in Problems field it's showing lot of these errors (not warnings).

JHi

JHi said:

I can compile the code and it will produce .out but in Problems field it's showing lot of these errors (not warnings).

Are you sure the errors you see in the Problems view are for this particular project that you are building? By default, in CCS 5.1, the problems view displays the errors/warnings for all projects in the workspace unless you set up filters to only look at the ones relevant to the active (selected) project. The Resource field within the problems view tells you which project the error/warning pertains to.

Did you try cleaning the project and then rebuilding (Clean Project, then Build Project)?
How about cleaning the workspace or trying a new workspace? http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#General_IDE

All the faults were from the project I was building but deleting .metadata file did the trick. No more errors (so far).

EDIT: Wrong.

When I opened the .c file after I had build the project I got back the faults.

Which ISA are you using?  Which version of the compiler (not CCS version)?

I'm developing code to TMS320F28027.

Code-generation tools: TI v6.0.1

Code Composer Studio
Version: 5.1.0.06000

One more thing. The Errors doesn't come when I compile. Those come immediately when I open a file which has IER lines. So I guess this is more a CCSv5 problem than a compiler problem.

JHi

JHi said:

One more thing. The Errors doesn't come when I compile. Those come immediately when I open a file which has IER lines. So I guess this is more a CCSv5 problem than a compiler problem.

Yes, the error is not coming from the compiler but is coming from the Eclipse CDT parser. Did you import a CCSv4 project into CCSv5? If so, was it an example project and which one was it?

I was able to reproduce the behavior (Symbol IER could not be resolved errors in CCS editor) by importing some of the older CCSv4 example projects that were included with "2802x Header Files and Peripheral Examples". I suspect there is a problem with importing some of these older format CCSv4 projects.

If I import the same example but from a recent install of ControlSuite, then it imports fine, and there are no such syntax errors in the CCS editor. Could you please try importing the examples for F28027 included with ControlSuite and confirm that the issue does not occur?

The project is my own which I started with CCS4, but I had too much problems with debuggin lately with v4 so I decided to try v5. v5 is much faster and I don't have problems with debugging.

And yes I get the same errors (IER and IFR) when I import Example_2802xSWPrioritizedInterrupts project. I just installed last week controlSUITE from the newest zip so it should be new enough. It can't find the definitions to IER and IFR (extern cregister volatile unsigned int IFR; extern cregister volatile unsigned int IER;) when I press F3 or when I press ctrl+mouse click. It just doesn't go anywhere and it should jump to definition.

JHi

The issue seems somehow related to how the original project was created for CCSv4 (maybe the version of v4 that it was created with, but I'm not sure).

I tried importing Example_2802xSWPrioritizedInterrupts project as you suggested. I see the errors with symbol not resolved for IER and IFR but only with the oldest version of the project within ControlSuite (in folder C:\ti\controlSUITE\device_support\f2802x\v125\DSP2802x_examples_ccsv4\sw_prioritized_interrupts). If I use the project inside the latest version (C:\ti\controlSUITE\device_support\f2802x\v129\DSP2802x_examples_ccsv4\sw_prioritized_interrupts), then there are no errors.

I will submit a bug report so we address the issue with importing those specific older projects. In the meantime, you may need to work around it by re-creating the affected source files and adding them again to the project.

The defect # for this issue is SDSCM00041358.

I also got the errors with v129 examples. First I created a complitely new workspace and then imported sw_prioritized_interrupts project and the errors were again there. 

And it also didn't help to create a new source file for my own project, I still get the same errors.

JHi

Can you zip up and attach the example project you imported and see the errors with? I'd like to see if I can recreate the issue with the same project you are using, because I have tried a few different examples from v129 and do not see the issue.

Out of curiosity, have you tried starting eclipse.exe with the -clean option to see if that helps? http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#General_IDE

There is also now a CCS5.1M7 version available for download which you can give a try when you have a chance and see if the behavior persists.
http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5#Downloads

-clean didn't help and I'm just downloading the M7. Project is included with this post.

JHi

EDIT: Updating to M7 didn't solve the problem. Btw I had to remove manually M6 (uninstall didn't work) to be able to install M7 because installation gave so much errors.

JHi,

I still couldn't reproduce the errors with your attached project, which I think is strange, but there could be a way for you to disable these indexer errors from appearing.

Please see this related post: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/128575/461093.aspx#461093

As mentioned there, try the workaround of disabling the syntax checking functionality of the indexer by doing the following:
Right click on the project and select properties; near the bottom click on "Show Advanced Settings", then expand to C/C++ General/Code Analysis/Launching and uncheck "Run as you type(selected checkers)". You will most likely need to delete existing errors/warnings from problems view(select multiple errors and hit delete).

I had a similar problem, and AartiG's solution did get rid of the errors.  I just thought I'd add that I was able to re-enable it afterwards and the errors did not return.

seems like I am not alone at this problem. 

I was wondering if there is a reasonable answer for such behaivor when updating a CCS4 project to CCS5. Anyway i am going to try what AartiG said, although it is very annoy.