			SkyEye README  0.8.8
			  2005-03-01
please read README.SKYEYE-INSIGHT

1. configure the skyeye in cygwin or linux environment
cd SKYEYE_DIR

/*if SkyEye version is <= 0.6.0, then*/
./configure --target=arm-elf --prefix=/usr/local --without-gtk-prefix --without-gtk-exec-prefix --disable-gtktest

/*else (SkyEye version is > 0.6.0)*/
./configure --target=arm-elf --prefix=/usr/local

/* if you use gcc-3.4 and want to optimze the skyeye*/
CC=gcc-3.4 CFLAGS=-O2 ./configure --target=arm-elf --prefix=/usr/local

/* if you use gcc-3.3 and want to optimze the skyeye*/
CC=gcc-3.3 CFLAGS=-O2 ./configure --target=arm-elf --prefix=/usr/local

/* if you use gcc-2.95 and want to optimze the skyeye*/
CC=gcc-2.95 CFLAGS=-O2 ./configure --target=arm-elf --prefix=/usr/local



2 make and install

2.1 in linux environment
cd SKYEYE_DIR
make
make install

NOTICE:
 a. If your linux environment is Mandrake Linux, then you could meet errors when you compile skyeye.
    If the errors are related about readline, ncurse, termcap, etc.
    try command:
        ln -s /usr/include/ncurses/termcap.h /usr/local/include/termcap.h
    then you make again, you will make successfully!
 b. If your linux environment is Debian Linux, don't use gcc 2.95 or gcc 3.0, try gcc 3.2+.
 c. The gcc version should >=2.96
 d. If SkyEye version is > 0.6.0, then GTK softwares(LCD simulation needs this) should be installed in Linux system.

2.2 in cygwin environment
read buildskyeyeoncygwin.txt
NOTICE:
    now, only SkyEye-v0.1.1 can run on cygwin


3 run

NOTICE: 
 memmap.conf and skyeye.conf are all skyeye hardware configure files.
 memmap.conf is for skyeye-v0.2-, skyeye.conf is for skyeye-v.0.2.5+
 There should be a memmap.conf/skyeye.conf in skyeye current working directory. You can change and copy example memmap.conf/skyeye.conf  in skyeye related packages to working directory.
 
3.1 in linux environment
 a. the user id should be root
 b. should setup&install linux kernel driver tuo.o 
    (in RedHat, the file is  /lib/modules/2.4.x/kernel/drivers/net/tun.o)
    (if tun.o isn't in your system, just compile linux kernel to get a tun.o module)
 c.1 run tun driver module(almost in any linux distributions):
       #insmod /lib/modules/2.4.x/kernel/drivers/net/tun.o
    if you don't make device node, you should do commands
       #mkdir /dev/net
       #mknod /dev/net/tun c 10 200
 c.2 run vnet (virtual hub) driver module (not very compatible with other linux distributions, except redhat9):
       get vnet source
       build vnet.o 
       make device file
           #mknod /dev/net/vnet c 10 201
           #chmod 666 /dev/net/vnet 
       #insmod vnet.o
 d. Please read skyeye.conf.txt at first to know the meaning of skyeye.conf. 
    Edit skyeye.conf file to set tun/tap or vnet device for skyeye.
    If you run two more skyeyes at the same time, 
    please use different skyeye.conf for each skyeye instance, and only one skyeye run 
    first and related skyeye.conf content has hostip value:
       ......
       net: ... ethmod=vnet, hostip=ddd.ddd.ddd.ddd
    other skyeye.conf should has content(hostip[0] should be 0):
       ......
       net: ... ethmod=vnet, hostip=0.ddd.ddd.ddd     
    For example:
      #set nic info state=on/off  mac=xx:xx:xx:xx:xx:xx  ethmod=tuntap/vnet hostip=dd.dd.dd.dd
      #net: state=on, mac=0:4:3:2:1:f, ethmod=tuntap, hostip=10.0.0.1
      net: state=on, mac=0:4:3:2:1:f, ethmod=vnet, hostip=10.0.0.1
 e. run skyeye
 /*if you use ELF format kernel(uclinux, linux,...)*/
  #/usr/local/bin/skyeye ELF_format_kernel_name
  (SkyEye)target sim
  (SkyEye)load
  (SkyEye)run

 /*if you use binary image format kernel(uclinux, linux,...)*/
  #/usr/local/bin/skyeye
  (SkyEye)target sim
  (SkyEye)run
  
3.2 in cygwin environment
  have no time to support now


skyeye.conf file examples:

FOR AT91 (0)  special for ucosii
-------------------------------------------
cpu: arm7tdmi
mach: at91
mem_bank: map=M, type=RW, addr=0x00000000, size=0x00004000
mem_bank: map=M, type=RW, addr=0x01000000, size=0x00400000
mem_bank: map=M, type=R,  addr=0x01400000, size=0x00400000
mem_bank: map=M, type=RW, addr=0x02000000, size=0x00400000
mem_bank: map=M, type=RW, addr=0x02400000, size=0x00008000
mem_bank: map=M, type=RW, addr=0x04000000, size=0x00400000
mem_bank: map=I, type=RW, addr=0xf0000000, size=0x10000000


FOR AT91 (1) special for uclinux
-------------------------------------------
#skyeye config file sample
cpu: arm7tdmi
mach: at91
mem_bank: map=M, type=RW, addr=0x00000000, size=0x00004000
mem_bank: map=M, type=RW, addr=0x01000000, size=0x00400000
mem_bank: map=M, type=R,  addr=0x01400000, size=0x00400000, file=./boot.rom
mem_bank: map=M, type=RW, addr=0x02000000, size=0x00400000
mem_bank: map=M, type=RW, addr=0x02400000, size=0x00008000
mem_bank: map=M, type=RW, addr=0x04000000, size=0x00400000
mem_bank: map=I, type=RW, addr=0xf0000000, size=0x10000000
#set nic info state=on/off  mac=xx:xx:xx:xx:xx:xx  ethmod=tuntap/vnet hostip=dd.dd.dd.dd
net: state=on, mac=0:5:3:2:1:f, ethmod=tuntap, hostip=192.168.2.1


FOR AT91 (2) special for uclinux
-------------------------------------------
cpu: arm7tdmi
mach: at91
mem_bank: map=M, type=RW, addr=0x00000000, size=0x00004000
mem_bank: map=M, type=RW, addr=0x01000000, size=0x00400000
mem_bank: map=M, type=R,  addr=0x01400000, size=0x00400000, file=./boot.rom
mem_bank: map=M, type=RW, addr=0x02000000, size=0x00400000
mem_bank: map=M, type=RW, addr=0x02400000, size=0x00008000
mem_bank: map=M, type=RW, addr=0x04000000, size=0x00400000
mem_bank: map=I, type=RW, addr=0xf0000000, size=0x10000000
#set nic info state=on/off  mac=xx:xx:xx:xx:xx:xx  ethmod=tuntap/vnet hostip=dd.dd.dd.dd
net: state=on, mac=0:4:3:2:1:f, ethmod=tuntap, hostip=10.0.0.1


FOR EP7312 (1) speciall for linux
-------------------------------------------
cpu: arm720t
mach: ep7312
mem_bank: map=I, type=RW, addr=0x80000000, size=0x00010000
mem_bank: map=M, type=RW, addr=0xc0000000, size=0x00200000
mem_bank: map=M, type=RW, addr=0xc0200000, size=0x00200000, file=./initrd.img
mem_bank: map=M, type=RW, addr=0xc0400000, size=0x00c00000


FOR StrongArm SA1100 (1) speciall for linux
-------------------------------------------
cpu: sa1100
mach: sa1100
mem_bank: map=I, type=RW, addr=0x80000000, size=0x40000000
mem_bank: map=M, type=RW, addr=0xc0000000, size=0x00800000
mem_bank: map=M, type=RW, addr=0xc0800000, size=0x00400000, file=./initrd.img
mem_bank: map=M, type=RW, addr=0xc0c00000, size=0x01400000
mem_bank: map=I, type=RW, addr=0xe0000000, size=0x08000000
#0xe0000000 128M cache flush memory bank







-------------------------------------------------------------------------------
		   README for GNU development tools

This directory contains various GNU compilers, assemblers, linkers, 
debuggers, etc., plus their support routines, definitions, and documentation.

If you are receiving this as part of a GDB release, see the file gdb/README.
If with a binutils release, see binutils/README;  if with a libg++ release,
see libg++/README, etc.  That'll give you info about this
package -- supported targets, how to use it, how to report bugs, etc.

It is now possible to automatically configure and build a variety of
tools with one command.  To build all of the tools contained herein,
run the ``configure'' script here, e.g.:

	./configure 
	make

To install them (by default in /usr/local/bin, /usr/local/lib, etc),
then do:
	make install

(If the configure script can't determine your type of computer, give it
the name as an argument, for instance ``./configure sun4''.  You can
use the script ``config.sub'' to test whether a name is recognized; if
it is, config.sub translates it to a triplet specifying CPU, vendor,
and OS.)

If you have more than one compiler on your system, it is often best to
explicitly set CC in the environment before running configure, and to
also set CC when running make.  For example (assuming sh/bash/ksh):

	CC=gcc ./configure
	make

A similar example using csh:

	setenv CC gcc
	./configure
	make

Much of the code and documentation enclosed is copyright by
the Free Software Foundation, Inc.  See the file COPYING or
COPYING.LIB in the various directories, for a description of the
GNU General Public License terms under which you can copy the files.

REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info
on where and how to report problems.
