ARM/BIOS v 0.9

This is a project with the idea of a public GPL POST code,
for ARM systems, in order to improve their "embeddability".

So this is *very alpha*, it's supossed to work only on 
StrongArm 110 with FootBridge (21285) systems, like those
in Chalice CATS motherboard, Intel EBSA285 or Rebel Netwinder.
We have run this on EBSA285 and CATS.
I would like people to add more architectures, mainly for SA1100
and Xscale. It would be natural some guys at Intel to help here.

This project is not aimed to run any special operating system,
it should be able to run whatever. If you are interested in Linux,
take a look at README.Linux

I did this for supporting a commercial project, but I think it
would be useful to peopleout there. bootldr and ebsa285bios helped
me a lot as a reference. A lot of people from kernel-arm-linux
maillist also helped. I wanted to payback all them with another
contribution to open community.
This project is NOT for an enduser. If you don't have a minimum
of knowledge about ARM systems, don't use it, at least
at this stage. Remember is ALPHA software, expect some problems.

You can compile it as follows:

    export MK_BASE=/the/path/you/have/this
    make clean
    make

You should have it done. Resulting images are:

* For burning a new ROM:

   fw16.rom:    BOOTSTRAP (1st step) image.
   fw16sh.rom:  COMPLETE 1st+2nd+3rd image for a shell.

* For loading them by XMODEM or other uploading method:

   sh.rom:	2nd+3rd image for a shell (same as fw16sh.rom)
   os.rom:      2nd+3rd image for a emOS test.


This is a first release in order to get more ideas on doing this,
I have not released any driver for "emOS", so your only choices
are burn a image or download by XMODEM (maybe you need to change
the format of the binary, on systems like AIF).

BINARY FORMAT
-------------
I tried a simple format for downloading everything. tool/MKrom
is the tool that builds all these images. (1st step) has a 
minimum knowledge of this format, so it can recognize a
signature of this in rom, or properly load it by XMODEM.
(2nd step) has an in-depth knowledge of the format, because
it need to analyze the multipart image searching binaries and
devices in which load them. Take a look in "Documentation".
If somebody have ideas on improving this format (adding AIF
compatibility or whatever) it is welcomed.

I hope all this code be useful to you.

David Aparicio      (daparic@terra.es)
