Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

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.

CCS/CC3220SF: Creating a WiFi dongle that connects to a windows computer

Part Number: CC3220SF

Tool/software: Code Composer Studio

Hello All,

I am struggling to find where to start to create a WiFi dongle using the cc3220SF. I want to have the CC3220SF connect over USB to a PC in order to give the Access point internet. A cell phone would be able to connect to the CC3220SF and use the internet as if it connected to a regular home router. Ultimately, I want to be able to implement text over WiFi (RCS) communication from a cell phone to the CC3220SF.

Is there an example project, or readings I can look at to get started. I have looked at the portable with WiFi project in the Simple Academy workshops. Or is there a different part that would work better?  

I currently have a CC3220SF Launch pad and am running code composer 10.

Any help would be greatly appreciated.

Thanks,

Tyler

  • Hi Tyler,

    CC3220SF is not best device for this use case. It is not expected such use case and from this reason CC3220 does not support routing capability by default. You will need to implement many features by yourself, and this will required very big quantity of work at your side.

    It may to be a interesting research project, but value of developed device will be low. I think for your use case will be better use old router with OpenWRT capability or something like that.

    Jan

  • The only routing I want to perform is wifi texting, no other internet or routing functions. Is there a chip offered by TI that is designed to do this function? We want to be able to put this design on a board the size of a launchpad. I will look into the OpenWRT for now. Thank you for your help!

    -Tyler

  • Hi,

    I am not sure what do you mean by wifi texting. Can you better describe your needs and how concept of your application will work? Maybe some drawing will be useful.

    How will look interaction with your PC via USB? Do not forgot that CC3220 does not have USB interface. USB interface at LaunchPad is done via on-board debugger XDS-110. This chip will create virtual COM port at your computer and you will need your application running which will be able talk via this COM port with your CC3220 app.

    Jan

  • Basically, rather than an SMS being sent over your cellular data, the connection is established over WiFi using EAP-SIM or EAP-AKA authentication with the phone carrier's radius server. That way the person receiving your text message will see it as a normal text. It is very similar to imessaging on Apple devices. This type of wifi calling/texting is enabled on your phone through the messages settings. The phones must have rich communication services (RCS) setup to work.

    Here is an image of what our setup would look like.

    Initially we want our data to pass to and from the CC3220 to our computer/server so we can determine what information is sent over the link. We then want to implement some processing of the calls on the CC3220 in order to reduce the traffic on our eventual satellite link (USB or serial initially).

    Tyler

  • Hi Tyler,

    CC3220 devices does not support Enterprise security at AP mode. Also it will not be easy to implement routing from Wifi AP via USB/com port. Although implementation of such features at CC3220 could be possible, it will requires enormous quantity of work.

    Much easier will be to use device with OpenWRT capability or use Raspberry Pi. Implementation of such features at devices with Linux capability will be muh more easier.

    Jan

  • Thanks Jan,

    This has been helpful in figuring out where to even begin on this project. OpenWRT routers that support Radius server integration appears to be the way to go. I have never worked with routers before. The ultimate goal is to put the project in a portable device, so power consumption is important. As well, we do not require a very fast connection. In fact, all the routers I have seen appear to be major over kill for what I want to do. Do you have any suggestions on router chipsets that are low power?

    Thanks,

    Tyler

  • Hi Tyler,

    I am sorry, I am not able to recommand you a right chipset.

    Jan

  • Hi Tyler,

    For applications where you need to be able to route packets and bridge networks, I suggest you look into the Wilink products:

    http://www.ti.com/wireless-connectivity/simplelink-solutions/wi-fi/overview/wilink-combo-solutions.html

    These are devices designed to work in a Linux system, with higher performance than the CC32xx.

    As the typical setup of a Wilink device pairs it with a microcontroller running Linux, you will be able to use the Linux network stack for routing and high-level networking operations. You will also be able to use Linux tools and utilities, including its EAP supplicants. This is since the WL18xx devices only provide the low-level 802.11 MAC/PHY, which is unlike the CC32xx products which integrate the TCP/IP and TLS stacks as well.

    The suggestion by Jan to use a raspberry Pi type platform would make sense, and we have the Beaglebone Black + Wifi cape combination which fits that concept. You can find some details as to what that entails here:

    https://processors.wiki.ti.com/index.php/WL18xx_First_Time_Getting_Started_Guide_(Beaglebone)

    Do note that this solution won't be as low power as the CC3220. That being said, even if you were able to implement a custom stack on the CC3220 to support this use case, power consumption will likely be relatively high. This is since the CC3220 power numbers assume that you are operating the device in STA mode, not as a soft-AP. In AP mode, the CC3220 will be required to constantly wakeup and broadcast beacon packets at a minimum, in addition to responding to any data sent by the phone.

    Regards,

    Michael