1 of 1 people found this helpful
1. It looks confirmed as an issue as expressed in this thread: wiced_tcp_packet_send dropping data?
2. We buillt our wifi layer with WWD + LWIP with some modifications to make it work with our RTOS (not implemented by WICED). The advantage of WWD + LWIP is more granular control of your data flow, i.e. stack data like you want, control your sending timing more, ect. The downside is that if you want to use other WICED features, for example the currently proposed security implementation (in beta I beleive) then you can't do it. Those feature sets require all of WICED to be implemented to take advantage of all the different WICED threads. Also, without WICED you need to manage your connection yourself, like scanning, connecting, authenticating, DHCP stuff, reconnecting, disconnecting. It's not too burdensome to do, but it does take a bit of implementation and refinement. We've been running with WWD + LWIP only for a 2-year old product with a BCM43362 and for about 6 months with a BCM43341
Will it cause any problems if I have different sockets using different APIs in my system?
For examples, one socket is created by wiced_tcp_create_socket(), and another by lwip_socket()?
I don't have an answer for that because I have never tried it and I haven't looked enough into the wiced calls.