From: ppc user <ppc_user@lambdaaccess.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] bootp
Date: Mon, 01 Mar 2004 10:59:16 -0500 [thread overview]
Message-ID: <E1Axpp6-0001Vt-Oo@server4.anonymousnetworks.com> (raw)
A bit more info --
it looks like the correct file name is sent in the dhcp request,
but then u-boot switches to tftp mode with the incorrect file name in
the request.
I have placed the capture file here:
http://www.lambdaaccess.com/u-boot.libpcap
thanks again for your help.
> I captured some packets using ethereal and I see the request to the
> bootp server contains the wrong file name. The reply from the server
> matches the request.
>
> Here is the output from U-boot in the 3 cases I described:
>
> (1) Environment variable bootfile = zImage, try to load some other
file:
>
> u-boot> bootp 100000 10got.img
> BOOTP broadcast 1
> DHCP client bound to address 192.168.0.43
> TftpStart(zImage:192.168.0.1)
> TFTP from server 192.168.0.1; our IP address is 192.168.0.43
> Filename 'zImage'.
> Load address: 0x100000
> Loading:
> #################################################################
> ##################################################
> done
> Bytes transferred = 585718 (8eff6 hex)
> u-boot>
>
>
> (2) no bootfile env variable
>
>
> u-boot> bootp 100000 10got.img
> BOOTP broadcast 1
> DHCP client bound to address 192.168.0.43
> TftpStart(no bootfile:192.168.0.1)
> *** Warning: no boot file name; using '2B00A8C0.img'
> TFTP from server 192.168.0.1; our IP address is 192.168.0.43
> Filename '2B00A8C0.img'.
> Load address: 0x100000
> Loading: *
> TFTP error: 'File not found' (1)
> Starting again
>
> (3) tftpboot command
>
> u-boot> tftpboot 100000 10got.img
> TftpStart(zImage:192.168.0.1)
> TFTP from server 192.168.0.1; our IP address is 192.168.0.44
> Filename '10got.img'.
> Load address: 0x100000
> Loading: #
> done
> Bytes transferred = 921 (399 hex)
> u-boot>
>
>
> > In message <E1Awx0E-000193-Ly@server4.anonymousnetworks.com> you
> wrote:
> > > I'm using u-boot 1.0.0 on a xilinx embedded ppc 405 and I see the
> > > follow unexplained behavior:
> > >
> > > if I do a bootp <address> <filename> it always bootp's the
filename
> > > stored in environment variable bootfile rather than the filename
I
> > > specify in the command line. If I have no bootfile env variable
it
> > > tries to bootp a garbage file name.
> >
> > What does the reply packet sent by your BOOTP server contain
exactly?
> >
> > Best regards,
> >
> > Wolfgang Denk
> >
> > --
> > Software Engineering: Embedded and Realtime Systems, Embedded
Linux
> > Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email:
wd at denx.de
> > If God had a beard, he'd be a UNIX programmer.
> >
> >
> > -------------------------------------------------------
> > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > Build and deploy apps & Web services for Linux with
> > a free DVD software kit from IBM. Click Now!
> > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> > _______________________________________________
> > U-Boot-Users mailing list
> > U-Boot-Users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/u-boot-users
> >
> >
>
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>
>
next reply other threads:[~2004-03-01 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 15:59 ppc user [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-01 14:29 [U-Boot-Users] bootp ppc user
2004-02-28 5:27 ppc user
2004-02-29 17:23 ` Wolfgang Denk
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=E1Axpp6-0001Vt-Oo@server4.anonymousnetworks.com \
--to=ppc_user@lambdaaccess.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