ltib
[Top][All Lists]
Advanced

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

RE: [Ltib] NBOOT command and kernel boot


From: Tanya Jiang
Subject: RE: [Ltib] NBOOT command and kernel boot
Date: Thu, 02 Aug 2007 11:26:27 +0800

Hi, Tom

I got this email from 83xx maillist.  
Did you use MPC8313E_RDB_K26_20070719.iso? 

What is the erase block size setting when you create the jffs2 FS? 
Please set the erase block as 16K.

Which command you used to write jffs2 partition on NAND?
Please use "nand write.jffs2" instead of "nand write". (Do not know whether 
there is bad block on your board)

There is a detailed document about NAND usage in kernel/u-boot to reference. 
You can find it at %$LTIB_ISO/help/software/NAND-usage_MPC8313ERDB.html.  
You can follow the steps to boot kenerl with JFFS2 in NAND. 
  
If it still does not work, can you enclosed a full log to us ?


Best Regards 
Tanya Jiang

On Wed, 2007-08-01 at 22:08 +0800, Tom Moulton wrote:
> Yes the MTD drivers are compiled in (ie have an '*' by them, not 'M' in ltib 
> menus)
> 
> I tried loading the kernel that I have in Flash and tftp'ing the DTB file 
> into memory and then did "bootm 1000000 - 2000000"
> 
> => setenv ethact TSEC1 
> => tftp 2000000 nand/mpc8313erdb.dtb 
> [snip] 
> => run mtd_args 
> => echo $bootargs 
> root=/dev/mtdblock6 rw rootfstype=jffs2 
> mtdparts=nand0:1m(u-boot),2M(kernel),-(jffs2) 
> => bootm 1000000 - 2000000 
> => nand read 1000000 kernel
> 
> NAND read: device 0 offset 0x100000, size 0x200000 
>  2097152 bytes read: OK 
> => bootm 1000000 - 2000000
> 
> I used - for the file system since the bootargs had root= in it pointing to 
> NAND
> 
> And IT worked! But...
> 
> The filesystem had no extra space on it...
> 
> There must be an option I have set wrong because the size it reports is the 
> same as the partition size (0x1D00000) but the jffs2 file size is smaller 
> (0x1C38000) which would give me 800K free space...
> 
> Tom
> 
> 
> 
> 





reply via email to

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