• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 535 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.

Definitions for XS tool in SYS BIOS 6.30

palanivel guruvareddiar
Prodigy 100 points

Other Parts Discussed in Thread: OMAPL138

Hi,

I'm working with SYS BIOS 6.30.xx.xx  on a EVM OMAPL138 platform.

I'm also using 'customized' platform support package.

In my bios configuration file I have,

var name         = xdc.useModule ("ti.psp.mypsp");

and in "mypsp.h" I have the following piece of code,

#ifdef CHIP_C6748

           <do something>

#else

         printf("Error - No valid chip configuration");

#endif

I invoked the xs tool by,

xs -DCHIP_C6748 xdc.tools.configuro .........................

But I'm getting the error message of (Error - No valid chip configuration), though I defined CHIP_C6748.

Even I tried with,

xs  xdc.tools.configuro -DCHIP_C6748 .........................

But the result is same.

What I'm doing wrong here?

Thanks in advance.

Thanks & Best regards

Palanivel Guruvareddiar

  • 0
    TI__Mastermind 37985 points

    Palanivel,
    the command line variables supplied to configuro do not automatically transfer to C code. Are you using CCS4? If yes, then in Build Properties for your project, in C/C++ Build -> Tool Settings -> Predefined Symbols, you can define symbols that can be seen by the compiler.

    If you are not using CCS4, please let me know how are you building your code. Are you using package.bld files? In that case, whenever you define an executable with Pkg.addExecutable, you can add definitions using attrs.defs for that executable (http://rtsc.eclipse.org/cdoc-tip/xdc/bld/Executable.html#.Attrs).

  • 0 in reply to Sasha Slijepcevic
    Prodigy 100 points

    Hi Sasha,

    I'm using Make file environment in windows.

    BTW, I solved the issue by,

    xs  xdc.tools.configuro compileOptions "CHIP_C6748"  .........................

    I overlooked the documentation & assumed that -D option is for definition (in fact it looks like it will

    enable Java property).

    Thanks for your help.

    Thanks & Best regards

    Palanivel Guruvareddiar