Hello,
It seems that support for the '2272 was planned, but not actually
implemented (maybe?). When trying to compile for my MMCU, and
deliberately issuing an invalid -mmcu, I get the list of Known MCU
names...
msp430-gcc -mmcu=blah -g -Os -o testing.elf main.c
cc1.exe: MCU blah not supported
Known MCU names:
msp1
msp2
msp430x110
[snip]
msp430x2252
msp430x2272
msp430x2234
The 2272 is listed here. But, when I try to build for the 2272...
msp430-gcc -mmcu=msp430x2272 -g -Os -o testing.elf main.c
Known MCU names:
msp1
msp2
msp430x110
[snip]
msp430x2234
msp430x2254
msp430x2274
C:\DOCUME~1\jkonopka.S5W\LOCALS~1\Temp/ccSe6Wwz.s: Assembler messages:
C:\DOCUME~1\jkonopka.S5W\LOCALS~1\Temp/ccSe6Wwz.s:2: Fatal error:
unknown MCU: msp430x2272
The 2272 is now missing from the list, and the 2272 is reported as an
unknown MCU.
Here is my setup info:
WinXP
Mspgcc installed from mspgcc-20080619.exe
If I try the above command with -mmcu=msp430x2274 (note the '4' on the
end instead of '2') the compile works. But, gdb-proxy fails to connect
to the target, again because the 2272 is unknown.
I've also tried grabbing the source from the CVS repos, but am unable to
connect - timeout.
Thank you,
Josh
