From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Flash sanity checks
Date: Wed, 30 Sep 2009 14:19:08 +0200 [thread overview]
Message-ID: <200909301419.09036.sr@denx.de> (raw)
In-Reply-To: <200909301158.22708.dk-arm-linux@gmx.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
next prev parent reply other threads:[~2009-09-30 12:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 13:55 [U-Boot] kirkwood (openrd): saveenv will not work with environment in NAND Dieter Kiermaier
2009-09-29 15:16 ` Dieter Kiermaier
2009-09-30 6:21 ` Simon Kagstrom
2009-09-30 7:02 ` Dieter Kiermaier
2009-09-30 7:08 ` Simon Kagstrom
2009-09-30 7:40 ` Dieter Kiermaier
2009-09-30 7:57 ` Simon Kagstrom
2009-09-30 8:15 ` Dieter Kiermaier
2009-09-30 8:17 ` Simon Kagstrom
2009-09-30 8:25 ` Dieter Kiermaier
2009-09-30 9:28 ` [U-Boot] Flash sanity checks Prafulla Wadaskar
2009-09-30 9:58 ` Dieter Kiermaier
2009-09-30 12:19 ` Stefan Roese [this message]
2009-10-06 17:16 ` [U-Boot] kirkwood (openrd): saveenv will not work with environment in NAND Prafulla Wadaskar
2009-09-30 20:32 ` Wolfgang Denk
2009-10-01 7:29 ` [U-Boot] [PATCH] Make arm926ejs use -mabi=apcs-gnu to avoid EABI problems Simon Kagstrom
2009-10-01 9:56 ` Prafulla Wadaskar
2009-10-01 18:27 ` Wolfgang Denk
2009-10-02 14:44 ` Simon Kagstrom
2009-10-05 13:23 ` [U-Boot] [PATCH] arm926ejs: 16-byte align stack to avoid LDRD/STRD problems Simon Kagstrom
2009-10-05 14:30 ` Andrew Dyer
2009-10-05 14:35 ` Stefan Roese
2009-10-05 14:53 ` [U-Boot] [PATCH v2] " Simon Kagstrom
2009-10-05 15:44 ` Dieter Kiermaier
2009-10-05 18:37 ` Tom
2009-10-06 7:07 ` Simon Kagstrom
2009-10-05 22:07 ` Måns Rullgård
2009-10-06 4:13 ` Prafulla Wadaskar
2009-10-06 6:44 ` [U-Boot] [PATCH v3] arm926ejs: 8-byte " Simon Kagstrom
2009-10-06 16:50 ` Tom
2009-10-18 2:15 ` Tom
2009-10-05 14:40 ` [U-Boot] [PATCH] arm926ejs: 16-byte " Simon Kagstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200909301419.09036.sr@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox