We're seeing TFTP timed out when using it to copy files to the T1040RDB. Through Wireshark, we can see TFTP kept trying to send Data Packet Block 1 and there were no acknowledgement for Block 1. Does anyone know what the issue is? It seems that we can connect to the TFTP server and start the handshake. Thanks!
Is this request closed ? Even I'm also facing the similar problem on T1040 board .
Hello prashanth kumar gopal,
Would you please create a new thread to describe your problem in details?
Thanks,
Yiping
Hi Yiping,
I have created a new thread for this, thanks.
Regards
Prashanth
Hello HV HVO,
Did you encounter this problem in u-boot or Linux Kernel?
Which network interface did you use?
Did you use u-boot, fman firmware and Linux Kernel coming from the same Linux SDK?
It's better to send a whole log to us, including u-boot setting up, u-boot environment, Kernel booting up and all you operations. Thanks.
Have a great day,
Yiping
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
1) We encountered the TFTP timing out in u-boot
2) We used DTSEC4 for the network interface
3) We used whatever came with the T1040RDB. Here’s the config:
U-Boot 2014.07QorIQ-SDK-V1.7+g659b6a2 (Dec 13 2014 - 18:00:52)
CPU0: T1040E, Version: 1.1, (0x85280011)
Core: e5500, Version: 2.1, (0x80241021)
Clock Configuration:
CPU0:1400 MHz, CPU1:1400 MHz, CPU2:1400 MHz, CPU3:1400 MHz,
CCB:600 MHz,
DDR:800 MHz (1600 MT/s data rate) (Asynchronous), IFC:150 MHz
QE:300 MHz
FMAN1: 600 MHz
QMAN: 300 MHz
PME: 300 MHz
L1: D-cache 32 KiB enabled
I-cache 32 KiB enabled
Reset Configuration Word (RCW):
00000000: 0c18000e 0e000000 00000000 00000000
00000010: 66000002 80000002 ec027000 01000000
00000020: 00000000 00000000 00000000 00032810
00000030: 00000000 0342500f 00000000 00000000
Board: T1040RDB
Board rev: 0x01 CPLD ver: 0x09, vBank: 0
I2C: ready
SPI: ready
DRAM: Initializing....using SPD
Detected UDIMM 18KSF51272AZ-1G6K1
4 GiB (DDR3, 64-bit, CL=11, ECC on)
DDR Chip-Select Interleaving Mode: CS0+CS1
Flash: 256 MiB
L2: 256 KiB enabled
Corenet Platform Cache: 256 KiB enabled
Using SERDES1 Protocol: 102 (0x66)
NAND: 1024 MiB
MMC: FSL_SDHC: 0
Firmware 'Microcode version 0.0.1 for T1040 r1.0' for 1040 V1.0
QE: uploading microcode 'Microcode for T1040 r1.0' version 0.0.1
PCIe1: Root Complex, no link, regs @ 0xfe240000
PCIe1: Bus 00 - 00
PCIe2: Root Complex, no link, regs @ 0xfe250000
PCIe2: Bus 01 - 01
PCIe3: Root Complex, no link, regs @ 0xfe260000
PCIe3: Bus 02 - 02
PCIe4: Root Complex, no link, regs @ 0xfe270000
PCIe4: Bus 03 - 03
In: serial
Out: serial
Err: serial
Net: Initializing Fman
Fman1: Uploading microcode version 106.4.14
FSL_MDIO0:0 is connected to FM1@DTSEC1. Reconnecting to FM1@DTSEC2
FM1@DTSEC1, FM1@DTSEC2, FM1@DTSEC3, FM1@DTSEC4, FM1@DTSEC5
=>
4) Attached is a capture while running Wireshark to monitor the TFTP
5) When we took this T1040RDB and connected it to a different PC, we were able to run the TFTP without timing out. Attached is a capture while running Wireshark without the timing out
Thanks!
tftp timed out on a T1040RDB
reply from Yiping Wang<http://jiveon.jivesoftware.com/mpss/c/fAA/PDcDAA/t.1nx/iiQrKDNBRY2teANGi1l2Xw/h1/eqhG5v9o4WV1pCmWaB03cUjBPgRj-2F3GoJUaXSZ409bTuunTxDnqsgk6MvTmPNW-2BIbsMPeMV32yFxUPb-2BtQiSPGCG8wrrcaln-2FLLwVRV4WnU-3D> in QorIQ Processors - View the full discussion<http://jiveon.jivesoftware.com/mpss/c/fAA/PDcDAA/t.1nx/iiQrKDNBRY2teANGi1l2Xw/h2/eqhG5v9o4WV1pCmWaB03cUjBPgRj-2F3GoJUaXSZ409bTgfAllfeLHNLtP1kGi0Af86mCMcH51q5HKuXWHKJCRywZ-2B3UCXkYHfApDR6J51Unc-3D>
Hello HV HVO,
It's seems no content in the attachment, I suggest you check the following.
1. The TFTP server was setup without problem? Can you download the same file on other PC from the tftp server?
2. Is the board and the tftp server connected with a switch? On the target board, is PHY auto negotiation completed, and the Ethernet port is recognized as full duplex mode? Can you ping the server from the target board successfully? If necessary, you could boot up Linux and use "ethtool" to get more diagnostic information.
3. Is the network environment setup without problem? Is there IP collision problem? And all network parameters are configured correctly on the target board?
I guess this problem is caused by your network environment. Please feel free to contact me, if you have further information.
Have a great day,
Yiping
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------