• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 344 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS570LC4357: Code Composer Studio forum v8

Divya S
Prodigy 20 points
Part Number: TMS570LC4357

Hi All,

I am using ccs v8.3.0 for compilation. 

I always observe parse error in file stdint.h (path: CCS_V8.3.0.00009\ccsv8\tools\compiler\ti-cgt-arm_18.1.4.LTS\include) for the line 

#if __has_include(<sys/stdint.h>)

On further examination, its found that the macro is defined properly. 

Currently I added the following patch code :

#ifndef __has_include
#define __has_include(x) 0
#endif

I see that this macro has been introduced since ccs v8. This parse error does not appear in ccs v7.

Could you have a look?

Best Regards,

Divya

  • 0
    Guru 92251 points

    From a search found CCS/CCSTUDIO: CCS 8.1 decoding #includes incorrectly within IDE; compiler itself works. which looks to be the same issue.

    Ticket EXT_EP-9009 was raised, but the status is Declined with the comment:

    Decline Reason:CDT indexer behaves as expected

    Divya S said:
    This parse error does not appear in ccs v7.

    Can you confirm if the issue is in the CCS indexer, and that the program compiles successfully?

    Also, are you using the same compiler version with CCS v7 and v8?

    As per Compiler Installation and Selection the compiler version is not the same as the CCS version. 

  • 0 in reply to Chester Gillon
    Prodigy 20 points

    I am not using CCS for code compilation, instead a makefile.

    The compiler base path in the makefile is specified as,

    CCS_V8.3.0.00009\ccsv8\tools\compiler\ti-cgt-arm_18.1.4.LTS  ----> for ccs v8.3

    CCS_V7.4.0.00015\ccsv7\tools\compiler\ti-cgt-arm_16.9.6.LTS ------> for ccs v7.4

    But the macro "__has_include" is only introduced from v8 in stdint.h file. 

    I don't understand why the parse error,

    In file included from ../../../../external/thirdparty/flashlib/drvfls_tmsx70f021ti01hissub/include/Types.h:34,
    from ../../../../external/bsw/flash/flashdrv.h:48,
    from include/fbl_inc.h:88,
    from Source/fbl_apwd.c:158:
    d:/uti/compiler/ti/ccs_v8.3.0.00009/ccsv8/tools/compiler/ti-cgt-arm_18.1.4.lts/include/stdint.h:45: parse error

  • 0 in reply to Divya S
    Guru 92251 points
    Divya S said:

    The compiler base path in the makefile is specified as,

    CCS_V8.3.0.00009\ccsv8\tools\compiler\ti-cgt-arm_18.1.4.LTS  ----> for ccs v8.3

    CCS_V7.4.0.00015\ccsv7\tools\compiler\ti-cgt-arm_16.9.6.LTS ------> for ccs v7.4

    Installing Older Versions has some information about installing older compilers into CCS. Therefore, with CCS v8.3 you should be able to install ti-cgt-arm_16.9.6.LTS

    Divya S said:
    I don't understand why the parse error,

    Can you show the makefile. I'm guessing the makefile is trying to generate include dependencies for source files, but has an error trying to parse the __has_include directive.

    Which version of make (or gmake) is being used?

  • 0 in reply to Divya S
    TI__Guru**** 249175 points
    Chester Gillon said:

    From a search found CCS/CCSTUDIO: CCS 8.1 decoding #includes incorrectly within IDE; compiler itself works. which looks to be the same issue.

    Ticket EXT_EP-9009 was raised, but the status is Declined with the comment:

    Decline Reason:CDT indexer behaves as expected

    This issue was closed because it is fixed starting with CCS version 11.0.0. 

    This ...

    Divya S said:
    In file included from ../../../../external/thirdparty/flashlib/drvfls_tmsx70f021ti01hissub/include/Types.h:34,
    from ../../../../external/bsw/flash/flashdrv.h:48,
    from include/fbl_inc.h:88,
    from Source/fbl_apwd.c:158:
    d:/uti/compiler/ti/ccs_v8.3.0.00009/ccsv8/tools/compiler/ti-cgt-arm_18.1.4.lts/include/stdint.h:45: parse error

    ... looks different from a typical diagnostic issued by the TI ARM compiler.  What tool or utility issues this diagnostic?

    Thanks and regards,

    -George