Hi Steve,
There was no packaging! I just compiled the one piece of the Linux tool
chain people could not compile for themselves, and put that binary on
the web site. It might be the instructions that go with it are less than
clear :-) Everything else was left to be grabbed from CVS. A few weeks
ago I did an RPM package for binutils. Its my intention to do the same
for the rest of the Linux toolchain, but I've been somewhat snowed under
with higher priorities.
When I have some time I aim to complete a full set of RPMs. I probably
should do a version of binutils and gcc built with MinGW, as an interim
step to keep the Win98 people happy. As I have said before, a full MinGW
installer isn't really an option right now, as GDB won't build with
MinGW. Another thing to be done is to move the MSP430 GDB code to the
latest GDB. Its seems the MinGW folk are actively trying to get that
working with MinGW, so that might keep everyone happy at some point.
What passes for a MinGW GDB right now, is still very troublesome.
Has anyone done anything about moving the GDB code to the latest GDB? I
think someone else said they might have a go at this.
[C-Spy seems to be like the Cygwin builds of mspgcc (and a lot of other
apps for that matter). It seems to work OK on some Win98 machines, and
not on others.]
Regards,
Steve
Steve Hosgood wrote:
I've never heard Steve Underwood's comments, but I think this is just a silly
packaging oversight. It should get shipped with rproxy, but until it does,
Andreas is right - you have to build it from CVS.
See my prototype HOWTO on
http://tallyho.bc.nu/~steve/msp430howto-2.html
...mostly section 2.2 "Shopping List".
silly things like this can really put off company suits from choosing open-
source. Luckily I'm not a company suit, and don't have to answer to any. I've
been using rproxy/GDB for months solid now, and in that time the JTAG
interface has not once "lost" the processor.
( C-spy used to lose it about three or four times a day. )
