Martin's ARMs

I have a bunch of ARM systems from the Debian ARM EABI port and for my work with

They're on 24/7 so you are welcome to use them. They are:

n2100 - 600Mhz - 512MB

A 600 MHz XScale-80219 (v5l) w/ 512MB RAM + swap, 2 x 100MBps ethernet, 160GB disk. Debian armel sid with arm-etch, arm-sid and arm-lenny in chroots with a common /home.

arma - 200Mhz - 64MB

An atmark-techno Armadillo-9. based on the Cirrus Logic EP9315 chip: a 200MHz ARM920T (armv4t) integer processor with Maverick Crunch math coprocessor and 64MB RAM, 800x600 video output with mouse, keyboard, Debian root filesystem and swap all on a USB hub.

Running the Atmark 2.4.27 kernel and busybox userland, bootstrapped into a Debian "etch" system ARM on a 1GB USB pendrive. The old system is accessible via telnet or on the serial console from guest using

    $ minicom arma

Its /home is that of cluster.

Runs a web server, a forum and acts as an X terminal onto other hosts, is used for Debian old-ABI testing and as an access point from the net to other hosts on the local subnet.

You don't need to ask to use this; it is free to use over ssh as with user guest and password friend. In several years of free access this account doesn't ever seem to have been abused.

ts7250 - 200MHz - 64MB

A four-inch-square TS-7250 single-board computer close up On the intranet at another 200MHz EP9302 with 64MB RAM with SD card storage (for swap) and no screen 100 Mbps ethernet and the serial console is accessible from guest:
	$ minicom ts7250
It runs Debian armel sid on a root filesystem served over NFS from cluster's /tftpboot/armel-sid There are notes on building this and its custom linux kernel.

Used for ARM EABI development, testing EABI software on armv4t hardware and for testing MaverickCrunch FPU floating point code generation and speed.

/home is that of cluster.

h1940 - 266MHz - 64MB

h1940 loading
h1940 loaded
h1940 saying 'Configuring usb0:'
266MHz 64MB arm920t, local flash, usb net to guest OS: Angstrom minimal system booted using HaReT from WinCE. Debian armel rootfs over NFS a possibility.


On USB host guest:

    # ifconfig usb1
    # iptables -t nat -A POSTROUTING -s -j SNAT --to-source

On other local hosts:

    # route add netmask gateway

On itself, put

in /etc/resolv.conf.

boxer - 400MHz - 64MB

A very small laptop (palmtop) next to some computer mice A 400MHz XScale with 64MB RAM running Angstrom GPE graphical environment. Wireless (also USB) ethernet, touch screen.


None. It just picks up the open wifi.

neo - 266 MHz - 128MB

The NEO1973 linuxphone with 2x3 inch touch screen FIC neo1973 Linux phone

266MHz arm920t, 128MB RAM + swap, 500MB SD card, GPS/GSM modem, USB network to guest.
OS: OpenMoko 2007.2, optionally hosting a chroot of Debian armel sid over NFS.


On guest, configure USB net and provide internet for the device:

    # ifconfig usb0 netmask
    # iptables -t nat -A POSTROUTING -s -j SNAT --to-source
    # echo 1 > /proc/sys/net/ipv4/ip_forward

On other hosts and specially on the public/localnet gateway:

    # route add -net netmask gateway

On the ADSL router/name server etc, add the same route.

Angstrom config on the device: put

in /etc/resolv.conf

QEMU - ~200Mhz each - 247MB

On 2 x 2GHz AMD Athlon, three simulated ARM systems, each with 247MB RAM + swap: arm-etch, arm-sid and armel-sid, all sharing /home with the host
Martin Guy <>