ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Ltib] NBOOT command and kernel boot


From: Tom Moulton
Subject: [Ltib] NBOOT command and kernel boot
Date: Tue, 31 Jul 2007 13:28:15 -0500

I am trying to boot from a flash disk (NAND flash on mpc8313)

 

I am using the MTD commands (mtdparts etc) and am able to come up in u-boot, load & start the kernel but it never starts running

 

=> echo $bootargs

root=/dev/mtdblock6 rw rootfstype=jffs2 mtdparts=nand0:1m(u-boot),2M(kernel),-(jffs2)

=> setenv autostart yes

=> nboot kernel

 

Loading from NAND 32MiB 3,3V 8-bit, offset 0x100000

   Image Name:   Linux-2.6.20

   Created:      2007-07-31  13:41:49 UTC

   Image Type:   PowerPC Linux Kernel Image (gzip compressed)

   Data Size:    1836829 Bytes =  1.8 MB

   Load Address: 00000000

   Entry Point:  00000000

Automatic boot of image at addr 0x02000000 ...

## Booting image at 02000000 ...

   Image Name:   Linux-2.6.20

   Created:      2007-07-31  13:41:49 UTC

   Image Type:   PowerPC Linux Kernel Image (gzip compressed)

   Data Size:    1836829 Bytes =  1.8 MB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

 

 

I get the same thing if I use bootm

 

=> run mtd_args

=> echo $bootargs

root=/dev/mtdblock6 rw rootfstype=jffs2 mtdparts=nand0:1m(u-boot),2M(kernel),-(jffs2)

=> nand read 1000000 kernel

 

NAND read: device 0 offset 0x100000, size 0x200000

 2097152 bytes read: OK

=> bootm 1000000

## Booting image at 01000000 ...

   Image Name:   Linux-2.6.20

   Created:      2007-07-31  13:41:49 UTC

   Image Type:   PowerPC Linux Kernel Image (gzip compressed)

   Data Size:    1836829 Bytes =  1.8 MB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

 

Actually that is good (I hope) since it may then have *nothing* to do with NAND Flash

 

I have loaded from RAM and verified that the JFFS2 file system is in /dev/mtdblock6

 

I also have /boot in that system with the hopes that the kernel would find the extra files it needs from there

 

Anyone have any ideas?

 

tom

 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]