From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Fri, 27 Apr 2012 12:43:24 -0500
Subject: [U-Boot] Can't read kernel if bad blocks are present in
	partition
In-Reply-To: <4F9A47E6.9070706@ftemaximal.fr>
References: <4F99313F.1020800@ftemaximal.fr> <4F9981B7.6000000@logicpd.com>
	<4F99A1D5.5030005@freescale.com> <4F9A47E6.9070706@ftemaximal.fr>
Message-ID: <4F9ADABC.10802@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 02: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.
> 
>> That has been the default for a while now.  Why use something as ancient
>> as 1.3.1?
> Because my embedded linux distribution is STLinux which includes support
> for STM chips with this version of u-boot.

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?

-Scott