Advanced Operating Systems
Milestone 0: Familiarisation
This is a simple exercise designed to get you started on L4. It contains very detailed instructions, together with the existing source code and the L4 manual you should have no problem doing it.
Most of the 9242 binaries (eg. cross compilers) are in ~disy/crossdev/$ARCH. You can add this to your path with:
~ % arm5xdev=gcc-3.4.5-glibc-2.3.5/armv5b-softfloat-linux ~ % export PATH=$PATH:/home/disy/crossdev/$ARCH/$arm5xdev/bin ~ % export PATH=$PATH:/home/disy/bin
If you are lazy you can just use the 9242 command for the cs9242 shell:
~ % 9242 newclass starting new subshell for class COMP9242... ~ % armv5b-softfloat-linux-ld armv5b-softfloat-linux-ld: no input files
Your minicom should default to 115200, 8N1, no hardware flow control. If it doesn't then you will have problems talking to your slug.
Getting it Going
Booting your NSLU2 for the first time is easy:
We have developed a few tools to speed the development cycle along. The makefile can copy the sos operating system, known as a bootimage to your tftp directory and reset the slug. Below is a typical development cycle, assuming the path changes to your login script:
The example skeleton operating system includes an application
The example includes a
The second part of milestone zero is to find a partner for the rest of the project. The project is to be completed, in pairs, unless prior permission has been obtained from the LiC.
You will need to demonstrate user applications printing to the 2nd console via libserial, running on the slug hardware to the tutor during the demonstration period. You should be prepared to show your tutor which files you modified in your solution, and explain any design decisions you made. Your tutor will be particularly interested in the details of your IPC interface with different size blocks of data etc.
You will let the tutor know who your partner is so that group accounts can be created for you.
Last modified: 27 Jul 2006.