Part Number: 66AK2H14
Tool/software: Code Composer Studio
I am using 66AK2H14 processor with TI-RTOS/SYS-BIOS using CCSV7 tool.
I created my own application code as required by the client, for that I had to include driver file. So when I include driver file using "#include", I got fatal error.
c:\ti\pdk_k2hk_4_0_6\packages\ti\drv\gpio\soc\gpio_soc.h:45:30: fatal error: ti/drv/gpio/GPIO.h: No such file or directory #include <ti/drv/gpio/GPIO.h>
and also how to include ti/drv/gpio/src/GPIO_drv.c- This file contains the GPIO driver interface APIs. These APIs are used for configuration of general purpose I/O instanace. Using that file I have writtern application code.
I request you to tell me the procedure to include driver code to our own created application project as soon as possible.
Thanks and Regards,
In reply to desouza:
Thanks for your reply.
I have added my files which I needed. Later I referred example project C:\ti\pdk_k2hk_4_0_6\packages\ti\drv\gpio\test\led_blink\src/main_led_blink.c. It successfully got built without any errors.
So I included all files, header files, and directories path which are inserted in example project. But when I compiled my project(GPIO_int_app.c) I am getting error for GPIO_board.c file which is also included in already existing example project. Since I have inserted same file from example, I am not able to make out why those errors are coming to my project.
For your reference I have attached my project and even the screenshot of my project's error. Please help me to solve this error as soon as possible.
In reply to Aishwarya Bhat:
Thanks for sending the project. I noticed there are a few differences between your project and the example shipped with the SDK (GPIO_LebBlink_K2H_EVM_armTestProject):
- Some compiler symbols are missing, namely evmK2H and SOC_K2H. (under GNU Complier → Symbols → Define symbols)
- After inserting these, the project started to show some internal SYSBIOS errors that are described at section 10.6 of the page below:
- Per the description above, I removed the libraries gcc, m, nosys and c from the linker (under GNU Linker → Libraries → Libraries) and matched the paths to the Library Search Path shown in the example project.
- I then removed the option -specs=nano.specs from the Linker options (GNU Linker → Miscellaneous → Other flags) and added the option "rdimon.specs" to the Compiler options (GNU Compiler → Miscellaneous → Override built-in specs with... ) - this option adds a few libraries
- In the same screen I also matched the Assembly source specific flags and Other flags with the example project.
- I cleaned several include paths and references to source files .
At this point the project itself failed to build as the main source file does not define the task gpio_test (which you need to define) and other issues related to the migration process per se. In this case, I would strongly suggest you to check with the experts at the device forum.
The project I modified is shown attached.
Hope this helps,
How to contact experts to solve this problem? Can you suggest any one to help me as soon possible.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.