From: 张国富 <cleancode@163.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] network not work with u-boot
Date: Wed, 5 Dec 2018 18:25:39 +0800 (CST) [thread overview]
Message-ID: <3ddf0dcd.d340.1677de6d85a.Coremail.cleancode@163.com> (raw)
Hi all,
Recently I came across a problem, and I tried many things but it still does not work.
I have a board with a u-boot ready and the kernel image yet to upload. Unfortunately the board could not get the kernel image by ftp.
The kernel image was built ready and the ftp server was running in my WIN 10 desktop, whose IP Addr is 172.16.0.10/255.255.0.0, accordingly, the board was configured as IP Addr to be 172.16.0.100/255.255.0.0. This was what I get: No progress could be made and stuck there.
So I used the Wireshark to record what was going on from my desktop, and it showed me that: Destination unreachable (Port unreachable)
I thought it was the uImage file missing, but it turned out that it was definitely there: I downloaded the uImage file by chrome browser on ftp://172.16.0.10/
At last, I checked the u-boot configurations and I found a strange thing, as shown below:
The configuration item ipaddr1 could be introduced by misspelling, I guess this also happens sometime for everyone here.
But strange enough that it could not be deleted, I tried "setenv ipaddr1", "setenv ipaddr1 72.16.0.100", and the item ipaddr1 was still there.
What is the root cause for the failure of ftp operation? does it have something to do with the strange configuration item ipaddr1?
Any information or suggestion is highly appreciated.
--
Best wishes.
Zhangguofu (Gary)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 14985 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181205/508dfc5d/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 19172 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181205/508dfc5d/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 40420 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181205/508dfc5d/attachment-0002.png>
next reply other threads:[~2018-12-05 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 10:25 张国富 [this message]
2018-12-05 13:37 ` [U-Boot] network not work with u-boot Wolfgang Denk
2018-12-06 2:13 ` cleancode at 163.com
2018-12-06 8:13 ` Wolfgang Denk
2018-12-06 9:32 ` cleancode at 163.com
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=3ddf0dcd.d340.1677de6d85a.Coremail.cleancode@163.com \
--to=cleancode@163.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