Experimental Physics and
Industrial Control System

Andrew Johnson <[email protected]> · Wed, 01 Mar 2006 16:07:00 -0600

Dale L. Brewe wrote:

OK, so if I understand this, you're saying the bootROM client downloads
the boot image and disconnects before the data connection is closed,
before the server is listening for the command, and the server sits
there waiting until it times out. But, if the bootROM client has
successfully downloaded the file, shouldn't I see it boot, and then hang
when it tries to download the script file because the server is still
waiting on the original connection? What I see is basically nothing
happening for a long time, then after the seven minutes are up, I see
the vxWorks logo and such, then the script file is downloaded very
quickly.

I think you got the order mixed up slightly there: the vxWorks client
gets all of the data, but then as part of its tidy up procedure it sends
a QUIT command to the server *before* closing the data socket. The
server however is insistant on fully closing the data socket before it
will listen to the next command though, so it waits until that close
process times out (a TCP socket timeout of some kind) before it will
accept the QUIT and actually close the command socket. This matches
your symptoms because the file transfer is not regarded as completely
over until the connection has been closed, so the bootrom won't continue
on to print the logo until then.
Also, I've noticed a problem w/ WS_FTP trying to download the
same vxWorks.st from the same server - in that case I get a graphical
indicator and it looks like the file transfer itself is very abnormally
slow.

I don't know what's happening there, but it's a different client anyway.
- Andrew
--
There is no S in exprexxo.

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System