Kernel panic on custom board

Hey GreatWhite... there are a couple things to watch out for when using flash on a custom board. The first item is the memory map and I think you're on the right track for that. There's nothing wrong with modifying one of the original memory maps to suit your need.

part one

You probably need something closer to:

#else
{
 .name =  "romfs/jffs2",
 .size =  0x100000,
 .offset = 0x200000,
},{
 .name =  "loader/kernel",
 .size =  0x200000,
 .offset = 0x0,
}, {
 .name =  "User configuration",
 .size =  0x80000,
 .offset = 0x300000,
}, {
 .name =  "safe configuration",
 .size =  0x80000,
 .offset = 0x380000,
 .mask_flags = MTD_WRITEABLE,  /* force read-only */
}# endif

I've made the portion of flash that holds the kernel to be 2MB and I've setup the ROMFS section to use up all remaining space between the kernel and the user configuration.

Now, smcnutt was telling you to change the root commandline argument in your "Default kernel command string" from:

root=/romfs/jffs2

to

root=/dev/mtdblock0

mtdblock0 corresponds to the first entry in your memory map. That's the easy part...

part two

From the kernel startup messages, it looks like the flash chip you're using may not be supported by the default distribution. Currently, we support a couple of different AMD flash chips. It's quite possible that the chip you're using isn't support right now.

Until the chip is supported, I don't know if you can mount a romdisk on your flash. Why don't you pass me the name of your flash and I'll see what I can do to help.