DSPRelated.com
Forums
   Forums    More Forums    c6x  

linking warning in fastrts67x.lib

Started by nishank pathak ●February 10, 2009
HI,
I get the following warning message on including fastrts67x.lib. Can anyone help?
 
>> warning: creating output section text without SECTIONS specification
 
Thanks
Nishank

_____________________________________
Reply by Michael Dunn ●February 10, 20092009-02-10
Nishank,

On Tue, Feb 10, 2009 at 1:33 PM, nishank pathak
wrote:
> HI,
> I get the following warning message on including fastrts67x.lib. Can anyone
> help?
>
>>> warning: creating output section text without SECTIONS specification


You have a missing or incomplete linker command file {LCF]. These
files are named .cmd and should appear in your project.

mikedunn
>
> Thanks
> Nishank

--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php

_____________________________________
Reply by nishank pathak ●February 10, 20092009-02-10
Also the link. cmd which I sent previosly includes appcfg.cmd which has a text section
 
SECTIONS {
        .bss:     {} > IRAM
       
        .far:     {} > IRAM
       
        .sysdata: {} > IRAM
       
        .mem:    {} > IRAM
       
        .sysinit:    {} > IRAM
       
        .sysregs: {} > IRAM
       
        .gblinit:    {} > IRAM
       
        .trcdata:    {} > IRAM
       
        .args: fill=0 {
            *(.args)
            . += 0x4;
        } > IRAM
       
        .cinit:    {} > IRAM
       
        .pinit:   {} > IRAM
       
        .data:    {} > IRAM
       
        .const:    {} > IRAM
       
        .switch:    {} > IRAM
       
        .cio:     {} > IRAM
       
        .text:    {} > IRAM
       
        frt:    {} > IRAM
       
        .bios:    {} > IRAM
       
        .stack: fill=0xc0ffee {
            GBL_stackbeg = .;
            *(.stack)
            GBL_stackend = GBL_stackbeg + 0x400 - 1;
            _HWI_STKBOTTOM = GBL_stackbeg + 0x400 - 4 & ~7;
            _HWI_STKTOP = GBL_stackbeg;
        } > IRAM
       
        .devtable: {} > IRAM
       
        .gio:     {} > IRAM
       
        .rtdx_data: {}  > IRAM
       
        .rtdx_text: {}  > IRAM
       
        .hst: {
             HST_A_TABBEG = .;
            _HST_A_TABBEG = .;
            *(.hst)
            HST_A_TABEND = .;
            _HST_A_TABEND = .;
             HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
            _HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
        } > IRAM
       
        .dsm: {} > IRAM
       
       /* RTA_fromHost buffer */
       .hst1: align = 0x4 {} > IRAM
       
       /* RTA_toHost buffer */
       .hst0: align = 0x4 {} > IRAM
       
        .hwi: {}  > IRAM
       
        .log: {
             LOG_A_TABBEG = .;
            _LOG_A_TABBEG = .;
            *(.log)
            LOG_A_TABEND = .;
            _LOG_A_TABEND = .;
             LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
            _LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
        } > IRAM
       
        .printf (COPY): {} > IRAM
       
        /* LOG_system buffer */
        .LOG_system$buf: align = 0x200 fill = 0xffffffff {} > IRAM
       
        /* logTrace buffer */
        .logTrace$buf: align = 0x200 fill = 0xffffffff {} > IRAM
       
        .pip: {
             PIP_A_TABBEG = .;
            _PIP_A_TABBEG = .;
            *(.pip)
            PIP_A_TABEND = .;
            _PIP_A_TABEND = .;
             PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
            _PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
        } > IRAM
       
        /* pipRx buffer */
        .pip0: align = 0x80 {} > IRAM
       
        /* pipRx0 buffer */
        .pip1: align = 0x100 {} > IRAM
       
        /* pipTx0 buffer */
        .pip2: {} > IRAM
       
        /* pipRx1 buffer */
        .pip3: align = 0x100 {} > IRAM
       
        /* pipTx1 buffer */
        .pip4: {} > IRAM
       
        /* pipTx buffer */
        .pip5: align = 0x80 {} > IRAM
       
        .sts: {
             STS_A_TABBEG = .;
            _STS_A_TABBEG = .;
            *(.sts)
            STS_A_TABEND = .;
            _STS_A_TABEND = .;
             STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
            _STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
        } > IRAM
       
        .sys:     {} > IRAM
       
        .udev: {} > IRAM
       
        .IRAM$heap: {
            IRAM$B = .;
            _IRAM_base = .;
            IRAM$L = 0x5e20;
            _IRAM_length = 0x5e20;
            . += 0x5e20;
        } > IRAM
       
        .SDRAM$heap: {
            SDRAM$B = .;
            _SDRAM_base = .;
            SDRAM$L = 0x90000;
            _SDRAM_length = 0x90000;
            . += 0x90000;
        } > SDRAM
       
}
--- On Wed, 11/2/09, Michael Dunn wrote:

From: Michael Dunn
Subject: Re: [c6x] linking warning in fastrts67x.lib
To: n...@yahoo.co.in
Cc: c...
Date: Wednesday, 11 February, 2009, 4:24 AM

Nishank,

On Tue, Feb 10, 2009 at 1:33 PM, nishank pathak
wrote:
> HI,
> I get the following warning message on including fastrts67x.lib. Can anyone
> help?
>
>>> warning: creating output section text without SECTIONS specification


You have a missing or incomplete linker command file {LCF]. These
files are named . cmd and should appear in your project.

mikedunn
>
> Thanks
> Nishank

--
www.dsprelated. com/blogs- 1/nf/Mike_ Dunn.php
Reply by nishank pathak ●February 10, 20092009-02-10
Hi Mike,
this is my link.cmd file
 
-l appcfg.cmd
/* include libraries for the IOM driver */
-l dsk6713_edma_aic23.l67
-l c6x1x_edma_mcbsp.l67
/* PIP to IOM adapter */
-l pio.l62
/* include the UTL debugging module (if needed) */
-l utl.l62
/* include the RF3 module implementing XDAIS algs. instantiation procedures */
-l algrf.l62
/*
 *  Algorithm FIR: bind the generic FIR symbol to TI's implementation
 *  of the algorithm, and include the appropriate library
 */
-l fir_ti.l62
_FIR_IFIR = _FIR_TI_IFIR;
 
I guess I have to add -l fastrts67x.lib, but I have tried that also and it is still the same.
 
Thanks
Nishank
 
 
--- On Wed, 11/2/09, Michael Dunn wrote:

From: Michael Dunn
Subject: Re: [c6x] linking warning in fastrts67x.lib
To: n...@yahoo.co.in
Cc: c...
Date: Wednesday, 11 February, 2009, 4:24 AM

Nishank,

On Tue, Feb 10, 2009 at 1:33 PM, nishank pathak
wrote:
> HI,
> I get the following warning message on including fastrts67x.lib. Can
anyone
> help?
>
>>> warning: creating output section text without SECTIONS
specification


You have a missing or incomplete linker command file {LCF]. These
files are named .cmd and should appear in your project.

mikedunn
>
> Thanks
> Nishank

--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
Reply by Michael Dunn ●February 10, 20092009-02-10
Nishank,

On Tue, Feb 10, 2009 at 5:45 PM, nishank pathak
wrote:
>
> Also the link. cmd which I sent previosly includes appcfg.cmd which has a
> text section
>
> SECTIONS {
> .bss: {} > IRAM
>
> .far: {} > IRAM
>
> .sysdata: {} > IRAM
>
> .mem: {} > IRAM
>
> .sysinit: {} > IRAM
>
> .sysregs: {} > IRAM
>
> .gblinit: {} > IRAM
>
> .trcdata: {} > IRAM
>
> .args: fill=0 {
> *(.args)
> . += 0x4;
> } > IRAM
>
> .cinit: {} > IRAM
>
> .pinit: {} > IRAM
>
> .data: {} > IRAM
>
> .const: {} > IRAM
>
> .switch: {} > IRAM
>
> .cio: {} > IRAM
>
> .text: {} > IRAM

---
Look at your linker map file.
It looks like the '.text' was created in 'IRAM' only. You probably ran
out of IRAM and the compiler automatically created a .text. section in
SDRAM for the code that did not fit.

mikedunn
>
> frt: {} > IRAM
>
> .bios: {} > IRAM
>
> .stack: fill=0xc0ffee {
> GBL_stackbeg = .;
> *(.stack)
> GBL_stackend = GBL_stackbeg + 0x400 - 1;
> _HWI_STKBOTTOM = GBL_stackbeg + 0x400 - 4 & ~7;
> _HWI_STKTOP = GBL_stackbeg;
> } > IRAM
>
> .devtable: {} > IRAM
>
> .gio: {} > IRAM
>
> .rtdx_data: {} > IRAM
>
> .rtdx_text: {} > IRAM
>
> .hst: {
> HST_A_TABBEG = .;
> _HST_A_TABBEG = .;
> *(.hst)
> HST_A_TABEND = .;
> _HST_A_TABEND = .;
> HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
> _HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
> } > IRAM
>
> .dsm: {} > IRAM
>
> /* RTA_fromHost buffer */
> .hst1: align = 0x4 {} > IRAM
>
> /* RTA_toHost buffer */
> .hst0: align = 0x4 {} > IRAM
>
> .hwi: {} > IRAM
>
> .log: {
> LOG_A_TABBEG = .;
> _LOG_A_TABBEG = .;
> *(.log)
> LOG_A_TABEND = .;
> _LOG_A_TABEND = .;
> LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
> _LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
> } > IRAM
>
> .printf (COPY): {} > IRAM
>
> /* LOG_system buffer */
> .LOG_system$buf: align = 0x200 fill = 0xffffffff {} > IRAM
>
> /* logTrace buffer */
> .logTrace$buf: align = 0x200 fill = 0xffffffff {} > IRAM
>
> .pip: {
> PIP_A_TABBEG = .;
> _PIP_A_TABBEG = .;
> *(.pip)
> PIP_A_TABEND = .;
> _PIP_A_TABEND = .;
> PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
> _PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
> } > IRAM
>
> /* pipRx buffer */
> .pip0: align = 0x80 {} > IRAM
>
> /* pipRx0 buffer */
> .pip1: align = 0x100 {} > IRAM
>
> /* pipTx0 buffer */
> .pip2: {} > IRAM
>
> /* pipRx1 buffer */
> .pip3: align = 0x100 {} > IRAM
>
> /* pipTx1 buffer */
> .pip4: {} > IRAM
>
> /* pipTx buffer */
> .pip5: align = 0x80 {} > IRAM
>
> .sts: {
> STS_A_TABBEG = .;
> _STS_A_TABBEG = .;
> *(.sts)
> STS_A_TABEND = .;
> _STS_A_TABEND = .;
> STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
> _STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
> } > IRAM
>
> .sys: {} > IRAM
>
> .udev: {} > IRAM
>
> .IRAM$heap: {
> IRAM$B = .;
> _IRAM_base = .;
> IRAM$L = 0x5e20;
> _IRAM_length = 0x5e20;
> . += 0x5e20;
> } > IRAM
>
> .SDRAM$heap: {
> SDRAM$B = .;
> _SDRAM_base = .;
> SDRAM$L = 0x90000;
> _SDRAM_length = 0x90000;
> . += 0x90000;
> } > SDRAM
>
> }
> --- On Wed, 11/2/09, Michael Dunn wrote:
>
> From: Michael Dunn
> Subject: Re: [c6x] linking warning in fastrts67x.lib
> To: n...@yahoo.co.in
> Cc: c...
> Date: Wednesday, 11 February, 2009, 4:24 AM
>
> Nishank,
>
> On Tue, Feb 10, 2009 at 1:33 PM, nishank pathak
> wrote:
>> HI,
>> I get the following warning message on including fastrts67x.lib. Can
>> anyone
>> help?
>>
>>>> warning: creating output section text without SECTIONS specification
>
>
> You have a missing or incomplete linker command file {LCF]. These
> files are named . cmd and should appear in your project.
>
> mikedunn
>>
>> Thanks
>> Nishank
>>
>> --
> www.dsprelated. com/blogs- 1/nf/Mike_ Dunn.php
> ________________________________
> Get perfect Email ID for your Resume. Get before others grab.

--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php

_____________________________________
Reply by nishank pathak ●February 10, 20092009-02-10
Mike,
I am gettin gthe same warning even after putting the .text to SDRAM.
 
Thanks
Nishank
 
--- On Wed, 11/2/09, Michael Dunn wrote:

From: Michael Dunn
Subject: Re: [c6x] linking warning in fastrts67x.lib
To: n...@yahoo.co.in, "C6x"
Date: Wednesday, 11 February, 2009, 5:30 AM

Nishank,

On Tue, Feb 10, 2009 at 5:45 PM, nishank pathak
wrote:
>
> Also the link. cmd which I sent previosly includes appcfg.cmd which has a
> text section
>
> SECTIONS {
> .bss: {} > IRAM
>
> .far: {} > IRAM
>
> .sysdata: {} > IRAM
>
> .mem: {} > IRAM
>
> .sysinit: {} > IRAM
>
> .sysregs: {} > IRAM
>
> .gblinit: {} > IRAM
>
> .trcdata: {} > IRAM
>
> .args: fill=0 {
> *(.args)
> . += 0x4;
> } > IRAM
>
> .cinit: {} > IRAM
>
> .pinit: {} > IRAM
>
> .data: {} > IRAM
>
> .const: {} > IRAM
>
> .switch: {} > IRAM
>
> .cio: {} > IRAM
>
> .text: {} > IRAM

---
Look at your linker map file.
It looks like the '.text' was created in 'IRAM' only. You
probably ran
out of IRAM and the compiler automatically created a .text. section in
SDRAM for the code that did not fit.

mikedunn
>
> frt: {} > IRAM
>
> .bios: {} > IRAM
>
> .stack: fill=0xc0ffee {
> GBL_stackbeg = .;
> *(.stack)
> GBL_stackend = GBL_stackbeg + 0x400 - 1;
> _HWI_STKBOTTOM = GBL_stackbeg + 0x400 - 4 & ~7;
> _HWI_STKTOP = GBL_stackbeg;
> } > IRAM
>
> .devtable: {} > IRAM
>
> .gio: {} > IRAM
>
> .rtdx_data: {} > IRAM
>
> .rtdx_text: {} > IRAM
>
> .hst: {
> HST_A_TABBEG = .;
> _HST_A_TABBEG = .;
> *(.hst)
> HST_A_TABEND = .;
> _HST_A_TABEND = .;
> HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
> _HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
> } > IRAM
>
> .dsm: {} > IRAM
>
> /* RTA_fromHost buffer */
> .hst1: align = 0x4 {} > IRAM
>
> /* RTA_toHost buffer */
> .hst0: align = 0x4 {} > IRAM
>
> .hwi: {} > IRAM
>
> .log: {
> LOG_A_TABBEG = .;
> _LOG_A_TABBEG = .;
> *(.log)
> LOG_A_TABEND = .;
> _LOG_A_TABEND = .;
> LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
> _LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
> } > IRAM
>
> .printf (COPY): {} > IRAM
>
> /* LOG_system buffer */
> .LOG_system$buf: align = 0x200 fill = 0xffffffff {} > IRAM
>
> /* logTrace buffer */
> .logTrace$buf: align = 0x200 fill = 0xffffffff {} > IRAM
>
> .pip: {
> PIP_A_TABBEG = .;
> _PIP_A_TABBEG = .;
> *(.pip)
> PIP_A_TABEND = .;
> _PIP_A_TABEND = .;
> PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
> _PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
> } > IRAM
>
> /* pipRx buffer */
> .pip0: align = 0x80 {} > IRAM
>
> /* pipRx0 buffer */
> .pip1: align = 0x100 {} > IRAM
>
> /* pipTx0 buffer */
> .pip2: {} > IRAM
>
> /* pipRx1 buffer */
> .pip3: align = 0x100 {} > IRAM
>
> /* pipTx1 buffer */
> .pip4: {} > IRAM
>
> /* pipTx buffer */
> .pip5: align = 0x80 {} > IRAM
>
> .sts: {
> STS_A_TABBEG = .;
> _STS_A_TABBEG = .;
> *(.sts)
> STS_A_TABEND = .;
> _STS_A_TABEND = .;
> STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
> _STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
> } > IRAM
>
> .sys: {} > IRAM
>
> .udev: {} > IRAM
>
> .IRAM$heap: {
> IRAM$B = .;
> _IRAM_base = .;
> IRAM$L = 0x5e20;
> _IRAM_length = 0x5e20;
> . += 0x5e20;
> } > IRAM
>
> .SDRAM$heap: {
> SDRAM$B = .;
> _SDRAM_base = .;
> SDRAM$L = 0x90000;
> _SDRAM_length = 0x90000;
> . += 0x90000;
> } > SDRAM
>
> }
> --- On Wed, 11/2/09, Michael Dunn wrote:
>
> From: Michael Dunn
> Subject: Re: [c6x] linking warning in fastrts67x.lib
> To: n...@yahoo.co.in
> Cc: c...
> Date: Wednesday, 11 February, 2009, 4:24 AM
>
> Nishank,
>
> On Tue, Feb 10, 2009 at 1:33 PM, nishank pathak
> wrote:
>> HI,
>> I get the following warning message on including fastrts67x.lib. Can
>> anyone
>> help?
>>
>>>> warning: creating output section text without SECTIONS
specification
>
>
> You have a missing or incomplete linker command file {LCF]. These
> files are named . cmd and should appear in your project.
>
> mikedunn
>>
>> Thanks
>> Nishank
>>
>> --
> www.dsprelated. com/blogs- 1/nf/Mike_ Dunn.php
> ________________________________
>
Reply by Michael Dunn ●February 10, 20092009-02-10
Nishank,

On Tue, Feb 10, 2009 at 6:07 PM, nishank pathak
wrote:
>
> Mike,
> I am gettin gthe same warning even after putting the .text to SDRAM.


Look at your map file carefully. Is there a section 'text' and a
section '.text'??

I'm not exactly sure if the above is your problem, but there should be
some section in the map file that was added by the linker.

You are proceeding down the correct path. When you have a compiler or
linker warning, you should resolve it [or in some rare cases you may
just understand why it is occurring if it is benign].

mikedunn
>
> Thanks
> Nishank
>
> --- On Wed, 11/2/09, Michael Dunn wrote:
>
> From: Michael Dunn
> Subject: Re: [c6x] linking warning in fastrts67x.lib
> To: n...@yahoo.co.in, "C6x"
> Date: Wednesday, 11 February, 2009, 5:30 AM
>
> Nishank,
>
> On Tue, Feb 10, 2009 at 5:45 PM, nishank pathak
> wrote:
>>
>> Also the link. cmd which I sent previosly includes appcfg.cmd which has a
>> text section
>>
>> SECTIONS {
>> .bss: {} > IRAM
>>
>> .far: {} > IRAM
>>
>> .sysdata: {} > IRAM
>>
>> .mem: {} > IRAM
>>
>> .sysinit: {} > IRAM
>>
>> .sysregs: {} > IRAM
>>
>> .gblinit: {} > IRAM
>>
>> .trcdata: {} > IRAM
>>
>> .args: fill=0 {
>> *(.args)
>> . += 0x4;
>> } > IRAM
>>
>> .cinit: {} > IRAM
>>
>> .pinit: {} > IRAM
>>
>> .data: {} > IRAM
>>
>> .const: {} > IRAM
>>
>> .switch: {} > IRAM
>>
>> .cio: {} > IRAM
>>
>> .text: {} > IRAM
>
> ---
> Look at your linker map file.
> It looks like the '.text' was created in 'IRAM' only. You
> probably ran
> out of IRAM and the compiler automatically created a .text. section in
> SDRAM for the code that did not fit.
>
> mikedunn
>>
>> frt: {} > IRAM
>>
>> .bios: {} > IRAM
>>
>> .stack: fill=0xc0ffee {
>> GBL_stackbeg = .;
>> *(.stack)
>> GBL_stackend = GBL_stackbeg + 0x400 - 1;
>> _HWI_STKBOTTOM = GBL_stackbeg + 0x400 - 4 & ~7;
>> _HWI_STKTOP = GBL_stackbeg;
>> } > IRAM
>>
>> .devtable: {} > IRAM
>>
>> .gio: {} > IRAM
>>
>> .rtdx_data: {} > IRAM
>>
>> .rtdx_text: {} > IRAM
>>
>> .hst: {
>> HST_A_TABBEG = .;
>> _HST_A_TABBEG = .;
>> *(.hst)
>> HST_A_TABEND = .;
>> _HST_A_TABEND = .;
>> HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
>> _HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
>> } > IRAM
>>
>> .dsm: {} > IRAM
>>
>> /* RTA_fromHost buffer */
>> .hst1: align = 0x4 {} > IRAM
>>
>> /* RTA_toHost buffer */
>> .hst0: align = 0x4 {} > IRAM
>>
>> .hwi: {} > IRAM
>>
>> .log: {
>> LOG_A_TABBEG = .;
>> _LOG_A_TABBEG = .;
>> *(.log)
>> LOG_A_TABEND = .;
>> _LOG_A_TABEND = .;
>> LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
>> _LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
>> } > IRAM
>>
>> .printf (COPY): {} > IRAM
>>
>> /* LOG_system buffer */
>> .LOG_system$buf: align = 0x200 fill = 0xffffffff {} > IRAM
>>
>> /* logTrace buffer */
>> .logTrace$buf: align = 0x200 fill = 0xffffffff {} > IRAM
>>
>> .pip: {
>> PIP_A_TABBEG = .;
>> _PIP_A_TABBEG = .;
>> *(.pip)
>> PIP_A_TABEND = .;
>> _PIP_A_TABEND = .;
>> PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
>> _PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
>> } > IRAM
>>
>> /* pipRx buffer */
>> .pip0: align = 0x80 {} > IRAM
>>
>> /* pipRx0 buffer */
>> .pip1: align = 0x100 {} > IRAM
>>
>> /* pipTx0 buffer */
>> .pip2: {} > IRAM
>>
>> /* pipRx1 buffer */
>> .pip3: align = 0x100 {} > IRAM
>>
>> /* pipTx1 buffer */
>> .pip4: {} > IRAM
>>
>> /* pipTx buffer */
>> .pip5: align = 0x80 {} > IRAM
>>
>> .sts: {
>> STS_A_TABBEG = .;
>> _STS_A_TABBEG = .;
>> *(.sts)
>> STS_A_TABEND = .;
>> _STS_A_TABEND = .;
>> STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
>> _STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
>> } > IRAM
>>
>> .sys: {} > IRAM
>>
>> .udev: {} > IRAM
>>
>> .IRAM$heap: {
>> IRAM$B = .;
>> _IRAM_base = .;
>> IRAM$L = 0x5e20;
>> _IRAM_length = 0x5e20;
>> . += 0x5e20;
>> } > IRAM
>>
>> .SDRAM$heap: {
>> SDRAM$B = .;
>> _SDRAM_base = .;
>> SDRAM$L = 0x90000;
>> _SDRAM_length = 0x90000;
>> . += 0x90000;
>> } > SDRAM
>>
>> }
>> --- On Wed, 11/2/09, Michael Dunn wrote:
>>
>> From: Michael Dunn
>> Subject: Re: [c6x] linking warning in fastrts67x.lib
>> To: n...@yahoo.co.in
>> Cc: c...
>> Date: Wednesday, 11 February, 2009, 4:24 AM
>>
>> Nishank,
>>
>> On Tue, Feb 10, 2009 at 1:33 PM, nishank pathak
>> wrote:
>>> HI,
>>> I get the following warning message on including fastrts67x.lib. Can
>>> anyone
>>> help?
>>>
>>>>> warning: creating output section text without SECTIONS
> specification
>>
>>
>> You have a missing or incomplete linker command file {LCF]. These
>> files are named . cmd and should appear in your project.
>>
>> mikedunn
>>>
>>> Thanks
>>> Nishank
>>>
>>> --
>> www.dsprelated. com/blogs- 1/nf/Mike_ Dunn.php
>> ________________________________
>> Get perfect Email ID for your Resume. Get before others grab.
>
> --
> www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
>
> ________________________________
> Get rid of Add-Ons in your email ID. Get y...@rocketmail.com. Sign up
> now!

--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php

_____________________________________
Reply by nishank pathak ●February 10, 20092009-02-10
Mike,
Yes, I have 2 sections 'text' and '.text' , How to resolve this?
Thanks
Nishank
--- On Wed, 11/2/09, Michael Dunn wrote:

From: Michael Dunn
Subject: Re: [c6x] linking warning in fastrts67x.lib
To: n...@yahoo.co.in
Cc: "C6x"
Date: Wednesday, 11 February, 2009, 5:49 AM

Nishank,

On Tue, Feb 10, 2009 at 6:07 PM, nishank pathak
wrote:
>
> Mike,
> I am gettin gthe same warning even after putting the .text to SDRAM.


Look at your map file carefully. Is there a section 'text' and a
section '.text'??

I'm not exactly sure if the above is your problem, but there should be
some section in the map file that was added by the linker.

You are proceeding down the correct path. When you have a compiler or
linker warning, you should resolve it [or in some rare cases you may
just understand why it is occurring if it is benign].

mikedunn
>
> Thanks
> Nishank
>
> --- On Wed, 11/2/09, Michael Dunn wrote:
>
> From: Michael Dunn
> Subject: Re: [c6x] linking warning in fastrts67x.lib
> To: n...@yahoo.co.in, "C6x"
> Date: Wednesday, 11 February, 2009, 5:30 AM
>
> Nishank,
>
> On Tue, Feb 10, 2009 at 5:45 PM, nishank pathak
> wrote:
>>
>> Also the link. cmd which I sent previosly includes appcfg.cmd which
has a
>> text section
>>
>> SECTIONS {
>> .bss: {} > IRAM
>>
>> .far: {} > IRAM
>>
>> .sysdata: {} > IRAM
>>
>> .mem: {} > IRAM
>>
>> .sysinit: {} > IRAM
>>
>> .sysregs: {} > IRAM
>>
>> .gblinit: {} > IRAM
>>
>> .trcdata: {} > IRAM
>>
>> .args: fill=0 {
>> *(.args)
>> . += 0x4;
>> } > IRAM
>>
>> .cinit: {} > IRAM
>>
>> .pinit: {} > IRAM
>>
>> .data: {} > IRAM
>>
>> .const: {} > IRAM
>>
>> .switch: {} > IRAM
>>
>> .cio: {} > IRAM
>>
>> .text: {} > IRAM
>
> ---
> Look at your linker map file.
> It looks like the '.text' was created in 'IRAM' only. You
> probably ran
> out of IRAM and the compiler automatically created a .text. section in
> SDRAM for the code that did not fit.
>
> mikedunn
>>
>> frt: {} > IRAM
>>
>> .bios: {} > IRAM
>>
>> .stack: fill=0xc0ffee {
>> GBL_stackbeg = .;
>> *(.stack)
>> GBL_stackend = GBL_stackbeg + 0x400 - 1;
>> _HWI_STKBOTTOM = GBL_stackbeg + 0x400 - 4 & ~7;
>> _HWI_STKTOP = GBL_stackbeg;
>> } > IRAM
>>
>> .devtable: {} > IRAM
>>
>> .gio: {} > IRAM
>>
>> .rtdx_data: {} > IRAM
>>
>> .rtdx_text: {} > IRAM
>>
>> .hst: {
>> HST_A_TABBEG = .;
>> _HST_A_TABBEG = .;
>> *(.hst)
>> HST_A_TABEND = .;
>> _HST_A_TABEND = .;
>> HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
>> _HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
>> } > IRAM
>>
>> .dsm: {} > IRAM
>>
>> /* RTA_fromHost buffer */
>> .hst1: align = 0x4 {} > IRAM
>>
>> /* RTA_toHost buffer */
>> .hst0: align = 0x4 {} > IRAM
>>
>> .hwi: {} > IRAM
>>
>> .log: {
>> LOG_A_TABBEG = .;
>> _LOG_A_TABBEG = .;
>> *(.log)
>> LOG_A_TABEND = .;
>> _LOG_A_TABEND = .;
>> LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
>> _LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
>> } > IRAM
>>
>> .printf (COPY): {} > IRAM
>>
>> /* LOG_system buffer */
>> .LOG_system$buf: align = 0x200 fill = 0xffffffff {} > IRAM
>>
>> /* logTrace buffer */
>> .logTrace$buf: align = 0x200 fill = 0xffffffff {} > IRAM
>>
>> .pip: {
>> PIP_A_TABBEG = .;
>> _PIP_A_TABBEG = .;
>> *(.pip)
>> PIP_A_TABEND = .;
>> _PIP_A_TABEND = .;
>> PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
>> _PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
>> } > IRAM
>>
>> /* pipRx buffer */
>> .pip0: align = 0x80 {} > IRAM
>>
>> /* pipRx0 buffer */
>> .pip1: align = 0x100 {} > IRAM
>>
>> /* pipTx0 buffer */
>> .pip2: {} > IRAM
>>
>> /* pipRx1 buffer */
>> .pip3: align = 0x100 {} > IRAM
>>
>> /* pipTx1 buffer */
>> .pip4: {} > IRAM
>>
>> /* pipTx buffer */
>> .pip5: align = 0x80 {} > IRAM
>>
>> .sts: {
>> STS_A_TABBEG = .;
>> _STS_A_TABBEG = .;
>> *(.sts)
>> STS_A_TABEND = .;
>> _STS_A_TABEND = .;
>> STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
>> _STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
>> } > IRAM
>>
>> .sys: {} > IRAM
>>
>> .udev: {} > IRAM
>>
>> .IRAM$heap: {
>> IRAM$B = .;
>> _IRAM_base = .;
>> IRAM$L = 0x5e20;
>> _IRAM_length = 0x5e20;
>> . += 0x5e20;
>> } > IRAM
>>
>> .SDRAM$heap: {
>> SDRAM$B = .;
>> _SDRAM_base = .;
>> SDRAM$L = 0x90000;
>> _SDRAM_length = 0x90000;
>> . += 0x90000;
>> } > SDRAM
>>
>> }
>> --- On Wed, 11/2/09, Michael Dunn
wrote:
>>
>> From: Michael Dunn
>> Subject: Re: [c6x] linking warning in fastrts67x.lib
>> To: n...@yahoo.co.in
>> Cc: c...
>> Date: Wednesday, 11 February, 2009, 4:24 AM
>>
>> Nishank,
>>
>> On Tue, Feb 10, 2009 at 1:33 PM, nishank pathak
>> wrote:
>>> HI,
>>> I get the following warning message on including fastrts67x.lib.
Can
>>> anyone
>>> help?
>>>
>>>>> warning: creating output section text without SECTIONS
> specification
>>
>>
>> You have a missing or incomplete linker command file {LCF]. These
>> files are named . cmd and should appear in your
project.
>>
>> mikedunn
>>>
>>> Thanks
>>> Nishank
>>>
>>> --
>> www.dsprelated. com/blogs- 1/nf/Mike_ Dunn.php
>> ________________________________
>>
Reply by Michael Dunn ●February 10, 20092009-02-10
Nishank,

On Tue, Feb 10, 2009 at 6:25 PM, nishank pathak
wrote:
> Mike,
> Yes, I have 2 sections 'text' and '.text' , How to resolve this?


Someone has probably done this explicitly in the code.
1. Check your map file - are there any .obj files in the 'text'
section. That could be a clue.
2. Check your code for pragma's that specify a section.
3. If you have any asm files [like for interrupt vectors], verify that
the section is correct.
4. You should have found it by now. If not, search every file for
'text' and check them out. If you decent tools, you should be able to
do a match on 'text' and pipe them to 'no match' on '.text'.

mikedunn
> Thanks
> Nishank
> --- On Wed, 11/2/09, Michael Dunn wrote:
>
> From: Michael Dunn
> Subject: Re: [c6x] linking warning in fastrts67x.lib
> To: n...@yahoo.co.in
> Cc: "C6x"
> Date: Wednesday, 11 February, 2009, 5:49 AM
>
> Nishank,
>
> On Tue, Feb 10, 2009 at 6:07 PM, nishank pathak
> wrote:
>>
>> Mike,
>> I am gettin gthe same warning even after putting the .text to SDRAM.
>
>
> Look at your map file carefully. Is there a section 'text' and a
> section '.text'??
>
> I'm not exactly sure if the above is your problem, but there should be
> some section in the map file that was added by the linker.
>
> You are proceeding down the correct path. When you have a compiler or
> linker warning, you should resolve it [or in some rare cases you may
> just understand why it is occurring if it is benign].
>
> mikedunn
>>
>> Thanks
>> Nishank
>>
>> --- On Wed, 11/2/09, Michael Dunn wrote:
>>
>> From: Michael Dunn
>> Subject: Re: [c6x] linking warning in fastrts67x.lib
>> To: n...@yahoo.co.in, "C6x"
>> Date: Wednesday, 11 February, 2009, 5:30 AM
>>
>> Nishank,
>>
>> On Tue, Feb 10, 2009 at 5:45 PM, nishank pathak
>> wrote:
>>>
>>> Also the link. cmd which I sent previosly includes appcfg.cmd which
> has a
>>> text section
>>>
>>> SECTIONS {
>>> .bss: {} > IRAM
>>>
>>> .far: {} > IRAM
>>>
>>> .sysdata: {} > IRAM
>>>
>>> .mem: {} > IRAM
>>>
>>> .sysinit: {} > IRAM
>>>
>>> .sysregs: {} > IRAM
>>>
>>> .gblinit: {} > IRAM
>>>
>>> .trcdata: {} > IRAM
>>>
>>> .args: fill=0 {
>>> *(.args)
>>> . += 0x4;
>>> } > IRAM
>>>
>>> .cinit: {} > IRAM
>>>
>>> .pinit: {} > IRAM
>>>
>>> .data: {} > IRAM
>>>
>>> .const: {} > IRAM
>>>
>>> .switch: {} > IRAM
>>>
>>> .cio: {} > IRAM
>>>
>>> .text: {} > IRAM
>>
>> ---
>> Look at your linker map file.
>> It looks like the '.text' was created in 'IRAM' only. You
>> probably ran
>> out of IRAM and the compiler automatically created a .text. section in
>> SDRAM for the code that did not fit.
>>
>> mikedunn
>>>
>>> frt: {} > IRAM
>>>
>>> .bios: {} > IRAM
>>>
>>> .stack: fill=0xc0ffee {
>>> GBL_stackbeg = .;
>>> *(.stack)
>>> GBL_stackend = GBL_stackbeg + 0x400 - 1;
>>> _HWI_STKBOTTOM = GBL_stackbeg + 0x400 - 4 & ~7;
>>> _HWI_STKTOP = GBL_stackbeg;
>>> } > IRAM
>>>
>>> .devtable: {} > IRAM
>>>
>>> .gio: {} > IRAM
>>>
>>> .rtdx_data: {} > IRAM
>>>
>>> .rtdx_text: {} > IRAM
>>>
>>> .hst: {
>>> HST_A_TABBEG = .;
>>> _HST_A_TABBEG = .;
>>> *(.hst)
>>> HST_A_TABEND = .;
>>> _HST_A_TABEND = .;
>>> HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
>>> _HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
>>> } > IRAM
>>>
>>> .dsm: {} > IRAM
>>>
>>> /* RTA_fromHost buffer */
>>> .hst1: align = 0x4 {} > IRAM
>>>
>>> /* RTA_toHost buffer */
>>> .hst0: align = 0x4 {} > IRAM
>>>
>>> .hwi: {} > IRAM
>>>
>>> .log: {
>>> LOG_A_TABBEG = .;
>>> _LOG_A_TABBEG = .;
>>> *(.log)
>>> LOG_A_TABEND = .;
>>> _LOG_A_TABEND = .;
>>> LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
>>> _LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
>>> } > IRAM
>>>
>>> .printf (COPY): {} > IRAM
>>>
>>> /* LOG_system buffer */
>>> .LOG_system$buf: align = 0x200 fill = 0xffffffff {} > IRAM
>>>
>>> /* logTrace buffer */
>>> .logTrace$buf: align = 0x200 fill = 0xffffffff {} > IRAM
>>>
>>> .pip: {
>>> PIP_A_TABBEG = .;
>>> _PIP_A_TABBEG = .;
>>> *(.pip)
>>> PIP_A_TABEND = .;
>>> _PIP_A_TABEND = .;
>>> PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
>>> _PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
>>> } > IRAM
>>>
>>> /* pipRx buffer */
>>> .pip0: align = 0x80 {} > IRAM
>>>
>>> /* pipRx0 buffer */
>>> .pip1: align = 0x100 {} > IRAM
>>>
>>> /* pipTx0 buffer */
>>> .pip2: {} > IRAM
>>>
>>> /* pipRx1 buffer */
>>> .pip3: align = 0x100 {} > IRAM
>>>
>>> /* pipTx1 buffer */
>>> .pip4: {} > IRAM
>>>
>>> /* pipTx buffer */
>>> .pip5: align = 0x80 {} > IRAM
>>>
>>> .sts: {
>>> STS_A_TABBEG = .;
>>> _STS_A_TABBEG = .;
>>> *(.sts)
>>> STS_A_TABEND = .;
>>> _STS_A_TABEND = .;
>>> STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
>>> _STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
>>> } > IRAM
>>>
>>> .sys: {} > IRAM
>>>
>>> .udev: {} > IRAM
>>>
>>> .IRAM$heap: {
>>> IRAM$B = .;
>>> _IRAM_base = .;
>>> IRAM$L = 0x5e20;
>>> _IRAM_length = 0x5e20;
>>> . += 0x5e20;
>>> } > IRAM
>>>
>>> .SDRAM$heap: {
>>> SDRAM$B = .;
>>> _SDRAM_base = .;
>>> SDRAM$L = 0x90000;
>>> _SDRAM_length = 0x90000;
>>> . += 0x90000;
>>> } > SDRAM
>>>
>>> }
>>> --- On Wed, 11/2/09, Michael Dunn
> wrote:
>>>
>>> From: Michael Dunn
>>> Subject: Re: [c6x] linking warning in fastrts67x.lib
>>> To: n...@yahoo.co.in
>>> Cc: c...
>>> Date: Wednesday, 11 February, 2009, 4:24 AM
>>>
>>> Nishank,
>>>
>>> On Tue, Feb 10, 2009 at 1:33 PM, nishank pathak
>>> wrote:
>>>> HI,
>>>> I get the following warning message on including fastrts67x.lib.
> Can
>>>> anyone
>>>> help?
>>>>
>>>>>> warning: creating output section text without SECTIONS
>> specification
>>>
>>>
>>> You have a missing or incomplete linker command file {LCF]. These
>>> files are named . cmd and should appear in your
> project.
>>>
>>> mikedunn
>>>>
>>>> Thanks
>>>> Nishank
>>>>
>>>>
>>>
>>> --
>>> www.dsprelated. com/blogs- 1/nf/Mike_ Dunn.php
>>>
>>>
>>> ________________________________
>>> Get perfect Email ID for your Resume. Get before others grab.
>>
>> --
>> www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
>>
>> ________________________________
>> Get rid of Add-Ons in your email ID. Get y...@rocketmail.com. Sign up
>> now!
>
> --
> www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
>
> ________________________________
> Get perfect Email ID for your Resume. Get before others grab.

--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php

_____________________________________
Reply by nishank pathak ●February 10, 20092009-02-10
Mike,
As I mentioned earlier, this warning comes only when I include fastrtsx.lib. Th emap file shows
 
text 0 00011020 00000180
          00011020 00000180 fastrts67x.lib : expsp.obj (text)
--- On Wed, 11/2/09, Michael Dunn wrote:

From: Michael Dunn
Subject: Re: [c6x] linking warning in fastrts67x.lib
To: n...@yahoo.co.in
Cc: "C6x"
Date: Wednesday, 11 February, 2009, 6:07 AM

Nishank,

On Tue, Feb 10, 2009 at 6:25 PM, nishank pathak
wrote:
> Mike,
> Yes, I have 2 sections 'text' and '.text' , How to resolve
this?


Someone has probably done this explicitly in the code.
1. Check your map file - are there any .obj files in the 'text'
section. That could be a clue.
2. Check your code for pragma's that specify a section.
3. If you have any asm files [like for interrupt vectors], verify that
the section is correct.
4. You should have found it by now. If not, search every file for
'text' and check them out. If you decent tools, you should be able to
do a match on 'text' and pipe them to 'no match' on
'.text'.

mikedunn
> Thanks
> Nishank
> --- On Wed, 11/2/09, Michael Dunn wrote:
>
> From: Michael Dunn
> Subject: Re: [c6x] linking warning in fastrts67x.lib
> To: n...@yahoo.co.in
> Cc: "C6x"
> Date: Wednesday, 11 February, 2009, 5:49 AM
>
> Nishank,
>
> On Tue, Feb 10, 2009 at 6:07 PM, nishank pathak
> wrote:
>>
>> Mike,
>> I am gettin gthe same warning even after putting the .text to SDRAM.
>
>
> Look at your map file carefully. Is there a section 'text' and a
> section '.text'??
>
> I'm not exactly sure if the above is your problem, but there should be
> some section in the map file that was added by the linker.
>
> You are proceeding down the correct path. When you have a compiler or
> linker warning, you should resolve it [or in some rare cases you may
> just understand why it is occurring if it is benign].
>
> mikedunn
>>
>> Thanks
>> Nishank
>>
>> --- On Wed, 11/2/09, Michael Dunn
wrote:
>>
>> From: Michael Dunn
>> Subject: Re: [c6x] linking warning in fastrts67x.lib
>> To: n...@yahoo.co.in, "C6x"

>> Date: Wednesday, 11 February, 2009, 5:30 AM
>>
>> Nishank,
>>
>> On Tue, Feb 10, 2009 at 5:45 PM, nishank pathak
>> wrote:
>>>
>>> Also the link. cmd which I sent previosly includes appcfg.cmd
which
> has a
>>> text section
>>>
>>> SECTIONS {
>>> .bss: {} > IRAM
>>>
>>> .far: {} > IRAM
>>>
>>> .sysdata: {} > IRAM
>>>
>>> .mem: {} > IRAM
>>>
>>> .sysinit: {} > IRAM
>>>
>>> .sysregs: {} > IRAM
>>>
>>> .gblinit: {} > IRAM
>>>
>>> .trcdata: {} > IRAM
>>>
>>> .args: fill=0 {
>>> *(.args)
>>> . += 0x4;
>>> } > IRAM
>>>
>>> .cinit: {} > IRAM
>>>
>>> .pinit: {} > IRAM
>>>
>>> .data: {} > IRAM
>>>
>>> .const: {} > IRAM
>>>
>>> .switch: {} > IRAM
>>>
>>> .cio: {} > IRAM
>>>
>>> .text: {} > IRAM
>>
>> ---
>> Look at your linker map file.
>> It looks like the '.text' was created in 'IRAM' only.
You
>> probably ran
>> out of IRAM and the compiler automatically created a .text. section in
>> SDRAM for the code that did not fit.
>>
>> mikedunn
>>>
>>> frt: {} > IRAM
>>>
>>> .bios: {} > IRAM
>>>
>>> .stack: fill=0xc0ffee {
>>> GBL_stackbeg = .;
>>> *(.stack)
>>> GBL_stackend = GBL_stackbeg + 0x400 - 1;
>>> _HWI_STKBOTTOM = GBL_stackbeg + 0x400 - 4 & ~7;
>>> _HWI_STKTOP = GBL_stackbeg;
>>> } > IRAM
>>>
>>> .devtable: {} > IRAM
>>>
>>> .gio: {} > IRAM
>>>
>>> .rtdx_data: {} > IRAM
>>>
>>> .rtdx_text: {} > IRAM
>>>
>>> .hst: {
>>> HST_A_TABBEG = .;
>>> _HST_A_TABBEG = .;
>>> *(.hst)
>>> HST_A_TABEND = .;
>>> _HST_A_TABEND = .;
>>> HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
>>> _HST_A_TABLEN = (. - _HST_A_TABBEG) / 20;
>>> } > IRAM
>>>
>>> .dsm: {} > IRAM
>>>
>>> /* RTA_fromHost buffer */
>>> .hst1: align = 0x4 {} > IRAM
>>>
>>> /* RTA_toHost buffer */
>>> .hst0: align = 0x4 {} > IRAM
>>>
>>> .hwi: {} > IRAM
>>>
>>> .log: {
>>> LOG_A_TABBEG = .;
>>> _LOG_A_TABBEG = .;
>>> *(.log)
>>> LOG_A_TABEND = .;
>>> _LOG_A_TABEND = .;
>>> LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
>>> _LOG_A_TABLEN = (. - _LOG_A_TABBEG) / 24;
>>> } > IRAM
>>>
>>> .printf (COPY): {} > IRAM
>>>
>>> /* LOG_system buffer */
>>> .LOG_system$buf: align = 0x200 fill = 0xffffffff {} >
IRAM
>>>
>>> /* logTrace buffer */
>>> .logTrace$buf: align = 0x200 fill = 0xffffffff {} >
IRAM
>>>
>>> .pip: {
>>> PIP_A_TABBEG = .;
>>> _PIP_A_TABBEG = .;
>>> *(.pip)
>>> PIP_A_TABEND = .;
>>> _PIP_A_TABEND = .;
>>> PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
>>> _PIP_A_TABLEN = (. - _PIP_A_TABBEG) / 100;
>>> } > IRAM
>>>
>>> /* pipRx buffer */
>>> .pip0: align = 0x80 {} > IRAM
>>>
>>> /* pipRx0 buffer */
>>> .pip1: align = 0x100 {} > IRAM
>>>
>>> /* pipTx0 buffer */
>>> .pip2: {} > IRAM
>>>
>>> /* pipRx1 buffer */
>>> .pip3: align = 0x100 {} > IRAM
>>>
>>> /* pipTx1 buffer */
>>> .pip4: {} > IRAM
>>>
>>> /* pipTx buffer */
>>> .pip5: align = 0x80 {} > IRAM
>>>
>>> .sts: {
>>> STS_A_TABBEG = .;
>>> _STS_A_TABBEG = .;
>>> *(.sts)
>>> STS_A_TABEND = .;
>>> _STS_A_TABEND = .;
>>> STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
>>> _STS_A_TABLEN = (. - _STS_A_TABBEG) / 16;
>>> } > IRAM
>>>
>>> .sys: {} > IRAM
>>>
>>> .udev: {} > IRAM
>>>
>>> .IRAM$heap: {
>>> IRAM$B = .;
>>> _IRAM_base = .;
>>> IRAM$L = 0x5e20;
>>> _IRAM_length = 0x5e20;
>>> . += 0x5e20;
>>> } > IRAM
>>>
>>> .SDRAM$heap: {
>>> SDRAM$B = .;
>>> _SDRAM_base = .;
>>> SDRAM$L = 0x90000;
>>> _SDRAM_length = 0x90000;
>>> . += 0x90000;
>>> } > SDRAM
>>>
>>> }
>>> --- On Wed, 11/2/09, Michael Dunn
> wrote:
>>>
>>> From: Michael Dunn
>>> Subject: Re: [c6x] linking warning in fastrts67x.lib
>>> To: n...@yahoo.co.in
>>> Cc: c...
>>> Date: Wednesday, 11 February, 2009, 4:24 AM
>>>
>>> Nishank,
>>>
>>> On Tue, Feb 10, 2009 at 1:33 PM, nishank pathak
>>> wrote:
>>>> HI,
>>>> I get the following warning message on including
fastrts67x.lib.
> Can
>>>> anyone
>>>> help?
>>>>
>>>>>> warning: creating output section text without SECTIONS
>> specification
>>>
>>>
>>> You have a missing or incomplete linker command file {LCF]. These
>>> files are named . cmd and should appear in your
> project.
>>>
>>> mikedunn
>>>>
>>>> Thanks
>>>> Nishank
>>>>
>>>>
>>>
>>> --
>>> www.dsprelated. com/blogs- 1/nf/Mike_ Dunn.php
>>>
>>>
>>> ________________________________
>>>