Rick,

I had the exact same problem when using LAN91C111 on the Nios DK-1C20 board (same status & incorrect length). You may need to define CONFIG_SMC_USE_32_BIT. If your bus interface to the chip is 32-bits, a full 32-bit read might be occuring when the data register is read.

This throws away the second 16-bit word of the packet buffer (which is the packet length) -- so you end up skipping every other set of 2-bytes after reading the incorrect length.

Regards, --Scott

-----Original Message----- From: Rick.Lee [SMTP:cisc@tom.com] Sent: Tuesday, October 21, 2003 9:51 AM To: U-Boot-Users@lists.sourceforge.net Subject: [U-Boot-Users] Problem with LAN91C113

The Ethernet Chip on my board is SMSC LAN91C113,the driver I used is smc91111.c. I've defined CONFIG_DRIVER_SMC91111,undefined xxx_USE_32_BIT undefined xxxx_EXT_PHY. When u-boot runs up, I try to ping my host from u-boot,but the sniffer on my host cannot catch any hardware packet,but my host sends ARP REPLY packet to my board. and the sended packet is captured by sniffer.Unfortunitly,board does'nt seem to have received right packet.I've enabled ET_DEBUG,It prints: RCV: STATUS 42 LENGTH 8.

AND LEDA & LEDB both lights!

What is the reason? Can you give me some ideas? Thanks a lot!

Ricky