• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 55 subscribers
  • Views 1332 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.

CCS/TMS320F28035: Missing Separator When Build with CGTv4.1.3 on CCSv7.2.0

Ricky Zhang
Genius 9520 points
Part Number: TMS320F28035


Tool/software: Code Composer Studio

Hi, Champs,

My customer is using CCSv7.2.0 with CGTv4.1.3 for F28035 project which is moved from early CCSv3.3.

They can build the whole project successfully but when they do an incremental build after "build all", they will get error of "missing separator" which refers to an extra "\" symbol in the end of line for included header file (see picture attached). Customer can manually remove the "\" and get the build succeeded but why this occurs? They don't have .d file in their source codes so this should be auto-generated.

I also searched similar post here but it seems not to be the same issue. Although it might relate to makefile, I'm still confused why an extra "\" is generated here.

e2e.ti.com/.../109767 separator

e2e.ti.com/.../160412 separator

Best Regards,

Ricky Zhang

  • 0
    Guru 92251 points

    Can the customer check all the places in the source code where CanIf_Cbk.h is included.

    Based upon the other threads you referenced, suspect the issue is caused by something like an extra space in one include of CanIf_Cbk.h.

    E.g. one of the source files might have something like the following (a space between the 'h' and " characters):

    #include "CanIf_Cbk.h "

  • 0 in reply to Chester Gillon
    TI__Guru**** 171309 points
    Hi,

    Interesting; a few days ago I saw the exact same issue and the root cause is identical to what was mentioned by Chester. The backslash in the .d listing file is, in fact, an escape <space> character or \0x20

    Regards,
    Rafael
  • 0 in reply to Chester Gillon
    TI__Genius 9520 points

    Chester, Lafael,

    Thanks for timely response.

    Customer did find "the extra space" between the 'h' and " characters.

    This issue was fixed and the post can be closed now.

    Best Regards,

    Ricky Zhang