All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Pan <pppeterpppan@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] The command "nand write.yaffs" is not working correctly
Date: Fri, 30 Sep 2011 23:35:31 +0800	[thread overview]
Message-ID: <CAGQXtZHrk_eNM1EKTy5zdALw6V4Pz-38d2i_hU6wy=t9atEU8w@mail.gmail.com> (raw)
In-Reply-To: <BE72CBA69B1D6F44B0680DF984332A32291DCC@039-SN1MPN1-005.039d.mgd.msft.net>

Thank you, Zhengxiong.

The patch seems reasonable. My nand flash has no bad block currently. That
need_skip will skip the oob write part.

I will check that after the golden holiday.
? 2011-9-30 ??5:10?"Jin Zhengxiong-R64188" <R64188@freescale.com>???
>> -----Original Message-----
>> From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de]
On
>> Behalf Of Peter Pan
>> Sent: Wednesday, September 21, 2011 9:09 AM
>> To: u-boot at lists.denx.de
>> Subject: [U-Boot] The command "nand write.yaffs" is not working correctly
>>
>> I'm recently facing a yaffs2 image write problem in u-boot.
>>
>> In u-boot console, I write the yaffs2 image in ram to an already erased
nand
>> flash with command "nand write.yaffs ${loadaddr} ${nandrootoffset}
${filesize}".
>> After that, if I boot using a ramdisk and mount that yaffs2 partition, I
can
>> only see a folder of "lost+fount". I seems nothing has been written into
that
>> partition.
>>
>> But if now I write this image using "nandwrite -a -o /dev/mtd4
yaffs2.img" and
>> mount that partition, it's working.
>>
>> Anyone met that problem already? Or if I did anything wrong?
>
> [Jin Zhengxiong-R64188]
> I once met the similar issue with 2011.03 base and fixed it with following
patch, But
> I didn't do a detail checking for that, FYI...
>
> @@ -499,6 +499,7 @@ int nand_write_skip_bad(nand_info_t *nand, loff_t
offset, size_t *length,
> return -EINVAL;
> }
>
> +#ifndef CONFIG_CMD_NAND_YAFFS
> if (!need_skip) {
> rval = nand_write (nand, offset, length, buffer);
> if (rval == 0)
> @@ -509,13 +510,12 @@ int nand_write_skip_bad(nand_info_t *nand, loff_t
offset, size_t *length,
> offset, rval);
> return rval;
> }
> -
> +#endif
> while (left_to_write > 0) {
> size_t block_offset = offset & (nand->erasesize - 1);
> size_t write_size;
>
> WATCHDOG_RESET ();
> -
> if (nand_block_isbad (nand, offset & ~(nand->erasesize - 1))) {
> printf ("Skip bad block 0x%08llx\n",
> offset & ~(nand->erasesize - 1));
> @@ -546,7 +546,7 @@ int nand_write_skip_bad(nand_info_t *nand, loff_t
offset, size_t *length,
> ops.oobbuf = ops.datbuf + pagesize;
>
> rval = nand->write_oob(nand, offset, &ops);
> - if (!rval)
> + if ( rval != 0)
> break;
>
> offset += pagesize;
>
>

  reply	other threads:[~2011-09-30 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21  1:09 [U-Boot] The command "nand write.yaffs" is not working correctly Peter Pan
2011-09-30  9:10 ` Jin Zhengxiong-R64188
2011-09-30 15:35   ` Peter Pan [this message]
2011-10-03 20:43   ` Scott Wood

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='CAGQXtZHrk_eNM1EKTy5zdALw6V4Pz-38d2i_hU6wy=t9atEU8w@mail.gmail.com' \
    --to=pppeterpppan@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.