Hello all,

Thanks to Vijain for pointing out the patch for skyeye. I could now run at91rm u-boot successfully on skyeye.

I compiled a uImage from the vmlinux elf binary (take from the skyeye testsuite). When i try to expand this image i always get a checksum error. I didn't need to do a tftp or cp.b as i could directly load the image in memory using the emulator.

Can some please point out if there is an issue with this?

[root@localhost at91rm]# skyeye SKYEYE: If you have ELF kernel file, please use -e option to indicate your ELF format kernel filename SKYEYE: If you only have kernel binary image, you should put the filename of kernel binary image in skyeye.conf file arch: arm cpu info: armv4, arm920t, 41009200, ff00fff0, 2 mach info: name at91rm92, mach_init addr 0x8069c80 uart info: input device is /dev/stdin, fd is 4. uart info: output device is /dev/stdout, fd is 5. SKYEYE: use arm920t mmu ops Loaded RAM ./u-boot.bin Loaded RAM ./uImage Loaded RAM ./uImage

U-Boot 1.1.4 (Mar 31 2006 - 17:42:28)

U-Boot code: 21F00000 -> 21F16EEC BSS: -> 21F33E04 RAM Configuration: Bank #0: 20000000 32 MB Atmel: Flash: 0 kB *** Warning - bad CRC, using default environment

In: serial Out: serial Err: serial U-Boot> bootm 0x20000010 ## Booting image at 20000010 ... Image Name: Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 756397 Bytes = 738.7 kB Load Address: 20000010 Entry Point: 20000010 Verifying Checksum ... Bad Data CRC U-Boot>

skyeye.conf cpu : arm920t mach: at91rm92

mem_bank: map=M, type=RW, addr=0x00000000, size=0x40000, file=./u-boot.bin, boot=yes mem_bank: map=M, type=RW, addr=0x10000000, size=0x1000000, file=./uImage mem_bank: map=M, type=RW, addr=0x20000010, size=0x5000000, file=./uImage mem_bank: map=I, type=RW, addr=0xfffa0000, size=0x00060000 uart: fd_in=/dev/stdin, fd_out=/dev/stdout