Compiler/TMS320F28377S: Linker command file: group library sections

Consider these lines, which appear outside the GROUP ...

DSPGER said:

MyLibrary

{

-l..\path\to\my\library.lib(.text)

}

This says to create an output section named MyLibrary.  It's input sections are the .text sections from mylibrary.lib.  No allocation is specified, so linker allocates it by default.  While this is legal syntax, it is never wise to do it this way.

When you write MyLibrary inside the GROUP ... This says to create an output section name MyLibrary.  Multiple output sections of the same name are allowed, but generally a bad idea.  It is made up of all the input sections also named MyLibrary.  I'm sure there aren't any, so this output section is empty.  

To fix it, remove the MyLibrary section outside the GROUP.  Inside the group, right after the MyLibrary line, write this ...

DSPGER said:

{

-l..\path\to\my\library.lib(.text)

}

DSPGER said:

2) I've read I can define -l..\path\to\my\library.lib at the top of the file and then just use the name library.lib. Where / how do I need to define it?

That's a matter of preference.  The linker needs to know 3 things.

1. The name of the library
2. The directory where the library is located
3. What output section gets the input sections from the library

There are multiple ways to supply this information.  The Primer article shows one.  You show another.  Another one is shown in the section titled Specifying Library or Archive Members as Input to Output Sections in the C28x assembly tools manual.  Use whatever method you think will make the linker command file easier to use.

Thanks and regards,

-George

Hello George,

like this?

GROUP : >> RAMLS0 | RAMLS1 | RAMLS2 | RAMLS3 | RAMLS4, PAGE = 0
{
	.text
	MyLibrary
	{
		-l..\path\to\my\library.lib(.text)
	}
	.cinit
	.econst
}

I've tried this before and the linker places MyLibrary before .text:

TEXT Section .text (Little Endian), 0x460 words at 0x00008835
TEXT Section MyLibrary.1 (Little Endian), 0x800 words at 0x00008000
TEXT Section MyLibrary.2 (Little Endian), 0x35 words at 0x00008800
DATA Section .cinit (Little Endian), 0x18 words at 0x00008c95

Not the answer I wanted to have, but good to know. Thanks.

George Mock said:

Note this means that functions or data will start to span across the 0x800 address boundaries.  I presume there is no reason to be concerned about that.  But maybe there is?

Not sure.