Ping works but UDP doesn't??

Assaf,

it is not clear to me what you mean by opcode 03, 05 and 06270f. Can you elaborate what API you are calling in socket.c and what are the arguments you are passing to these APIs?

What I can say is that the return value of -57 indicates that the socket you are trying to receive from is closed.

Shlomi

Hi,

Hi Assaf,

I managed to reproduce a similar behavior. It will be handled in next release as it requires some debugging and a new patch in the CC3000 itself.

What I can suggest is a work-around that seems to work for me.

Just before binding the socket to the local port address, send dummy data. Then bind the socket and you would be able to sendto/recvfrom with no constraints.

Please let me know if it works for you.

BR,

Shlomi

Hi

Hi Assaf,

The procedure is not exactly as you describe.

The steps are:

1. open a socket on the cc3000
2. send data from cc3000. This is just a dummy data.
3. bind the socket on the cc3000 to a port
4. now you can sendto/recvfrom with no constraints

Btw, reading again your original post, I might understood it differently. You stated that on CC3000 you apply: socket, bind and then recvfrom (sending from another device). In this case, if you are not sending from the CC3000 and only receiving, I do not see any problem.

The error code of -57 means that the socket is not active (or not exsiting). It may be related to the fact that the socket is closed upon timeout.

I'm not sure what is the timeout you use for sockets but for testing you can manipulate it via netapp_timeout_values() API (not as part of BasicWiFiApplication so you need to call this API yourself).

Shlomi

Hi,

asaaf, 

Could you please tell me where you have added this line? Is this under the case: UART_COMMAND_RCV_DATA?

Thanks!

Hi,