Hi DJ,
Thank you for your prompt reply, I understand, it is just always
frustrating for Windows users to deal with this, i will try your
configuration and do some research.
On a different note, i was wondering if anybody on the list have the same
problem as me, using the TI pre-compiled binaries for the MSP430 (the RH
port, downloaded from TI web site), the msp430-elf-gdb.exe , works Ok with
430 and 430X but using only small memory model for a 430X. If you switch to
large memory and have code above 64K, it will build ok the .elf file or
.hex file (all addresses are OK), but msp430-elf-gdb.exe does not load code
or debug any address above the 64K. In fact address like 0x10000 wraps
around to 0x0000. If you step into a function that supposed to be in high
memory, the GDB simply report as invalid address, and try to step into
0x0000 instead of 0x10000. Anybody experienced this behavior?
Cheers.
On Thu, Mar 6, 2014 at 9:53 PM, DJ Delorie <d...@redhat.com> wrote:
>
> > Great news and thank you for the update, is it possible to throw
> > somewhere the Windows binaries? I think it is time for fresh windows
> > binaries, the last one was back in December.
>
> Sorry, I don't work for TI, so I can't make them do a release or say
> anything about their schedule or intentions. All I do is maintain the
> port in the FSF source tree.
>
> Also, please keep in mind that this is a patch that's still a
> work-in-progress, subject to change, etc. Certainly not a supported
> or official thing yet.
>
> > or some nice documentation on how I can build the msp-elf RH tools
> > myself.
>
> Note: msp430-elf, not msp-elf
>
> The answer here is "the same way you build any other cross toolchain."
> There's nothing magic about he msp430-elf tools, assuming you know how
> to build a cross toolchain at all. If not, you're probably going to
> be frustrated, but in case you want to try anyway...
>
> Basically (and substituate your real paths as desired):
>
> P="--prefix=/usr/local"
> T="--target=msp430-elf"
>
> export PATH=/usr/local/bin:$PATH
>
> cd $binutilsworkdir
> $somewhere/binutils-sources/configure $P $T
> make
> make install
>
> cd $gccworkdir
> $somewhere/gcc-sources/configure $P $T --with-newlib
> --enable-languages=c,c++
> make all-host
> make install-host
>
> cd $newlibworkdir
> $somewhere/newlib-sources/configure $P $T
> make
> make install
>
> cd $gccworkdir
> make all-target
> make install-target
>
--
Nader Shehayed
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
