[U-Boot-Users] tftp problem

[U-Boot-Users] tftp problem

[Martinez Sonia]

Hi all,
We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform. We've
been able to boot Linux from RAM, with JFFS2 and nfsroot too. But we've a
problem with tftp. 
We know that the tftp server works because we've tested it with other
clients. But with tftp in u-boot we're only able to transfer little files
(1, 2 Kb).. 
Which can be the problem?? Newer versions work fine??
Thanks in advance
Regards, 
Sonia    

[U-Boot-Users] tftp problem

[Wolfgang Denk]

In message <A5F3D6A490BAD1118AAE00A0C94C2664034025EA@CORREO> you wrote:
>
> We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform. We've

Why are you posting the very same message twice  from  two  different
mail addresses?

Please NEVER do this again!!!!

> We know that the tftp server works because we've tested it with other
> clients. But with tftp in u-boot we're only able to transfer little files
> (1, 2 Kb).. 

What happens then? Is there an error mesaage or what? Did you try  to
debug the problem?

> Which can be the problem?? Newer versions work fine??

Ummm... did you try it out? If yes, what was the result? If not, why not???


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
Another dream that failed.  There's nothing sadder.
	-- Kirk, "This side of Paradise", stardate 3417.3

[U-Boot-Users] tftp problem

[George G. Davis]

On Mon, May 10, 2004 at 11:08:07AM +0200, Wolfgang Denk wrote:
> In message <A5F3D6A490BAD1118AAE00A0C94C2664034025EA@CORREO> you wrote:
> >
> > We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform. We've
> 
> Why are you posting the very same message twice  from  two  different
> mail addresses?
> 
> Please NEVER do this again!!!!
> 
> > We know that the tftp server works because we've tested it with other
> > clients. But with tftp in u-boot we're only able to transfer little files
> > (1, 2 Kb).. 
> 
> What happens then? Is there an error mesaage or what? Did you try  to
> debug the problem?
> 
> > Which can be the problem?? Newer versions work fine??
> 
> Ummm... did you try it out? If yes, what was the result? If not, why not???

FWIW, I've noticed that the Lubbock SMC_inb macro in drivers/lan9196.h is
broken. Take a look at that Lubbock SMC_inb macro definition:

#define SMC_inb(p)	({ \
	unsigned int __p = (unsigned int)(SMC_BASE_ADDRESS + (p * 4)); \
	unsigned int __v = *(volatile unsigned short *)((__p) & ~1); \
	if (__p & 1) __v >>= 8; \
	else __v &= 0xff; \
	__v; })


I believe that definition should be rewritten as follows (ignoring issues
of coding style or personal preferences : ):

#define SMC_inb(p)	({ \
	unsigned int __p = (unsigned int)(SMC_BASE_ADDRESS + ((p) * 4)); \
	unsigned int __v = *(volatile unsigned short *)(__p & ~4); \
	if (__p & 4) __v >>= 8; \
	else __v &= 0xff; \
	__v; })


I don't have a Lubbock target so I can't vouch for the accuracy of my
assertion. But it clearly seems broken as currently written. Also have a
look at the Lubbock kernel lan91c96 support to review those macros there
and draw your own conclusions.

I have no idea if this will help with this problem. But it probably won't
hurt. : )

HTH!

--
Regards,
George

[U-Boot-Users] tftp problem -> Solved

[Sonia Martinez]

TFTP works. I applied the changes suggested by James Jiao.
I've modified the udelay routine in /cpu/pxa/interrupts.c the way he
explained and it works.
Thank you all for your help
Sonia
----- Original Message -----
From: "George G. Davis" <davis_g@comcast.net>
To: "Wolfgang Denk" <wd@denx.de>
Cc: "Martinez Sonia" <SMartinez@ikerlan.es>; "Sonia Martinez"
<anexwarrior@hotmail.com>; <u-boot-users@lists.sourceforge.net>
Sent: Monday, May 10, 2004 5:28 PM
Subject: Re: [U-Boot-Users] tftp problem


> On Mon, May 10, 2004 at 11:08:07AM +0200, Wolfgang Denk wrote:
> > In message <A5F3D6A490BAD1118AAE00A0C94C2664034025EA@CORREO> you wrote:
> > >
> > > We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform.
We've
> >
> > Why are you posting the very same message twice  from  two  different
> > mail addresses?
> >
> > Please NEVER do this again!!!!
> >
> > > We know that the tftp server works because we've tested it with other
> > > clients. But with tftp in u-boot we're only able to transfer little
files
> > > (1, 2 Kb)..
> >
> > What happens then? Is there an error mesaage or what? Did you try  to
> > debug the problem?
> >
> > > Which can be the problem?? Newer versions work fine??
> >
> > Ummm... did you try it out? If yes, what was the result? If not, why
not???
>
> FWIW, I've noticed that the Lubbock SMC_inb macro in drivers/lan9196.h is
> broken. Take a look at that Lubbock SMC_inb macro definition:
>
> #define SMC_inb(p) ({ \
> unsigned int __p = (unsigned int)(SMC_BASE_ADDRESS + (p * 4)); \
> unsigned int __v = *(volatile unsigned short *)((__p) & ~1); \
> if (__p & 1) __v >>= 8; \
> else __v &= 0xff; \
> __v; })
>
>
> I believe that definition should be rewritten as follows (ignoring issues
> of coding style or personal preferences : ):
>
> #define SMC_inb(p) ({ \
> unsigned int __p = (unsigned int)(SMC_BASE_ADDRESS + ((p) * 4)); \
> unsigned int __v = *(volatile unsigned short *)(__p & ~4); \
> if (__p & 4) __v >>= 8; \
> else __v &= 0xff; \
> __v; })
>
>
> I don't have a Lubbock target so I can't vouch for the accuracy of my
> assertion. But it clearly seems broken as currently written. Also have a
> look at the Lubbock kernel lan91c96 support to review those macros there
> and draw your own conclusions.
>
> I have no idea if this will help with this problem. But it probably won't
> hurt. : )
>
> HTH!
>
> --
> Regards,
> George
>

[U-Boot-Users] TFTP PROBLEM

[Sonia Martinez]

Hi all,

We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform. We've
been able to boot Linux from RAM, with JFFS2 and nfsroot too. But we've a
problem with tftp.

We know that the tftp server works because we've tested it with other
clients. But with tftp in u-boot we're only able to transfer little files
(1, 2 Kb)..

Which can be the problem?? Newer versions work fine??

Thanks in advance

Regards,

Sonia

[U-Boot-Users] TFTP PROBLEM

[Masami Komiya]

TFTP can work fine in 1.0.0, but be affected by network environment.
What's kind of the server do you use for the host configuration, DHCP, BOOTP ?

Could you show the console messages ?
Also I want to know your environment variables.
That is shown by "printenv" command.

Masami Komiya

Sonia Martinez wrote:
> Hi all,
> 
> We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform. We've
> been able to boot Linux from RAM, with JFFS2 and nfsroot too. But we've a
> problem with tftp.
> 
> We know that the tftp server works because we've tested it with other
> clients. But with tftp in u-boot we're only able to transfer little files
> (1, 2 Kb)..
> 
> Which can be the problem?? Newer versions work fine??
> 
> Thanks in advance
> 
> Regards,
> 
> Sonia
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
> deliver higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
> 
> 

[U-Boot-Users] TFTP PROBLEM

[Sonia Martinez]

TFTP server in the host (Mandrake 9.2 ) is configured like this:

  service tftp

  {

  disable = no

  socket_type = dgram

  protocol = udp

  wait = yes

  user = root

  server = /usr/sbin/in.tftpd

  server_args = -s /tftpboot

  #per_source = 11

  #cps = 100 2

  #flags = IPv4

  }

The environment variables are:

  $ printenv

  bootargs=root=/dev/mtdblock2 devfs=mount console=ttyS0,115200

  bootcmd=bootm 40000

  bootdelay=3

  baudrate=115200

  ethaddr=00:08:33:33:00:01

  stdin=serial

  stdout=serial

  stderr=serial

  filesize=4a6

  netmask=255.255.0.0

  ipaddr=172.16.16.220

  serverip=172.16.16.70

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





----- Original Message ----- 
From: "Masami Komiya" <mkomiya@sonare.it>
To: "Sonia Martinez" <anexwarrior@hotmail.com>
Cc: <u-boot-users@lists.sourceforge.net>
Sent: Monday, May 10, 2004 11:08 AM
Subject: Re: [U-Boot-Users] TFTP PROBLEM


> TFTP can work fine in 1.0.0, but be affected by network environment.
> What's kind of the server do you use for the host configuration, DHCP, BOOTP ?
> 
> Could you show the console messages ?
> Also I want to know your environment variables.
> That is shown by "printenv" command.
> 
> Masami Komiya
> 
> Sonia Martinez wrote:
> > Hi all,
> > 
> > We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform. We've
> > been able to boot Linux from RAM, with JFFS2 and nfsroot too. But we've a
> > problem with tftp.
> > 
> > We know that the tftp server works because we've tested it with other
> > clients. But with tftp in u-boot we're only able to transfer little files
> > (1, 2 Kb)..
> > 
> > Which can be the problem?? Newer versions work fine??
> > 
> > Thanks in advance
> > 
> > Regards,
> > 
> > Sonia
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email is sponsored by Sleepycat Software
> > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
> > deliver higher performing products faster, at low TCO.
> > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
> > _______________________________________________
> > U-Boot-Users mailing list
> > U-Boot-Users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/u-boot-users
> > 
> > 
> 
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20040510/1b3f416a/attachment.htm 

[U-Boot-Users] TFTP PROBLEM

[Masami Komiya]

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

[U-Boot-Users] TFTP PROBLEM

[DeLaGarza, Robert]

Sonia Martinez wrote:
> Hi all,
> 
> We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform. We've
> been able to boot Linux from RAM, with JFFS2 and nfsroot too. But we've a
> problem with tftp.
> 
> We know that the tftp server works because we've tested it with other
> clients. But with tftp in u-boot we're only able to transfer little files
> (1, 2 Kb)..
> 
> Which can be the problem?? Newer versions work fine??
> 

You've probably checked this, but make sure the cable is good.  I've had 
a bunch of problems with crossover cables in particular.  For example, I 
worked on one board that had no problems with the crossover cable under 
Linux, but under U-Boot, TFTP just wouldn't work.  Using an Ethernet hub 
alleviated this.

I also have a Sony notebook computer that connects fine over a crossover 
cable to a 10Base-T card, but not to a 100Base-T card.

Consequently, I've pretty much given up using crossover cables, for the 
time being.

[U-Boot-Users] TFTP PROBLEM

[Tolunay Orkun]

On 10 May 2004 at 13:20, DeLaGarza, Robert wrote:

> Sonia Martinez wrote:
> > Hi all,
> > 
> > We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform. We've
> > been able to boot Linux from RAM, with JFFS2 and nfsroot too. But we've a
> > problem with tftp.
> > 
> > We know that the tftp server works because we've tested it with other
> > clients. But with tftp in u-boot we're only able to transfer little files
> > (1, 2 Kb)..
> > 
> > Which can be the problem?? Newer versions work fine??
> > 
> 
> You've probably checked this, but make sure the cable is good.  I've had 
> a bunch of problems with crossover cables in particular.  For example, I 
> worked on one board that had no problems with the crossover cable under 
> Linux, but under U-Boot, TFTP just wouldn't work.  Using an Ethernet hub 
> alleviated this.
> 
> I also have a Sony notebook computer that connects fine over a crossover 
> cable to a 10Base-T card, but not to a 100Base-T card.
> 
> Consequently, I've pretty much given up using crossover cables, for the 
> time being.

It sounds like some of you have duplex negotiation or mismatch 
problems.

Regards,
Tolunay