按照网上的方法移植CS8900驱动到FS2410开发板，但是无法ping通，特来求助！
本帖最后由 Mrzhen009 于 2012-05-30 10:44 编辑按照网上的方法（《完全手册》中也有）移植CS8900驱动到FS2410开发板，但是无法ping通，特来求助！以下是启动信息：
## Booting image at 32000000 ...
Image Name: Linux-2.6.22.6
Created: 2012-05-2914:29:25 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1601728 Bytes =1.5 MB
Load Address: 30008000
Entry Point:30008000
Verifying Checksum ... OK
OK
Starting kernel ...
Uncompressing Linux........................................................................................................ done, booting the kernel.
Linux version 2.6.22.6 (root@localhost.localdomain) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #1 Tue May 29 22:27:08 CST 2012
CPU: ARM920T revision 0 (ARMv4T), cr=00007177
Machine: FS2410
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.Total pages: 16256
Kernel command line: root=/dev/mtdblock2 rootfstype=jffs2 rw init=/linuxrc noinitrd console=ttySAC0,115200
irq: clearing subpending status 00000002
PID hash table entries: 256 (order: 8, 1024 bytes)
timer tcon=00500000, tcnt a2c1, tcfg 00000200,00000000, usec 00001eb8
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61452KB available (2976K code, 310K data, 124K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
S3C2410 Power Management, (c) 2004 Simtec Electronics
S3C2410: Initialising architecture
S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics
DMA channel 0 at c4800000, irq 33
DMA channel 1 at c4800040, irq 34
DMA channel 2 at c4800080, irq 35
DMA channel 3 at c48000c0, irq 36
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048 )
TCP reno registered
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
yaffs May 29 2012 22:23:17 Installing.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
s3c2410-lcd s3c2410-lcd: no platform data for lcd, cannot attach
s3c2410-lcd: probe of s3c2410-lcd failed with error -22
lp: driver loaded but no devices found
ppdev: user-space parallel port driver
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
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
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: module loaded
cs89x0:cs89x0_probe(0x0)
cs89x0.c: v2.4.3-pre1 Russell Nelson <nelson@crynwr.com>, Andrew Morton <andrewm@uow.edu.au>
eth0: cs8900 rev K found at 0xc4c00300
cs89x0: Extended EEPROM checksum bad and no Cirrus EEPROM, relying on command line
cs89x0 mediaIRQ 53, programmed I/O, MAC 08: 89: 89: 89: 89: 89
cs89x0_probe1() successful //从这看，貌似是移植成功了
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
s3c2410-nand s3c2410-nand: Tacls=3, 30ns Twrph0=7 70ns, Twrph1=3 30ns
NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit)
Scanning device for bad blocks
Creating 8 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x00000000-0x00004000 : "Boot Agent"
0x00000000-0x00200000 : "S3C2410 flash partition 1"
0x00400000-0x00800000 : "S3C2410 flash partition 2"
0x00800000-0x00a00000 : "S3C2410 flash partition 3"
0x00a00000-0x00e00000 : "S3C2410 flash partition 4"
0x00e00000-0x01800000 : "S3C2410 flash partition 5"
0x01800000-0x03000000 : "S3C2410 flash partition 6"
0x03000000-0x04000000 : "S3C2410 flash partition 7"
usbmon: debugfs is not available
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
mice: PS/2 mouse device common for all mice
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c2410-i2c s3c2410-i2c: slave address 0x10
s3c2410-i2c s3c2410-i2c: bus frequency set to 390 KHz
s3c2410-i2c s3c2410-i2c: i2c-0: S3C I2C adapter
TCP cubic registered
NET: Registered protocol family 1
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
jffs2_scan_inode_node(): CRC failed on node at 0x00303bcc: Read 0xffffffff, calculated 0xc3e573ee
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 124K
Please press Enter to activate this console.
我完全是按照网上的修改方法修改的，检查了多遍，保证没有笔误敲错字母之类的。
现在的问题是CS8900到底有没有移植成功？移植成功的话，为什么ping不通？有网友说断号不对可以编译通过但是会出现ping不通的现象。我看过开发板的原理图了，使用的就是EINT9，而且基址就是0x19000000，这两点应该不会有问题。
主机使用的是VM虚拟机，桥接方式，已经关闭防火墙。使用U-boot下载正常，也可以ping通主机。
还望各位前辈予以指点啊！谢谢！ 你给自己的板子设置IP地址了吗？ 本帖最后由 Mrzhen009 于 2012-05-31 21:54 编辑
回复 2# l2y3n2
终于有朋友回答了，太感动了！
U-Boot里边有设置过，Linux里面没有设置，因为无法使用ifconfig命令。编译内核的时候可以设置IP吗？
现在这种状况不知道是不是网卡没有真正移植成功啊。出现这种现象和根文件系统有关系吗？
我看帖子的时候，看到一些移植成功的内核启动打印信息中有eth0的值（IP），而且还有网卡工作于半双工状态的信息，而我这块板子上的就没有这些信息……
回复 2# l2y3n2
现在终于可以使用ifconfig功能了，首先在进入系统后使用ifconfig功能设置IP，但重启开发板后IP消失必须重新设置。于是在/etc/init.d/rcS文件中添加“ifconfig *.*.*.*”这样每次重启板子就都自动获得IP了。
现在又有了新问题：系统启动后（也就是说挂载jffs2文件系统启动）可以由NFS挂载文件系统，但是如果直接使用NFS挂载文件系统启动内核还是不成功。网上一种说法是nfs默认使用UDP连接，丢包严重，要用TCP，但是在U-Boot中修改bootargs后依旧无法启动，望高人指点，谢谢！
页:
[1]