微波EDA网,见证研发工程师的成长!
首页 > 硬件设计 > 嵌入式设计 > linux-2.6.30.4移植至2440开发板

linux-2.6.30.4移植至2440开发板

时间:11-22 来源:互联网 点击:

Buffer I/O error ondevice mtdblock2, logical block 0

uncorrectable error :<3>end_request: I/O error, dev mtdblock2, sector 0

Buffer I/O error ondevice mtdblock2, logical block 0

uncorrectable error :<3>end_request: I/O error, dev mtdblock2, sector 8

Buffer I/O error ondevice mtdblock2, logical block 1

uncorrectable error :<3>end_request: I/O error, dev mtdblock2, sector 8

Buffer I/O error ondevice mtdblock2, logical block 1

uncorrectable error :<3>end_request: I/O error, dev mtdblock2, sector 16

Buffer I/O error ondevice mtdblock2, logical block 2

uncorrectable error :<3>end_request: I/O error, dev mtdblock2, sector 16

Buffer I/O error ondevice mtdblock2, logical block 2

uncorrectable error :<3>end_request: I/O error, dev mtdblock2, sector 24

Buffer I/O error ondevice mtdblock2, logical block 3

uncorrectable error :<3>end_request: I/O error, dev mtdblock2, sector 24

Buffer I/O error ondevice mtdblock2, logical block 3

uncorrectable error :<3>end_request: I/O error, dev mtdblock2, sector 0

FAT: unable to read bootsector

VFS: Cannot open rootdevice "mtdblock2" or unknown-block(31,2)

Please append a correct"root=" boot option; here are the available partitions:

1f00 256 mtdblock0 (driver?)

1f01 2048 mtdblock1 (driver?)

1f02 257536 mtdblock2 (driver?)

Kernel panic - notsyncing: VFS: Unable to mount root fs on unknown-block(31,2)

MTD分区与bootloader不匹配

#elif defined(CONFIG_more_than_256MB_NAND)

[0]= {

.name = "Board_uboot",

.offset = 0x00000000,

.size = 0x00080000,

},

[1]= {

.name = "Board_kernel",

.offset= 0x00240000,

.size = 0x00200000,

},

[2]= {

.name = "Board_yaffs2",

.offset= 0x00440000,

.size = 0x0FB40000,

}

**************************************************************************************************************************************************************

[0]和[1]分区不连贯的表面原因 中间的部分存放uboot的参数以及开机画面???环境变量

uboot分区信息:

0x0 到0x40000为uboot的分区,256K,
0x40000到0x4c000 为parameters分区,48K,
0x50000到0x70000 为eboot分区,128K,
0x70000到0x1F0000为logo分区,1536K,
0x1F0000 到0x3F0000为kernel分区,2M,
0x3F0000 到0x3FF8000 为root分区,60.03125M

nand分区信息:

static struct mtd_partition smdk_default_nand_part[] = {
[0] = {
.name = "TQ2440_uboot",
.size = 0x00040000,
.offset = 0x00000000,
},
[1] = {
.name = "TQ2440_kernel",
.offset = 0x0004C000,
.size = 0x00200000,
},
[2] = {
.name = "TQ2440_yaffs2",
.offset = 0x0024C000,
.size = 0x03DB0000,
}
};

uboot的分区和文件系统的分区,没有联系的。唯一的联系就是uboot引导启动的时候,命令要根据文件系统的分区信息来引导。比如要从mtdblock2启动,那么bootcmd中的命令bootm0xXXXXXXX就要和mtdblock2的首地址一样。。。。

Copyright © 2017-2020 微波EDA网 版权所有

网站地图

Top