I had a similar error when compiled toolchain myself. To fix compilation you have to install binutils-2.17 *WITH* patch in tools/binutils from SF.net cvs.
gschatz wrote: > > I've some problems using msp430-gcc to compile a program for msp430xG4618 > MCU. Does anyone try to compile something for msp430xG4618 MCU on Linux > using the last update of the toolchain available on > http://sourceforge.net/projects/mspgcc/ > > When I try to compile a C file using the following command, I get an error > message from "as" which is the assembler . (no msp430-xG4618 MCU > mentioned) > msp430-gcc -mmcu=msp430xG4618 -c main.c > Known MCU names: > msp1 > msp2 > msp430x110 > msp430x112 > msp430x122 > msp430x122 > msp430x1222 > msp430x1122 > msp430x1132 > msp430x123 > msp430x1232 > msp430x133 > msp430x135 > msp430x147 > msp430x148 > msp430x149 > msp430x412 > msp430x413 > msp430x311 > msp430x312 > msp430x313 > msp430x314 > msp430x315 > msp430x323 > msp430x325 > msp430x336 > msp430x337 > msp430x1101 > msp430x1111 > msp430x1121 > msp430x1331 > msp430x1351 > msp430x435 > msp430x436 > msp430x437 > msp430x447 > msp430x448 > msp430x449 > msp430x167 > msp430x168 > msp430x169 > msp430x155 > msp430x156 > msp430x157 > > /tmp/cc1U8AJo.s: Assembler messages: > /tmp/cc1U8AJo.s:2: Fatal error: unknown MCU: msp430xG4618 > > But, if I make a mistake in the mcu option, I get the following message! > (Here, msp430xG4618 is mentioned) > msp430-gcc -mmcu=MyMistake -c main.c > cc1: MCU MyMistake not supported > Known MCU names: > msp1 > msp2 > msp430x110 > msp430x112 > msp430x1101 > msp430x1111 > msp430x1121 > msp430x1122 > msp430x1132 > msp430x122 > msp430x123 > msp430x1222 > msp430x1232 > msp430x133 > msp430x135 > msp430x1331 > msp430x1351 > msp430x147 > msp430x148 > msp430x149 > msp430x1471 > msp430x1481 > msp430x1491 > msp430x155 > msp430x156 > msp430x157 > msp430x167 > msp430x168 > msp430x169 > msp430x1610 > msp430x1611 > msp430x1612 > msp430x2001 > msp430x2011 > msp430x2002 > msp430x2012 > msp430x2003 > msp430x2013 > msp430x2101 > msp430x2111 > msp430x2121 > msp430x2131 > msp430x2232 > msp430x2252 > msp430x2272 > msp430x2234 > msp430x2254 > msp430x2274 > msp430x311 > msp430x312 > msp430x313 > msp430x314 > msp430x315 > msp430x323 > msp430x325 > msp430x336 > msp430x337 > msp430x412 > msp430x413 > msp430x415 > msp430x417 > msp430x423 > msp430x425 > msp430x427 > msp430x4250 > msp430x4260 > msp430x4270 > msp430xE423 > msp430xE425 > msp430xE427 > msp430xW423 > msp430xW425 > msp430xW427 > msp430xG437 > msp430xG438 > msp430xG439 > msp430x435 > msp430x436 > msp430x437 > msp430x447 > msp430x448 > msp430x449 > msp430xG4616 > msp430xG4617 > msp430xG4618 > msp430xG4619 > (null):0: confused by earlier errors, bailing out > > In fact, it seems that gcc (cc1) works well, but "as" seems to be not up > to date. Have you any idea about this problem. > > Thank you, > Guillaume > -- View this message in context: http://www.nabble.com/msp430-gcc-on-linux---compilation-problem-for-msp430xG4618-tf3525125.html#a10231490 Sent from the MSP430 gcc - Users mailing list archive at Nabble.com.
