This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3000 Basic Wi-Fi example application for MSP430

Hi, 

I have been working on the CC3000 Basic Wi-Fi example application for MSP430 (http://processors.wiki.ti.com/index.php/CC3000_Basic_Wi-Fi_example_application_for_MSP430#Open_UDP_Socket) and have a question regarding the UDP implementation.

Before I describe my problem, here are my setup to get the cc3000 connected to the AP.

1) I download code using IAR and keep in debug mode, as there is an issue regarding the 1.7.2.2 version for hyperterminal.

2) I connected to cc3000 using docklight (alternative to hyperterminal). 

3) Enter "01/r" in hyperterminal to initiate the first time configuration.  I have my laptop broadcast an ssid ="TTTeTP-LINK_339BF20" and got an acknowledge of "Simple config DONE" 

4) Enter "080000000000000000/r" in hyperterminal to initiate the DHCP.  Setting pucIP_Addr and pucIP_DefaultGWAddr == zero will force a DHCP connection.  I then check Client List on the AP and saw the MAC address of the cc3000 with the IP address = 192.168.1.100.  It is pingable.

5) I then tried to perform UDP send data, but have not been able to get it working and I was not able to see the UDP packet data when I was monitoring on Wireshark.  

Here are my steps to performing the UDP:

5.1) Enter "03/r" to open socket for UDP:  

IAR Debug:  ulSocket = socket(AF_INET, SOCK_DGRAM, IPPROTO_UDP);

ulSocket = 0

AF_INET = 2

SOCK_DGRAM=2

IPPROTO_UDP=17

5.2) Enter "0405Hello021111c0a8017a/r" to send data over UDP.  length = 05, data = Hello, socket = 02, port = 0x1111, dest IP = c0a8017a (192.168.1.122).  

I was not able to see the data "Hello" being transmitted wireshark when I sniffing WiFi packets.  In addition, I did not see any packets on my laptop when using wireshark to monitor the interface.  However, when I was in debug and probing the results of "sendto", it returned the value of 5 for the # of bytes transmitted.  

Is there a problem with how the sendto is implemented?

Ben.