linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arun Dharankar <ADharankar@ATTBI.Com>
To: "gao xiaoguo" <gaoxg@guoguang.com.cn>,
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: tftp on ppcboot 1.1.5
Date: Wed, 15 May 2002 05:58:01 -0400	[thread overview]
Message-ID: <200205150558.01854.ADharankar@ATTBI.Com> (raw)
In-Reply-To: <001301c1fbed$0efb5da0$6801a8c0@guoguangacer>


Following is different in my case (8260ADS board):
- Load address is 0x500000 (this may not be a problem)
- ethaddr is 00:11:22:33:44:55 (this prevented tftp in my case
   with similar symptoms as you describe if I used
   a1:b2:c3:d4:e5:c6, and I dont know why, and could
   be the problem in your case)
- tftp server has full path in inetd.conf; i.e. in.tftpd -s /tftpboot
  and then use tftp 0x500000 /tftpboot/testfile (this may not
  be a problem)
- Another possibility (as in my case of another similar board),
  the board was not setup properly in start.S.




On Wednesday 15 May 2002 04:46 am, gao xiaoguo wrote:
> I want to use tftp to download file into target machine,but always failed.
> The tftp server on linux has already been setup and tested, I tftp a file
> successfully by using other tftp client on windows.
>
> Following is my environment and operation log, and I found the ip/udp
> datagram on network really is 0.0.0.69->192.168.1.105,so nobody will answer
> to the tftp request. Why the ip address of server is changed from
> 192.168.1.105 to 0.0.0.69 ? Are there something I leave.
>
> CPU:   XPC860xxZPnnD3 at 48 MHz: 4 kB I-Cache 4 kB D-Cache FEC present
> Board: FADS with db MPC821, MPC860 / MPC860SAR / MPC860T rev ENG or PILOT
> DRAM:  (4 MB SDRAM)  8 MB
> FLASH:  2 MB
>
> =>printenv
>
> bootargs=
> bootcmd=bootm 2800100
> baudrate=115200
> loads_echo=1
> clocks_in_mhz=1
> ethaddr=00:00:00:01:02:03
> serverip=192.168.1.105
> ipaddr=192.168.1.99
> netmask=255.255.255.0
>
> =>tftpt boot 100000 testfile
>
> ARP broadcast 1
>
> Retry count exceeded; starting again
> ARP broadcast 1
> TFTP from server 192.168.1.105; our IP address is 192.168.1.99
> Filename 'testfile'.
> Load address: 0x100000
> Loading: *T T T T
> Retry count exceeded; starting again
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-05-15  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15  8:46 tftp on ppcboot 1.1.5 gao xiaoguo
2002-05-15  9:58 ` Arun Dharankar [this message]
2002-05-15 11:49 ` Wolfgang Denk
2002-05-15 13:08   ` 8260 and SPI driver Julien Eyries
  -- strict thread matches above, loose matches on Subject: below --
2002-05-15 10:14 tftp on ppcboot 1.1.5 Kári Davíesson

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=200205150558.01854.ADharankar@ATTBI.Com \
    --to=adharankar@attbi.com \
    --cc=gaoxg@guoguang.com.cn \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).