[U-Boot] 30-Second TFTP Timeout at Start-Up

Jason Hanna jason.m.hanna.at.coincident at gmail.com
Wed Mar 31 22:09:16 CEST 2010


Hi All,

I'm seeing a strange TFTP issue and hoping someone on the list can help.

I'm running a Sequoia reference board and at start-up my TFTP transfer
always times out for 30 seconds, then proceeds without error or
further issue.

I ran Wireshark on my TFTP server, and also performed a port mirror of
the Sequoia board. I can confirm TFTP requests are only initiated 30
seconds after tftpboot is run.

Running with a static IP and the latest RC2 release of U-Boot. Boot
command is as follows:

net_nfs_fdt=tftp 200000 ${bootfile};tftp ${fdt_addr} ${fdt_file};run
nfsargs addip addtty;bootm 200000 - ${fdt_addr}

Startup log always looks the same...

U-Boot 2010.03-rc2-00011-gc0bf2cf-dirty (Mar 30 2010 - 20:10:06)

CPU:   AMCC PowerPC 440EPx Rev. A at 666.667 MHz (PLB=166 OPB=83
EBC=55 PCI=83 MHz)
       Security/Kasumi support
       Bootstrap Option H - Boot ROM Location I2C (Addr 0x52)
       Internal PCI arbiter enabled, PCI async ext clock used
       32 kB I-Cache 32 kB D-Cache
Board: Sequoia - AMCC PPC440EPx Evaluation Board, Rev. F, PCI-Async=66 MHz
I2C:   ready
DRAM:  256 MB
FLASH: 64 MB
NAND:  32 MiB
PCI:   Bus Dev VenId DevId Class Int
USB:   Host(int phy) Device(ext phy)
DTT:   1 is 38 C
Net:   ppc_4xx_eth0, ppc_4xx_eth1
Type "run net_nfs_fdt" to load via TFTP and mount root via NFS
Hit any key to stop autoboot:  0
Waiting for PHY auto negotiation to complete... done
ENET Speed is 1000 Mbps - FULL duplex connection (EMAC0)
Using ppc_4xx_eth0 device
TFTP from server X.X.X.X; our IP address is X.X.X.Y
Filename 'sequoia/uImage'.
Load address: 0x200000
Loading: T T T T T T
#################################################################
         ########################################
done
Bytes transferred = 1528036 (1750e4 hex)
Using ppc_4xx_eth0 device
TFTP from server X.X.X.X; our IP address is X.X.X.Y
Filename 'sequoia/sequoia.dtb'.
Load address: 0x1000000
Loading: #
done
Bytes transferred = 8669 (21dd hex)

I think this has always been happening, even with older versions of
U-Boot. I finally got annoyed enough with this problem to dig a little
further.
:-)

Thanks,
-jmh
Jason Hanna


More information about the U-Boot mailing list