Boot problem Mini6410 with image by Pengutronix BSP

Hi guys, 
I have a Mini6410 with 7" touchscreen.
I got my rootfs by ptxdist (last version OSELAS.BSP-Pengutronix-Mini6410
from git). 
At the end of the procedure in the images directory I have the files:
u-boot, linuximage and root.jffs2.
I created the SD Card boot following the procedure by FriendlyARM using the
3 files got in this way.
I edited the file FriendlyARM.ini:

CheckOneButton=No

Action=install

OS= linux



VerifyNandWrite=No



StatusType = Beeper| LED



#################### Linux #####################

#Linux-BootLoader = Linux/u-boot_nand-ram256.bin

Linux-BootLoader = Linux/u-boot.bin

Linux-Kernel = Linux/linuximage

Linux-CommandLine = root=/dev/mtdblock2 rootfstype=jffs2 init=/sbin/init
console=ttySAC0,115200

Linux-RootFs-InstallImage = Linux/root.jffs2

#Linux-RootFs-RunImage = Linux/root.ext2


I powered the Mini6410, the kernel is loaded correctly, but when it starts
loading the rootfs, the system fails.

Download bootloader...
Download bootloader succeed
Download kernel...
Download kernel succeed
Download yaffs-image ...
Download yaffs-image failed

Why this happens, in Linux-CommandLine I edited rootfstype=jffs2.
I tried to setup yaffs rootfs in platformconfig of ptxdist, but it's not
possible.
Could someone help me?

I managed to create the rootfs yaffs2 mkyaffs2image through the tool-128M.
Now both the kernel and the rootfs are loaded into Flash.
Unfortunately when I boot the system from NAND it gives me this error:

Creating 3 MTD partitions on "nand":
0x000000000000-0x000000100000 : "uboot"
0x000000100000-0x000000300000 : "kernel"
0x000000300000-0x000040000000 : "rootfs"
dm9000 Ethernet Driver, V1.31
eth0: dm9000a at d085c000,d085e004 IRQ 108 MAC: 08:90:90:90:90:90 (chip)
input: gpio-keys as /devices/platform/gpio-keys/input/input0
samsung-ts s3c64xx-ts: driver attached, registering input device
input: S3C24XX TouchScreen as /devices/virtual/input/input1
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c-rtc s3c64xx-rtc: rtc disabled, re-enabling
s3c-rtc s3c64xx-rtc: rtc core: registered s3c as rtc0
TCP cubic registered
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
s3c-rtc s3c64xx-rtc: setting system clock to 2011-10-29 02:13:35 UTC
(1319854415)
VFS: Cannot open root device "mtdblock2" or unknown-block(31,2)



Please append a correct "root=" boot option; here are the available
partitions:
1f00            1024 mtdblock0  (driver?)
1f01            2048 mtdblock1  (driver?)
1f02         1045504 mtdblock2  (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(31,2)


[<c002ae38>] (unwind_backtrace+0x0/0xe4) from [<c021fc4c>]
(panic+0x68/0x180)
[<c021fc4c>] (panic+0x68/0x180) from [<c0008cdc>]
(mount_block_root+0x1b8/0x1f8)
[<c0008cdc>] (mount_block_root+0x1b8/0x1f8) from [<c0008dbc>]
(mount_root+0xa0/0xc0)
[<c0008dbc>] (mount_root+0xa0/0xc0) from [<c0008ef8>]
(prepare_namespace+0x11c/0x17c)
[<c0008ef8>] (prepare_namespace+0x11c/0x17c) from [<c0008944>]
(kernel_init+0xe4/0x118)
[<c0008944>] (kernel_init+0xe4/0x118) from [<c0026594>]
(kernel_thread_exit+0x0/0x8)

What's the problem?

my Linux-CommandLine = root=/dev/mtdblock2 rootfstype=yaffs2 init=/linuxrc
console=ttySAC0,115200

If you are using the kernel from my BSP, there is still no support for the
NAND in it. That's why it *must* fail. Development for the Mini6410 happens
slowly on my side...

Thanks Jurgen,
does the kernel from your BSP support SDCARD ?
If yes, what's the Linux-CommandLine I do in ini file?
Or can you explain me what's the procedure to boot the system when I obtain
u-boot, linuximage and root.tgz?

Thanks in advance.

Same problem. Not SD, nor USB, nor NAND. Helpers are welcome to add these
features.