• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 42 subscribers
  • Views 607 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

New CC3000MOD module won't respond

Dan Gotko1
Prodigy 20 points
Other Parts Discussed in Thread: MSP-EXP430FR5739, MSP430FR5739

I just ordered a large number of CC3000MOD modules for my initial product run.  I place them on my custom PCB and they get stuck in hci_event_handler because tSLInformation.usEventOrDataReceived = 0 and doesn't change.  If I replace the recently ordered CC300MOD module with the CC3000MOD module from the CC3000 evaluation module (that i used for initial development) everything works as designed.  If I place a recently ordered CC3000MOD module onto the evaluation board, I get stuck in the hci_event_handler again.  So, the problem follows the recently ordered CC3000MOD modules.  I tried to run the driver and firmware patches and get stuck in the same place (I  had to modify the driver and firmware patch code to work with my specific pinout).  Is there something special that I need to do to ensure that the CC3000MOD modules are working and properly programmed with the latest firmware?

  • 0
    Genius 4895 points

    Hi Dan,

    I assume the module contains different patches. Have you checked (read out) currently used patch version ?

    Is it happing during startup or later when you already try to build up a connection?

    Do you know which function/which command hangs?

    Best regards,

    Martin

  • 0 in reply to Marie Maurer
    Intellectual 340 points

    Hi Martin, 

    I have same experience with Dan. The problem seems to be the patch cannot load on the CC3000MOD EEPROM. I see the cc3000 request the patch event. I try to download the patch through SPI from the MSP demo board. But it seems not successful. Can you help to detail explain how to write the patch into the CC3000MOD EEPROM? We try follow the wiki patch programming method to do, but not successfully.

    Thanks

    Roderick 

  • 0 in reply to Roderick
    Genius 4895 points

    Hi Roderick,

    have a look into files PatchProgrammer*.c which are contained in patch programmer downloads:

    http://processors.wiki.ti.com/index.php/CC3000_Wi-Fi_Downloads#Patch_Programmer

    (I had no look into latest download, but previous downloads contained this file).

    There you see the sequence how to load patches.

    Or search for PatchProgrammer.c in E2E forum, you find various explanation and sequences.

    Pay attention that you must start without patches loaded, load patches, then start with patches loaded.

    This value is obsolete (you can comment it out):

    SL_PATCHES_REQUEST_FORCE_HOST

    You will never see (otherwise you have something wrong):

    #define HCI_EVENT_PATCHES_DRV_REQ           (1)
    #define HCI_EVENT_PATCHES_FW_REQ            (2)
    #define HCI_EVENT_PATCHES_BOOTLOAD_REQ      (3)

    Good luck!

    Best regards,

    Martin

  • 0 in reply to Marie Maurer
    Intellectual 340 points

    Hi Martin,

    we try follow the wiki suggestion and load the patch as below. But the result is only LED5 turns on, that means the patch on both firmware and driver is not successful to load on the CC3000MOD.

    Do you have any idea, what's going wrong from us ?

    Thanks

    Roderick

    Burning the patches to the module is also available with a binary file. In order to burn the patches using executable binary follow these instructions:

    MSP-EXP430FR5739

    Open Start -> All Programs -> CC3000 Patch Programmer -> MSP430FR5739 -> Download Driver Patches
    LED5 and LED8 turn on upon successful completion.
    If LED1 turns on as well, it indicates a missing MAC address.

    Open Start -> All Programs -> CC3000 Patch Programmer -> MSP430FR5739 -> Download Firmware Patches 
    LED5 and LED8 turn on upon successful completion.

  • 0 in reply to Roderick
    Genius 4895 points

    Hi Roderick,

    sorry, I can't help, never updated patches via MSP430 platform and/or delivered TI MSP430 software.

    Best regards,

    Martin

  • 0 in reply to Marie Maurer
    Intellectual 340 points

    Hi Martin,

    Noted with thanks.

    Did any TI supporter or TI member can help there?

    Thanks

    Roderick

  • 0
    Expert 2685 points

    Hi Dan,

    As suggested by others the very first thing you need to do is find out what version of the service pack your new modules have. You can do this with the following code:

        // Check the service pack version
        static uint8_t spVersion[2];
        nvmem_read_sp_version(spVersion);
        if (spVersion[0] != 1 || spVersion[1] != 26)
            while (1); // put a breakpoint here and look at the two numbers


    Version 1.26 is the latest and indicates that no patching is needed. If your new modules have a lesser service pack version, please post what it is, maybe other users have encountered it as well.