Hi @chage, no I’ve not had problems getting the IP for “www.ti.com”, and I’m on a satellite network. Might pay to check the DNS settings in the router/ssid you are connecting to. Can you get good resolution of DNS lookups from a regular client device (like a PC) connected to the same router/ssid.
Peter
I have tried tweaking and checking my router settings, nothing seems wrong. Yes all my other clients can connect and get resolution without issues (win PC, mac OS, android, iOS), only this tiny little thing refused to work…
I am sure this is too much to ask for, if by any chance you run the wlan_station project again, can you set a breakpoint on the SL_NETAPP_IPV4_IPACQUIRED_EVENT handler and see if there is any DNS in the event response?
I constantly get both acquired IP and gateway IP, but the DNS is 0.
Will do. Might be a few days before I get back to it as I’m trying to finish off something else right now 
You are sure your DHCP server has the DNS address right?
I will think that it is correct. I did a ipconfig /all from windows and it returns the right DNS value, is that a good indication that the router DHCP and DNS is working properly?
Well, you made me check! My router is my DHCP and DNS agent, and the event packet have all three correct: IP - 192.158.1.106, GW - 192.168.1.1, DNS - 192.168.1.1. Not much help, I know, but at least you can be pretty sure its not the 3200 or the host software. I’d recheck your router configuration.
thanks for checking!! you rock!
just curios, is your router running DNS? why is it pointing the DNS the same as GW? I will expect DNS to be an external IP.
Actually it make me wonder if the host software is having issue dealing with my router setup, I can’t really be sure it is the router fault since all other system connect to the same router without issue.
It’s just a regular $20 Netgear router from Walmart. I think its the way most of them work. It gets its DNS settings when it does the PTP connection with the satellite modem to establish the WAN connection. So it acts as the DNS agent to the real DNS out there in Dish land somewhere. Just passes the DNS requests thru, I imagine, Don’t know much about, just that it works.
still no luck. Inspected the DHCP traffic using wireshark and confirm the router returned DNS records in DHCP offer stage. It is returning an external DNS IP, not as in your case where it return same IP as gateway. Anyway, the DHCP offered DNS are matching those return from ipconfig /all.
So I assume DHCP is behaving fine on the router, am i missing anything? clueless now…
If its there on the network but no in the packet delivered to the event handler then it must have disappeared during the creation and queue of the event data. If it works for me and not for you, I’m wondering whether you followed the instructions in the Project0 directions and recompiled the SimpleLink and Driver projects! If not, try that and see if it makes a difference.
I just switch to another AP (freedompop) and everything works fine from connecting to the AP and pinging external host, so we can eliminate possibility of project0 issue. Looks like this is related to the previous linksys router settings, i posted this issue on TI forum as well and some gentlemen is looking at it, hopefully I can get some hint from there. I will keep it posted here.
Happy to hear its working . I’ll be interested to hear what the problem was with the LinkSys
Pra, just an update. issue resolved after some debugging with TI support. refer to this thread from TI forum http://e2e.ti.com/support/wireless_connectivity/f/968/t/351524.aspx?pi307168=2 on the details.
Makes sense. That was great teamwork between you and TI to get that resolved
Great to see some more work has been done on this. Has anyone been able to port over the spark and have programs up and running yet? i know it was the plan and if so i may have missed it.
With so many pins that can all be used for virtually anything i could see this chip be connected to separate base boards that all for more of the pins to be used, say a 20pin board or a 100pin board
no need to buy new processors and wireless that way 
Just FYI for anyone on a 3.12 kernel or later the modprobe arguments for VID/PID are no longer used.
From: modprobe ftdi_sio errors / Kernel & Hardware / Arch Linux Forums
From kernel 3.12, the ftdi-sio module no longer accepts the "vendor" and "product" parameters(commit link).
I think it was assumed that this was a debugging feature that should
not be used by end users, and so the change was not at all publicised.The
new way to add a new VID/PID pair for the ftdi-sio driver is to write
them both, one after the other, to /sys/bus/usb-serial/drivers/ftdi_sio/new_id
# modprobe ftdi-sio
# echo 0451 c32a > /sys/bus/usb-serial/drivers/ftdi_sio/new_id
Good to know. I’ve added that to a Hackpad that I’ve been using to collect everything that I know about getting it to run: https://hackpad.com/Using-the-CC3200-Launchpad-Under-Linux-Rrol11xo7NQ
(Anyone is free to add to it if you see something missing or wrong.)
We uploaded a patch file for the latest version of Nuttx (V7.5) to our server at http://www.droidifi.com/nuttx_droidifi_cc3200_2014-08-19.patch
Instructions -
git clone http://git.code.sf.net/p/nuttx/git nuttx-code
cd nuttx-code/nuttx
patch -p2 < nuttx_droidifi_cc3200_2014-08-19.patch
Use the nuttx buildroot script to build an arm compiler and tools (see the Nuttx documentation) or install via apt-get.
Run -
cd nuttx-code/nuttx/tools;./configure.sh cc3200-launchpad/nsh
cd nuttx-code/nuttx; make
The openocd config file is in nuttx-code/nuttx/configs/cc3200-launchpad/tools.
See Azdle’s Hackpad page or the Nuttx documentation for more info.
We will have a firmware flashing tool for Linux available shortly. Check back for updates.
Just wondering how it is going with the CC3200? 
Nuttx has been patched directly to support the CC3200. You no longer need step 2) above.