[U-Boot-Users] CFI driver does not verify writes in buffered mode - feature?

public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed

From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CFI driver does not verify writes in buffered mode - feature?
Date: Wed, 09 May 2007 18:32:22 +0200	[thread overview]
Message-ID: <m27iriarft.fsf@sowhat.denx.de> (raw)

Hi,

when using the CFI flash driver with CFG_FLASH_USE_BUFFER_WRITE the
"usual" verification whether the write did indeed happen correctly is
not done:

  => erase fc000000 +1
  
  . done
  Erased 1 sectors
  => mw 200000 55555555 100
  => cp.b 200000 fc000000 100
  Copy to Flash... done
  => md fc000000
  fc000000: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000010: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000020: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000030: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000040: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000050: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000060: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000070: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000080: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000090: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc0000a0: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc0000b0: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc0000c0: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc0000d0: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc0000e0: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc0000f0: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  => mw 200000 ffffffff 100
  => cp.b 200000 fc000000 100
  Copy to Flash... done
  => md fc000000
  fc000000: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000010: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000020: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000030: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000040: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000050: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000060: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000070: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000080: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc000090: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc0000a0: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc0000b0: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc0000c0: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc0000d0: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc0000e0: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  fc0000f0: 55555555 55555555 55555555 55555555    UUUUUUUUUUUUUUUU
  

So the write did indeed *not proceed* correctly without the expected
"flash not erased" error message appearing.

The behaviour is not consistent, so either we should do verification
of the write or we should have some kind of warning here.  Does anyone
see an easy way to become consistent here?

Thanks
  Detlev

-- 
Emacs seems a more likely candidate  to contain a mail system than the
mail system to contain an Emacs, so this is the way it was done.
                                            -- Bernard S. Greenberg
--
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office: Kirchenstr. 5, D-82194 Groebenzell, Germany +49 8142 66989 40

next             reply	other threads:[~2007-05-09 16:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09 16:32 Detlev Zundel [this message]
2007-05-09 20:25 ` [U-Boot-Users] CFI driver does not verify writes in buffered mode - feature? Tolunay Orkun
2007-05-09 22:33   ` Wolfgang Denk
2007-05-10  3:40     ` Tolunay Orkun
2007-05-10  6:53       ` Detlev Zundel
2007-05-14  3:05         ` Tolunay Orkun

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=m27iriarft.fsf@sowhat.denx.de \
    --to=dzu@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