Unable to mount root fs: s3c2410 based board, Nand flash

Hi My name is Swapnil,
I'm trying to load linux 2.6.24.1 to Samsung s3c2410 based board.

The board has 32MB of RAM, and 32MB of samsung NAND flash.
It has vivi bootloader and is able to boot the cross compiled kernel
(zImage). I have a cramfs. pls advice how to mount it.
I have enabled support for cramfs in the kernel configuration.

Kernel = linux-2.6.24.1 (no patches added)
cross compiler = gcc-4.0.3 (arm)

The following is the kernel debug message on serial port.

/**********************************************************************/

VIVI version 0.1.4 (sonu@sonu-desktop) (gcc version 2.95.3 20010315 (release)) #0.1.4 Mon Feb 25 12:53:08 HKT 2008

Modified by sonu PTID ver3
MMU table base address = 0x31DFC000
Succeed memory mapping.
NAND device: Manufacture ID: 0xec, Chip ID: 0x75 (Samsung KM29U256T)
Found saved vivi parameters.
Press Return to start the LINUX now, any other key for vivi
Copy linux kernel from 0x00030000 to 0x30008000, size = 0x00200000 ... done
zImage magic = 0x016f2818
Setup linux parameters at 0x30000100
linux command line is: "console=ttySAC2 root=/dev/mtdblock3"
MACH_TYPE = 193
NOW, Booting Linux......
Uncompressing Linux.................................................................... done, booting the kernel.
Linux version 2.6.24.1 (sonu@sonu-desktop) (gcc version 4.0.3) #12 Mon Feb 25 17:37:08 HKT 2008
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
Machine: SMDK2410
ATAG_INITRD is deprecated; please update your bootloader.
Memory policy: ECC disabled, Data cache writeback
CPU S3C2410A (id 0x32410002)
S3C2410: core 200.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz
S3C24XX Clocks, (c) 2004 Simtec Electronics
CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
Kernel command line: console=ttySAC2 root=/dev/mtdblock3
irq: clearing subpending status 000000c0
irq: clearing subpending status 00000080
PID hash table entries: 128 (order: 7, 512 bytes)
timer tcon=00000000, tcnt a2c1, tcfg 00000200,00000000, usec 00001eb8
Console: colour dummy device 80x30
console [ttySAC2] enabled
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 30296KB available (1848K code, 198K data, 100K init)
SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 64 bytes
NET: Registered protocol family 16
S3C2410: Initialising architecture
S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics
DMA channel 0 at c2800000, irq 33
DMA channel 1 at c2800040, irq 34
DMA channel 2 at c2800080, irq 35
DMA channel 3 at c28000c0, irq 36
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Console: switching to colour frame buffer device 80x25
fb0: Virtual frame buffer device, using 1024K of video memory
s3c2410-uart.0: s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2410
s3c2410-uart.1: s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2410
s3c2410-uart.2: s3c2410_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2410
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
s3c2410-nand s3c2410-nand: Tacls=4, 40ns Twrph0=7 70ns, Twrph1=7 70ns
NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 8-bit)
Scanning device for bad blocks
Creating 5 MTD partitions on "NAND 32MiB 3,3V 8-bit":
0x00000000-0x00020000 : "vivi"
0x00020000-0x00030000 : "param"
0x00030000-0x00230000 : "kernel"
0x00230000-0x00630000 : "root cramfs"
0x00630000-0x02000000 : "filesystem"
mice: PS/2 mouse device common for all mice
TCP cubic registered
NET: Registered protocol family 1
VFS: Cannot open root device "mtdblock3" or unknown-block(31,3)
Please append a correct "root=" boot option; here are the available partitions:
1f00 128 mtdblock0 (driver?)
1f01 64 mtdblock1 (driver?)
1f02 2048 mtdblock2 (driver?)
1f03 4096 mtdblock3 (driver?)
1f04 26432 mtdblock4 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3)
/***********************************************************************/

Can any one pls tell how is the cramfs generated / mounted.

I haven't gotten that far yet, I'm still figuring out the bootloader bits! So far I only have the Samsung 2410loader and I think I just figured out how that works (going to try tomorrow, too tired tonight).

I keep hearing about Mizi linux and vivi bootloader and there are lots of links to the Mizi site saying grab this and grab that, but they have passworded FTP access as far as I can tell. Do you need an account to download or is it a general public thing and I'm just not seeing the 'Use xxx and yyyy' to login?

Originally Posted by PatM I keep hearing about Mizi linux and vivi bootloader and there are lots of links to the Mizi site saying grab this and grab that, but they have passworded FTP access as far as I can tell. Do you need an account to download or is it a general public thing and I'm just not seeing the 'Use xxx and yyyy' to login?

I emailed Mizi and got no response but the other day I was googling and followed a link that took me to the mizi ftp server and it didn't ask for a loging. Curious, I went back and followed the same links as before (from the Mizi Linux Online Manual) and it no longer asks for a login. I can only assume that the login requirement was an oops and its been fixed.

I did get and compile vivi (took some messing around since it uses yet another cross-compiler which I didn't have yet - think I have 4 now!). Turns out I can't use it because of my setup. I have 1MB Nor flash which is used for booting and 64MB nand flash for the rest. Vivi (appears) to work with either NOR or NAND, not both. If I compiler for a nor boot, the nand isn't recognized and visa-versa.

Thats ok though since I finally learned enough about Linux/Arm/C that I got a working u-Boot config for my s3c2410 machine. Turned out that u-Boot has advanced but the s3c2410 config files have not (no s3c2410 maintainer) and all it needs is updating of the include/configs/<board>.h to get it running.

Hi

We are using SMDK2450 development board. We are trying to mount rootfs through NAND Flash and we are facing a similar issue like
1f02 4096 mtdblock2 (driver?).

Can you please let us know how you resolved this issue? Could you mount rootfs from NAND flash in your system?

hello there,
has anyone of you managed to compile some version of U-boot for the s3c2410 processor, for the sbc2410x board?????

please respond please respond!