• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 207 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.

CC2640: Timer stopped

Hector Urroz
Intellectual 290 points

Part Number: CC2640

Hello, I've been pursuing a problem where the RTC freezes for no apparent reason. Other than this freeze, our BLE app is complete and working very well, and we need to be shipping it soon.

I had originally posted here, but then went over to the RTOS forum, where Alan was very helpful. We looked at stacks, Hwi, memory, registers, etc., but found no apparent cause for the freeze, and Alan suggested to come back here thinking that maybe the BLE stack code is doing something to halt the timer, or that you would know under what conditions the RTC would be stopped. We're running with power saving disabled and I put in notification hook to verify that hibernating is not getting invoked. We also measured consumption during the freeze and it's the same as when we're running successfully. During the freeze the tasks all look appropriately blocked on a semaphore or in task_sleep. Unfortunately, nothing much happens since the RTC is not advancing.

Here's the link to the discussion with Alan. Please let me know if you have any ideas that might help get us out of this jam.

Thanks!

  • 0
    TI__Mastermind 25035 points
    Hi,

    Does it freeze after a certain amount of time? Have you verified the frequency of the 32 kHz oscillator as posted here:
    e2e.ti.com/.../553877

    Best wishes
  • 0 in reply to Zahid Haq
    Intellectual 290 points

    HI Zahid,

    The freeze pattern is non-deterministic. What I can say is:

    1) There's no freeze before establishing a BLE connection

    2) After establishing a BLE connection we exchange messages at about 60/sec

    3) We can be on this message exchange mode for a long period of time (hours) without freezing, but a freeze can also occur after a few seconds

    4) If we change timing using logs, or modify some timeouts we can get the freeze to occur with more or less frequency. So very timing dependent.

    I'll get in touch with our hardware guy to see if we can check the frequency as you suggested. Would having the frequency be a little off cause the clock to stop altogether?

    Alan in the RTOS forum thought your BLE team might be able to come up with some possibilities that might cause clock trouble, maybe via some interaction with the stack. Can you think of anything?

    Thanks,

    Hector