Hey Phil, sorry for the delay and thanks for your answer I'm on windows and building the toolchain on my own is out of questions at the moment, so I would like to make sure that the windows binary on you web site can be used as is (as far as patches or other build issues are concerned)
If yes, I will try to play with it as soon as I have a time slot thanks j > > Sorry Joe, > I've been up to my neck in alligators here (on other unrelated projects) > so all of my email has been suffering. I can tell you that it is > possible to use MSPGCC for extended memory development on the > F2418/F2618 devices - they're exactly what I'm using, for development on > both Windows and Linux platforms. > > A really good starting point for you is the compiler, build script, and > patches found here:- <http://www.innoventis.de/downloads/mspgcc/> - > these will get you a basic 430X environment going on GCC 3.x. I have had > to add some patches to the compiler and libraries to get things working > as well as I like. I've made a few posts on my observations in the last > few months - I've made one or two posts which you'll find in the list > archives. You'll want to use the -mdata-64k switch in compilation - this > forces constant data to be kept in the lower 64k of flash. > > There are lingering issues with function pointers - which I've worked > around with some asssembler macros - and you'll have to decide which > functions end up in FAR memory yourself, but overall it works pretty > well. I'd love to move up to the GCC 4.X compiler, but as far as I'm > aware it doesn't yet fully support the 430X processor, and alas I don't > have time to spend at present on assisting that development effort. > Cheers > phil > > _________________________________________________________________ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3
