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.

TMS320C6727 DSP linker error

Other Parts Discussed in Thread: TMS320C6727

hi,

I am building  project with TMS320c6727 DSP and i wrote the following linker command in the linker command file:

MEMORY
{
ROM_VECS : origin = 0x00000000 length = 0x00001000
ROM : origin = 0x00001000 length = 0x000BF000
VEC : origin = 0x10000000 length = 0x00001C00
RAM : origin = 0x10001C00 length = 0x00020E74
SLOWRAM : origin = 0x10022A74 length = 0x0001D58C
SDRAM : origin = 0x80000000 length = 0x08000000
ASYNC2 : origin = 0x90000000 length = 0x00008000
}

SECTIONS
{
.TIBoot: load = RAM
.urt : load = RAM
{
Init.obj (.text)
}
.text: load = RAM
{ *(.text)
}
.stack load = RAM fill = 0xdeadbeef
.cinit load = RAM
.cio load = RAM
.const load = RAM
.data load = RAM
.switch load = RAM
.far load = RAM
.bss load = RAM
.sysmem load = RAM
.pinit load = RAM
.Hannsect load = SLOWRAM
INTERNAL_MEMORY load = RAM
EXTERNAL_MEMORY load = SDRAM
}

It gives me the error as :

error: system error, can't open file 'Init.obj' for input: No
such file or directory

Init. obj is a user C source file written by the user.

What  could be the source of the error?

As per the linker documents, I am allowed to link input sections explicitly to form an output section which i named it "usr".

  • Just as a test, /* comment out */ these lines ...

    anushree mahapatra said:
    .urt : load = RAM
    {
    Init.obj (.text)
    }

    and change the linker invocation so that Init.obj appears an input file.   Does it work then?

    Thanks and regards,

    -George

  • I didnt understand the line when you said " change the linker invocation so that it appears an input file "?

    because I believe the Init.obj is itself considered as an input file with the current syntax.

    anushree

  • Hi,

    Thank you for your help. Actually CCS 3.3 has a different way of invoking the linker using the .cmd file. If you include the .obj files as input in the "Build Option" dialog box, still it does not accept the .obj file as input file.

    I finally included the path to the .obj file in the linker command file itself by doing the following,

    -z "C:\Lyrtech\PADK\dsp\examples\analog loopback ori\AnalogLoopback1\Debug\Init.obj"

    and it now recognised init.obj file and no linker error.

    Thanks.

    Anushree