EmStar Download Page

by The EmStar Team
2005-10-05

Site and Mailing List Search:

EmStar Releases

Tar file	CVS Tag	Release date
EmStar 2.5	EMSTAR_RELEASE_2_5	October 5, 2005
EmStar 2.1	EMSTAR_RELEASE_2_1	February 14, 2005
EmStar 2.0	EMSTAR_RELEASE_2_0	September 9, 2004
EmStar 2.0 beta1 (UNSTABLE)	EMSTAR_RELEASE_2_0_beta1	April 18, 2004
EmStar 1.3.2	EMSTAR_RELEASE_1_3_2	February 20, 2004
EmStar 1.3.1	EMSTAR_RELEASE_1_3_1	February 12, 2004
EmStar 1.3	EMSTAR_RELEASE_1_3	February 11, 2004
EmStar 1.2	EMSTAR_RELEASE_1_2	February 4, 2004
EmStar 1.1	EMSTAR_RELEASE_1_1	January 29, 2004
EmStar 1.0	EMSTAR_RELEASE_1_0	November 18, 2003

Installation Instructions for Release 2.5

Release notes

CVS Access

Current development happens in our CVS Repository. Code in CVS is not guaranteed to work. Those who don't want to live on the bleeding edge should use the releases above.

The CVS module name is emstar. For anonymous checkout, use the following snippet:

$ cvs -d :pserver:anoncvs@cvs.cens.ucla.edu:/home/cvs/cvsroot login
(When prompted for a password, type anoncvs)
$ cvs -z9 -d :pserver:anoncvs@cvs.cens.ucla.edu:/home/cvs/cvsroot co emstar

We have online source browsing tools:

ViewCVS
LXR

CVS Snapshots

If you can't access CVS, you can download a CVS snapshot as a tar file. These snapshots are automatically generated every day. Get them here:

CVS Snapshot Directory

Platform Toolchains

You can download toolchain tarballs for several supported EmStar platforms. Note that these toolchains are not needed to compile and run on Linux x86 hardware, e.g. for simulation or emulation; they are only needed to compile and run on non-x86 platforms, such as the Intel/Crossbow Stargate or the iPAQ.

To use a platform package, download the tarball and unpack it in /usr/local/lecs. Unfortunately, the toolchain can not be relocated easily; this is a limitation of GCC and related utilities.

After the appropriate compiler has been installed in /usr/local/lecs, you should be able to build for that platform using make, e.g.

make ARCH=stargate

To run emstar code on the platform, you will also need to copy over any shared libraries that are used by the EmStar system. If you are building the EmStar libraries as shared objects, you should copy over the obj.<platform>/lib directory with the other EmStar code, and set LD_LIBRARY_PATH to include that library on the platform. You will also typically need to install the glib-2.0.so files on the platform in the usual place. These libraries are packaged with the toolchain, and often are available as installable packages e.g. ipkg as well.

Note:

If you are using a different kernel from the one that comes with the toolchain, you will need to further modify make.platform make sure that the correct kernel includes are used.

If your root file system is based on a different version of glibc than the toolchain, you cannot use that toolchain; you will need to get an updated one that uses a matching version of glibc (e.g. whatever tools were used to build the binaries in the root file system).

Stargate Release 7

This platform package supports the Intel/Crossbow Stargate platform, running the Release 7 kernel and root filesystem available from Intel. It uses gcc version 3.2 and libc 2.2.5. Use ARCH=stargate to build with these tools. Download Stargate platform (July 18 2004)

Stargate UCLA Release 5

This platform package supports the Intel/Crossbow Stargate platform, running the 2.4.19-rmk7-pxa1-stargate5-devfs kernel, and the standard Stargate root file system. It uses gcc version 3.2 and libc 2.2.5. Use ARCH=stargate-ucla to build with these tools. Download Stargate platform (Mar 18 2004)

iPAQ

This platform package supports the Compaq iPAQ H3100 series platform, running the 2.4.7-rmk3-np1-devfs kernel, and the Familiar 0.5 release root file system. It uses gcc version 2.95.4 and libc 2.2.5. Download iPAQ Familiar 0.5 platform

EmTOS

These platform packages support EmTOS (compilation of TinyOS/NesC applications to run on EmStar platforms) and the AVR-based Mote platforms. Installing them is the most straightforward way to build Transceiver (the Mote side of "MoteNIC") and other Mote-based components of EmStar.

EmTOS requires NesC to be installed on your system. If you already have NesC installed, you can modify Make.conf to compile EmTOS targets; otherwise you can download this package: Download NesC 1.1 Compiler.

EmTOS also requires that a version of TinyOS be reachable from your EmStar tree. If you already have TinyOS installed, then add a symlink to it to emstar/tinyos-1.x, and then add the symlinks described in the Install Page. Note, that the TinyOS interfaces have changed over time and not all past versions work with the current version of EmTOS. The CVS version of EmStar works with TinyOS-1.1.13. The 2.1 Release works with TinyOS-1.1.11.

If you don't already have a TinyOS tree checked out, you can download a pre-configured version (currently version 1.1.13) from this server and untar it directly into your EmStar tree: Download Pre-configured TinyOS. Note, as of EmStar release 2.1, this tarball will automatically be downloaded during the build process if a tinyos-1.x directory is not already present.

The EmStar build can build Mote targets for Transceiver and other EmStar-related Mote software. This requires that the appropriate AVR compiler tools be installed on your system. If you already have an AVR compiler installed, you can modify Make.conf; otherwise you can download this package: Download AVR 3.3 Compiler.

Supporting New Platforms

Information on supporting new platforms can be found on the porting page.

Presentation Materials

Tutorials

A great EmStar tutorial by Vinayak Naik, covering everything from download to writing code: http://www.cse.ohio-state.edu/~naik/talks/naik_emstar.ppt[An Introduction to EmStar: A Practitioners Perspective] Mirrored 4/29/05