A litrtle bit more info. I turned on the debug statements in u-boot and when
I do an ls of the jffs2 file system, I see this:
*=> ls
---mtdparts_init---
dev id: type = 1, num = 0, size = 0x0100, mtd_id = single part
part : name = static, size = 0x0100, offset = 0x
--- jffs2_part
I believe the command line to the kernel is indeed not quite complete, but
here it is at this point:
*bootargs root=mtd:nor0 rw rootfstype=jffs2
mtdparts=nor0:3072k(u-boot),-(jffs2) console=ttyS0,115200*
With this command line, the kernel printk's just before it panics are:
*MTDSB: dev_name "mtd:
Dear Charles Krinke,
In message you
wrote:
>
> I have *CONFIG_CMD_JFFS2* defined, but not *CONFIG_CMD_MTDPARTS* as they
> seem to be mutually exclusive.
They are not. There are 64 boards in mainline which define both.
> thinking this would define sufficiently mtdparts for the Linux kernel to
I have a project with the Freescape MPC8323ERDB board and am having a little
trouble booting the jffs2 image and I suspect it is either a u-boot
environment string, a u-boot CONFIG* setting or a Linux CONFIG* setting.
At this point, I can build a rootfs.jffs2, include uImage into the
rootfs.jffs2
4 matches
Mail list logo