[Skyeye-developer] hi! where I should put those files?

kang shuo blackfin.kang at gmail.com
Sat Apr 7 16:07:36 CST 2007


Please do not put so long message on the top of your post. It is hard
to find your message.
You can put vmlinux to the same directory with skyeye, but it is not nessary.

-- Thanks
-- Michael.Kang

On 4/5/07, cole <s_thtang at stu.edu.cn> wrote:
> skyeye-developer-request at lists.gro.clinux.org wrote:
> > Send Skyeye-developer mailing list submissions to
> >       skyeye-developer at lists.gro.clinux.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >       http://lists.gro.clinux.org/cgi-bin/mailman/listinfo/skyeye-developer
> > or, via email, send a message with subject or body 'help' to
> >       skyeye-developer-request at lists.gro.clinux.org
> >
> > You can reach the person managing the list at
> >       skyeye-developer-owner at lists.gro.clinux.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Skyeye-developer digest..."
> >
> >
> > Today's Topics:
> >
> >    1. Re: [SkyEye DOC] How to run ARMLinux 2.6.14 on  SkyEye's
> >       SMDK2410 simulation (Arnab Som)
> >    2. Re: [SkyEye DOC] How to run ARMLinux 2.6.14 on  SkyEye's
> >       SMDK2410 simulation (Anthony Lee)
> >    3. Re: problem in loading the arm image (Anthony Lee)
> >    4. [SkyEye Doc] How to run RedBoot on SkyEye's     SMDK2410
> >       simulation (Anthony Lee)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Wed, 4 Apr 2007 14:04:16 +0900
> > From: "Arnab Som" <arnabsom at gmail.com>
> > Subject: Re: [Skyeye-developer] [SkyEye DOC] How to run ARMLinux
> >       2.6.14 on       SkyEye's SMDK2410 simulation
> > To: "=?ISO-8859-1?Q?Skyeyee&lt, _e=0F=11h=05d8=13g=14(i=02.d,
> >       _6e=08=17h!(?=" <skyeye-developer at lists.gro.clinux.org>
> > Message-ID:
> >       <701cbbc40704032204j78afb35bn4ab2c9709fada628 at mail.gmail.com>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > Hi Anthony,
> >                      I have applied the patch and compiled but after getting
> > the vmlinux in the top directory i tried to simulate using the initrd.img in
> > testsuite2 . But the skyeye system hanged ..
> > How to generate the initrd.img file?
> >
> > Regards
> > Arnab
> >
> >
> > On 4/3/07, Anthony Lee <don.anthony.lee+program at gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> Here is the the patch and howto for running ARMLinux 2.6.14
> >> on SkyEye's SMDK2410 simulation including the UART, LCD, NET sections.
> >>
> >> Hope that it's useful for beginner to both Linux and SkyEye.
> >>
> >> Though the patch contains changing of UART settings, you still have a
> >> chance
> >> to debug your linux kernel through JTAG DCC, but you need the SkyEye from
> >> the current SVN head source.
> >>
> >>
> >> Cheers.
> >>
> >> Anthony Lee
> >>
> >>
> >> #######################################################################
> >>
> >>
> >>                         ARMLinux 2.6.14 for SMDK2410 on SkyEye
> >>
> >> How to run:
> >> ===========
> >>         - First you need skyeye that released after 2007-02-09 ( > v1.2.1)
> >>         - And you should get a "initrd.img" (2M)
> >>         - Run the command below
> >>                 $ skyeye -e vmlinux -c skyeye.conf
> >>
> >>
> >> How to build vmlinux:
> >> =====================
> >>         - Apply the patch "linux-2.6.14-skyeye.patch"
> >>                 ~/linux $ patch -p1 < linux-2.6.14-skyeye.patch
> >>
> >>         - Apply the default configuration for s3c2410_skyeye
> >>                 ~/linux $ make ARCH=arm CROSS_COMPILE=arm-linux-uclibc-
> >> s3c2410_skyeye_defconfig
> >>
> >>         - Build vmlinux
> >>                 ~/linux $ make ARCH=arm CROSS_COMPILE=arm-linux-uclibc-
> >>
> >>
> >> linux-2.6.14-skyeye.patch contains:
> >> ===================================
> >>         - Fixed CS8900A driver.
> >>         - Fixed LCD driver.
> >>         - Changed the UART settings of S3C2410x so that we can run it on
> >> SkyEye.
> >>
> >> _______________________________________________
> >> Skyeye-developer mailing list
> >> Skyeye-developer at lists.gro.clinux.org
> >> http://lists.gro.clinux.org/cgi-bin/mailman/listinfo/skyeye-developer
> >>
> >>
> >>
> >>
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: http://lists.gro.clinux.org/pipermail/skyeye-developer/attachments/20070404/2aebf41a/attachment-0001.htm
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Wed, 4 Apr 2007 17:41:10 +0800
> > From: "Anthony Lee" <don.anthony.lee+program at gmail.com>
> > Subject: Re: [Skyeye-developer] [SkyEye DOC] How to run ARMLinux
> >       2.6.14 on       SkyEye's SMDK2410 simulation
> > To: "=?UTF-8?Q?Skyeyee&lt, _e=0F=11h=05d8=13g=14(i=02.d,
> >       _6e=08=17h!(?=" <skyeye-developer at lists.gro.clinux.org>
> > Message-ID:
> >       <638bf0dd0704040241l4451c4fdyfa2ffe8f723de9cb at mail.gmail.com>
> > Content-Type: text/plain; charset=UTF-8; format=flowed
> >
> >
> >> How to generate the initrd.img file?
> >>
> >
> > Please search from google.
> >
> > Anyway, you can get it from the skyeye testsuite 2.1.
> > but need to add /dev/ttySAC0 to it.
> >
> > # mount initrd.img /mnt -o loop
> > # cd /mnt/dev
> > # mknod ttySAC0 c 204 64
> > # cd -
> > # umount /mnt
> >
> >
> > 2007/4/4, Arnab Som <arnabsom at gmail.com>:
> >
> >> Hi Anthony,
> >>                      I have applied the patch and compiled but after getting
> >> the vmlinux in the top directory i tried to simulate using the initrd.img in
> >> testsuite2 . But the skyeye system hanged ..
> >> How to generate the initrd.img file?
> >>
> >> Regards
> >> Arnab
> >>
> >>
> >>
> >> On 4/3/07, Anthony Lee <don.anthony.lee+program at gmail.com >
> >> wrote:
> >>
> >>> Hi all,
> >>>
> >>> Here is the the patch and howto for running ARMLinux 2.6.14
> >>> on SkyEye's SMDK2410 simulation including the UART, LCD, NET sections.
> >>>
> >>> Hope that it's useful for beginner to both Linux and SkyEye.
> >>>
> >>> Though the patch contains changing of UART settings, you still have a
> >>>
> >> chance
> >>
> >>> to debug your linux kernel through JTAG DCC, but you need the SkyEye from
> >>> the current SVN head source.
> >>>
> >>>
> >>> Cheers.
> >>>
> >>> Anthony Lee
> >>>
> >>>
> >>>
> >>>
> >> #######################################################################
> >>
> >>>                         ARMLinux 2.6.14 for SMDK2410 on
> >>>
> >> SkyEye
> >>
> >>> How to run:
> >>> ===========
> >>>         - First you need skyeye that released after 2007-02-09 ( > v1.2.1
> >>>
> >> )
> >>
> >>>         - And you should get a " initrd.img" (2M)
> >>>         - Run the command below
> >>>                 $ skyeye -e vmlinux -c skyeye.conf
> >>>
> >>>
> >>> How to build vmlinux:
> >>> =====================
> >>>         - Apply the patch "linux-2.6.14-skyeye.patch "
> >>>                 ~/linux $ patch -p1 < linux-2.6.14-skyeye.patch
> >>>
> >>>         - Apply the default configuration for s3c2410_skyeye
> >>>                 ~/linux $ make ARCH=arm CROSS_COMPILE=arm-linux-uclibc-
> >>> s3c2410_skyeye_defconfig
> >>>
> >>>         - Build vmlinux
> >>>                 ~/linux $ make ARCH=arm CROSS_COMPILE=arm-linux-uclibc-
> >>>
> >>>
> >>> linux-2.6.14-skyeye.patch contains:
> >>> ===================================
> >>>         - Fixed CS8900A driver.
> >>>         - Fixed LCD driver.
> >>>         - Changed the UART settings of S3C2410x so that we can run it on
> >>>
> >> SkyEye.
> >>
> >>> _______________________________________________
> >>> Skyeye-developer mailing list
> >>> Skyeye-developer at lists.gro.clinux.org
> >>>
> >>>
> >> http://lists.gro.clinux.org/cgi-bin/mailman/listinfo/skyeye-developer
> >>
> >>>
> >>>
> >> _______________________________________________
> >> Skyeye-developer mailing list
> >> Skyeye-developer at lists.gro.clinux.org
> >> http://lists.gro.clinux.org/cgi-bin/mailman/listinfo/skyeye-developer
> >>
> >>
> >>
> >
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Wed, 4 Apr 2007 17:51:57 +0800
> > From: "Anthony Lee" <don.anthony.lee+program at gmail.com>
> > Subject: Re: [Skyeye-developer] problem in loading the arm image
> > To: "=?UTF-8?Q?Skyeyee&lt, _e=0F=11h=05d8=13g=14(i=02.d,
> >       _6e=08=17h!(?=" <skyeye-developer at lists.gro.clinux.org>
> > Message-ID:
> >       <638bf0dd0704040251o723977efhad604b05e2465f1d at mail.gmail.com>
> > Content-Type: text/plain; charset=UTF-8; format=flowed
> >
> > Hi,
> >
> > You could turn on JTAG DCC console by change "linux/.config"
> > like the lines shown below:
> >
> > #########################################
> > CONFIG_SERIAL_CORE=y
> > CONFIG_SERIAL_CORE_CONSOLE=y
> > CONFIG_SERIAL_DCC=y
> > CONFIG_SERIAL_DCC_CONSOLE=y
> > ##########################################
> >
> > and add "console=ttyJ0" to your CONFIG_CMDLINE,
> > ttyJ0: major number is 4, minor number is 64, maybe you should delete ttyS0
> >
> >
> > Then, add "uart: mod=stdio, converter=dcc" to your "skyeye.conf" and retry it
> > to see what happens.
> >
> >
> > BTW, the introduction shown above needs the SkyEye from current SVN head.
> >
> > 2007/4/4, Arnab Som <arnabsom at gmail.com>:
> >
> >> Hi,
> >>      I have compiled the linux-2.6.20.4 with the kb9202_defconfig and my
> >> skyeye.conf looks like
> >> -----------------------------------------------------------------------------------------------------
> >> #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=RW, addr=0x02400000, size=0x00008000
> >> mem_bank: map=M, type=RW, addr=0x04000000, size=0x00400000
> >> mem_bank: map=M, type=RW, addr=0xc0000000, size=0x00400000,file=./vmlinux
> >>
> >> mem_bank: map=I, type=RW, addr=0xf0000000, size=0x10000000
> >>
> >> mem_bank: map=M, type=RW, addr=0xc0000000, size=0x00100000
> >>
> >> #lcd: type=ep7312,mod=gtk
> >> #dbct: state=on
> >> #dbct: state=off
> >>
> >> ----------------------------------------------------------------------------------------------------
> >>
> >> But when i run it as follows i get a hung up situation like below
> >> Any guesses
> >>
> >> [arnabsom at localhost boot]$ skyeye -c skyeye.conf -e vmlinux
> >> arch: arm
> >> cpu info: armv3, arm7tdmi, 41007700, fff8ff00, 0
> >> mach info: name at91, mach_init addr 0x8057490
> >> uart_mod:0, desc_in:, desc_out:
> >> SKYEYE: use arm7100 mmu ops
> >> Loaded RAM   ./vmlinux
> >> exec file "vmlinux"'s format is elf32-little.
> >> load section .init: addr = 0xc0008000  size = 0x00019000.
> >> load section .text: addr = 0xc0021000  size = 0x0021dc78.
> >> not load section .rodata: addr = 0xc023f000  size = 0x00000000 .
> >> not load section .pci_fixup: addr = 0xc023f000  size = 0x00000000 .
> >> not load section .rio_route: addr = 0xc023f000  size = 0x00000000 .
> >> load section __ksymtab: addr = 0xc023f000  size = 0x00003f70.
> >> load section __ksymtab_gpl: addr = 0xc0242f70  size = 0x00000d50.
> >> not load section __ksymtab_unused: addr = 0xc0243cc0  size = 0x00000000 .
> >> not load section __ksymtab_unused_gpl: addr = 0xc0243cc0  size = 0x00000000
> >> .
> >> load section __ksymtab_gpl_future: addr = 0xc0243cc0  size = 0x00000018.
> >> not load section __kcrctab: addr = 0xc0243cd8  size = 0x00000000 .
> >> not load section __kcrctab_gpl: addr = 0xc0243cd8  size = 0x00000000 .
> >>  not load section __kcrctab_unused: addr = 0xc0243cd8  size = 0x00000000 .
> >> not load section __kcrctab_unused_gpl: addr = 0xc0243cd8  size = 0x00000000
> >> .
> >> not load section __kcrctab_gpl_future: addr = 0xc0243cd8  size = 0x00000000
> >> .
> >> load section __ksymtab_strings: addr = 0xc0243cd8  size = 0x0000aeb8.
> >> load section __param: addr = 0xc024eb90  size = 0x00000370.
> >> load section .data: addr = 0xc0250000  size = 0x0001d43c.
> >> not load section .bss: addr = 0xc026d440  size = 0x00015854 .
> >> not load section .comment: addr = 0x00000000  size = 0x000024fc .
> >> start addr is set to 0xc0008000 by exec file.
> >>
> >>
> >> _______________________________________________
> >> Skyeye-developer mailing list
> >> Skyeye-developer at lists.gro.clinux.org
> >> http://lists.gro.clinux.org/cgi-bin/mailman/listinfo/skyeye-developer
> >>
> >>
> >>
> >
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Thu, 5 Apr 2007 06:52:51 +0800
> > From: "Anthony Lee" <don.anthony.lee+program at gmail.com>
> > Subject: [Skyeye-developer] [SkyEye Doc] How to run RedBoot on
> >       SkyEye's        SMDK2410 simulation
> > To: skyeye-developer at lists.gro.clinux.org
> > Cc: dorin at chaski.com
> > Message-ID:
> >       <638bf0dd0704041552y1b5037d7xd593433ff6e991f5 at mail.gmail.com>
> > Content-Type: text/plain; charset=UTF-8; format=flowed
> >
> > Hi Mike,
> >
> > RedBoot now can run on SkyEye from current SVN head source,
> > it's the bug of SkyEye, and I already fixed it.
> > Please try again followed by the step and step shown below.
> >
> > NOTE:
> > Platform: CygWin
> > SkyEye: current SVN trunk
> > arm-elf-gcc: 2.95.3
> > ecos: 2.0-b1
> >
> >
> > #########################################################################
> > $ cd ~
> > $ wget http://download.atmark-techno.com/armadillo-j/cross-dev/arm-elf-tools-cygwin-aj0.tgz
> > $ cd /usr/local
> > $ tar zxvf ~/arm-elf-tools-cygwin-aj0.tgz
> >
> > $ mkdir -p /opt/ecos/bin
> > $ cd /opt/ecos
> > $ cvs -d :pserver:anoncvs at ecos.sourceware.org:/cvs/ecos login
> > $ cvs -z3 -d :pserver:anoncvs at ecos.sourceware.org:/cvs/ecos co -P ecos
> > $ mv ecos ecos-cvs
> > $ wget http://www.ecoscentric.com/snapshots/ecosconfig-060710.exe.bz2
> > $ bzip2 -d ecosconfig-060710.exe.bz2
> > $ mv ecosconfig-060710.exe bin/ecosconfig.exe
> > $ chmod +x bin/ecosconfig.exe
> >
> > $ export ECOS_REPOSITORY=/opt/ecos/ecos-cvs/packages
> > $ export PATH=/opt/ecos/bin:$PATH
> >
> > $ mkdir -p /opt/ecos/redboot
> > $ cd /opt/ecos/redboot
> > $ ecosconfig new smdk2410 redboot
> > $ ecosconfig import
> > /opt/ecos/ecos-cvs/packages/hal/arm/arm9/smdk2410/current/misc/smdk2410_redboot_ROMRAM.ecm
> > $ ecosconfig tree
> > $ make OLDGCC=1
> >
> > $ cd /opt
> > $ svn co http://skyeye.svn.sourceforge.net/svnroot/skyeye/skyeye-v1/trunk
> > skyeye-v1-svn
> > $ cd skyeye-v1-svn
> > $ make
> >
> > $ mkdir -p /opt/smdk2410-redboot
> > $ cp /opt/ecos/redboot/install/bin/redboot.bin .
> >
> > $ cat >> skyeye.conf <<_______EOF
> >
> >> # skyeye config file for SMDK2410
> >>
> >> cpu: arm920t
> >> mach: s3c2410x
> >>
> >> # physical memory
> >> mem_bank: map=M, type=R,  addr=0x00000000, size=0x01000000, file=./redboot.bi
> >>
> > n
> >
> >> mem_bank: map=M, type=RW, addr=0x30000000, size=0x01000000
> >>
> >> # all peripherals I/O mapping area
> >> mem_bank: map=I, type=RW, addr=0x48000000, size=0x20000000
> >>
> >> _______EOF
> >>
> >
> > $ /opt/skyeye-v1-svn/binary/skyeye.exe
> >
> > **************************** WARNING **********************************
> > If you want to run ELF image, you should use -e option to indicate
> > your elf-format image filename. Or you only want to run binary image,
> > you need to set the filename of the image and its entry in skyeye.conf.
> > ***********************************************************************
> >
> > big_endian is false.
> > arch: arm
> > cpu info: armv4, arm920t, 41009200, ff00fff0, 2
> > mach info: name s3c2410x, mach_init addr 00421A20
> > uart_mod:0, desc_in:, desc_out:, converter:
> > SKYEYE: use arm920t mmu ops
> > Loaded ROM   ./redboot.bin
> > ERROR: s3c2410x_io_write_word(0x53000000) = 0x00000000
> > ERROR: s3c2410x_io_write_word(0x4c000000) = 0x00ffffff
> > ERROR: s3c2410x_io_write_word(0x48000000) = 0x22111120
> > ERROR: s3c2410x_io_write_word(0x48000004) = 0x00000700
> > ERROR: s3c2410x_io_write_word(0x48000008) = 0x00000700
> > ERROR: s3c2410x_io_write_word(0x4800000c) = 0x00000700
> > ERROR: s3c2410x_io_write_word(0x48000010) = 0x00000700
> > ERROR: s3c2410x_io_write_word(0x48000014) = 0x00000700
> > ERROR: s3c2410x_io_write_word(0x48000018) = 0x00000700
> > ERROR: s3c2410x_io_write_word(0x4800001c) = 0x00018005
> > ERROR: s3c2410x_io_write_word(0x48000020) = 0x00018005
> > ERROR: s3c2410x_io_write_word(0x48000024) = 0x008e0459
> > ERROR: s3c2410x_io_write_word(0x48000028) = 0x00000032
> > ERROR: s3c2410x_io_write_word(0x4800002c) = 0x00000030
> > ERROR: s3c2410x_io_write_word(0x48000030) = 0x00000030
> > ERROR: s3c2410x_io_write_word(0x4c000004) = 0x00054011
> > SKYEYE: WARNING: illegal write word to 0x0 of 0xea00000e @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x4 of 0xe59ff018 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x8 of 0xe59ff018 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xc of 0xe59ff018 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x10 of 0xe59ff018 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x14 of 0x0 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x18 of 0xe59ff018 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x1c of 0xe59ff018 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x100 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x104 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x108 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x10c of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x110 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x114 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x118 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x11c of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa700 of 0x50 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa704 of 0x3d090 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa708 of 0xe1a0c00d @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa70c of 0xe92dd800 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa710 of 0xe24cb004 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa714 of 0xe2800008 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa718 of 0xe3500007 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa71c of 0x979ff100 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x50 of 0x80017 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x54 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x58 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x5c of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x140 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x144 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x148 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x14c of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x60 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x64 of 0x24da0 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x68 of 0x24da0 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x6c of 0x10d90 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x70 of 0x10d80 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x74 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x78 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x7c of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa660 of 0xe1a0f002 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa664 of 0xe5943000 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa668 of 0xe5930000 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa66c of 0xe593200c @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa670 of 0xe3a01008 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa674 of 0xe1a0e00f @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa678 of 0xe1a0f002 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa67c of 0xe5943000 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x80 of 0x10bc8 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x84 of 0x10cd4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x88 of 0x0 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x8c of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x90 of 0x10b7c @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x94 of 0x0 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x98 of 0x10b68 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0x9c of 0x0 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa680 of 0xe5930000 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa684 of 0xe593200c @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa688 of 0xe3a01008 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa68c of 0xe1a0e00f @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa690 of 0xe1a0f002 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa694 of 0xe5943000 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa698 of 0xe5930000 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa69c of 0xe593200c @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa0 of 0x10894 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa4 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa8 of 0x10910 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xac of 0x109ac @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xb0 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xb4 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xb8 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xbc of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6a0 of 0xe3a01008 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6a4 of 0xe1a0e00f @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6a8 of 0xe1a0f002 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6ac of 0xe5943000 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6b0 of 0xe5930000 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6b4 of 0xe593200c @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6b8 of 0xe3a01008 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6bc of 0xe1a0e00f @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xc0 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xc4 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xc8 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xcc of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xd0 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xd4 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xd8 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xdc of 0x1a4a8 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6c0 of 0xe1a0f002 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6c4 of 0xebfffd74 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6c8 of 0xe3a03001 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6cc of 0xe584342c @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6d0 of 0xe91ba810 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6d4 of 0xe1a0e00f @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6d8 of 0xe1a0f004 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6dc of 0xe3500000 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xe0 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xe4 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xe8 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xec of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xf0 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xf4 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xf8 of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xfc of 0x10bb4 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6e0 of 0xaafffffb @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6e4 of 0xe59f3014 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6e8 of 0xe59f0014 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6ec of 0xe5932048 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6f0 of 0xe1a0e00f @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6f4 of 0xe1a0f002 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6f8 of 0xe91ba810 @ 0x0
> > SKYEYE: WARNING: illegal write word to 0xa6fc of 0x23090 @ 0x0
> > +SKYEYE: WARNING: illegal write halfword to 0xaaa of 0xf0 @ 0x0
> > SKYEYE: WARNING: illegal write halfword to 0xaaa of 0xaa @ 0x0
> > SKYEYE: WARNING: illegal write halfword to 0x554 of 0x55 @ 0x0
> > SKYEYE: WARNING: illegal write halfword to 0xaaa of 0x90 @ 0x0
> > SKYEYE: WARNING: illegal write halfword to 0x0 of 0xf0 @ 0x0
> > FLASH: driver init failed: Driver does not support device
> > Sorry, FLASH config exceeds available space in FIS directory
> >
> > RedBoot(tm) bootstrap and debug environment [ROMRAM]
> > Non-certified release, version UNKNOWN - built 05:49:39, Apr  5 2007
> >
> > Platform: SMDK2410 system (ARM9)
> > Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
> > Copyright (C) 2003, 2004, 2005, 2006 eCosCentric Limited
> >
> > RAM: 0x00000000-0x04000000, [0x00027440-0x03ff1000] available
> > FLASH: 0x00000000 - 0x1, 0 blocks of 0x00000000 bytes each.
> > RedBoot> help
> > Manage aliases kept in FLASH memory
> >    alias name [value]
> > Manage machine caches
> >    cache [ON | OFF]
> > Display/switch console channel
> >    channel [-1|<channel number>]
> > Compute a 32bit checksum [POSIX algorithm] for a range of memory
> >    cksum -b <location> -l <length>
> > Display (hex dump) a range of memory
> >    dump -b <location> [-l <length>] [-s] [-1|-2|-4]
> > Execute an image - with MMU off
> >    exec [-w timeout] [-b <load addr> [-l <length>]]
> >         [-r <ramdisk addr> [-s <ramdisk length>]]
> >         [-c "kernel command line"] [-t <target> ] [<entry_point>]
> > Manage FLASH images
> >    fis {cmds}
> > Manage configuration kept in FLASH memory
> >    fconfig [-i] [-l] [-n] [-f] [-d] | [-d] nickname [value]
> > Execute code at a location
> >    go [-w <timeout>] [-c] [entry]
> > Help about help?
> >    help [<topic>]
> > Display command history
> >    history
> > Load a file
> >    load [-r] [-v] [-d] [-m <varies>] [-c <channel_number>]
> >         [-b <base_address>] <file_name>
> > Compare two blocks of memory
> >    mcmp -s <location> -d <location> -l <length> [-1|-2|-4]
> > Copy memory from one address to another
> >    mcopy -s <location> -d <location> -l <length> [-1|-2|-4]
> > Fill a block of memory with a pattern
> >    mfill -b <location> -l <length> -p <pattern> [-1|-2|-4]
> > Reset the system
> >    reset
> > Display RedBoot version information
> >    version
> > Display (hex dump) a range of memory
> >    x -b <location> [-l <length>] [-s] [-1|-2|-4]
> > RedBoot>
> >
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > Skyeye-developer mailing list
> > Skyeye-developer at lists.gro.clinux.org
> > http://lists.gro.clinux.org/cgi-bin/mailman/listinfo/skyeye-developer
> >
> >
> > End of Skyeye-developer Digest, Vol 31, Issue 11
> > ************************************************
> >
> I run the Skyeye ,but it prompts no vmlnuz file so
> where I should put those file? In the same dir with skyeye?
>
>
> _______________________________________________
> Skyeye-developer mailing list
> Skyeye-developer at lists.gro.clinux.org
> http://lists.gro.clinux.org/cgi-bin/mailman/listinfo/skyeye-developer
>



More information about the Skyeye-developer mailing list