I haven't played around with the socket library since they came out with EDK 6.1, but I seem to recall that at the time, only one side (server side) had been implemented, which would explain why there is only a xilsock_accept, and no xilsock_connect. Additionally, I remember many a discussion (you might want to do an archive search) on this NG about the flakiness of the socket library (I was hoping it had been improved with
6.1, which version are you using?). For what it's worth, I personally never got it to work reliably. However, from what I can tell of the code I have, xilsock_accept was blocking. If you want to compare your non-working code to my non-working code (I seem to recall that I could at least accept connections, however unreliably), I'd be happy to make it available, although I heavily based it on the (MicroBlaqze) web server example I got from Xilinx, which I assume you've already looked at.
Has anyone out there ever gotten the xilsock library to work reliably? I don't want to waste any more time on it unless there's a good chance of success at the end...
--
Pierre-Olivier
-- to email me directly, remove all _N0SP4M_ from my address --
Jimbo wrote:
> Does anyone know why Xilinx' socket function library, xilsock.h, does
> not contain a xilsock_connect() function?
>
> Also, do you know how xilsock_accept() works? It appears to be
> non-blocking by default. Is this the case?
>
> At this moment, the client I have running on a windows PC is getting a
> WSACONNREFUSED error when it attempts to connect() to a socket on the
> V2Pro. The server on the V2Pro is spinning in a loop that executes
> xilsock_accept().
>
> I've tried various port numbers and the connect error is the same. If
> you have any insight from just this info, please let me know. Also if
> you have the time and would like to see the code, I'd be happy to
> email it to you. Or I can probably post it here later.
>
> Thanks,
> Jim