L1100 linker errors with CodeWarrior HC12 toolchain

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

L1100 linker errors with CodeWarrior HC12 toolchain

Jump to solution
2,113 Views
svenny29
Contributor I
Hi all!

I'm using the CodeWarrior HC12 toolchain V5.0.28 Build 5073. My project is based on standard software modules from different companies, so I can't change the source code. One software module is using a microcontroller register definition file for the MC9S12XDP512 (called Reg_xdp512.h). This file doesn't suit my needs (too few or missing bit and mask definitions etc.) and I want to use "mc9s12xdp512.h" from _CODEWARRIOR_DIR_\lib\hc12c\include.

As soon, as I include this file in my sources, I get the following warnings:

WARNING L1100: Segments .absSeg0 (0x0) and .absSeg652 (0x0) overlap
WARNING L1100: Segments .absSeg652 (0x0) and .absSeg1168 (0x0) overlap
WARNING L1100: Segments .absSeg1168 (0x0) and .absSeg1820 (0x0) overlap
WARNING L1100: Segments .absSeg1820 (0x0) and .absSeg653 (0x1) overlap
WARNING L1100: Segments .absSeg1 (0x2) and .absSeg654 (0x2) overlap
WARNING L1100: Segments .absSeg654 (0x2) and .absSeg1169 (0x2) overlap
WARNING L1100: Segments .absSeg1169 (0x2) and .absSeg1821 (0x2) overlap
WARNING L1100: Segments .absSeg1821 (0x2) and .absSeg655 (0x3) overlap
WARNING L1100: Segments .absSeg2 (0x4) and .absSeg656 (0x4) overlap
WARNING L1100: Segments .absSeg656 (0x4) and .absSeg1170 (0x4) overlap
WARNING L1100: Segments .absSeg1170 (0x4) and .absSeg1822 (0x4) overlap
WARNING L1100: Segments .absSeg1822 (0x4) and .absSeg657 (0x5) overlap
WARNING L1100: Segments .absSeg3 (0x6) and .absSeg658 (0x6) overlap
WARNING L1100: Segments .absSeg658 (0x6) and .absSeg1171 (0x6) overlap
WARNING L1100: Segments .absSeg1171 (0x6) and .absSeg1823 (0x6) overlap
WARNING L1100: Segments .absSeg1823 (0x6) and .absSeg659 (0x7) overlap
WARNING L1100: Segments .absSeg4 (0x8) and .absSeg660 (0x8) overlap
WARNING L1100: Segments .absSeg660 (0x8) and .absSeg1172 (0x8) overlap
WARNING L1100: Segments .absSeg1172 (0x8) and .absSeg1824 (0x8) overlap
WARNING L1100: Segments .absSeg5 (0x9) and .absSeg661 (0x9) overlap
WARNING L1100: Segments .absSeg661 (0x9) and .absSeg1173 (0x9) overlap
WARNING L1100: Segments .absSeg1173 (0x9) and .absSeg1825 (0x9) overlap
WARNING L1100: Segments .absSeg6 (0xA) and .absSeg662 (0xA) overlap
WARNING L1100: Segments .absSeg662 (0xA) and .absSeg1174 (0xA) overlap
WARNING L1100: Segments .absSeg1174 (0xA) and .absSeg1826 (0xA) overlap
WARNING L1100: Segments .absSeg7 (0xB) and .absSeg663 (0xB) overlap
WARNING L1100: Segments .absSeg663 (0xB) and .absSeg1175 (0xB) overlap
WARNING L1100: Segments .absSeg1175 (0xB) and .absSeg1827 (0xB) overlap
WARNING L1100: Segments .absSeg8 (0xC) and .absSeg664 (0xC) overlap
WARNING L1100: Segments .absSeg664 (0xC) and .absSeg1176 (0xC) overlap
WARNING L1100: Segments .absSeg1176 (0xC) and .absSeg1828 (0xC) overlap
WARNING L1100: Segments .absSeg9 (0xD) and .absSeg665 (0xD) overlap
WARNING L1100: Segments .absSeg665 (0xD) and .absSeg1177 (0xD) overlap
WARNING L1100: Segments .absSeg1177 (0xD) and .absSeg1829 (0xD) overlap
WARNING L1100: Segments .absSeg10 (0x10) and .absSeg668 (0x10) overlap
WARNING L1100: Segments .absSeg668 (0x10) and .absSeg1178 (0x10) overlap
WARNING L1100: Segments .absSeg1178 (0x10) and .absSeg1830 (0x10) overlap
WARNING L1100: Segments .absSeg11 (0x12) and .absSeg669 (0x12) overlap
WARNING L1100: Segments .absSeg669 (0x12) and .absSeg1179 (0x12) overlap
WARNING L1100: Segments .absSeg1179 (0x12) and .absSeg1831 (0x12) overlap
WARNING L1100: Segments .absSeg12 (0x13) and .absSeg670 (0x13) overlap
WARNING L1100: Segments .absSeg670 (0x13) and .absSeg1180 (0x13) overlap
WARNING L1100: Segments .absSeg1180 (0x13) and .absSeg1832 (0x13) overlap
WARNING L1100: Segments .absSeg13 (0x16) and .absSeg672 (0x16) overlap
WARNING L1100: Segments .absSeg672 (0x16) and .absSeg1181 (0x16) overlap
WARNING L1100: Segments .absSeg1181 (0x16) and .absSeg1833 (0x16) overlap
WARNING L1100: Segments .absSeg14 (0x17) and .absSeg673 (0x17) overlap
WARNING L1100: Segments .absSeg673 (0x17) and .absSeg1182 (0x17) overlap
WARNING L1100: Segments .absSeg1182 (0x17) and .absSeg1834 (0x17) overlap
WARNING L1100: Segments .absSeg15 (0x1A) and .absSeg675 (0x1A) overlap
INFORMATION L2: Message overflow, skipping WARNING messages



Before I added the linker option "-WmsgSw1100" these warnings were errors! As I don't like to see/get these warnings/errors everytime
I compile my project, I would like to fix it, but I don't know how:
I can't change the software module which is including the other definition file and I want to use "my own" favorite register definition file.

Is there any way to get rid of these warnings (without turning this warning off)?

Thanks for your help!
Labels (1)
Tags (1)
0 Kudos
1 Solution
488 Views
J2MEJediMaster
Specialist I
I've seen this slew of errors when I use the CodeWarrior project wizard to build the HC12 version of OSEK. OSEK provides its own HC12 header information. Those files, along with the standard boiler-plate headers the CodeWarrior project provides, create redundant definitions. What you are seeing is the linker complaining of these redundant definitions.

You're either going to have to live with the other software's header files, or carefully edit the CodeWarrior header file to include only the information that the other header files lack.

---Tom

View solution in original post

0 Kudos
1 Reply
489 Views
J2MEJediMaster
Specialist I
I've seen this slew of errors when I use the CodeWarrior project wizard to build the HC12 version of OSEK. OSEK provides its own HC12 header information. Those files, along with the standard boiler-plate headers the CodeWarrior project provides, create redundant definitions. What you are seeing is the linker complaining of these redundant definitions.

You're either going to have to live with the other software's header files, or carefully edit the CodeWarrior header file to include only the information that the other header files lack.

---Tom
0 Kudos