hi chris,

no, i'm sorry, i don't. we ran into too many problems trying to support cygwin years ago, and someone came up with the idea to use a vmware image that envelopes the entire native development environment in one bundle that everyone (well, mac users must pay, of course) can use and maintain for free.

i wish i had better news,

steve

On 06/21/2012 08:58 AM, Chris B wrote:
thanks for the update, Steve.
Any advice for cygwin users? know of any cygwin rpm locations?

regards

Chris

 > Date: Tue, 19 Jun 2012 15:03:25 -0400
 > From: [email protected]
 > To: [email protected]
 > Subject: [Shimmer-users] toolchain upgrade
 >
 > all,
 >
 > i just checked in a set of small updates/upgrades, some of which will be
 > critical to support the first major mspgcc toolchain upgrade in tinyos
 > in years. as of early this month, tinyos has decided to upgrade from
 > version 3.2.3 (circa late 2003) to 4.6.3.
 >
 > anyway, a few of my commits are bugfixes, only revealed during compiler
 > testing. a few others are just cleanup; and one is just a really minor
 > new feature (Time adds mktime).
 >
 > the short story is that anyone who updates their tinyos-main repository
 > will find their ability to compile applications broken.
 >
 > i must apologize to anyone caught by this, as i wasn't paying attention
 > to the fact that another member of tinyos core was busily preparing the
 > codebase for the new compiler, which uses slightly different
 > designations for the msp430 variations; when the old compiler sees the
 > new designation, it chokes. (this designation lives in
 > tos/<shimmer_variant>/.platform).
 >
 > anyway, the next time you update your tinyos-main:
 >
 > cd ~/tinyos-main
 > svn update
 >
 > you will see new code scattered over the tree (depends upon how *long*
 > you've been neglecting this), but current shimmer-specific changes are:
 >
 > tos/platforms/shimmer/Time*.nc
 > /shimmerAnalogSetupP.nc
 > /chips/msp430/Msp430I2C*.nc
 > /chips/msp430/FastClockP.nc
 > /chips/sd/SDP.nc
 > support/make/shimmer*.target
 > /span.target
 >
 > what you need to do:
 >
 > if you upgrade the tree, you need to
 >
 > 1) install a new msp430-gcc toolchain, version 4.6.3, along with
 > upgrading nesc to v1.3.3. the virtual package msp430-46 will manage all
 > of them, or you can install everything but gdb if you're short on space.
 >
 > packages for ubuntu, both 32- and 64-bit platforms, are hosted at
 >
 > http://tinyprod.net/repos/debian
 >
 > follow the instructions in README_46. ignore the now-outdated warnings
 > that the release is experimental; it has logged a great many hours of
 > testing since that was written.
 >
 > if you need to upgrade, installing nesc is similar to the other packages:
 >
 > sudo apt-get install nesc
 >
 > *or*
 >
 > 2) make a temporary hack that will allow you to use the old compiler
 > until you upgrade. in your platform's .platform file, file the msp430
 > mmcu flag, and replace msp430f1611 with the old-style msp430x1611.
 >
 > i strongly recommend that you not delay upgrading for too long. the new
 > compiler is a real upgrade.
 >
 > if anyone runs into trouble, please post here, and you will receive help.
 >
 > -steve
 >
 >
 > _______________________________________________
 > Shimmer-users mailing list
 > [email protected]
 > https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users

_______________________________________________
Shimmer-users mailing list
[email protected]
https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users

Reply via email to