The problem can be fixed by patching the patch ;-) CVS: packaging/patches/msp430-gdb-6.8.patch
line 84 bug N (16, bfd_mach_msp43, "msp:44", FALSE, NULL) fix N (16, bfd_mach_msp44, "msp:44", FALSE, NULL) Matthias Hartmann schrieb: > Yes, it fixes the problem. > > I rebuild msp430-gdb with the fix below and it worked fine for an x449 > device. > > > Sergey A. Borshch schrieb: > >> Matthias Hartmann wrote: >> >> >>> A workaround could be, to run >>> - the compiler with -mmcu=msp430x449 >>> - the linker with -mmcu=msp430xG439 >>> >>> The 2 devices have same size of ram and flash. >>> >>> Does anybody know, if above workaround will bring any trouble? >>> >>> >> Thank you for reporting this bug. I think I found where it comes from. >> It's not a linker but gdb bug. There is mistyping in >> gdb-6.8/bfd/cpu-msp430.c: >> /* msp430x44x. */ >> N (16, bfd_mach_msp43, "msp:44", FALSE, & arch_info_struct[21]), >> must be >> /* msp430x44x. */ >> N (16, bfd_mach_msp44, "msp:44", FALSE, & arch_info_struct[21]), >> gdb simply can't find machine description for msp430x44x. >> >> Can you rebuild and test gdb with this fix? >> >> >> > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > > > >
