>From looking at what I get out of the compiler, I believe the status of mspgccx is:
1. pointers are only 16 bits regardless of what they point to (data, text or far text). This is a problem if you want to define void (*proc)(); because if proc is in a far text segment you will not jump to the right place. As far as I can tell specifying -mdata-64k has little effect on the code except that it pushes/pops 20 bit pointers onto the stack (which just slows things down). 2. Text can be in the far segment but you have to make sure you put all interrupt routines into non-far segments (this is a processor restriction but could be overcome by the compiler with an extra branch). 3. It seems that strings and initialized variables are put into the lower 64k of text segments, so given #1 above you are OK as long as you can fit all of your interrupt routines, routines branched to indirectly, data and strings/data consts into low 64k. 3. To get header files for 5xxx parts you must specify -DNEWVERSION 4. I have updated my uif430 code to program 5XXX parts in linux. 5. There are certainly bugs but I haven't yet got any meaningful code to compile and link completely. Seems that printf and/or varargs has some issues based on other posts. Robert Phil Sutherland wrote: > > Gentle folk, > I'm currently using mspgcc (and latterly mspgcc4) quite successfully for > development of a project based on an MSP430F2618. However, I'm now > getting close to the 64k address space limit on code, and will shortly > need to switch to using a compiler capable of handling the 430X CPU so I > can use the other 64K of flash in my device. So, what's the current > state of play with 430X compilation, particularly on the mspgcc4 branch? > Many thanks > phil > > > > Checked for Virus & Spam by West Australian Networks Internet Service > Providers see www.westnet.net.au > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > > -- View this message in context: http://old.nabble.com/MSP430X-and-mspgcc---current-status--tp26764096p27380835.html Sent from the MSP430 gcc - Users mailing list archive at Nabble.com.
