CCS/MSP430FR5992: linker main file placement

Please see the article Linker Command File Primer.  At the end of the sub-chapter titled Form Output Sections, it gives an example of how to force an input section to be the first one in an output section.

Thanks and regards,

-George

Thanks, George:

      None of the existing groups seem appropriate, so I added the GROUP(INITIALMEMORY) as shown following:

    GROUP(SIGNATURE_SHAREDMEMORY)

    {

        .ipesignature       : {}            /* IPE Signature                     */

        .jtagpassword       : {}            /* JTAG Password                     */

    } > IPESIGNATURE

       GROUP(INITIALMEMORY)

       {

              main.obj(.text)

       } > (FRAM | FRAM2)

    .bss        : {} > RAM                  /* Global & static vars              */

    .data       : {} > RAM                  /* Global & static vars              */

    .TI.noinit  : {} > RAM                  /* For #pragma noinit                */

    .stack      : {} > RAM (HIGH)           /* Software system stack             */

    .tinyram    : {} > TINYRAM              /* Tiny R

This results in the error:  expecting section type(COPY, DSECT, or NOLOAD) instead of “.text”.

Then removed the (.text) which caused it to compile but main() still is placed at 0x13d84.  By the way the link cmd file was 

generated by ccs automatically.

What should I do?

John

Hi, George:

     Thought to facilitate this solution I'd generate a test project that has main.c, and FuncA.c and FuncB.c modules.

This project is attached.  Would like to put FuncA.obj in Fram at about 0x4800 (FRAM) and main above 0x10000 (FRAM2).

I tried several directives (marked as John) but none did the trick.

     Hopefully you can find what to do to achieve this.

Thanks,TestLinkCmd 2-12-19B.zip

John

8863.TestLinkCmd 2-12-19B.zipThanks, George:

     This didn't work with the real project (yet) so went back to the TestLinkCfg test project attached.

Would like main to start at >0x10000 and AFun to be at 0x4800.

The Results were:

This doesn’t run:

   .text

{

    main.obj(.text)

    *(.text)

} >> FRAM | FRAM2 //John/George

This puts everything in low FRAM:

   .text

{

    main.obj(.text)

    *(.text)

} >> FRAM | FRAM2 //John/George

This puts main at 0x4080 and AFun() at 0x4104.  (Would like main to start at >0x10000 and AFun to be at 0x4800)

  .text

{

    FuncA.obj(.text)

    *(.text)

} >> FRAM | FRAM2 // John/George

This project is attached as zipped files.

Thanks,

John

Thanks, George:

     You're definately a life saver.

It works on the testlinkcfg proj, now I'll put it into the real project.

John

lnk_msp430fr5994.zipHi George:

Well this didn't work in the real project. Instead it put main at 0x8184 and AFun at 0xdd8c.
Believe the code is less than 64k so the linker may not have used large model??
Attached is the zipped link cmd file.

John

George, please, before we close this:

     What if we need to have another function say BFun come right after AFun in FUNC_START(at 0x4800)?

Thanks,

John

Change this line ...

    .text:AFun > 0x4800

to something similar to ...

   output_section_for_functions
   {
      *(.text:AFun)
      *(.text:BFunc)
   } > 0x4800

This creates an output section named output_section_for_functions.  It contains, in order, all the input sections named .text:AFunc, and all the input sections named .text:BFunc.  Though there is only one of each such input sections.

Thanks and regards,

-George