Hello,
Customer of mine is trying to get the sensor app up and running, can you please offer some assistance here:
I am working with MSP-EXP430FR5739 board and CC3000 WiFi module model TiWi-SL. I am trying to get the Sensor Demo app to work. The problem I am hitting is when the PC (the GUI app) initiates connection, connection never gets established. Network analyzer shows the packets are sent and received back and forth correctly for a short while, but after 2-3 successful SYN packets there is SYN packet sent from the PC to the device, that never gets any response, like it's never received by the device. The behavior does not seem to be always the same, sometimes I think I see data packet (with payload 'DATA' in ASCII) but no response. Sometimes there is a short (<1s) visualization of the blue "moon" in the GUI but it quickly disappears.
DHCP works always, and I can always send data out over UDP in my test app, and sometimes (randomly) I can even establish an outgoing TCP connection, but as soon as I start sending over TCP the MCU starts behaving erratically and I cannot step over machine instructions in the debugger.
Thanks,
Jason
---------------------------------------------------------------------------------------------------------Please click the Verify Answer button on this post if it answers your question.---------------------------------------------------------------------------------------------------------
Hi Nikola,
Also try setting the policy as:
wlan_ioctl_set_connection_policy (1,1,1);
You may check this link, it shows how to add the policy:
http://processors.wiki.ti.com/index.php/CC3000_Host_Programming_Guide#Using_WLAN_policy_and_profiles
For example you could try something like this:
err = wlan_add_profile (WLAN_SEC_WPA2,"TP-LINK", 7, NULL, 0,0,0,0, "sifra123", 8);err = wlan_ioctl_set_connection_policy (1,1,1);wlan_stop(); __delay_cycles(600000);wlan_start(0);
Pedro
Hi Gustavo, Pedro,
I have tried both of your suggestions for connection policy but the result is the same.
Regards,
Nikola
I would like to upload my test app, in case that might help. How do I use upload in this forum?
Use the Insert File (the clip icon), see below.
Regarding the policy, could you try to see if the open security works, for example:
err = wlan_add_profile (WLAN_SEC_UNSEC,"TP-LINK", 7, NULL, 0,0,0,0,NULL, 0); err = wlan_ioctl_set_connection_policy (0,0,1); wlan_stop(); __delay_cycles(600000); wlan_start(0);
Ok, I see the button. Here is my test app attached.
Nikola 5270.StartUpWiFi Application.zip
Setting a non-secure profile worked. I can connect wlan and tcp. So there has to be something wrong in the way I am specifying security settings. Does CC3000 driver support WPA?
I will try other methods.
I've tried all other encryption methods and none of them works. Has anyone been successful in using secure wifi with profiles?
Is there anything i can do to get more information? Should I re-implement profiles using wlan_connect method and scan for networks myself? but then i will soon run out of FRAM space.
Nikola,
I hope you took into account the fact that the 1st time a profile with security is used, it takes about 6 seconds to calculate the key.
I recommend that in the meantime, that you use the wlan_connect. It also creates a profile (if the policy is set that profiles be used).
Why do you need to scan for networks manually? The CC3000 does that all by itself.
Regards,Gustavo
Gustavo,
Great, wlan_connect really saves profiles and automatically scans next time connection is lost. But i can't delete the profiles saved with wlan_connect by using del_profile. what would be the procedure to delete a profile created this way?
Did you read somewhere that del_profile doesn't erase the profiles created by wlan_connect? I had the understanding it does.
I tested wlan_ioctl_del_profile today and it failed. But i have found another way of deleting profiles (set policy 0,0,0 and restart device), so i don't worry too much about this any more.
Another problem with wlan_connect is that it does not save the profile into NVMEM unless it is able to connect. This would prevent us from setting up the device on one's PC or Mac at home and then using it on another network. The device actually has to be connected on a network to be set up. Is there a workaround for this limitation?
Could you try something like this:
err = wlan_add_profile (WLAN_SEC_WPA2,"TP-LINK", 7, NULL, 0,0x18, x1e, 0x2, "sifra123", 8); err = wlan_ioctl_set_connection_policy (0,0,1); wlan_stop(); __delay_cycles(600000); wlan_start(0);
The arguments in bold are constants. Could you try this.
Yes, this worked! This allows us to program a profile if needed outside the wi-fi network range.