[Tinyos-1.2wg] Re: Tools for 1.2

[Cory Sharp]

My comments:

--- make ---
I've had corroborated reports that having two versions of make on the
same system (say, one in /usr/bin and one /usr/local/bin) breaks the
build system.  It's unclear why, but it appears to be an issue with
make, specifically, and not the build scripts.  At a minimum, *not*
overwriting the system make should be *thoroughly* tested before
release.  (I suspect it won't work.)

--- build-mspgcc ---
Weekly snapshot of gcc-binutils is for a reason. MSP430 F1611 support
(Telos Rev B) doesn't exist on the most recent release.  We could try
to freeze which particular patchset we're using, but I haven't been
motivated enough, yet, to do this.

CVS HEAD checkout of mspgcc libc is for no particular reason, we could
pick some tag in time and freeze.

The other items in build-mspgcc are frozen against strict version
numbers (iirc).

--- mspgcc-pybsl ---
It should work on Linux just fine, though the instructions don't
indicate how ... because it's so damn easy :).  Windows must build an
exe/binary because serial port access isn't supported in the Cygwin
python.  Linux python serial port access is A-OK, so the bsl.py script
runs directly.  We've found it sufficient to just symlink bsl.py to
/opt/msp430/bin/msp430-bsl.

--- Linux kernel ---
We may want to recommend Linux users use 2.4.x series kernel because
USB support in 2.6.x is f'ed up -- we get intermittent strange
behavior on USB otherwise.  The other options is to work with the
Linux kernel developers and stabilize USB support (hahaha).

... those are all the comments I have off the top of my head.  I might
have more later.

- Cory

On Fri, 18 Feb 2005 16:45:43 -0800, David Gay <dgay42 at gmail.com> wrote:
> This got garbled. That should read: "We're going to have a common
> toolchain...". And I bet tinyos-1.2wg won't accept your answers, so
> please reply to me and Kristin...
> 
> David
> 
> 
> On Fri, 18 Feb 2005 16:44:09 -0800, David Gay <dgay42 at gmail.com> wrote:
> > We're g a common toolchain for 1.2 and 2.0, do either of you have
> > additional feedback on what versions of what tools we need to build?
> >
> > David
> >
> >
> > ---------- Forwarded message ----------
> > From: David Gay <dgay42 at gmail.com>
> > Date: Fri, 18 Feb 2005 16:41:29 -0800
> > Subject: Tools for 1.2
> > To: "tinyos-1.2" <tinyos-1.2wg at mail.millennium.berkeley.edu>
> >
> > General
> > -------
> >
> > nesC: 1.2 (don't build yet)
> > Java: do we want to switch to Java 1.5? Note that the IBM JVM is still at 1.4.
> >
> > make: we need Phil's patched 3.80 make (it should install to
> > /usr/local/bin to avoid clashing with the system standard one).
> >
> > graphviz: I suggest sticking with 1.10 (is there any reason to change?)
> >
> > We should make our rpms install to /usr, rather than /usr/local (note
> > that build-mspgcc uses /opt/msp430 at the moment).
> >
> > gcc, gdb, binutils are at ftp://ftp.gnu.org/pub/gnu/
> >
> > AVR
> > ---
> > avr-gcc 3.4.3
> > avr-binutils: 2.15
> > avr-insight (gdb) 6.3
> > avarice 2.3.20041206 (that's "latest CVS")
> > avr-libc 1.2.3 (http://savannah.nongnu.org/download/avr-libc/)
> > uisp: what's in tools/src/uisp (will be part of tinyos-tools-avr)
> >
> > MSP
> > ---
> > whatever the build-mspgcc scripts does (but, afaik, it actually does
> > some amount of "fetch the latest version", so we should note what we
> > actually fetched).
> >
> > msp430-bsl (what's in tools/src/mspgcc-pybsl - this will need work I
> > believe - it doesn't work out-of-the-box on Linux at least)
> >
> > ARM
> > ---
> >
> > Not necessary for 1.2, but we can at least start working on the
> > story... Phil B., any suggestions?
> >
> > David
> >
> 
>