ozymandias 7 Posted February 3, 2012 Share Posted February 3, 2012 once upon a time i managed to bumble my way into getting programs to correctly compile for the G2231s that i have lying around using the flag -mmcu=msp430x2012 . my first question is, does anybody know why this works, as it seems it shouldn't and second, what would be the proper flag for the FRaunchpad? mspdebug seems to talk to it fine, but i'm not sure how to compile for it just yet. PS. does anybody have the code to the demo program that comes aboard the FRaunchpad? it would be a great reference. Quote Link to post Share on other sites
Fe2o3Fish 33 Posted February 3, 2012 Share Posted February 3, 2012 once upon a time i managed to bumble my way into getting programs to correctly compile for the G2231s that i have lying around using the flag -mmcu=msp430x2012 . my first question is, does anybody know why this works, as it seems it shouldn't and second, what would be the proper flag for the FRaunchpad? mspdebug seems to talk to it fine, but i'm not sure how to compile for it just yet. msp430-gcc -mmcu=msp430fr5739 works for me just fine. This, naturally, will depend on whether or not you have one of the newer versions of msp430-gcc. PS. does anybody have the code to the demo program that comes aboard the FRaunchpad? it would be a great reference. It's available from the Fraunchpad webpage, http://www.ti.com/tool/msp-exp430fr5739 -Rusty- ozymandias 1 Quote Link to post Share on other sites
pabigot 355 Posted February 3, 2012 Share Posted February 3, 2012 once upon a time i managed to bumble my way into getting programs to correctly compile for the G2231s that i have lying around using the flag -mmcu=msp430x2012 . my first question is, does anybody know why this works, as it seems it shouldn't It would work if the size and offsets of the flash and RAM segments, and the addresses of all the peripherals you use, are the same between the MSP430G2231 and the MSP430F2012. For any chip, you should simply use the lower-cased version of the MCU name. E.g., -mmcu=msp430g2231 While I decided to keep support for the legacy genericized MCU identifiers along with the preferred ones in LTS20110716 and its patches, those aliases were removed in the current development series, starting around 20111205. ozymandias 1 Quote Link to post Share on other sites
ozymandias 7 Posted February 5, 2012 Author Share Posted February 5, 2012 Cool cool. Thanks guys. It looks like I have an old version of 430gcc, but it works at the moment for my 2231's, so I'll just wait until a newer version pops up on the YUM repos. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.