• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 40 subscribers
  • Views 402 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Is migration from cc3000 to cc3200 worth the effort

Kumar Nishant
Prodigy 110 points
Other Parts Discussed in Thread: CC3200, CC3100

Hi

I am using CC3000 for my application. CC3200 looks robust as compared to CC3000 but I am slightly reluctant to change my micro (I've already spent a lot of time in development of CC3000 with Arduino Mega). I am using firmware version 1.28.

For me CC3000 is working just fine, with some disconnection issues (but not very frequent). Should I shift to CC3100 or CC3200. Is there any known issues with these new ICs, since they are pretty new and I am afraid there may be issues not known at this time.

I wanted to know that if there is some serious bug with CC3000 which cannot be solved in the current hardware ?

And also, what is meant by "new  CC3000 Release (v 1.14)" which a TI employee Adnan talked about in one of its posts. Is it a new improved hardware or just a firmware?

Thanks.

  • 0
    Expert 2685 points

    The answer to this question (as well as all other questions in the universe) is: it depends.

    I asked myself the same question and have already answered it for myself and this is what I can share.

    The CC3000 has a lot of issues - this is a fact. But it is dirt cheap and FCC certified, so things balance out nicely. I already designed my device to use the CC3000 and spend a lot of time coming up with all the workarounds I need. Now everything is working perfectly and there is no reason for me move to CC3100 or CC3200. Besides the CC3100/CC3200 modules are not out yet - the chips by themselves can be used only for prototyping since they are not FCC certified.

    For the next version of my device I will move to CC3100 and maybe to CC3200 only for one reason - the AP ability. This is something that will increase the value of my device and it is worth the development cost. But, I will do this for the next version, after the current version of my product is already on the market. These new chips will have either the same or new issues that will also need to be addressed. My guess is the time I will spend on finding workarounds will be the same as the time I spent on the CC3000.

    Also I think migration is an incorrect term in this case. The correct one is redesign.

  • 0 in reply to Ivor Sargoytchev
    Prodigy 110 points

    Thanks a lot Ivor. I have decided to stick to CC3000 for now.

    Same as you, I may shift to cc3200 later. 

    And indeed "migration" is an incorrect term here :|