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.

CC2640 and CC2650

Other Parts Discussed in Thread: CC2640, CC2650, CC2630

Hi,

I am planning to build a proprietary wireless system with CC26XX series if possible to take a low power consumption feature of the series.

But I want to check the feasibility before I commit.

Questions, 

1. Based on technical doc, application of CC2640 is limited to Bluetooth. Does this mean CC2640 can NOT be used for a proprietary system?

2. CC2650 is for multistandard, does the multistandard include a proprietary spec? Or is it limited as listed in the  datasheet such as Blueetooth, ZigBee ...

3. If CC2640 is only for Bluetooth and CC2650 is for multistandard, what are the hardware difference between those two? Rough comparison of them doesn't show any difference.

4. Is there any plan to make automotive qualified product of the series?

Thanks,

Inseop

  • Hey Inseop,

    Inseop Lee said:
    1. Based on technical doc, application of CC2640 is limited to Bluetooth. Does this mean CC2640 can NOT be used for a proprietary system?

    Wrong. CC2640 supports proprietary protocols as well. CC2640 does not support ZigBee/6lowPAN/RF4CE etc.

    Inseop Lee said:
    2. CC2650 is for multistandard, does the multistandard include a proprietary spec? Or is it limited as listed in the  datasheet such as Blueetooth, ZigBee ...

    CC2650 is limited to the radio modes described in the datasheet

    Inseop Lee said:
    3. If CC2640 is only for Bluetooth and CC2650 is for multistandard, what are the hardware difference between those two? Rough comparison of them doesn't show any difference.

    CC2640 is designed for Bluetooth low energy (Bluetooth Classic is not supported). The differences are related to amount of testing that is performed on the devices. For a product developer, CC2650 and CC2640 should be transparent in the example of Bluetooth low energy, in the same way as CC2630 and CC2650 is transparant for ZigBee.

    Inseop Lee said:
    4. Is there any plan to make automotive qualified product of the series?

    That would be a great idea, although I do not have any details. Please contact your local TI Sales representative for enquiries regarding roadmap etc.

    Best Regards

    Joakim

  • Joakim,

    Thanks for the prompt answer. I guess it is getting clearer but got couple more questions.

    1. Only hardware difference of CC2630, 2640, 2650 is PHY.
    CC2630 supports only QPSK DSSS for Zigbee
    CC2640 supports only GFSK FHSS for BLE
    CC2650 supports both QPSK DSSS and GFSK FHSS
    is this correct?

    2. Use CC2640 as 2.4 GHz(ISM band) tranceiver and implement own stack not using BLE stack. Is this possible?

    3. If case 2 is true, what is the maximum air data rate that CC2640 can achieve with permitting RF performance?

    Thanks,

    Inseop
  • Hi,

    Both CC2650 and CC2640 will support proprietary mode, however, this has not been characterized yet. The max datarate will then be 5 Mbps. 

  • So you're saying that at some point in the future documentation for the radio interface will be released so that we can write our own proprietary radio stacks (mesh networks, etc.)?
  • That is correct:)
  • Hi CHS and Jaokim, do you have any idea what the road map and time frame for the proprietary radio might be available? It seems in some of the forums there was notes about a previous data sheet that had a chapter about this... I've not been able to find it.. I have to make a design decision shortly, about what IC's to use. 5Mbs-1 is very interesting! thats plenty fast enough for me. ( 2M )..

    How do i get some more information on this.. Can I get a connection to the TI sales team somewhere..

    I have the 2650 Dev Kit, here, and ready to rock!
  • My sources tell me that the CC2640 does not in fact offer proprietary mode, which I think does not make any sense. Why would I want to buy the almost twice as expensive CC2650, if I only plan to use the proprietary mode, and not any of the licensed protocols?

    What's up with that?
  • Sorry, missed this one. I do not know if you have gotten any feedback elsewhere, but 5Mbps and 2Mbps modes are beeing tested now so we should be able to share more on this very soon.
  • Christiaan, CC2640 supports proprietary mode.
  • That is good news! So let me get this straight: if we roll out a product with the CC2640 right now, we can later update our firmware to make use of the proprietary mode?
  • Christiaan,

    Note also that our BLE stack does not currently support concurrent (with time slots) radio protocols with BLE + proprietary. Currently the only solution is to re-boot and start up the needed radio stack.

    Regards,
    Svend
  • Thanks CHS and svendbt for the responses!

    It's good to hear that there is an update path. We realise we cannot run the stacks in parallel. If we would need that, we could implement that ourselves I guess.
  • CHS said:
    yes

    So we spoke to our local distributor again, and they said that proprietary radio mode will only be officially supported on the CC2650: TI will not give you support if you have any issues with it on the CC2640. They got that information from the local TI office...
  • Hi,

    I have checked internally here in Oslo, and the CC2640 do support proprietary mode. so my answer is still correct. Unfortunately your distributor and local TI office have the wrong information. Thanks for the feedback on this, I will push internally on improving the information we provide externally on this matter.