recvfrom 'known limitation' for UDP packets

Sachin Agrawal

Hi TI,

As per release notes, CC3000 will not provide UDP packets one-by-one to the Host.

We believe that this is a sever limitation in regards to using this device for any generic/standardized protocols which depends on UDP (such as: MDNS, CoAP, mesh networking, multicasting etc) or anywhere else where you would want to make your device compatible with somebody else's implementation of the same protocol.

Can TI provide some kind of workaround such as putting Sender IP/Port and Data length in front of the packet?

CC3000 is a great solution in many other areas for IOT field and do not let this issue become a blocker :(.

Please re-consider providing a resolution for this issue.

Thanks

Sachin

over 9 years ago

0 Raghavendra Shenoy over 9 years ago

TI__Mastermind 27095 points

Hi Sachin,

At present we do not have the plans to provide a fix for this.There is another thread where a similar issue was discussed, please refer to this if any of it relates to your issue(http://e2e.ti.com/support/wireless_connectivity/f/851/p/298482/1150033.aspx#1150033). Or is it strictly limited to compliance with 3rd party devices and applications?

Thanks & Regards,
Raghavendra

0 Anthony Wieser over 9 years ago in reply to Raghavendra Shenoy

Intellectual 320 points

I think that's pretty much the death knell for this chip for us then.

There's no way to prevent something sending a udp message of a different length than our predetermined fixed length on the network, so there's no way that you can use UPD.

This whole exercise with this chip appears to have been a colossal waste of time. I should have given up two weeks ago as was my first instinct.

This is the release note mentioned:

http://www.ti.com/lit/er/swrz044b/swrz044b.pdf

Wi-Fi

Wi-Fi forum

recvfrom 'known limitation' for UDP packets