From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Thu, 4 Aug 2011 13:02:47 -0500
Subject: [U-Boot] Nand: Uboot-Environment at bad block
In-Reply-To: <4E3A6F44.5000808@esd.eu>
References: <BANLkTimtNJ5Au4uPp2D7q8hZkbk3x5RERA@mail.gmail.com>
	<4E3A6F44.5000808@esd.eu>
Message-ID: <4E3ADEC7.30802@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 08/04/2011 05:07 AM, Daniel Gorsulowski wrote:
> Arno Steffen wrote:
>> In one of my devices, uboot-environment is located at a bad block.
>> "save
>> Saving Environment to NAND...
>> Erasing Nand...
>> Skipping bad block at  0x000c0000
>>
>> Writing to Nand... FAILED!"
>>
>> In my memory mapping I have already reseverd 2blocks.
>> How can I setup uboot in a way, that it will look at c0000 or (in case
>> of bad block) at the next block e0000?

Use CONFIG_ENV_RANGE.

-Scott