From mboxrd@z Thu Jan  1 00:00:00 1970
From: Manukumar <manukumar@signal-networks.com>
Date: Thu, 31 May 2012 09:45:11 +0530
Subject: [U-Boot] problem while making kernel up
In-Reply-To: <4FC64859.2070609@freescale.com>
References: <1337677828.2382.30.camel@Manukumar>
	<201205221615.07965.marex@denx.de> <4FBBD34F.5010501@freescale.com>
	<1337752596.2378.37.camel@Manukumar>
	<20120523080211.B633820025A@gemini.denx.de>
	<1337761847.2378.71.camel@Manukumar> <4FBD0D43.1060208@freescale.com>
	<1338354171.2370.13.camel@Manukumar> <4FC64859.2070609@freescale.com>
Message-ID: <1338437711.2367.9.camel@Manukumar>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

thanks scott.

i loaded my u-boot image to nand flash its fine.
and also 
I need my  kernel image and rootfs also in nand flash
so that my system should make kernel UP using nand flash.
how can i do this using nand flash as we are using only nand flash as
boot device.

manukumar
siganl-networks


On Wed, 2012-05-30 at 11:18 -0500, Scott Wood wrote:
> On 05/30/2012 12:02 AM, Manukumar wrote:
> > hello,
> > I was able to solve nand erase and nand write and saveenv.
> > Now,I am making kernel up and followed below steps..
> > 
> > 1)  tf 1000000 uImage_icm_v1.1
> >     nand erase 0x00200000 361483
> >     nand write 1000000 0x00200000 361483
> > 
> > 2)  tf c00000 p1021rdb_32b.dtb
> >     nand erase 0x00100000 3000
> >     nand write c00000 0x00100000 3000
> > 
> > 3)  tf 2000000 mini.rootfs.ext2.gz.uboot
> >     nand erase 0x00600000 2115d4
> >     nand write 2000000 0x00600000 2115d4
> > 
> > then to boot kernel from nand i used 
> > 	bootm 0x00200000 0x00600000 0x00100000
> 
> Bootm takes a RAM address, not a NAND address.  Unlike NOR flash, NAND
> is not directly addressable.  You need to use "nand read" first.
> 
> -Scott
>