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

CC2340R5-Q1: About the watchdog timer at standby mode

Mike Wu1
Expert 2841 points
Part Number: CC2340R5-Q1

Tool/software:

Hi Team, 

My customer is using CC2340R5-Q1  and no power button and reset button in the design.

They have finished the test of power consumption and it is good for mass production.

But if watchdog timer is activated, the power consumption is not good.

We know the watchdog timer runs on a 32 kHz clock rate and operates in device active, idle, and standby modes and cannot be stopped once enabled.

However, we may save in warehouse or shipping by sea for months. 

Since we don’t know how long it will remain in standby mode, it will make more reset than the case without setting watchdog timer. 

And more reset will cost more power consumption while using watchdog timer. 

Please help to provide comments to reduce reset caused by watchdog time-out.

If system error is less happened at stand-by mode, can we just disable watchdog timer before entering standby mode and enable it after leave standby mode?

  • 0
    TI__Prodigy 270 points

    Hello Mike, 

    Which SDK is the customer using and what do they mean by reset? Can you clarify what kind of reset is being performed by the customer, are they resetting the entire device or just the watchdog timer? 

    To reduce reset caused by watchdog time-out, could be to set the time to a very large number. 

    In the driver files, Watchdog.h, there are functions for closing / stopping and starting the watchdog timer. Has the customers tried these functions by closing the watchdog before entering standby mode and then opening the timer after leaving standby mode?

    Regards, 

    David

  • 0 in reply to David Chen
    Expert 2841 points

    Hi David,

    SDK  version: simplelink_lowpower_f3_sdk_7_20_01_10.

    the reset reason is checked and caused by watchdog timer expired.

    The API: Watchdog_close() is called before entering stand-by mode. 

    Please help to provide comments.

    Thanks.

  • 0 in reply to Mike Wu1
    TI__Prodigy 270 points

    Hello Mike, 

    When the device is being created, is the watchdog timer being initialized and opened? If so, then the watchdog timer will continue to run until it expires (even when entering standby mode or Watchdog_close() is called).

    There is a function in Watchdog.h, called Watchdog_Clear(), that will prevent the reset from occurring and it should be called periodically to ensure that the timer does not timeout and reset. 

    Regards, 

    David

  • 0 in reply to David Chen
    Expert 2841 points

    Hi David, 

    I have suggest my customerto update the SDK to the latest version. 

    About calling the Watchdog_Clear() periodically to ensure that the timer does not timeout and reset, I will request my customer to review again.

    Thanks.