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.

CC2650: Can I use a CC2650 Launchpad as a host MCU for a bluetooth/wifi enabled LF-RFID project?

Part Number: CC2650
Other Parts Discussed in Thread: CC2640R2F, CC2652R, CC3200

Hi There,

I would like to know if I can use the CC2650 as a host MCU for an LF-RFID project. I need to interface an analog front circuit with it. At the same time, I would also like to have bluetooth/wifi functionalities or be able to add them in the future. 

Best,

A

  • Hi Azim,

    If you are wanting both Bluetooth and Wifi in a single chip, I think something in the Wilink family of devices would be a better fit for you: www.ti.com/.../wilink-combo-solutions.html

    Regards,
    Katie
  • Hi Katie,
    Are there any launchpads for the same just like CC2650? Or would the CC2650/2640R be good to go for the LF-RFID application.
    Best,
    A
  • Hi Katie, I did see a CS3220, which has WiFi but not bluetooth. I think the CC2650/CC2640series are only for Bluetooth applications, am I right?
  • Hi Azim,

    The CC2650/CC2640R2F only support Bluetooth but not Wifi. However there are Wilink devices that support both Bluetooth and Wifi together: www.ti.com/.../products.html

    Regards,
    Katie

  • Hi Katie,

    I mentioned the CC2650/2640 series, as I was informed about it. A launchpad or an MCU dev kit would be great. The 3320s/sf looks good taking into consideration that it supports both WiFi and Bluetooth. Do you address any queries regarding MSP432 on here? or would you like me to post them in the forum? I just wanted to know if the MSP comes with inbuilt wifi/bluetooth modules or should add booster packs to enable the same.

    Best,
    A

  • Hi Azim,

    MSP432 queries will get better answers if posted in the MSP forum. However the MSP doesn't have built-in Wifi/Bluetooth hardware - you'd have to add boosterpacks/other chips. However there are examples for MSP432 for Bluetooth or Wifi when used in combination with another chip like one of our Bluetooth modules, but you'd also need to still add a wifi chip e2e.ti.com/.../maximize-your-iot-design-with-new-dual-mode-bluetooth-msp432-mcu-bundle. I don't know if there are any examples about using all of those at the same time in the same environment however - I believe that would be one advantage of the Wilink parts in that they are already designed to be able to use the Bluetooth and Wifi in the same environment.

    Since there are so many protocols you are talking about integrating there are a lot of different ways to go to be honest:
    - you could have an MCU like the MSP432 connected to a bluetooth module and a wifi module,
    - you could have a microcontroller with integrated bluetooth like the CC2652R (you probably want the largest memory you can get if you're adding so many other things which is why I recommend this one) along with a wifi module,
    - you could get a wifi processor to do all your main functions and add a bluetooth module
    - you could use something like the Wilink parts I mentioned to do it all in one.
    There are probably yet more options. It is something you will have to decide for your own particular use-case to balance your system requirements.

    Regards,
    Katie
  • If you want to go all Launchpads, you might want to do like this post and use CC3200 Launchpad + CC2640R2 Launchpad: e2e.ti.com/.../600843 You can write code for them to communicate using some sort of interface.

  • Hello Katie,

    Thank you for the inputs.

    I am looking for something to start with. I see that the CC2650 is a good option to begin with. It also reduces the trouble of having multiple booster packs for adding features on the MSP. All I need for the first phase of the project is Bluetooth and be able to control the hardware and implement some decoding alogrithms to read encoded user data. I think the CC2650 would be fine to meet those requirements for now. For future implementations, the CC3220 series could be considered.

    Best,

    A