From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Roese <sr@denx.de>
Date: Wed, 30 Sep 2009 14:19:08 +0200
Subject: [U-Boot] Flash sanity checks
In-Reply-To: <200909301158.22708.dk-arm-linux@gmx.de>
References: <73173D32E9439E4ABB5151606C3E19E202EF7E9826@SC-VEXCH1.marvell.com>
	<200909301158.22708.dk-arm-linux@gmx.de>
Message-ID: <200909301419.09036.sr@denx.de>
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 Wednesday 30 September 2009 11:58:22 Dieter Kiermaier wrote:
> > We use Raw NAND/flash and copy the binary there,
> > After copy,
> > is there a way to check the flash sanity after we have burnt an image?
> > (e.g. by nand reading and diffing with the binary in RAM?)
> >
> > Are there any feature/utility/commands readily available for u-boot?
> 
> I've done it in the past by reading it back to ram and use cmp command.
> Maybe it is usefull for you, too?

Sure, this can be done. But the NAND driver core supports validation of 
written data using this configuration option:

CONFIG_MTD_NAND_VERIFY_WRITE

I would enable it only for test purposes though.

Cheers,
Stefan

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de