cc3200 ethernet and bluetooth

Hi Stefano,

I cannot answer your question directly, however I recommend you looking into the following:-

Regarding Ethernet, I recommend you look into the EK-TM4C1294XL - Tiva C Series TM4C1294 Connected LaunchPad  which has on-chip 10/100 Ethernet MAC and PHY. You could then use one of the boosterpack headers with the CC3100BOOST - SimpleLink Wi-Fi CC3100 BoosterPack

Regarding Bluetooth, you could use the PAN1323ETU which plugs into the BOOSTXL-SENSHUB - Sensor Hub BoosterPack and you could then use the 2nd BoosterPack headers on the TM4C1294 Connected LaunchPad.

Alternatively, you might want to consider the WiLink family of chips from TI, these offer Wifi and Bluetooth integrated together on one chip. You will however require a Linux or Android host operating system, as all the TCP/IP stack etc. will need to be provided by the host device. More information: http://processors.wiki.ti.com/index.php/WL18xx and http://www.ti.com/lsds/ti/wireless_connectivity/wilink/overview.page?paramCriteria=no

Glenn.

Thanks Glenn

It is what I suspected. CC3200 is  a very nice product , however it is fully oriented to wifi applications. I Just was thinkong if the itnernal tcp-ip stack could be eventually deployed on an external compoent in order to managa also an ethernet interface.  But I believe it is not possible.

Stefnao

Stefanao, your understanding is correct

"...deployed on an external compoent in order to manage also an ethernet interface. "

You mean like connect to your internet router, PC, Android Mini PC or Tablet that has a physical Ethernet connection with a physical Ethernet connection on a CC3200 instead of wirelessly through WiFi? 

I think that would be taking a step backwards.  But I know what mean. :)

... Somewhere someone at TI is shacking their head saying "I went through all that trouble to eliminate a physical connection and now their asking for Ethernet??" LOL!

I suggested this question since a nice component as cc3200 should contain a TCP-IP stack on top of wifi layer. So , since I need a device with wifi but also an additional ethernet port for some installations ,  I was thinking : Since there is a TCP-IP stack ( usually to be placed on  top of Data link and Physical layer ) , Why is'nt it possible to recycle it to connect an extra ethernet port ?  Lots of application can receive great benefit from a wifi connections , but many customers have still prejudice , expecially when safety requirements are tight , against wifi and the possibility to have some 'man in the middle' problems. So an extra ethernet port could solve goad and cabbage .

Stefano

Very true Stefano.  But if safety and security are your main concern, then you wouldn't be using a Wifi device in the first place.  Having both options in this case would only put your setup at risk if someone should somehow enable the Wifi connection.

As Glenn pointed out, the Tiva with Ethernet is a better solution.  It is similar enough to the CC3200 to make working with the two manageable.

Thanks,

In your reply, you are touching my current problem. 

First Info : My application does not run an OS. Partly because It has to be low cost.

I currently consider using the CC3100 modules currently being certified. The TCP and UDP stacks are available as source code from TI.  This code seems easy to port, quite compact and is not related to any OS. That really seems OK  to run that code on my own "little" MCU.

Because I have doubts about the maturity of this product (module for the CC3100, and CC3100 itself), I studied today the Wilink modules. The WL1801 would be OK for me.

However, I don't understand why the code provided to drive the WL18x is only designed to be run on an OS.  

Is it easy for me to use this chip without an OS, while not having to rewrite all the source code ?  

Why only talking about these big Arm Cortex A8 ?  Does that mean the WL1801 needs a very powerful processor ? I this is the case, can you explain why ?

Could I manage the WL1801 with just the MSP430F5x ? And less than 32KB of binary for the Stack ? (FYI, binary size with example firmware for UDP in/out on CC3100 is about 17Kb non optimized)

In terms of maturity of product, how is the WL1801MOD as compared to the CC3100 Module ? 

Laurent CHABIN1 said:

I currently consider using the CC3100 modules currently being certified. The TCP and UDP stacks are available as source code from TI.  This code seems easy to port, quite compact and is not related to any OS. That really seems OK  to run that code on my own "little" MCU.

You would not need to port the TCP/IP stack to your MCU, this is provided with the CC3100 within its own MCU (Network Wifi Processor). You would just need to communicate with the CC3100 APIs using SPI or UART.

Laurent CHABIN1 said:

Because I have doubts about the maturity of this product (module for the CC3100, and CC3100 itself), I studied today the Wilink modules. The WL1801 would be OK for me.

I believe a new product that is mostly bug free, is much better than a mature product full of bugs (this is not in reference to the WL1801MOD, but products in general). The CC3100 has had a lot of testing with many people already designing products with it, and the lack of reports of issues in this forum is a testament to its quality. 

Laurent CHABIN1 said:

In terms of maturity of product, how is the WL1801MOD as compared to the CC3100 Module ? 

The WL1801MOD was never designed to work with a small MCU, it was designed to work with a device which has a host OS. I really believe you would have a lot less issue with the new CC3100 that was designed for your little MCU, then trying to get a module working that was never designed for it.

Glenn.