主题 : Tiny210移植Linux3.2.48,dm9000 dm9000: read wrong id 0x2b2a2928 复制链接 | 浏览器收藏 | 打印
级别: 新手上路
UID: 83593
精华: 0
发帖: 11
金钱: 55 两
威望: 11 点
综合积分: 22 分
注册时间: 2012-12-08
最后登录: 2013-07-19
楼主  发表于: 2013-07-19 10:20

 Tiny210移植Linux3.2.48,dm9000 dm9000: read wrong id 0x2b2a2928

小弟最近移植Linux3.2.48,在移植的过程中,出现了dm9000 dm9000: read wrong id 0x2b2a2928的错误,但是我可以通过开发板ping通虚拟机的tftp和nfs主机,请问前辈们,这是什么原因呢?如果ping的通,那么我的DM9000驱动因该就是正确的,而且通过tftp上传内核uImage,并启动内核都正常,那为什么会出现上面的错误呢?
这是我的启动参数配置
bootargs=noinitrd console=ttySAC0,115200 root=/dev/nfs nfsroot=192.168.1.99:/home/linux/nfsdir ip=192.168.1.88

以下是错误代码
......
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: wrong id: 0x2b2a2928
dm9000 dm9000: not found (-19).

mousedev: PS/2 mouse device common for all mice
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c-rtc s3c64xx-rtc: rtc disabled, re-enabling
s3c-rtc s3c64xx-rtc: rtc core: registered s3c as rtc0
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2
s3c-rtc s3c64xx-rtc: setting system clock to 2013-07-18 08:08:46 UTC (1374134926)
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:

1f00            1024 mtdblock0  (driver?)
1f01            5120 mtdblock1  (driver?)
1f02           81920 mtdblock2  (driver?)
1f03          174080 mtdblock3  (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[<80018f84>] (unwind_backtrace+0x0/0xf0) from [<8026dc08>] (panic+0x70/0x1ac)
[<8026dc08>] (panic+0x70/0x1ac) from [<80341c20>] (mount_block_root+0x15c/0x210)
[<80341c20>] (mount_block_root+0x15c/0x210) from [<80341e9c>] (mount_root+0xd8/0xf4)
[<80341e9c>] (mount_root+0xd8/0xf4) from [<80342018>] (prepare_namespace+0x160/0x1b8)
[<80342018>] (prepare_namespace+0x160/0x1b8) from [<803418d8>] (kernel_init+0xf4/0x12c)
[<803418d8>] (kernel_init+0xf4/0x12c) from [<80014884>] (kernel_thread_exit+0x0/0x8)


级别: 新手上路
UID: 83593
精华: 0
发帖: 11
金钱: 55 两
威望: 11 点
综合积分: 22 分
注册时间: 2012-12-08
最后登录: 2013-07-19
1楼  发表于: 2013-07-19 10:22
从启动的信息上看,DM9000还是有问题,如果DM9000有问题,那为什么可以tftp加载3.2的内核uImage呢???     
级别: 新手上路
UID: 83593
精华: 0
发帖: 11
金钱: 55 两
威望: 11 点
综合积分: 22 分
注册时间: 2012-12-08
最后登录: 2013-07-19
2楼  发表于: 2013-07-19 12:59
没人知道吗?
级别: 新手上路
UID: 44864
精华: 0
发帖: 13
金钱: 65 两
威望: 13 点
综合积分: 26 分
注册时间: 2011-04-29
最后登录: 2013-10-28
3楼  发表于: 2013-08-03 23:33
tftp加载3.2的内核uImage 是 uboot的支持
引导内核之后是内核的支持
Cya,Reggie.
级别: 侠客
UID: 81867
精华: 1
发帖: 67
金钱: 390 两
威望: 78 点
综合积分: 154 分
注册时间: 2012-11-14
最后登录: 2014-10-30
4楼  发表于: 2013-08-04 08:30
I wonder if you need to set the mac address in the commandline string?