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.

CC3000 Patch Programmer for MSP430F5529

Other Parts Discussed in Thread: MSP430F5529

I've been trying to make progress getting my EXP-MSP430F5529 talking to the CC3000

I followed this link:

http://processors.wiki.ti.com/index.php/CC3000_Wi-Fi_Downloads#CC3000.2BMSP430F5529

and downloaded and installed the MSP430F5529+CC3000 Basic WiFi Application.  This doesn't work for the MSP430F5529.  In looking inside the code that is installed in the source directory, it has references to wrong pinouts, for example SPI_IRQ_PIN is defined as BIT3, but on this board it is actually BIT4.  So it doesn't look like this code is really intended for the MSP430FF29.

What is the proper method for applying the patch to the CC3000 using the EXP-MSP430F5529?  Are there steps or instructions somewhere for this board?  There are links to patch programmers for the other CPUs on that patch, but no link for the MSP430F5529.

Thanks in advance.

  • So I noticed something very strange.  On the download page:

    http://processors.wiki.ti.com/index.php/CC3000_Wi-Fi_Downloads#CC3000.2BMSP430F5529

    Clicking the 'Download' button takes you to

    http://www.ti.com/litv/zip/swrc265B

    However clicking the V1.9 link takes you to

    http://www.ti.com/litv/zip/swrc242

    The swrc265B is for a different CPU as I unfortunately had the opportunity to confirm.  The swrc242 appears to be for the MSP430F5529.  I've started digging into it.  One thing that jumps out is that the 'CC3000 Host Driver' seems to be quite a bit older.  In comparing it with the current CC3000Host Driver there are several files missing and quite a bit of functionality missing.  For example the nvmem_read_sp_version(patchversion) function which would be useful is not there...

    So can I use this older code and update the firmware on the CC3000?

  • I went ahead and compiled this version 1.9 code.  The code successfully compiled without any modifications.  The board definition matches the pin out of my dev board.  I downloaded it to the MSP430FF529, however upon running it nothing happened.  No LEDs not characters in the console.  I then stepped through it in the debugger to see what was happening.

    The DemoInitDriver function calls

      
        DispatcherUARTConfigure();
        DemoInitSpi();
        wlan_init( CC3000_UsynchCallback, (tFWPatches )sendWLFWPatch, (tDriverPatches)sendDriverPatch, (tBootLoaderPatches) sendBootLoaderPatch, ReadWlanInterruptPin, WlanInterruptEnable, WlanInterruptDisable, WriteWlanPin);

    all of which return successfully.  However the call to
        wlan_start(0);

    never returns.

    Stepping through wlan_start(0);

        tSLInformation.pucTxCommandBuffer = wlan_tx_buffer;
        SpiOpen(SpiReceiveHandler);

    return , but as soon as
        ulSpiIRQState = tSLInformation.ReadWlanInterruptPin();

    is called, that function never returns.  When I pause the debugger I'm stuck in the hci_event_handler waiting for tSLInformation.usEventOrDataReceived not to equal to zero.

    I'm stuck here.

    I've confirmed that all of my jumpers and switches are exactly as shown they should be on this page:

    http://processors.wiki.ti.com/index.php/CC3000_Wi-Fi_MSP-EXP430F5529

    I'm really at a loss as to how to proceed?  Any help or direction would be greatly appreciated!

  • Hi,

    Did you ever get this resolved? Turns out I have the exact same problem and have pretty much exhausted all avenues I know of (googling, 34oh, etc.)

    thanks

    Kaj

  • Can you paste what your ReadWlanInterruptPin() method looks like?

  • Kaj,

    Sorry for the delay in responding.  I've been out of town.  I did get this problem resolved.  I had to update to the latest patch to resolve the issue.  The problem for me was that the patch did not work every time.  I had to keep programming the patch multiple times until it was finally successful, then things started working with the stock code from the website.