Hi!
Is there someone using the combo in $SUBJECT?
I'm using a modified at91rm9200dk.h config file, the ethernet relevant section:
#define CONFIG_DRIVER_ETHER #define CONFIG_NET_RETRY_COUNT 20
/* * MII PHY configuration * */ #define CONFIG_MII 1 /* MII PHY management */ #define CONFIG_PHY_ADDR 0 /* PHY address */ #define CONFIG_PHY_CMD_DELAY 40 /* PHY COMMAND delay */ /* 32usec min. for LXT971A */ #define CONFIG_PHY_RESET_DELAY 300 /* PHY RESET recovery delay */
#define CONFIG_ETHADDR 02:80:ad:20:31:c8
#define CONFIG_IPADDR 192.168.0.100 #define CONFIG_SERVERIP 192.168.0.2
(for the full setup, see the bottom of the mail)
after starting u-boot i do:
U-Boot> tftp 21000000 zImage PHY not connected!! TFTP from server 192.168.0.2; our IP address is 192.168.0.100 Filename 'zImage'. Load address: 0x21000000 Loading: T T T T T T T T T T T T T T T T T T T T Abort U-Boot>
On the server PC i'm using tftp-hpa server. Here is the dump of the ethernet traffic: 18:59:38.903037 arp who-has 192.168.0.2 tell 192.168.0.100 18:59:39.160951 arp reply 192.168.0.2 is-at 00:50:8d:53:ec:34 18:59:43.902587 arp who-has 192.168.0.2 tell 192.168.0.100 18:59:43.902626 arp reply 192.168.0.2 is-at 00:50:8d:53:ec:34 18:59:58.903396 IP 192.168.0.100.1373 > 192.168.0.2.tftp: 25 RRQ "zImage" octet timeout 5 18:59:58.918175 IP 192.168.0.2.32968 > 192.168.0.100.1373: UDP, length: 12 19:00:03.903759 IP 192.168.0.100.1373 > 192.168.0.2.tftp: 25 RRQ "zImage" octet timeout 5 19:00:03.905782 IP 192.168.0.2.32971 > 192.168.0.100.1373: UDP, length: 12 19:00:03.906187 IP 192.168.0.100.1373 > 192.168.0.2.32971: UDP, length: 4 19:00:03.906590 IP 192.168.0.2.32971 > 192.168.0.100.1373: UDP, length: 516 19:00:03.917236 arp who-has 192.168.0.100 tell 192.168.0.2 19:00:03.917566 arp reply 192.168.0.100 is-at 02:80:ad:20:31:c8 19:00:03.923288 IP 192.168.0.2.32968 > 192.168.0.100.1373: UDP, length: 12 19:00:08.903911 IP 192.168.0.100.1373 > 192.168.0.2.32971: UDP, length: 4 19:00:08.907847 IP 192.168.0.2.32971 > 192.168.0.100.1373: UDP, length: 516 19:00:13.904233 IP 192.168.0.100.1373 > 192.168.0.2.32971: UDP, length: 4 19:00:13.923953 IP 192.168.0.2.32968 > 192.168.0.100.1373: UDP, length: 12 19:00:18.904649 IP 192.168.0.100.1373 > 192.168.0.2.32971: UDP, length: 4 19:00:18.912829 IP 192.168.0.2.32971 > 192.168.0.100.1373: UDP, length: 516 19:00:23.904979 IP 192.168.0.100.1373 > 192.168.0.2.32971: UDP, length: 4 19:00:28.905379 IP 192.168.0.100.1373 > 192.168.0.2.32971: UDP, length: 4 19:00:33.905692 IP 192.168.0.100.1373 > 192.168.0.2.32971: UDP, length: 4 19:00:33.928161 IP 192.168.0.2.32968 > 192.168.0.100.1373: UDP, length: 12 19:00:38.906060 IP 192.168.0.100.1373 > 192.168.0.2.32971: UDP, length: 4 19:00:38.917350 IP 192.168.0.2.32971 > 192.168.0.100.1373: UDP, length: 516 19:00:38.926918 arp who-has 192.168.0.100 tell 192.168.0.2 19:00:39.926751 arp who-has 192.168.0.100 tell 192.168.0.2 19:00:39.927037 arp reply 192.168.0.100 is-at 02:80:ad:20:31:c8 19:00:43.906424 IP 192.168.0.100.1373 > 192.168.0.2.32971: UDP, length: 4 19:00:53.907197 IP 192.168.0.100.1373 > 192.168.0.2.32971: UDP, length: 4 19:00:58.907554 IP 192.168.0.100.1373 > 192.168.0.2.32971: UDP, length: 4 19:01:03.907910 IP 192.168.0.100.1373 > 192.168.0.2.32971: UDP, length: 4 19:01:08.908269 IP 192.168.0.100.1373 > 192.168.0.2.32971: UDP, length: 4
It looks like that u-boot is ignoring the returned packages for some reason. Maybe u-boot is still configured to think that the phy is a dm9161, as on the original AT91 DK board? How to change that to the LXT971? What could be that cause that outgoing packages are OK, but incoming packages are ignored?
I'd appreciate any hints on this!
Regards, Zoli