From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] The command of nand write cannot write zImage to nandflash
Date: Thu, 24 May 2007 12:43:38 +0200 [thread overview]
Message-ID: <200705241243.38321.sr@denx.de> (raw)
In-Reply-To: <2858522.2167441179932150829.JavaMail.coremail@bj163app61.163.com>
On Wednesday 23 May 2007, zj_31529 wrote:
> Hi all: I patch NAND (including boot-from-NAND via steppingstone)
> support to the S3C2410 SoC code in
> u-boot(http://svn.openmoko.org/trunk/src/target/u-boot/patches/uboot-s3c241
>0-nand.patch). The u-boot-1.1.6 print the nandflash info to DNW,and the
> command of "tftp 0x31000000 zImage" is ok,but the command of "nand
> write.jffs2 0x31000000 0x2030000 0xc0000 "cannot write the zImage of Linux
> 2.4 to the nandflash and the u-boot print "Bad block check failed". When I
> excuted the command of "nand write 0x31000000 0x2030000 0xc0000",the u-boot
> print "0 bytes writed". Can you give me a hand. Thank you very much!
What U-Boot version are you using? 1.1.6? If yes, could you please give the
current top-of-git version a try. There was a patch a few months ago, that
fixed a problem where NAND writing aborted, when bad blocks were detected. So
please give the current version a try and let me know if it helped.
I hope the patch mentioned above does apply without too much problems.
Best regards,
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
=====================================================================
prev parent reply other threads:[~2007-05-24 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 14:55 [U-Boot-Users] The command of nand write cannot write zImage to nandflash zj_31529
2007-05-24 10:43 ` Stefan Roese [this message]
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=200705241243.38321.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