CCSv5-1 indexing errors on source files

Bruce Weyrauch

I just installed the latest build of CCSv5.1 ( Build numbers: CCS5.1.0.07001_linux and CCS5.1.0.07001_win32) in two VMware virtual machines. I imported a project that uses a separate directory for header files. In both the Windows and linux versions, I experienced a problem with file indexing. The project will build completely with no errors, but when I view a file, any reference to external includes in my own specified directories are marked in the editor with errors.

Project structure:

PROJECT

> include

types.h

source1.c

source2.c

Contents of a typical source file:

#include "types.h"

...

uint32_t tvar = 5;

...

Error when viewing the file:

Type uint32_t could not be resolved.

The sources are the BSL files from Logic provided with the expOMAPL138 board. I can provide the entire project if needed.

over 14 years ago

0 Lisa TI over 14 years ago

TI__Guru*** 130875 points

Hi Bruce,

In your source file (source1.c for example) assume tvar (defined in types.h) is reference/used. CCS needs to know that this is defined elsewhere.

In source1.c, do you do the following?

extern uint32_t tvar;

You of course will also need to do the same for the definition of any such externals.

Please keep me informed if this helps.

Best Regards,

Lisa

0 Bruce Weyrauch over 14 years ago in reply to Lisa TI

Intellectual 535 points

Lisa,

Your suggestion does not fix my issue. The errors are not actually problems with compiling or linking. I can build my project without errors or warnings. After successful build, if I open a file with the editor in CCSv5.1, many errors show up in the problem view. At this point, if I launch the debugger, it warns me that my project contains errors.

None of this occurs with the same project using CCSv5.03

I tried creating a simple project from scratch and did not get the same behavior.in CCSv5.1, so at this point I am a little stuck. Can I send you the two projects, one with problems and one without? Maybe you can spot what is wrong.

0 Lisa TI over 14 years ago in reply to Bruce Weyrauch

TI__Guru*** 130875 points

Hi Bruce,

ok that is probably a good idea and I will take a look. You could, if you would prefer, also do an offline send to me in a message through the forum here.

I guess I was not completely understanding what you are experiencing. Have you been importing projects then?

Best Regards,
Lisa

0 Bruce Weyrauch over 14 years ago in reply to Lisa TI

Intellectual 535 points

Lisa,

I would prefer to send you the files offline. How do I do that?

0 MartinS over 14 years ago in reply to Bruce Weyrauch

TI__Genius 15860 points

Bruce, Lisa,

We know what the issue is. We trying to get this fixed for next 5.1 update (i.e. M8). Bruce is correct, indexer flags any type that it is not aware of, including most of TI internal types.

As a workaround; you could disable the syntax checking functionality of the indexer and let the compiler flag these types of errors.

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). Once you recompile compiler/linker errors/warning will be regenerated.

Martin

0 Lisa TI over 14 years ago in reply to MartinS

TI__Guru*** 130875 points

Hi Martin, Bruce,

Martin - many thanks for the help and clarification.

Bruce and Martin - once again appologies if I misunderstud the issue here.

Cheers,
Lisa

0 Bruce Weyrauch over 14 years ago in reply to Lisa TI

Intellectual 535 points

Martin,

Thanks for the help. This solution worked for me. I'm moving forward again.

Code Composer Studio™︎

Code Composer Studio forum

CCSv5-1 indexing errors on source files