• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 52 subscribers
  • Views 3076 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.

Original question:

Cannot access driverlib.h

CCS/TMS320F28379D: Getting problem with including header file "driverlib.h"

Adarsh Kumar1
Prodigy 70 points

Part Number: TMS320F28379D
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

I was trying to configure pins as a input or output pin. On building the code, it gave error message

"fatal error #1965: cannot open source file "driverlib.h"

I looked through the forum and found that I needed to include the directory to #include search path

I added the following two directories.

I built the code again and got the following error.

I looked through the driverlib.h file and found that it includes "inc/hw_memmap.h" header file. I searched in C2000ware software and found the corresponding header file. I copied the "inc" folder to the directory added in search path. 

I built the code again and got this error message:

I found that adc.h is the next header file included in driverlib.h file. I don't think that copying every header file in the above directory is the solution to the error. What can I do?

  • 0
    TI__Guru**** 173310 points

    It appears that your project is using a combination of bit-field structures and driver library APIs. If you are needing both, then yes you do have more include paths to provide so the compiler is able to find all the required header files. I would recommend importing the example project named "Driverlib + Bit-Field Empty Example CCS Project" from C2000Ware and taking a look at the include paths in that example. That is a minimum set you would need for such projects.

    On the other hand, if you choose either the bit-field method or driverlib API method of development, then fewer include paths would be required. Again looking at one of the C2000Ware examples (either under Bitfield or Driverlib) should give you an idea of the minimum set of required include paths.

    Hope this helps.