Uploaded image for project: 'Embedded Software & Tools'
  1. Embedded Software & Tools
  2. EXT_EP-8962

Clock tick resync problem with PowerCC32XX_sleepPolicy

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • TI Device Drivers
    • TIDRIVERS-1623
    • 3.50.00
    • 3.60.01
    • Hide
      Some applications are failing to wake from LPDS if there is a long delay that prevents the PowerCC32XX_sleepPolicy() from running.

      Drift between time according to RTC and Clock ticks was found to be the cause of the failures. The TIRTOS and NoRTOS policies were referencing back to first tick and RTC count on first LPDS entry, which becomes a problem if the two timebases are not locked together and drifting. Updated these policies to not reference back to first LPDS entry, but to just the tick and RTC count before the recent entry to LPDS. Also updated the 'catchup' logic to trigger when newTick is the same or greater than workTick (rather than previous trigger, which looked at time spent in LPDS).
      Show
      Some applications are failing to wake from LPDS if there is a long delay that prevents the PowerCC32XX_sleepPolicy() from running. Drift between time according to RTC and Clock ticks was found to be the cause of the failures. The TIRTOS and NoRTOS policies were referencing back to first tick and RTC count on first LPDS entry, which becomes a problem if the two timebases are not locked together and drifting. Updated these policies to not reference back to first LPDS entry, but to just the tick and RTC count before the recent entry to LPDS. Also updated the 'catchup' logic to trigger when newTick is the same or greater than workTick (rather than previous trigger, which looked at time spent in LPDS).

      Clock tick resync problem with PowerCC32XX_sleepPolicy

            syncuser TI User
            syncuser TI User
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: