Hi Gunther,
I've been attempting to use your patch and adding some more to it and
I have a problem with binutils.
Building ld is producing a problem I cant find the cause of affecting
241x and 26x devices, compilation will fail at link for any of these
devices with the following:
msp430-gcc -mmcu=msp430x2619 -o leds.elf main.o
msp430-ld: target not found
Is this the same problem you had Steve?
If it is can you let me know what the patch you used was as I cant see
it anywhere.
If thats the case, then the rest of this email is redundant so please ignore it.
Otherwise if this is a problem still:
I've found it is caused by some missing string entries in intermediate
build files in "build/binutils-2.17/ld/", the files are
"emsp430x241x.c" and "emsp430x261x.c" for x=6,7,8,9 there are two
empty strings that should not be, see "emsp430x2410.c" for an example
of a good file, the key differences are at the end of this email.
I'm guessing the cause is something to do with msp:241 and msp:26
being lost somewhere but I cant see anything in the binutils patch
that is different for the 24x devices so I cant find why they are
coming through the build ok.
Thanks,
Mat
exerpt of diff output of example 24x and 26x files:
--- build/binutils-2.17/ld/emsp430x2410.c 2008-03-06
15:24:42.000000000 +0000
+++ build/binutils-2.17/ld/emsp430x2616.c 2008-03-06
15:24:45.000000000 +0000
@@ -38,34 +38,34 @@
static void
-gldmsp430x2410_before_parse (void)
+gldmsp430x2616_before_parse (void)
{
#ifndef TARGET_ /* I.e., if not generic. */
- ldfile_set_output_arch ("msp:24", bfd_arch_unknown);
+ ldfile_set_output_arch ("", bfd_arch_unknown);
#endif /* not TARGET_ */
}
@@ -74,9 +74,9 @@
set_output_arch_default,
ldemul_default_target,
before_allocation_default,
- gldmsp430x2410_get_script,
- "msp430x2410",
- "elf32-msp430",
+ gldmsp430x2616_get_script,
+ "msp430x2616",
+ "",
finish_default,
NULL,
NULL,
