• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 41 subscribers
  • Views 488 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.

Empty CC3000 ??- How to get into production???

Fabrizio Filippini
Prodigy 150 points
Other Parts Discussed in Thread: MSP430FR5739

Hi All,

We are facing some production issues with the CC3000 that needs to be answered, but I got different answers so I want to make sure we are getting it right.

The CC3000s  we ordered, are not guarantee to get to my manufacturer  with any specific FW revision, correct?

We noticed that our FW is incompatible with different FW revisions of the CC3000. Is this normal? It usually hung on the SPI waiting for an incoming message. Updating the libraries this get solved, but if it does not work, we won't be able to update it Over the air through WiFi.

Our manufacture claims the CC3000 came in with NO FW installed. Does this mean we can program Driver and Firmware fresh on the device (which was our plan, but we are having issues implementing that into our MCU), or that we need to program the CC3000 with a I2C programmer before installing those on the board? Is it true that the design recommended in the data sheet does not provide the I/O to program through I2C, or we are just missing those?

sorry for the many questions, but we have production stopped for this issue. 

thank you!

  • 0
    TI__Mastermind 27095 points
    Hi,

    The CC3000 should ideally come with the 1.10.1 version. Did you try reading the service pack version using the 'nvmem_read_sp_version' API? The service pack should read '1.10'. The mapping can be found here http://processors.wiki.ti.com/index.php/CC3000_Release_Notes#Finding_Out_Current_Service_Pack_Version.

    You can check the release notes for the necessary feature set, and decide whether or not to upgrade to the latest patches. Based on your decision, you can always flash the patches on to the EEPROM.

    The recommended way to flash the patches is to use the Patch programmer utility. You can run this on your MCU as an application which downloads the patches on to the EEPROM. To make use of patch programmer, you should make sure that that host driver version matches the service pack. This could be the reason why the service pack in the CC3000 device behaves differently with different host driver code. Please refer to the above link and use the corresponding host driver version.
    For example: The host driver from SDK 1.10.1 uses the opcode 'SL_PATCHES_REQUEST_FORCE_HOST' during SIMPLE_LINK_START. Whereas this is deprecated in the newer releases.

    The not-so-recommended way would be flash over the I2C, using an I2C programmer. For more information you can refer to this link: http://e2e.ti.com/support/low_power_rf/f/851/p/282698/1039721.aspx#1039721. But as I said, it is not recommended.

    Regards,
    Raghavendra
  • 0 in reply to Raghavendra Shenoy
    Prodigy 150 points

    Hi Raghavendra,

    If the cc3000 comes with the 1.10.1, it would be fine to us. We can use that version. The other question I have: is it possible to READ the version with any host driver, and then evaluate weather to upgrade the CC3000 or not?

    We are trying to create a FW with the programming capabilities..but we are having problems. Shall we just blindly program it and move on?

    Thanks

  • 0 in reply to Fabrizio Filippini
    TI__Mastermind 27095 points
    Hi Fabrizio,

    Apologies for the delay in response. If you plan to use the version 1.10.1, then you should use the host driver from that corresponding release to flash the patches.

    You can use any host driver to read the FW version using API 'nvmem_read_sp_version'.

    If you want to move to a later version, say SP 1.24, then directly use the patch programmer from version 1.11.1 and burn the patches.

    If you still see issues, as an alternative, if you have a MSP430FR5739 MCU, you can directly try flashing the patches by using the patch programmer utility for MSP430FR5739.

    Instructions:
    http://processors.wiki.ti.com/index.php/CC3000_Patch_Programmer#Running_Patch_Programmer_Application_with_executable_binary

    Patch programmer for SDK version 1.11.1:
    http://processors.wiki.ti.com/index.php/CC3000_Wi-Fi_Downloads_1.11.1#CC3000_Platform_Dependent_Downloads

    Patch programmer for SDK version 1.10.1:
    http://processors.wiki.ti.com/index.php/CC3000_Wi-Fi_Downloads_1.10.1#CC3000_Platform_Dependent_Downloads

    Regards,
    Raghavendra