- 论坛徽章:
- 0
|
如果把基址改为:
#define CONFIG_DM9000_BASE 0x20000300
#define DM9000_IO CONFIG_DM9000_BASE
#define DM9000_DATA (CONFIG_DM9000_BASE +4)
ping的时候出现如下情况,即not found at 0x20000300
- U-Boot 2010.03 ( 9月 06 2011 - 21:30:57)
- modified by tekkamanninja
- (tekkamanninja@163.com)
- Love Linux forever!!
- Hit any key to stop autoboot: 0
- [u-boot@MINI2440]# printenv
- bootargs=noinitrd root=/dev/nfs rw nfsroot=192.168.0.1:/home/tekkaman/working/nfs/rootfs ip=192.168.0.2:192.168.0.1::255.255.255.0 console=ttySAC0,115200 init=/linuxrc mem=64M
- bootcmd=nfs 0x30008000 192.168.0.1:/home/tekkaman/working/nfs/zImage.img;bootm
- bootdelay=1
- baudrate=115200
- ethaddr=08:08:11:18:12:27
- ipaddr=192.168.0.2
- serverip=192.168.0.16
- gatewayip=192.168.0.1
- netmask=255.255.255.0
- tekkaman=bmp d 70000
- stdin=serial
- stdout=serial
- stderr=serial
- ethact=dm9000
- Environment size: 471/131068 bytes
- [u-boot@MINI2440]# ping 192.168.0.16
- dm9000_init
- resetting DM9000
- resetting the DM9000, 1st reset
- resetting the DM9000, 2st reset
- 2b9e299edm9000 not found at 0x20000300 id: 0x2b9e299e
- ping failed; host 192.168.0.16 is not alive
- [u-boot@MINI2440]#
- dm9000_init
- resetting DM9000
- resetting the DM9000, 1st reset
- resetting the DM9000, 2st reset
- 2900dm9000 not found at 0x20000300 id: 0x00002900
- ping failed; host 192.168.0.16 is not alive
- [u-boot@MINI2440]#
复制代码 如果把基址改为:
#define CONFIG_DM9000_BASE 0x18000300 //或者19000300,或者18000000.现象一样。我的DM9000AEP的CS接nGCS3,CMD接LADDR2,我觉得应该是0x19000300,vivi上就是这样的,并且vivi可以ping通。
#define DM9000_IO CONFIG_DM9000_BASE
#define DM9000_DATA (CONFIG_DM9000_BASE +4)
ping的时候出现如下情况,即not found at 0x20000300
这样的结果是:ping不通,并且好像重启了一样,屏幕闪了几下,然后就死机了。
如下图
- [u-boot@MINI2440]# ping 192.168.0.16
- dm9000_init
- resetting DM9000
复制代码 我已经打开DEBUG开关了。
也就是在DM9000_iow(DM9000_GPCR,1)时死机重启了。//DM9000_GPCR和VIVI上的一样,都是0X1E
希望大家帮我查下什么原因,为什么一读那个地址就死机重启。基址到底是什么?我的开发板是BASIC2440,是恒丰锐科的,S3C2440. |
|