From: Masami Komiya <mkomiya@sonare.it>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] TFTP PROBLEM
Date: Tue, 11 May 2004 00:23:16 +0900 [thread overview]
Message-ID: <409F9E64.8020702@sonare.it> (raw)
In-Reply-To: BAY15-DAV14nkB4ltFl00017133@hotmail.com
Sonia Martinez wrote:
> TFTP server in the host (Mandrake 9.2 ) is configured like this:
> service tftp
> {
> disable = no
(snip)
> #flags = IPv4
> }
as the same as mine.
> The environment variables are:
> $ printenv
(snip)
> netmask=255.255.0.0
> ipaddr=172.16.16.220
> serverip=172.16.16.70
no problem.
> Output with minicom:
> $ tftp a1000000 little
> TFTP from server 172.16.16.70; our IP address is 172.16.16.220
> Filename 'little'.
> Load address: 0xa1000000
> Loading: T T #T #
> done
> Bytes transferred = 1190 (4a6 hex)
>
> $ tftp a1000000 hello.img
> TFTP from server 172.16.16.70; our IP address is 172.16.16.220
> Filename 'hello.img'.
> Load address: 0xa1000000
> Loading: T T invalid RARP header
> invalid RARP header
> #T T #T T T #T T T
> Retry count exceeded; starting again
> TFTP from server 172.16.16.70; our IP address is 172.16.16.220
> Filename 'hello.img'.
> Load address: 0xa1000000
> Loading: #T T T T T T #T T T #T
> Retry count exceeded; starting again
Many timeout are occured. It seems hardware trouble...
I recommend recompile with debug flag of net.c and the driver's code
to get the more messages. also observe the packet with ethereal
or tcpdump command.
Masami Komiya
next prev parent reply other threads:[~2004-05-10 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 7:57 [U-Boot-Users] TFTP PROBLEM Sonia Martinez
2004-05-10 9:08 ` Masami Komiya
2004-05-10 13:21 ` Sonia Martinez
2004-05-10 15:23 ` Masami Komiya [this message]
2004-05-10 20:20 ` DeLaGarza, Robert
2004-05-10 21:35 ` Tolunay Orkun
-- strict thread matches above, loose matches on Subject: below --
2004-05-10 7:44 [U-Boot-Users] tftp problem Martinez Sonia
2004-05-10 9:08 ` Wolfgang Denk
2004-05-10 15:28 ` George G. Davis
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=409F9E64.8020702@sonare.it \
--to=mkomiya@sonare.it \
--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