Hi,
On Mon, Aug 23, 2010 at 10:12:42PM +0200, Dr. H. Nikolaus Schaller wrote:
> Hi Ruben,

> Am 23.08.2010 um 21:53 schrieb Ruben Viets:
> > Looks like you didn't damage the u-boot for one of the bricked minibooks. 
> > Although it looks like there are some issues with ecc/nand.

There are issues with ecc/nand: the original image has the
hardware ecc turned off.

> Yes, U-Boot still works.

Just to be clear about the letux-400 vs the epc700:
- We know how to boot an image from sd on the epc700. But the key
  combo for this is the same that flashes the kernel on the
  letux-400.
- We know that the letux-400 can do a lot more (like
  tftpbooting), but we just don't know the key combo yet :-(. The
  only thing we know is how to flash an uImage, and boot it.

> No, I think there is no ecc/nand issue - it is just that the 2.6 kernel is 
> too big for the partition and/or only
> partially copied to flash. Therefore the attempt to load but CRC fails.

The easiest way is to use kexec but I don't know if it works.
If I am correct (and not substituting another embedded system in
my mind), the image may be as large as 1.5MB.

> >  For kernel 2.6 we need to copy uImage manually with, cat uImage /dev/mtd1, 
> > but first any nand ecc issues need to be resolved. good luck with JTAG 
> > setup.

Hmmm, just wondering if I can use a cas3+ interface for that
(from duo labs).

> The reason may be that the 2.6 kernel is bigger and the automatic mode of 
> U-Boot doesn't copy it completely.
Yes, I know there were some weird discrepancies in the size of
the partition, and the size that is actually copied.

-- 
.signature not found

_______________________________________________
Mipsbook-devel mailing list
Mipsbook-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/mipsbook-devel

Reply via email to