The version with which I compiled earlier was mspgcc4.4.3 I switched to 4.4.4 and I'm trying to compile on this now. In saw that the register-memory mappings are a lot more detailed in the corresponding header files, so obviously work has undergone in this direction.
However, I cannot seem to compile as msp430-gcc-4.4.4 somehow invokes "as" (gnu assembler) and not mps430-as. Here is an output snippet: --------------------------------------------- msp430-gcc-4.4.4 -Wl,--section-start=.fartext=0x10000 -mmcu=msp430x5438 -I"C:\Mihai\kit\compilers\mspgcc\v4.4.4\msp430\include" -IC:\Mihai\kit\compilers\mspgcc\v4.4.4\lib\gcc\msp430\4.4.4\include -O0 -g3 -Wall -Dmsp430x5438 -MMD -MP -MF"Util/ramUtils.d" -MT"Util/ramUtils.d" -o"Util/ramUtils.o" "../Util/ramUtils.c" as: unrecognized option `-mmcu=msp430x5438' --------------------------------------------- What am I doing wrong? - I tried removing the -mmcu flag and I got the following : Output: --------------------------------------------- Building file: ../Util/ramUtils.c Invoking: Cygwin C Compiler msp430-gcc-4.4.4 -Wl,--section-start=.fartext=0x10000 -I"C:\Mihai\kit\compilers\mspgcc\v4.4.4\msp430\include" -IC:\Mihai\kit\compilers\mspgcc\v4.4.4\lib\gcc\msp430\4.4.4\include -O0 -g3 -Wall -Dmsp430x5438 -MMD -MP -MF"Util/ramUtils.d" -MT"Util/ramUtils.d" -o"Util/ramUtils.o" "../Util/ramUtils.c" /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s: Assembler messages: /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:2: Error: no such architecture: `msp430x169' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:14: Error: junk at end of line, first unrecognized character is `,' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:16: Error: junk at end of line, first unrecognized character is `,' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:18: Error: junk at end of line, first unrecognized character is `,' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:20: Error: junk at end of line, first unrecognized character is `,' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:373: Error: unknown pseudo-op: `.4byte' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:374: Error: unknown pseudo-op: `.2byte' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:375: Error: unknown pseudo-op: `.4byte' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:378: Error: unknown pseudo-op: `.4byte' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:380: Error: unknown pseudo-op: `.4byte' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:381: Error: unknown pseudo-op: `.4byte' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:382: Error: unknown pseudo-op: `.2byte' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:383: Error: unknown pseudo-op: `.2byte' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:384: Error: unknown pseudo-op: `.4byte' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:385: Error: unknown pseudo-op: `.4byte' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:411: Warning: unknown section attribute 'M' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:411: Warning: unknown section attribute 'S' /cygdrive/c/DOCUME~1/CONCEP~1/LOCALS~1/Temp/cc2fVqy8.s:411: Error: junk at end of line, first unrecognized character is `,' make: *** [Util/ramUtils.o] Error 1 -------------------------------- I tried compiling with -c / or -S and then calling the linker, but it says it does not recognise the output format. Anyhow, I suspect msp430-as is not called as it should be... Any thoughts on this? Regards, Mihai --- On Tue, 9/21/10, Mihai Galos <[email protected]> wrote: > From: Mihai Galos <[email protected]> > Subject: Re: [Mspgcc-users] calling functions above 64KB of address space > To: [email protected] > Date: Tuesday, September 21, 2010, 11:36 AM > Thierry, > > Thank you for the scoop! > > I'm gonna switch over to the aforementioned X branch in the > CVS. I kinda find it amazing that the two branches weren't > mereged. There should be something like a compiler/linker > flag to select between normal and extended addressing. > > I know I'm asking a lot there, and from the looks of > things, Peter is a one-man army, tweaking and patching the > mspgcc alone. > > As for your question, I am using mspgcc4. > > I know building your toolchain can be a real pain, I've > built mspdebug on a Win box and it took some tricks to > build; wasn't easy at all :( > > Mihai > > > > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment > and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users >
