From: Rafal Jaworowski <raj@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Multicast TFTP problems
Date: Thu, 23 Aug 2007 11:41:21 +0200 [thread overview]
Message-ID: <46CD5641.7060306@semihalf.com> (raw)
Dave,
I'm having problems with tftp transfer with current U-Boot running on
MPC5121 (FEC controller); since your mcast tftp implementation we first
attempt to transfer using some bigger blocksize:
#define TFTP_MTU_BLOCKSIZE 1468, and it seems my problems are related to
this size.
When running current code (ET_DEBUG enabled) it fails like the following:
=> run load
Using FEC ETHERNET device
TFTP from server 192.168.1.1; our IP address is 192.168.160.77
Filename '/tftpboot/ads5121/u-boot.bin'.
Load address: 0x100000
Loading: send option "timeout 5"
Got OACK: timeout 5
Blocksize ack: 1468, 1468
T T T T T T T T T T
Retry count exceeded; starting again
Using FEC ETHERNET device
TFTP from server 192.168.1.1; our IP address is 192.168.160.77
Filename '/tftpboot/ads5121/u-boot.bin'.
Load address: 0x100000
Loading: send option "timeout 5"
Got OACK: timeout 5
Blocksize ack: 1468, 1468
Abort
=>
It fails with TFTP_MTU_BLOCKSIZE values above 1454, but it's ok with
anything up to this (including 1454):
=> run load
Using FEC ETHERNET device
TFTP from server 192.168.1.1; our IP address is 192.168.160.77
Filename '/tftpboot/ads5121/u-boot.bin'.
Load address: 0x100000
Loading: send option "timeout 5"
Got OACK: timeout 5
Blocksize ack: 1454, 1454
###########
done
Bytes transferred = 157720 (26818 hex)
=>
Any hints on these observations? What might be going wrong here?
kind regards,
Rafal
next reply other threads:[~2007-08-23 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 9:41 Rafal Jaworowski [this message]
2007-08-23 14:07 ` [U-Boot-Users] Multicast TFTP problems Ben Warren
2007-08-23 14:47 ` David Updegraff
2007-08-29 7:37 ` Rafal Jaworowski
2007-08-29 15:17 ` Ben Warren
2007-09-05 17:06 ` Rafal Jaworowski
2007-09-05 17:30 ` Ben Warren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46CD5641.7060306@semihalf.com \
--to=raj@semihalf.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox