Hi,
I'm migrated a project from CCSv3 to CCSv6 and I'm fighting with all sorts of problems.
My current battle is that I'm missing the files sem.h, lck.h, tsk.h.
Any idea where these files came from? And how to replace them?
Thank you,
Ilan
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.
Hi,
I'm migrated a project from CCSv3 to CCSv6 and I'm fighting with all sorts of problems.
My current battle is that I'm missing the files sem.h, lck.h, tsk.h.
Any idea where these files came from? And how to replace them?
Thank you,
Ilan
Ilan,
What version of SYS/BIOS do you have installed with your CCSv6?
Those header files with short names are part of DSP/BIOS, which is the predecessor to the current SYS/BIOS. SYS/BIOS, up to v6.37, has support for "legacy" DSP/BIOS, and there is an app note in bios_6_37_05_35/docs/Bios_Legacy_App_Note.pdf that describes the process of importing and building a DSP/BIOS application.
Ilan Tiagai said:My current battle is that I'm missing the files sem.h, lck.h, tsk.h.
Any idea where these files came from? And how to replace them?
Those header files correspond to DSP/BIOS modules. You cannot simply replace them with some other header file, since they define and declare the APIs from DSP/BIOS that your application is using. SYS/BIOS 6 contains completely new module/API names with functionality almost identical to DSP/BIOS. DSP/BIOS SEM becomes SYS/BIOS Semaphore, DSP/BIOS TSK becomes SYS/BIOS Task, etc. While you can build your DSP/BIOS application using the legacy support, the recommended route is to convert your application to use SYS/BIOS modules/APIs. This is not a small effort, though.
Regards,
- Rob