From: zj_31529 <zj_31529@163.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] The command of nand write cannot write zImage to nandflash
Date: Wed, 23 May 2007 22:55:50 +0800 (CST) [thread overview]
Message-ID: <2858522.2167441179932150829.JavaMail.coremail@bj163app61.163.com> (raw)
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-s3c2410-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!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20070523/96da11da/attachment.htm
next reply other threads:[~2007-05-23 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 14:55 zj_31529 [this message]
2007-05-24 10:43 ` [U-Boot-Users] The command of nand write cannot write zImage to nandflash Stefan Roese
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=2858522.2167441179932150829.JavaMail.coremail@bj163app61.163.com \
--to=zj_31529@163.com \
--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