CCS/TCI6630K2L: using CSL in non-OS project

R6MF49T2

Part Number: TCI6630K2L

Tool/software: Code Composer Studio

Hello

I create new project in CSS v7.4.0.00015
In project propertis - Products - enabled "Keystone2 PDK" v 3.1.0.3

In "C6000 Compiler" - "Include Options" I see "${TI_PDK_INCLUDE_PATH}", but this variable = <none>
In "C6000 Compiler" - "Predefined Symbols" I see ${TI_PDK_SYMBOLS}, but this variable = <none>
In "C6000 Linker" - "File Search Path" I see ${TI_PDK_LIBRARIES} and ${TI_PDK_LIBRARY_PATH}, but this variables = <none>
How to properly connect the csl to the non-OS project?

over 7 years ago

0 R6MF49T2 over 7 years ago

Prodigy 50 points

Any thoughts?

0 Yordan Kovachev over 7 years ago in reply to R6MF49T2

TI__Guru**** 161600 points

We're looking into this.

Best Regards,
Yordan

0 db_woodall over 7 years ago

TI__Mastermind 21025 points

You can either define these yourself, or try importing one of the driver tests to CCS, see what these variables are set to, then copy them to your project. In either case, they should point to the C:\ti\xxx folder where the components are installed.

0 R6MF49T2 over 7 years ago in reply to db_woodall

Prodigy 50 points

If connect manually, then there is no problem, but then why is it necessary item in the property project - Products - "Keystone 2 PDK"?

0 db_woodall over 7 years ago in reply to R6MF49T2

TI__Mastermind 21025 points

For non-OS projects, you shouldn't have to specify the PDK product if you are specifying the paths manually. The best way to check is to look at the output in the Console window when you are doing a build. It will list all the paths that it has constructed from the defined variables. Another way is to look at the project properties - at the top level properties for "Compiler" and "Linker". It should list all the flags and paths that it will use in a build.

Processors

Processors forum

CCS/TCI6630K2L: using CSL in non-OS project