public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ubi part failing on NAND
Date: Mon, 21 Dec 2009 11:02:40 +0100	[thread overview]
Message-ID: <200912211102.40869.sr@denx.de> (raw)
In-Reply-To: <4B2B9ABC.2000701@theptrgroup.com>

On Friday 18 December 2009 16:07:40 Jeff Angielski wrote:
> Stefan Roese wrote:
> > On Friday 18 December 2009 13:35:26 hedwin wrote:
> >> Jeff, what is the size of your allocateble memory. Had to increase it to
> >>  4MB to get it working.
> >
> > I've got 1MByte for my test on Kilauea. This should be enough. There
> > is already a compile-time check in the UBI code:
> >
> >
> > #if (CONFIG_SYS_MALLOC_LEN < (512 << 10))
> > #error Malloc area too small for UBI, increase CONFIG_SYS_MALLOC_LEN to
> > >= 512k #endif
> >
> > Please let me know if this really is not enough. But for me, 1MB is
> > working.
> 
> As per Hedwin's suggestion I increased my CONFIG_SYS_MALLOC_LEN to 4MB
> and the error disappeared.  Thanks Hedwin!  And now the UBI output
> matches my part (e.g. PEB size).

Hmmm. Must be because my test platform used a small page NAND device. I'll 
give it a try on a large page NAND soon. The code must be lacking a check for 
malloc failure.

Cheers,
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

  parent reply	other threads:[~2009-12-21 10:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 21:09 [U-Boot] ubi part failing on NAND Jeff Angielski
2009-12-18  8:16 ` Stefan Roese
2009-12-18 12:35   ` hedwin
2009-12-18 12:41     ` Stefan Roese
2009-12-18 15:07       ` Jeff Angielski
2009-12-19 12:56         ` hedwin
2009-12-21 10:02         ` Stefan Roese [this message]
2009-12-18 14:47     ` Jeff Angielski

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=200912211102.40869.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