• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 40 subscribers
  • Views 702 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.

FR5969 SL_ASSERT infinite loop on disabling CC3100

Salvatorre
Expert 1460 points

e2e.ti.com/.../1416682

I also had the issue in the above closed thread this past weekend. I am running the CC3100 with the MSP430FR5969. I am sending short UDP messages to a server and then going into LPM3. The process repeats after every sleep period. My test ran for a longer period of time, so maybe it will help, although my sleep periods are pretty long. I sent 74 messages over the course of many hours before I got hung up here.

Perhaps SL_ERROR would be better to use than SL_ASSERT so that the application code can decide what to do if the error occurred.

What causes this error though? My serial port monitor shows that my last message was sent, connection was closed, and the device was disconnected from the ap. I would normally get two more messages that the CC3100 was turned off and that the MSP was going to sleep.

I intend to add the watchdog function once my application code is more stable, but I wouldn't want the watchdog to have to have to come to the rescue every day.

  • 0
    TI__Mastermind 27565 points

    Hi Salvatore,

    Can you try something for me? Please try your normal program, but without putting the MSP430 to sleep ever.

    Thanks,
    Aaron

  • 0 in reply to made4engineering
    Expert 1460 points

    Aaron,


    Thanks for your response.

    I implemented your requested change. I'll keep it running and let you know how it does.


    Thanks,

    Sal

  • 0 in reply to Salvatorre
    Expert 1460 points
    So far so good, I'm on message 87 without failure. It had previously failed by message 74 and message 76. I'm going to keep it running and will report back. Please don't close this issue, yet.
  • 0 in reply to Salvatorre
    Expert 1460 points

    We've reached message 244 now. It looks like there is some connection to this problem with LPM3. Obviously, I would like to exploit LPM3 mode in my product. Is there anything I need to know to keep it working? Is there some peripheral that I need to re-initialize after exiting LPM3 mode (ie spi, digital clock, etc)?

    I'm ending this test now and moving on with other development.


    Thanks for your help!