We tested our embedded devices (which includes the CC3000) with different wifi routers and it worked fine. Now we are surprised to received the following problem report from our customer that the device does not connect to the cloud. Unfortunately the device is in Australia while our office is in Europe.
The connection from the reader wouldn't go through to the net, but I could see a ip address being assigned.
If I push google dns 8.8.8.8 through the dhcp settings to the reader it would work and connect out
but If I use the router address to forward DNS from the device, the connection would fail
Is it possible that the CC3000 has a problem when the router does also act as DNS server?
The CC3000 on our devices have SP 1.10. How serious are the bugs fixed since?
I know the release notes page: [http://processors.wiki.ti.com/index.php/CC3000_Release_Notes]
For me, some of the descriptions are quite cryptic and I can not guess if a certain fix has some relevance to my problem.
A CC3000 firmware update within our devices is not that easy it is therefore essential to know if an update would solve the problem. I think the customer is willing to pay for the development (porting) of the patch programmer when he can be sure that it works afterwards.
Would you start a product recall from around the world to perform a firmware update in the CC3000?
We make use of the following functions in the SimpleLink Library:
- wlan_add_profile (up to 7 profiles for different AP)
- gethostbyname (to get the IP address of the server)
- socket, connect, send, recv, closesocket (to communicate with the server)
