• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 346 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.

HAl.h cannot be opened

fylith
Prodigy 40 points
Other Parts Discussed in Thread: SIMPLICITI

I put Hal.h and all the other Hal.h files into the folders just like simplicity ti has them and put them in my project just like some ti code example has it. but when i try to run my project it comes up with a Hal.h not found error. if i put my main.c into the simplicity folder where their code is and attach it to their project then my code compiles fine. if i look at where the folders are in my project and simplicities project the only dif is theirs is in their project folder. I even changed the calling to make sure it called the hal.h files from the correct folders in my project folder but still it says it cant open Hal.h. what am i doing wrong? i would love to use Hal and simplicity but i cant figure out this problem. thanks Kim

sorry forgot to metion that i am using a 2510 soc and IAR kickstart.

  • 0
    Prodigy 40 points

    i guess noone can help me?

  • 0 in reply to fylith
    TI__Guru 64510 points

    Perhaps if you could describe the structure of your project it might help.

    It appears you are using SimpliciTI and wanting to integrate it into your own application project.  Have you modeled your project similar to the examples that are provided in the SimpliciTI release?  This is often a good way to make sure things work well from the start.  Of course, you may want to change the structure, but getting started with an example is always good.

    From your original post, it sounds like in a particular arrangement of file structure, etc, you are able to build the application.  But from what I gather, if you move your own application code to another directory and try to build, it does not work.  This sounds like a path issue to me when communicating to the compiler where your sources are and where it can find the various header and library files.