Hi Stefan,

CONFIG_NET_MULTI wasn't enabled. When I enable it the "miiphy_register: non unique device name 'ppc_4xx_eth0'" is exchanged with "Trying ppc_4xx_eth0", but it doesn't solve the main problem. See output below.

=> run setup Trying ppc_4xx_eth0 ENET Speed is 100 Mbps - FULL duplex connection BOOTP broadcast 1 DHCPHandler: got packet: (src=67, dst=68, len=300) state: 3 Filtering pkt = 0 DHCPHandler: got DHCP packet: (src=67, dst=68, len=300) state: 3 DHCP: state=SELECTING bp_file: "/tftpboot/kernel.img" TRANSITIONING TO REQUESTING STATE Bootfile: /tftpboot/kernel.img DhcpSendRequestPkt: Sending DHCPREQUEST Transmitting DHCPREQUEST packet: len = 343 DHCPHandler: got packet: (src=67, dst=68, len=300) state: 4 Filtering pkt = 0 DHCPHandler: got DHCP packet: (src=67, dst=68, len=300) state: 4 DHCP State: REQUESTING Bootfile: /tftpboot/kernel.img DHCP client bound to address 172.18.22.66 Using ppc_4xx_eth0 device TFTP from server 172.18.22.110; our IP address is 172.18.22.66 Filename '/tftpboot/kernel.img'. Load address: 0x200000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# #########################################################T T T Trying ppc_4xx_eth0 T T Trying ppc_4xx_eth0 T T T Trying ppc_4xx_eth0 T T Trying ppc_4xx_eth0

Retry count exceeded; starting again Trying ppc_4xx_eth0 ENET Speed is 100 Mbps - FULL duplex connection BOOTP broadcast 1 BOOTP broadcast 2 Trying ppc_4xx_eth0 BOOTP broadcast 3 BOOTP broadcast 4 BOOTP broadcast 5 Trying ppc_4xx_eth0

Retry count exceeded; starting again Trying ppc_4xx_eth0 ENET Speed is 100 Mbps - FULL duplex connection Trying ppc_4xx_eth0 BOOTP broadcast 1

//André

-----Original Message----- From: Stefan Roese [mailto:sr@denx.de] Sent: den 16 november 2005 18:53 To: u-boot-users@lists.sourceforge.net Cc: André Berggren; Wolfgang Denk Subject: Re: [U-Boot-Users] Network problem in u-boot.

Hi Andre,

On Wednesday 16 November 2005 14:09, André Berggren wrote:

I made some more tests and found that the old 405enet driver wont halt forever like the old 440 and the latest 4xx driver does. The old 405enet only outputs "ENET Speed is 100 Mbps - FULL duplex connection" sleeps for a while and then resumes the transfer.

Observe that the problem only occurs when another computer send packets to u-boot or broadcasting on the network. If non of this occurs the transfer is always successful.

OK.

I enabled debug and got following output:

=> run setup miiphy_register: non unique device name 'ppc_4xx_eth0'

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This is a problem recently added to the 4xx ethernet driver. I haven't found the time to fix it yet.

ENET Speed is 100 Mbps - FULL duplex connection BOOTP broadcast 1 DHCPHandler: got packet: (src=67, dst=68, len=300) state: 3 Filtering pkt = 0 DHCPHandler: got DHCP packet: (src=67, dst=68, len=300) state: 3 DHCP: state=SELECTING bp_file: "/tftpboot/kernel.img" TRANSITIONING TO REQUESTING STATE Bootfile: /tftpboot/kernel.img DhcpSendRequestPkt: Sending DHCPREQUEST Transmitting DHCPREQUEST packet: len = 343 DHCPHandler: got packet: (src=67, dst=68, len=300) state: 4 Filtering pkt = 0 DHCPHandler: got DHCP packet: (src=67, dst=68, len=300) state: 4 DHCP State: REQUESTING Bootfile: /tftpboot/kernel.img DHCP client bound to address 172.18.22.66 TFTP from server 172.18.22.110; our IP address is 172.18.22.66 Filename '/tftpboot/kernel.img'. Load address: 0x200000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ##########################################T miiphy_register: non unique device name 'ppc_4xx_eth0'

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

See above.

I assume, that you don't have CONFIG_NET_MULTI enabled right now. Correct? As a simple workaround for this problem, please enable CONFIG_NET_MULTI in your config file. And please let me know, if this helped.

Best regards, Stefan ###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/