From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Fri, 27 Apr 2012 12:39:35 -0500
Subject: [U-Boot] Can't read kernel if bad blocks are present in
	partition
In-Reply-To: <4F9AAD5B.2040306@logicpd.com>
References: <4F99313F.1020800@ftemaximal.fr> <4F9981B7.6000000@logicpd.com>
	<4F99A1D5.5030005@freescale.com>
	<4F9A47E6.9070706@ftemaximal.fr> <4F9AAD5B.2040306@logicpd.com>
Message-ID: <4F9AD9D7.6060009@freescale.com>
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

On 04/27/2012 09:29 AM, Peter Barada wrote:
> On 04/27/2012 03:16 AM, Alexandre Gambier wrote:
>> Hi,
>>
>>
>>>> Did you use "nand write.i"  to write the kernel and "nand read.i" to
>>>> read the kernel? the ".i" tells u-boot to skip bad blocks...
>> No I use "nand read $load_addr AppKernel" cause I didn't know we can use 
>> "nand read.i" - "help nand" doesn't display this information.
>> I tried "nand read.i" and now it works fine but I still can't boot the 
>> kernel cause its crc is wrong I will flash the kernel again with "nand 
>> write.i" and check if it works.
> Assuming you load the kernel to ram with tftp (and that "AppKernel" is
> an mtdparts partition in NAND), then you could do:
> 
> nand erase.part AppKernel
> tftp $load_addr uImage
> crc32 $load_addr $filesize
> nand write.i $load_addr AppKernel $filesize
> nand read.i $load_addr AppKernel $filesize
> crc32 $load_addr $filesize
> 
> To verify the CRCs match between what you load off tftp and what you
> read back from NAND.

There is no U-Boot version that both has "nand erase.part" and requires
a .i suffix on nand read/write.

-Scott