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/TMDSCNCD28335: include file issues on imported older version CCS project

Part Number: TMDSCNCD28335
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

I have an older CCS 5.0 project that I am trying to get working in CCS 8.0

I am noticing that the includes files are creating compilation errors

There are 5 includes files, but I is only the top most include file that is creating the error

So I top file creates the error, and I put it on the bottom of the list, the new top file will then list he error.

I have created a screen shot below of the configuration

The image shows the include files are in a sub directory and also where the include files are called from.

I'm sure there is some link path that shows the relative location of includes files for the compiler but am not sure where to find it

  • I have tried adding the include here but no luck.. same error

  • The location you have shown in your screenshot is the correct place to add include paths for header files - Project Properties->Build->Compiler->Include Options, under --include_path. However, I don't see DSP2833x_Device.h in that directory as per your screenshot of the Project Explorer.

    Could you ensure that the paths to all the header files are specified here, then rebuild and let us know which errors remain?

  • Put this on your include list:

    C:\ti\C2000Ware\C2000Ware_1_00_06_00_Software\device_support\f2833x\headers\include

    referring to your C2000Ware product related path:

  • Jim,

    It has been a while since your last post and I assume you were able to move past this issue. If not, please feel free to post a reply with an update below or create a new thread. Thanks!
  • I'm not sure what the point of posting here if the only reply I got was that you assume it is fixed?

    I was able to fix the issue last week.  I'm not 100% sure where it got fixed.

    It seems like reinporting the project a different way may have did the trick  (as a CCS old version project)

  • jim mac said:
    I'm not sure what the point of posting here if the only reply I got was that you assume it is fixed?

    Actually there were two replies with suggestions posted - one by me and one by Tom. Since we hadn't heard back from you regarding those suggestions I was checking whether the issue was fixed.

    jim mac said:
    I was able to fix the issue last week.

    Glad to hear that the issue is fixed and you are able to move forward with your development.