From: 郭劲 <guojin02@tsinghua.org.cn>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Why the flash always say "flash not erased" in u-boot?
Date: Sun, 18 May 2008 05:43:15 +0800 [thread overview]
Message-ID: <411060595.08932@tsinghua.org.cn> (raw)
Hi,friends,
I made two boards of MPC8360E with u-boot-1.3.0, the hardware on the board is the
same and the version of u-boot is also the same. One of the board is OK for erase
and cp.b command in u-boot,I can tftp the uImage,ramdisk,dtb,cfg.jffs2 to DDR,
then I used the cp.b command to write those file to flash, before the cp.b
command, I used the erase command to erase the flash first. But the second board
always told me"copy to flash ... flash not erased" when I used the cp.b command. I
used the "protect off all" command, I am sure that the erase command before cp.b
command is no problem.
Even the cp.b command not work, the setenv command is always no problem, the new
parameter built by setenv can write to flash by saveenv. The USBTAP also can write
the file to flash. Why just only cp.b command not work? How can I make the flash
does not say "flash not erased"?
Thanks.
reply other threads:[~2008-05-17 21:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=411060595.08932@tsinghua.org.cn \
--to=guojin02@tsinghua.org.cn \
--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