Wdg: SetTrigger condition not reloading the WDT down counter

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • MCAL
    • MCAL-23905
    • MCAL_SitaraMPU_09.00.00
    • Hide
      MCUSW_J7_10.00.00
      MCAL_SitaraMPU_10.00.00
      Show
      MCUSW_J7_10.00.00 MCAL_SitaraMPU_10.00.00
    • Hide
      am62a-evm
      am62p-evm
      am62x-evm
      j7200-evm
      j721e-evm
      j721s2-evm
      j722s-evm
      j784s4-evm
      am62d-evm
      Show
      am62a-evm am62p-evm am62x-evm j7200-evm j721e-evm j721s2-evm j722s-evm j784s4-evm am62d-evm

      According to the AutoSAR standards and SWS requirements for Watchdog driver, the setTrigger Condition has to perform the reloading of the WDG downcounter without use of any helper API's (in our case Wdg_Trigger( ) is being used). 

      This is a clear gap when used with vector WdgM (Watchdog Managers) which only knows 3 API's (Init, setTriggerCondition and SET_MODE). This is causing an intergration issues with customers trying to comply with 4.3.1 standards

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Connection: Intermediate to External PROD System
                EXTSYNC-4633 - Wdg: SetTrigger condition not reloa...
                SYNCHRONIZED
                • Last Sync Date: