mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: R Arun Kumar <paiarunk@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Regarding nandwrite issue for huge files ?
Date: Fri, 12 Feb 2010 08:30:13 +0100	[thread overview]
Message-ID: <20100212073013.GR17643@pengutronix.de> (raw)
In-Reply-To: <faef843a1002112302u6b80cb57we22db316d94e792e@mail.gmail.com>

Hi Arun,

On Fri, Feb 12, 2010 at 12:32:19PM +0530, R Arun Kumar wrote:
> Hai,
> 
> I am able to successfully port the barebox for my custom IMX31 board and
> also boot linux on the same.
> I am trying to write the uImage and the root.jffs2 file from barebox and
> found that even though uImage is written successfully and able to boot from
> nand flash also. The nand file write for files more than 3.5 mega size is
> not able to write and the barebox loader is hanged.
> 
> Please help or suggest what could be the issue ?

I don't know what is going wrong here. I often use this driver with
files > 3.5Mb, works for me. Can you add a #define DEBUG in
drivers/nand/nand.c and see if it's always the same location that fails?
You could also make your kernel partition a bit bigger so that the
rootfs starts at another place and see if it's still the same location
that fails.
Have you tried lowering the Nand clock?

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2010-02-12  7:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12  7:02 R Arun Kumar
2010-02-12  7:30 ` Sascha Hauer [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=20100212073013.GR17643@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=paiarunk@gmail.com \
    /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