From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alexandre Gambier <a.gambier@ftemaximal.fr>
Date: Wed, 02 May 2012 08:55:01 +0200
Subject: [U-Boot] Can't read kernel if bad blocks are present in
	partition
In-Reply-To: <4F9AD9D7.6060009@freescale.com>
References: <4F99313F.1020800@ftemaximal.fr> <4F9981B7.6000000@logicpd.com>
	<4F99A1D5.5030005@freescale.com>
	<4F9A47E6.9070706@ftemaximal.fr> <4F9AAD5B.2040306@logicpd.com>
	<4F9AD9D7.6060009@freescale.com>
Message-ID: <4FA0DA45.4090702@ftemaximal.fr>
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

>> 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.
Everything works fine now.
I now use "nand write.i" and "nand read.i" instead of "nand write" and 
"nand.read".
>> Does STLinux have a support contact?
>>
>> This list is for mainline U-Boot.  Have you checked whether these chips
>> are supported in current mainline U-Boot?
It was just a misunderstanding of u-boot commands.

Thank you guys for your help.