• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 678 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

hex6x ROMS spec file and linker preprocessing command settings

Suresh Chandresekar
Prodigy 210 points

The linker command file can use preprocessing directives on env. variables, such as

#ifdef SPECIAL_BUILD

 

#endif

Is there any way to use preprocessing directives in the hex6x ROMS specification as well?

I have a situation where I only want to generate one binary image if SPECIAL_BUILD defined, otherwise I want to generate two. 

 What I'm envisioning...

ROMS

{

#ifdef SPECIAL_BUILD

ROW1: origin=0x00000000 len=0x4000 romwidth=8

files={ appl.u0 appl.u1 app1.u2 appl.u3 }

#else

ROW2: origin=0x00004000 len=0x4000 romwidth=8

files={ app1.u4 appl.u5 appl.u6 appl.u7 }

#endif

}

Thanks

Suresh

  • 0
    TI__Guru**** 244930 points

    Suresh Chandresekar said:
    The linker command file can use preprocessing directives on env. variables

    I know what you are saying.  But I can't help but correct one minor error here.  Linker preprocessing does not look at OS level environment variables, but at preprocessing symbols set either on the linker command line or by an earlier #define directive.

    Suresh Chandresekar said:
    Is there any way to use preprocessing directives in the hex6x ROMS specification as well?

    Unfortunately, no.  I filed SDSCM00050829 in the SDOWP system to request that this feature be added to the hex utility.  You are welcome to track it with the SDOWP link below in my signature.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 210 points

    George,

    Thank you :)

    S