RE: [U-Boot-Users] Network problem in u-boot.

Hi again.
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.
I enabled debug and got following output:
=> run setup miiphy_register: non unique device name '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 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' ENET Speed is 100 Mbps - FULL duplex connection T T miiphy_register: non unique device name 'ppc_4xx_eth0' ENET Speed is 100 Mbps - FULL duplex connection T T T miiphy_register: non unique device name 'ppc_4xx_eth0' ENET Speed is 100 Mbps - FULL duplex connection T T T miiphy_register: non unique device name 'ppc_4xx_eth0' ENET Speed is 100 Mbps - FULL duplex connection T miiphy_register: non unique device name 'ppc_4xx_eth0' ENET Speed is 100 Mbps - FULL duplex connection
Retry count exceeded; starting again miiphy_register: non unique device name 'ppc_4xx_eth0' ENET Speed is 100 Mbps - FULL duplex connection BOOTP broadcast 1 BOOTP broadcast 2 miiphy_register: non unique device name 'ppc_4xx_eth0' ENET Speed is 100 Mbps - FULL duplex connection BOOTP broadcast 3 BOOTP broadcast 4 BOOTP broadcast 5 miiphy_register: non unique device name 'ppc_4xx_eth0' ENET Speed is 100 Mbps - FULL duplex connection
Retry count exceeded; starting again
Abort
//André
-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf Of André Berggren Sent: den 14 november 2005 16:34 To: Stefan Roese; u-boot-users@lists.sourceforge.net Cc: Wolfgang Denk Subject: RE: [U-Boot-Users] Network problem in u-boot.
Hi! Yes the mac is valid. I use 100Mbps FD and bootp to get an adress. U-boot gets IP 172.18.22.66 and netmask is 255.255.255.0
I´ll try to enable debugging later and post the results.
//Andre
-----Original Message----- From: Stefan Roese [mailto:sr@denx.de] Sent: den 14 november 2005 16:20 To: u-boot-users@lists.sourceforge.net Cc: Wolfgang Denk; André Berggren Subject: Re: [U-Boot-Users] Network problem in u-boot.
On Monday 14 November 2005 16:12, Wolfgang Denk wrote:
The problem is that sometimes the network in u-boot stops, e.g. just getting TTT in a tftp transfer. I foud out that this occurs when another packet not involed in the tftp fransfer arrives. It could be a TCP-connect attempt from another host to u-boot or a ARP request. With a network sniffer I can se that u-boot still send data, but all data ariving is never processed. A reset of the board is needed to get it up and running again.
The board is a custom bord whith AMCC440ep based on bamboo.
I cannot confirm this. I just tested approx. 20 downloads on a bamboo board without any such problems.
What exactly is your network configuration? 10 / 100 Mbps? FD / HD? IP addresses? Netmask?
And do you use a valid MAC address? Did you try to enable debugging in the 4xx ethernet driver? If not, please do this and post some results here.
Viele Grüße, Stefan ###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/
------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users ###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/

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
participants (2)
-
André Berggren
-
Stefan Roese