Documentation : Hardware | Software | Tutorials    Wardrobe : Jackets | Applications
Papers : Notes | Proposals | Research    Administration : Stock | Minutes | Progress

Setting up a bitsy on your own network

In order to set up a bitsy environment, perform the following steps:
Set up your wireless network
If you are setting up your own wireless network, call it Bristol.11 and set the password to some secret that we will tell you. If you use an existing wireless network, then you will have to do the following two steps, in order to customise the Bitsy to use that network:
Connect a serial cable
You need to connect a serial cable to the bitsy so that you can login to it, in order to change the wireless network settings. Connect pin 2 of your PC to pin 2 of the 9-wire bus, and pin 3 to pin 3, and pin 5 to pin 5. Do not connect any other wires. Set your terminal emulator (windows/linux/...) up with 38400 baud, 8 bits, no handshake (or use XON/XOFF if you want).
Set up your bitsy to match your wireless network
Restart the bitsy, type root and then create a file with the details of your network. Say that your network is called 'Monkey' and that the password is 'nutss', then do the following:
      mkdir /flash/wireless
      cat > /flash/wireless/net0 << EOF
      iwconfig $DEVICE essid Monkey
      iwconfig $DEVICE key s:nutss
Now reboot your bitsy, and it will first try to connect to Bristol.11 and then to Monkey -- the right light on the 802.11 card should stay on, once it has successfully connected to your network.

You can make as many files in /flash/wireless as you like, they will be tried in alphabetical order.

You can instead choose to ask us in Bristol to customise a Bitsy for your network.
Set up a DHCP server
You need a DHCP server that will give the bitsy an IP address. The DHCP server may be running already on your network (check with your sysadmin), and they may need to know the MAC address of your bitsy. It is printed on the bottom of the box. If you are arranging your own DHCP server, just add the following lines to /etc/dhcpd.conf:
ddns-update-style ad-hoc;

subnet netmask {
  option subnet-mask ;
  option broadcast-address ;
  option routers ;
  option domain-name "" ;
  option domain-name-servers, XXX.XXX.XXX.XXX ;
  range ;
  default-lease-time 300 ;
  max-lease-time 600 ;
  host {
    hardware ethernet 00:60:1D:1F:7B:AD ; fixed-address ;
  host {
    hardware ethernet 00:60:1D:20:6C:EC ; fixed-address ;
Where you replace the ethernet addresses on the last two lines with real MAC addresses, and you replace XXX with some good back-up DNS server on your local network. This assumes that a DNS server is running on; see below. Also replace with whatever you fancy as your domain name.

Set up a DNS server
The bitsy needs a DNS server, in order for it to find out who it is, and in order to find out the names of other machines. The IP address of the DNS server is passed on by DHCP, just make sure that that DNS server knows about the bitsy and the domain it resides in. If you want, you can create a separate domain, for example to keep the names of all your bitsies in. No one needs to know, except the bitsies and the DNS server that you are setting up!

Set up an NFS server
The bitsy will attempt to mount two file-systems from a machine called 'nfs'. ('nfs' on the domain where the bitsy resides that is). The first is a file system called /home/wearable/Exported, which is to be mounted on /home, and the second is /home/mXXX/Exported, which is to be mounted on /rd. The XXX is replaced with the last three digits of the wearables IP address. In order to export those, add two lines:
To a file /etc/exports on the machine with the name 'nfs'. If you have decided to have a dedicated gateway between the bitsy network and the rest of the world, then it makes sense to give that machine an alias 'nfs'.
Download a development toolkit
Download the toolkit for ARM cross compilation under linux from (19 Mbytes).
    bunzip2 /tmp/arm.tar.bz2
    cd /
    tar xvf /tmp/arm.tar
Note that the toolkit must be installed in /usr/local/arm (all absolute pathnames are compiled in). If you want to put it somewhere else, run lartify.c, entirely at your own risk.

Credits: this toolkit was compiled by the delft LART team, you can download it from their web server, but then it does in /data/...)

This page last updated June 30, 2003
The material displayed is provided 'as is'. Contents may not be reused without prior permission.
For problems or questions regarding this web contact Cliff Randell.