Hi guys. I have come across a bulletin that blames the problem (described bellow) on the U-Boot bootloader:
https://e2e.ti.com/support/embedded/linux/f/354/t/73788 And this is a typical bootup sequence happening for us: U-Boot 1.3.4 (Feb 28 2012 - 20:31:25) - AT91SAM9260@200 MHz - DRAM: 64 MB NAND: 256 MiB In: serial Out: serial Err: serial Net: smc911x, macb0 main_loop: BootStatus=not_ok main_loop: bootstatus_valid=0 main_loop: bootspace_target=1 main_loop: bootspace_target=1 main_loop: setting bootcmd to bootcmd1=nand read.jffs2 0x22000000 0x000c0000 0x00200000; bootm 0x22000000 main_loop: set BootSpace to 1 Erasing Nand... Erasing at 0xa0000 – 100% complete. Writing to Nand... done main_loop: setting bootargs to bootargs1=mem=64M console=ttyS0,115200 ubi.mtd=6,512 ubi.mtd=9,512 root=ubi0:ipc3-rootfs rootfstype=ubifs lpj=495616 loglevel=8 rw Hit any key to stop autoboot: 0 NAND read: device 0 offset 0xc0000, size 0x200000 Reading data from 0x17d000 – 37% complete.reading NAND page at offset 0x17d800 failed 2097152 bytes read: ERROR 1. 1. Booting kernel from Legacy Image at 22000000 ... Image Name: Angstrom/2.6.27/ipc3 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1098224 Bytes = 1 MB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! Enter password:RomBOOT > Is there any chance that you guys are aware of this problem and if it is really a u-boot problem? If so, do you know if this has been fixed and and in which version? Thank you. -- Boriša Jevtić _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
