Build Xinu

This page may require cleanup to meet academic/public standards. A page requiring cleanup may have been hastily added or difficult to understand by outsiders. More information can be found on the talk page.

---

This article or section needs to be updated. Parts of this article or section have been identified as no longer being up to date. Please update the article to reflect recent changes, and remove this template when finished.

---

We anticipate making our new MIPS port of XINU freely available on this site during the summer. (Licensing will be BSD-style, copyright Marquette University and Purdue Research Foundation.) The preliminary versions currently used in courses at Marquette are available upon request for interested faculty at reputable Universities and colleges. E-mail Dr. Brylow if interested.

A revision of Doug Comer's venerable Operating System Design - The XINU Approach textbook is in progress.

Cross-Compiler

In order to compile Embedded MIPS kernels on a workstation that is not itself a MIPS processor, it is necessary to build and install an appropriate cross compiler. There are many ways to accomplish this; for reference, we list the specific versions and steps we used for our installation.

As always, one should be wary of installing unfamilar software as the root user of the system. All of the steps below have been carried out as a lesser-privileged user with write access to the necessary directories.

First, we downloaded, compiled, and installed the appropriate binary utilities. We downloaded binutils version 2.17, untarred the source code, and and ran the following commands:

  ./configure  --prefix=/usr/local/project/mipsel-dev --target=mipsel
  make
  make install

We have chosen the path "/usr/local/project/mipsel-dev" to host our cross-compiler installation. Whatever path it used here must be reflected in the XINU build configuration file, "compile/makeVars" when you arrive at that step.

We are not building a true, full-blown UNIX cross-compiler here, and do not need a proper installation of the platform-specific C libraries; XINU has its own small libraries that compile with the kernel. However, the GCC compilation will want to see appropriate library headers, so we cheat here by linking the platform-specific include directory to the host machine's include directory.

  mkdir -p /usr/local/project/mipsel-dev/mipsel/usr
  ln -s /usr/include /usr/local/project/mipsel-dev/mipsel/usr/include

Second, we downloaded, patched, compiled and installed the GNU C Compiler. We downloaded GCC version 3.4.6. We applied a short patch to correct some kind of obscure fixproto error. We added the newly compiled binutils into the shell path (/usr/local/project/mipsel-dev/bin) for the gcc compilation to find them. This is also known to work with GCC version 4.1.2 unpatched, using this script to get around installing a bunch of platform-specific UNIX libraries.

  ./configure  --prefix=/usr/local/project/mipsel-dev --target=mipsel --with-sysroot=/usr/local/project/mipsel-dev/mipsel/ --enable-languages=c
  make
  make install

If all has gone well, you should now have a gcc cross-compiler from your host's native architecture to little-endian MIPS:

  /usr/local/project/mipsel-dev/bin/mipsel-gcc

---

One of the biggest hurdles for compiling on one computer and sending the binary to a second computer is the architecture type. For our purposes we are developing on a powerpc architecture and sending the compiled binary to a mips processor. This is done through the use of a crosscompiler, our powerpc to mips crosscompiler is located in:

/usr/local/project/EmbeddedOS/crosscompiler

All compiling programs are prefixed with mipsel-linux-uclibc- to differentiate the crosscompiler from the local system's compiling programs. A simple recommendation is to add the crosscompiler directory to your path. This can be done by typing:

export PATH=$PATH:/usr/local/project/EmbeddedOS/crosscompiler

Alternativly, this can be added to your .profile or .bashrc (or whatever script loads when you use a terminal...).

All the standard GNU Compiler Collection programs should exists (most importantly gcc and objdump are there).

Building the XINU image

Once you have downloaded and extracted the xinu tarball, you will see a basic directory structure:

AUTHORS   include/  LICENSE   README  system/  tty/
compile/  lib/      loader/   shell/  test/    uart/

AUTHORS is a brief history of contributors to the XINU operating system in it's varying iterations.

compile/ contains the Makefile and other necesities for building the XINU system once you have a cross-compiler.

include/ contains all the header files used by XINU.

lib/ contains a folder (libxc/) with a Makefile and source for the library, as well as a binary blob which contains the pre-compiled library.

LICENSE is the license under which this project falls.

loader/ contains assembly files and is where the bootloader will begin execution of O/S code.

README is this document.

shell/ contains the source for all shell related functions.

system/ contains the source for all system functions such as the nulluser process (initialize.c) as well as code to set up a C environment (startup.S).

test/ contains a number of testcases (which can be run using the shell command testsuite).

tty/ contains the source for the tty driver.

uart/ contains the source for the uart driver.

---

By this point it is assumed you have built a cross-compiler (from your host computer's architecture to MIPS), have obtained a supported router and have made the necessary modifications to use the serial port. If you have not it is suggested you visit http://mulug.mscs.mu.edu/xinu/ to understand what you need and why.

Once you have obtained all the required components building the XINU system is a straightforward process. Change into the compile directory and (if needed) update the makeVars file to point to your cross-compiler. Once you have done that you can simply execute make which should leave you with a xinu.boot file in the compile directory.

After creating the xinu.boot image you can hook the router's serial port up to your computer and connect using a serial communications program of your choice (the xinu-console tools available from http://www.mscs.mu.edu/~brylow/xinu/ contain a program called tty-connect which is a basic serial communication program). The settings needed are 8 data bits, no parity bit, and 1 stop bit (8N1) with a speed of 115,200 bps.

Upon connection you can power on the router and immediatly start sending breaks (Control-C) to the device, if your luck holds you will be greated with a CFE prompt. If you are using a DHCP server you can execute ifconfig eth0 -auto to obtain an IP, otherwise your computer can have a static IP in the 192.168.1.[2-255] range. On the host computer initiate a tftp put on the xinu.boot image and on the router type the command boot -elf [host ip]:xinu.boot. If all has gone correctly the router should now be running a XINU image and you will be greeted with a basic shell (xsh$ ).

Within the shell you have some basic commands: exit, gpiostat, help, kill, memstat, led, ps, reset, sleep, uartstat. Each can be described using [command] --help.

For more information check out the Embedded XINU wiki [1].