SPRZ444C February   2018  – November 2026 DRA780 , DRA781 , DRA782 , DRA783 , DRA786 , DRA787

 

  1.   1
  2. 1Introduction
    1.     Related Documentation
    2.     Trademarks
    3.     Modules Impacted
  3. 2Silicon Advisories
    1.     i202
    2.     i694
    3.     i727
    4.     i729
    5.     i767
    6.     i813
    7.     i814
    8.     i826
    9.     i829
    10.     i872
    11.     i874
    12.     i879
    13.     i883
    14.     i889
    15.     i893
    16.     i894
    17.     i898
    18.     i899
    19.     i914
    20.     i916
    21.     i930
    22.     i936
    23.     i938
    24.     i939
    25.     i940
  4. 3Silicon Limitations
    1.     i833
    2.     i873
    3.     i876
    4.     i877
  5. 4Silicon Cautions
    1.     i781
    2.     i827
    3.     i828
    4.     i836
    5.     i839
    6.     i864
    7.     i886
    8.     i912
  6. 5Revision History

i940

MPU COUNTER_REALTIME saturates after several hundred days

Details

After several hundred days (specific duration depends on the primary input clock SYS_CLK1 frequency, see table below for example durations) of continuous operation the MPU COUNTER_REALTIME saturates at 0xBB8000000000 and no longer generates interrupts. There is no way to reset the counter except for a system reset.

For software/systems that use this timer and operate for extended periods of time without any type of reset or power cycle, this can lead to a system hang. For systems that regularly go through a power cycle or reset there is no issue.

SYS_CLK1 Days until saturation
19.2 MHz 404
20 MHz 388
27 MHz 287

Workaround

Workaround 1: Avoid the issue by requiring the user to preform a scheduled reset/restart of the system sometime prior the saturation time (200 to 388 days).

Workaround 2: Recover from the issue by enabling a system watchdog reset to expire after the issue has occurred.

Workaround 3: Use GP Timer instead of COUNTER_REALTIME in systems requiring continuous up time.