SPRZ425G November   2014  – November 2026 TDA3LA , TDA3LX , TDA3MA , TDA3MD , TDA3MV

 

  1.   1
  2. 1Introduction
    1.     Related Documentation
    2.     Trademarks
    3.     Modules Impacted
  3. 2Silicon Advisories
    1.     i202
    2.     i694
    3.     i709
    4.     i727
    5.     i729
    6.     i767
    7.     i813
    8.     i814
    9.     i826
    10.     i829
    11.     i866
    12.     i868
    13.     i872
    14.     i874
    15.     i879
    16.     i882
    17.     i883
    18.     i888
    19.     i889
    20.     i891
    21.     i893
    22.     i894
    23.     i898
    24.     i899
    25.     i904
    26.     i911
    27.     i914
    28.     i915
    29.     i916
    30.     i924
    31.     i930
    32.     i936
    33.     i938
    34.     i939
    35.     i940
  4. 3Silicon Limitations
    1.     i833
    2.     i873
    3.     i876
    4.     i877
    5.     i892
  5. 4Silicon Cautions
    1.     i781
    2.     i827
    3.     i828
    4.     i836
    5.     i839
    6.     i864
    7.     i886
    8.     i908
    9.     i912
    10.     i923
  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.