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.

CC3100: works for most networks but not our office network

Part Number: CC3100

We manufacture a device that uses the CC3100 so that it can occasionally update its firmware and other files by connecting through the customer’s WiFi to our server.  Few if any customers have complained that it doesn’t work for them, so we assume they are having no difficulties.  However, here in the office, when we are, for example, testing our product, and we connect to our company’s WiFi to perform updates, the process fails.

We do not believe there is anything wrong with our company’s WiFi network, because it works for everything else, e.g. our work laptops, etc.  We likewise do not believe there is anything wrong with the CC3100 or our device which uses it, because, as noted above, it seems to work when connected to any other network (including when we use our phones as hotspots).  Rather, we believe there is some incompatibility between the CC3100 and our network configuration.

To help us troubleshoot this problem, are you aware of any possible network configuration which, in most cases, works fine, but which, when talking to a CC3100, fails?

  • Hi Rodney,

    i will dare to use this thread since we have the same problem with our device with CC3100MOD network processor on board.

    In our case, CC3100 operates as a station connecting to socket server. In most problematic cases reported by our clients, CC3100MOD would manage to connect to socket server but won't receive any packets from server or packet loss is 99% or more. There is increased rate of error -452 (SL_ESECCLOSED) when calling sl_Recv function in this case. Both, secured and non-secured TCP socket were tested but there was no improvement.

    On the other side, sending packets to socket server is successful in most cases.

    We've questioned our customers regaring their network equipment, ISPs, router configurations etc. but there is no obvious "pattern". Anyway. most of customers that were reporting problems are using 4G modem/WiFi routers of various brands and ISPs BUT this is not limited to 4G network. We've "accidentally" discovered that the same problem can be reproduced if i configure wireless network adapter on my laptop as an access point and bridge it to "wired" network adapter to provide internet access. Wireless network adapter in this case is Intel(R) Centrino(R) Advanced-N 6205.

    When device with CC3100MOD NWP is connected to this AP, most of packets from socket server are not received on CC3100.

    We established network traffic monitoring on network adapter with Wireshark and we can see TCP packets from socket server that are then transmitted and re-transmitted to our CC3100MOD device but they aren't received.

    Every other wireless device that is connected to this test setup operates normally including our previous generation device that uses obsolete CC3000 module. I should stop at this point since there are a lot of painfull memories of CC3000 module...

  • Some more information on our network. We are on an Ubiquiti Unifi Network running Unifi AP AC Pros. For some reason the CC3100 sees each individual Access Point instead of a single SSID for the wireless.
  • Primoz,

    Can you please share your Wireshark captures?

    Jordan,

    I am assuming you are using some flavor of our OTA example to perform these updates. On the device side, are you getting any error messages on any sl_ functions, and if yes, can you share them?


    Thanks,
    Vince
  • Also, verify your firewall settings. This is often setup in a office enviroment, and could be blocking traffic you need.

    Vince
  • At a minimum there is at least one error returned from sl_Send().  Of the errors that we are logging that is the first one on the list after an update attempt.  It could be that there were previous ones that were not logged, and some of the subsequent errors logged were sl_ functions.  It looks like the socket is opened successfully, but the first attempt to send fails.

  • I performed packet capture from my firewall I can share those results. These are the most verbose logs I have available. The firewall does not appear to be blocking anything and there is no packet drops or blocks.Logs 1-2-19.txt

  • Rodney,

    We will need to see where in the OTA process the device fails to debug further.

    Jordan,

    If possible, can you post another E2E thread on your issue? It will be easier to manage both questions this way.

    Thanks,
    Vince
  • Vince,

    I work with Rodney so this is an addendum to the same issue.

    Jordan

  • Okay, no problem.

    I would try running our example of OTA from the SDK, and see if that works on your network. If it does not, then we know for sure it's something with your network configuration.

    If it works, then we can look at your code for the OTA, and see where we are failing to try to diagnose the issue.

    Best Regards,

    Vince