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.

CC3200STK-WIFIMK: Firware source availability

Part Number: CC3200STK-WIFIMK
Other Parts Discussed in Thread: CC3200, CC2650

Hi,

After playing with the cc2650 in both sensortag and launchpad variants I had a client request I do some customisation to the wifi sensortag counterpart as the base for a proof of concept. I ordered a couple of cc3200 sensortags (as that is the device the client hopes to use for demos). I assumed things would be as simple and straightforward as TI has gotten me used to, so I even ignored the "For Wi-Fi development and prototyping, TI recommends the CC3220SF LaunchPad development kit featuring the CC3220SF wireless MCU." warning on the order page.

Receiving the sensortags, I tried to find the source code for the original firmware (so I can recover from mistakes) and some sdk to work with, and was kind of surprised to see that others have asked, and the answer is that it is not yet available as the device has not officially launched, whatever that means:

https://e2e.ti.com/support/wireless_connectivity/simplelink_wifi_cc31xx_cc32xx/f/968/p/575387/2112004

https://e2e.ti.com/support/wireless_connectivity/simplelink_wifi_cc31xx_cc32xx/f/968/t/618754

So I'm at a loss here... Is it still the case that TI will not provide a way to develop custom firmware for the cc3200 sensortag? Will this stay the case forever?

Thanks

  • Hi,

    My post (618754) is NOT correct. Reason why CC3200 SensorTag is not available due to certification restrictions (SAR regulations). TI cannot provide resources (firmware source code, support for own firmware development) due to this regulatory restrictions.

    Some informations about this restrictions you find here https://fccid.io/Z64-CC3200STK

    Jan
  • Hey Jan,

    Thank you for the reply, but honestly I'm still as confused. The link provide shows the device as certified, I don't see any exceptions, so I assume the theory is that it was certified with a specific capability that can be overridden using custom firmware?
    Even then I don't see the logic for TI to be prevented from supplying the firmware tools for R&D, as long as the device isn't sold after customization.

    But I guess I'll just have to be more careful in the future, as I ended up with a couple of very light paperweights that aren't even particularly pretty :)