当前位置: 技术问答>linux和unix
开发板烧写遇到问题,烦请高手指点
来源: 互联网 发布时间:2016-06-25
本文导语: 开发板启动不起来了,前期烧写了vivi,kernel和root,再重新起动,结果出现下面的信息,烦请高手指点下: VIVI version 0.1.4 (root@linux9) (gcc version 2.95.2 20000516 (release) [Rebel.4MMU table base address = 0x33DFC000 Succeed memory mapping....
开发板启动不起来了,前期烧写了vivi,kernel和root,再重新起动,结果出现下面的信息,烦请高手指点下:
VIVI version 0.1.4 (root@linux9) (gcc version 2.95.2 20000516 (release) [Rebel.4MMU table base address = 0x33DFC000
Succeed memory mapping.
NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung K9D1208V0M)
Could not found stored vivi parameters. Use default vivi parameters.
Press Return to start the LINUX now, any other key for vivi
Copy linux kernel from 0x00030000 to 0x30008000, size = 0x000c0000 ... done
zImage magic = 0x016f2818
Setup linux parameters at 0x30000100
linux command line is: 'noinitrd root=/dev/bon/2 init=/linuxrc console=ttyS0'
MACH_TYPE = 193
NOW, Booting Linux......
Uncompressing Linux................................................ done, booti.Linux version 2.4.18-rmk7-pxa1 (root@linux9) (gcc version 2.95.2 20000516 (rele4CPU: ARM/CIRRUS Arm920Tsid(wb) revision 0
Machine: Samsung-SMDK2410
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: noinitrd root=/dev/bon/2 init=/linuxrc console=ttyS0
DEBUG: timer count 15626
Console: colour dummy device 80x30
Calibrating delay loop... 99.94 BogoMIPS
Memory: 64MB = 64MB total
Memory: 62852KB available (1239K code, 300K data, 72K init)
Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode-cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
CPU clock = 200.000 Mhz, HCLK = 100.000 Mhz, PCLK = 50.000 Mhz
Starting kswapd
devfs: v1.10 (20020120) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
ttyS%d0 at I/O 0x50000000 (irq = 52) is a S3C2410
ttyS%d1 at I/O 0x50004000 (irq = 55) is a S3C2410
ttyS%d2 at I/O 0x50008000 (irq = 58) is a S3C2410
LCDcon1 = 0x00000779
LCDcon2 = 0x044fc041
LCDcon3 = 0x0030ef1e
LCDcon4 = 0x00000d03
LCDcon5 = 0x00016809
LCDaddr1 = 0x181e0800
LCDaddr2 = 0x001f3400
LCDaddr3 = 0x000000f0
LCDcon1 = 0x00000779
LCDcon2 = 0x044fc041
LCDcon3 = 0x0030ef1e
LCDcon4 = 0x00000d03
LCDcon5 = 0x00014809
LCDaddr1 = 0x181e0800
LCDaddr2 = 0x001f3400
LCDaddr3 = 0x000000f0
Console: switching to colour frame buffer device 30x40
Installed S3C2410 frame buffer
pty: 256 Unix98 ptys configured
s3c2410-ts initialized
S3C2410 Real Time Clock Driver v0.1
S3C2410 GPIO buttons: eint19(special) eint6(special) eint7(special) eint5(speci
block: 128 slots per queue, batch=32
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
eth0 network interface found iobase=c4840300
00:13:F6:6C:87:89:
00:13:F6:6C:87:89:
NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung K9D1208V0M)
bon0: 00000000-00000000 (00000000) 00000000
bon1: 00000000-00030000 (00030000) 00000000
bon2: 00030000-00100000 (000d0000) 00000000
bon3: 00100000-03ffc000 (03efc000) 00000000
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NetWinder Floating Point Emulator V0.95 (c) 1998-1999 Rebel.com
bon: ecc error, page = 0x00000180
end_request: I/O error, dev 61:02 (bon), sector 0
bon: ecc error, page = 0x00000188
end_request: I/O error, dev 61:02 (bon), sector 8
bon: ecc error, page = 0x00000190
end_request: I/O error, dev 61:02 (bon), sector 16
bon: ecc error, page = 0x00000198
end_request: I/O error, dev 61:02 (bon), sector 24
cramfs: wrong magic
bon: ecc error, page = 0x00000180
end_request: I/O error, dev 61:02 (bon), sector 0
FAT: unable to read boot sector
bon: ecc error, page = 0x00000180
end_request: I/O error, dev 61:02 (bon), sector 0
FAT: unable to read boot sector
Kernel panic: VFS: Unable to mount root fs on 61:02
VIVI version 0.1.4 (root@linux9) (gcc version 2.95.2 20000516 (release) [Rebel.4MMU table base address = 0x33DFC000
Succeed memory mapping.
NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung K9D1208V0M)
Could not found stored vivi parameters. Use default vivi parameters.
Press Return to start the LINUX now, any other key for vivi
Copy linux kernel from 0x00030000 to 0x30008000, size = 0x000c0000 ... done
zImage magic = 0x016f2818
Setup linux parameters at 0x30000100
linux command line is: 'noinitrd root=/dev/bon/2 init=/linuxrc console=ttyS0'
MACH_TYPE = 193
NOW, Booting Linux......
Uncompressing Linux................................................ done, booti.Linux version 2.4.18-rmk7-pxa1 (root@linux9) (gcc version 2.95.2 20000516 (rele4CPU: ARM/CIRRUS Arm920Tsid(wb) revision 0
Machine: Samsung-SMDK2410
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: noinitrd root=/dev/bon/2 init=/linuxrc console=ttyS0
DEBUG: timer count 15626
Console: colour dummy device 80x30
Calibrating delay loop... 99.94 BogoMIPS
Memory: 64MB = 64MB total
Memory: 62852KB available (1239K code, 300K data, 72K init)
Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode-cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
CPU clock = 200.000 Mhz, HCLK = 100.000 Mhz, PCLK = 50.000 Mhz
Starting kswapd
devfs: v1.10 (20020120) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
ttyS%d0 at I/O 0x50000000 (irq = 52) is a S3C2410
ttyS%d1 at I/O 0x50004000 (irq = 55) is a S3C2410
ttyS%d2 at I/O 0x50008000 (irq = 58) is a S3C2410
LCDcon1 = 0x00000779
LCDcon2 = 0x044fc041
LCDcon3 = 0x0030ef1e
LCDcon4 = 0x00000d03
LCDcon5 = 0x00016809
LCDaddr1 = 0x181e0800
LCDaddr2 = 0x001f3400
LCDaddr3 = 0x000000f0
LCDcon1 = 0x00000779
LCDcon2 = 0x044fc041
LCDcon3 = 0x0030ef1e
LCDcon4 = 0x00000d03
LCDcon5 = 0x00014809
LCDaddr1 = 0x181e0800
LCDaddr2 = 0x001f3400
LCDaddr3 = 0x000000f0
Console: switching to colour frame buffer device 30x40
Installed S3C2410 frame buffer
pty: 256 Unix98 ptys configured
s3c2410-ts initialized
S3C2410 Real Time Clock Driver v0.1
S3C2410 GPIO buttons: eint19(special) eint6(special) eint7(special) eint5(speci
block: 128 slots per queue, batch=32
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
eth0 network interface found iobase=c4840300
00:13:F6:6C:87:89:
00:13:F6:6C:87:89:
NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung K9D1208V0M)
bon0: 00000000-00000000 (00000000) 00000000
bon1: 00000000-00030000 (00030000) 00000000
bon2: 00030000-00100000 (000d0000) 00000000
bon3: 00100000-03ffc000 (03efc000) 00000000
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NetWinder Floating Point Emulator V0.95 (c) 1998-1999 Rebel.com
bon: ecc error, page = 0x00000180
end_request: I/O error, dev 61:02 (bon), sector 0
bon: ecc error, page = 0x00000188
end_request: I/O error, dev 61:02 (bon), sector 8
bon: ecc error, page = 0x00000190
end_request: I/O error, dev 61:02 (bon), sector 16
bon: ecc error, page = 0x00000198
end_request: I/O error, dev 61:02 (bon), sector 24
cramfs: wrong magic
bon: ecc error, page = 0x00000180
end_request: I/O error, dev 61:02 (bon), sector 0
FAT: unable to read boot sector
bon: ecc error, page = 0x00000180
end_request: I/O error, dev 61:02 (bon), sector 0
FAT: unable to read boot sector
Kernel panic: VFS: Unable to mount root fs on 61:02
|
在minicom中设置串口的时候需要使用ttyS0,但是在挂载的时候需要使用ttySAC0,是需要注意的,然后在进行烧写的时候,一定要注意分区的情况,注意算好每个分区的大小,在烧写的时候选好分区,在某个分区,如文件系统区曾经烧写过文件的话,要重新格式化后,再重新烧写,否则的话也会出现类似问题