• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 41 subscribers
  • Views 413 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.

Quick board-level validation of SPI bus interface to CC3000

Peter Fenn
Intellectual 315 points

On an untested prototype board, what is the quickest way to validate:

1) the CC3000 SPI bus interface and
2) that the CC3000 is functional... ? 

eg. does the CC3000 have a "Device ID" that could be read-back over the SPI bus?
If any SPI bus software example available this would be welcome!   

Thanks
Peter
 

  • 0
    TI__Mastermind 18455 points

    Hi Peter,

    We don't have any specific SPI test utility and there isn't any device ID.

    I think that the best way is to run our basic wifi sample application and check your proto board functionality with that.

    We provide reference SPI drivers for both MSP430 & Stellaris M4 platforms.

    Thanks,
    Alon.S

  • 0 in reply to Alon Srednizki
    Intellectual 315 points

    Alon

    Thanks for your follow-up. 
    - I'm thinking a slimmed-down piece of code doing a HCI_CMND_READ_SP_VERSION check of the NV memory could provide validation of the SPI interface to the CC3000?

    PS: Is there a generic "reference SPI driver" that you can recommend for porting to a non-TI (Cortex-M) microcontroller?

    Peter

  • 0 in reply to Peter Fenn
    TI__Mastermind 18455 points

    Hi Peter,

     Unfortunately, no, we don't have such reference code or documentation.
    But I'll take it into consideration for our future releases.

    Thanks,
    Alon.S

  • 0 in reply to Alon Srednizki
    Intellectual 755 points

    Alon,

    What Peter asked for would be very helpful to have.  Developers often work step by step.  Nobody wants to implement the whole host driver just to find out the rudimentary SPI calls don't work.  At that point, there's too many things that could be the problem, diagnosing back to the SPI could be very difficult.  The host driver porting guide (I'm also using a non-TI MCU) should include a very simple command that can be sent to the CC3000 where the CC3000 responds afterward by dropping SPI_IRQ to initiate a host read of the CC3000.   If the command Peter suggested works, HCI_CMND_READ_SP_VERSION, then include the byte sequence for that command in the host porting guide and specify what we should expect to be sent from the CC3000.  It would make host driver porting easier.

    Jim