On Wednesday 03 June 2009 20:05:51 Daniel Mack wrote:
I know there has been some traffic regaring the UBI layer recently,
however, reading the conversations didn't solve the issue I'm facing.
With a current U-Boot (git as of today) and 128MB NAND flash on a
PXA303, I get the following:
$
On Thu, Jun 04, 2009 at 08:42:40AM +0200, Stefan Roese wrote:
defaults:
mtdids : nand0=nand0
mtdparts:
mtdparts=nand0:512k(u-boot),128k(env),384k(splash),3M(kernel),-(ubilayer) $
ubi part ubilayer
Creating 1 MTD partitions on nand0:
0x0040-0x0800 : mtd=4
UBI: attaching
On Thursday 04 June 2009 08:50:21 Daniel Mack wrote:
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -12
UBI init error -12
exit not allowed from main input shell.
Did you erase the FLASH partition? If not please try again after
On Thursday 04 June 2009 10:06:55 Daniel Mack wrote:
I have to admit that I never used it this way. Using ubi part on an
erased partition works fine. I suggest you give it a try.
Hmm. That still doesn't work for me, and I still wonder about the
'attaching mtd1 to ubi0' string, which looks
On Thu, Jun 04, 2009 at 10:15:30AM +0200, Stefan Roese wrote:
Hmm. That still doesn't work for me, and I still wonder about the
'attaching mtd1 to ubi0' string, which looks like a mismatch to me.
I would have to check in more details here. But I'm pretty sure this is not
the reason for
On Thursday 04 June 2009 11:07:40 Daniel Mack wrote:
On Thu, Jun 04, 2009 at 10:15:30AM +0200, Stefan Roese wrote:
Hmm. That still doesn't work for me, and I still wonder about the
'attaching mtd1 to ubi0' string, which looks like a mismatch to me.
I would have to check in more details
Dear Daniel Mack,
In message 20090604090740.gd26...@buzzloop.caiaq.de you wrote:
Oh well - you're right. The code failed in vmalloc() due to a too small
CONFIG_SYS_MALLOC_LEN which I needed to augment to 512kB.
But then a big, fat error message is needed there!
Best regards,
Wolfgang Denk
On Thu, Jun 04, 2009 at 11:27:07AM +0200, Wolfgang Denk wrote:
Oh well - you're right. The code failed in vmalloc() due to a too small
CONFIG_SYS_MALLOC_LEN which I needed to augment to 512kB.
But then a big, fat error message is needed there!
In vmalloc(), yes. That bug could hit any
I know there has been some traffic regaring the UBI layer recently,
however, reading the conversations didn't solve the issue I'm facing.
With a current U-Boot (git as of today) and 128MB NAND flash on a
PXA303, I get the following:
$ mtdparts
device nand0 nand0, # parts = 5
#: name
9 matches
Mail list logo
