• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 39 subscribers
  • Views 524 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.

CCS/CC3100: Whether the underlying SPI driver needs to set timeout exit

DONG TAN
Prodigy 220 points
Part Number: CC3100


Tool/software: Code Composer Studio

HI all，

I use the STM32F103XX as the main controller of the CC3100.

I found that the underlying SPI driver read and write function does not have timeout exit mechanism in the official SDK. Is it necessary to do an exit mechanism.if you do not use the timeout exit mechanism will cause the driver to die ?

If the timeout setting is too small, it will cause the driver to hang,if the timeout is set too small, it may cause the driver to hang, specifically "VERIFY_PROTOCOL(0)" in the "_SlDrvMsgReadSpawnCtx()" function.

Please theoretically help me determine which method to use best.

thanks！

 

 



 

  • 0
    TI__Expert 8255 points

    Hi Dong,

    In the most recent CC3100 v1.3 SDK there was a timer tick update-- the host driver checks the device tick count to internally determine certain timeouts. For non-os applications, it is mandatory to support this option in the builds.

    This is essentially what you are requesting above as the host driver uses the sl_GetTimestamp function to determine SPI communication timeouts between the host MCU and NWP