Hi! This time _I_ have a problem :)
I want to write code for the new G series. The mspgcc we use for development and production is the latest 3.2.3 windows build. Since all our firmware is tested with this compile, a switch is not intended for near future. I have to stick on the old build. Now I want to do small projects with the G series. I know htat these have not been supported on the old mspgcc because they are too new. However, using the msp430x2012 setting, which comes close to the G2231, disabled MPY and a hand-tailored header file, i was able to compile some test code and the generated assembly looks good. However, the linker refuses to link with an error "cannot represent machine 'MSP:200' " (Yes, "MSP:200" Where does this come from?) Even if the linker files are not the right ones for the G2231 (I'll have to modify them), the linker should link for a x2012 and not give an error. Any ideas? Also, does someone know how to tell the linker to use a specific linker script (so I don't have to mess with the original files)? Thanks, JMGross ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
