MSPGCC memory mapping problem

I hate messing around with those funky gcc bracketfests. A more "portable" (if I may misuse the word that way) method of achieving the same thing is:

typedef struct INFO_MEM_STRUCT { unsigned char raw_data[64]; // and/or put in a union here } INFO_MEM_STRUCT, *PINFO_MEM_STRUCT;

PINFO_MEM_STRUCT infoA =3D (PINFOMEM) 0x200, infoB =3D (PINFOMEM) 0x240; // or whatever your addresses are

Since those messages almost certainly come from the linker, not the compiler, I believe you're mistaken.

That's not what the message is telling you. It states that the two sections overlap, i.e. you tried to locate two sections in the same space. Don't do that, and things will have a chance to work.

Thanks Hans,

I figured this one out.

The messages do come from the linker, but it's becuase the compiler was also doing some linking. I used the -c flag (compile/assemble only) for msp430-gcc and was able to prevent problem.

You misunderstand how the GCC toolchain works. The command you call, gcc, is _not_ the compiler. It's a frontend program for the entire toolchain, including the linker. The actual compiler (named "cc1"), the assembler and all other tools needed, are called by gcc as necessary.