Shared Tasks

Contains API prototypes for Tasks shared between several Task Managers. More...

Files
file	tasks_shared.c
	Implements APIs for Tasks shared between several Task Managers.
file	tasks_shared.h
	Contains API prototypes for Tasks shared between several Task Managers.
file	tasks_shared_private.c
	Implements private functions for tasks_shared.c.
file	tasks_shared_private.h
	Contains private function prototypes for tasks_shared.c.

Functions
void	T_HandleSyncWatchdog (uint32_t newTimeout)
	Waits until the current Synchronous Watchdog timeout is completed before clearing and setting the next timeout.
void	T_HandleWatchdog (void)
	Clears the Watchdog Timer (WDT) while performing the WDT count diagnostic.
void	T_HandleNotificationErrors (void)
	Ensures Error IDs with 'NOTIFICATION' criticality are handled.
void	ReportClearVregfailChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearBuserrChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearRam2ChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearFlash2ChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearOpcChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearSplimChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearRam1ChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearFlash1ChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearVregwarnChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearCfd0ChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearCfd1ChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearCfm0ChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearCfm1ChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearSwdtChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearEepromChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearEvsys0ChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.
void	ReportClearEvsys1ChannelError (void)
	Private function, only exposed for unit testing and should not be called directly.

Detailed Description

Contains API prototypes for Tasks shared between several Task Managers.

Copyright

© 2026 Microchip Technology Inc. and its subsidiaries.

Subject to your compliance with these terms, you may use Microchip software and any derivatives exclusively with Microchip products. It is your responsibility to comply with third party license terms applicable to your use of third party software (including open source software) that may accompany Microchip software.

THIS SOFTWARE IS SUPPLIED BY MICROCHIP "AS IS". NO WARRANTIES, WHETHER EXPRESS, IMPLIED OR STATUTORY, APPLY TO THIS SOFTWARE, INCLUDING ANY IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE.

IN NO EVENT WILL MICROCHIP BE LIABLE FOR ANY INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL OR CONSEQUENTIAL LOSS, DAMAGE, COST OR EXPENSE OF ANY KIND WHATSOEVER RELATED TO THE SOFTWARE, HOWEVER CAUSED, EVEN IF MICROCHIP HAS BEEN ADVISED OF THE POSSIBILITY OR THE DAMAGES ARE FORESEEABLE. TO THE FULLEST EXTENT ALLOWED BY LAW, MICROCHIP'S TOTAL LIABILITY ON ALL CLAIMS IN ANY WAY RELATED TO THIS SOFTWARE WILL NOT EXCEED THE AMOUNT OF FEES, IF ANY, THAT YOU HAVE PAID DIRECTLY TO MICROCHIP FOR THIS SOFTWARE.

UML Class Diagrams

UML Activity Diagrams

UML Sequence Diagrams

Function Documentation

ReportClearBuserrChannelError()

void ReportClearBuserrChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearCfd0ChannelError()

void ReportClearCfd0ChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearCfd1ChannelError()

void ReportClearCfd1ChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearCfm0ChannelError()

void ReportClearCfm0ChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearCfm1ChannelError()

void ReportClearCfm1ChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearEepromChannelError()

void ReportClearEepromChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearEvsys0ChannelError()

void ReportClearEvsys0ChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearEvsys1ChannelError()

void ReportClearEvsys1ChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearFlash1ChannelError()

void ReportClearFlash1ChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearFlash2ChannelError()

void ReportClearFlash2ChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearOpcChannelError()

void ReportClearOpcChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearRam1ChannelError()

void ReportClearRam1ChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearRam2ChannelError()

void ReportClearRam2ChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearSplimChannelError()

void ReportClearSplimChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearSwdtChannelError()

void ReportClearSwdtChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearVregfailChannelError()

void ReportClearVregfailChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

ReportClearVregwarnChannelError()

void ReportClearVregwarnChannelError

(

void

)

Private function, only exposed for unit testing and should not be called directly.

Here is the call graph for this function:

T_HandleNotificationErrors()

void T_HandleNotificationErrors

(

void

)

Ensures Error IDs with 'NOTIFICATION' criticality are handled.

This function checks all Error Controller channels configured with 'NOTIFICATION' criticality. For each set channel, except EVSYS0 and EVSYS1, it reads and clears the error source, clears the channel, and reports the error to the Error Handler to be logged as a 'NOTIFICATION' error. Once all the notification errors are logged, the function invokes the Error Handler to process the log, which may include previously logged errors.

Note

To optimize memory usage, the static configuration in the errorIdCritLut is used to include or exclude channels at compile-time.

Note

Error Controller channels set to 'IGNORE' in the errorIdCritLut are not checked.

Note

For scheduling of this Task see DUR_HANDLE_NOTIFICATION_ERRORS.

Warning

Configuring the EVSYS0 or EVSYS1 Error Controller channels to use a "level" event type as the error source in the Event System will prevent clearing the channel, requiring both the source and channel to be cleared in the notification error handler callback.

The following Error IDs may be reported to the Error Handler by this Task and corresponds to error channel hardware flags or their sources:

• ERRID_CFD0_CH, ERRID_CFD1_CH, ERRID_CFM0_CH, ERRID_CFM1_CH, ERRID_BUSERR_BUSERR, ERRID_RAM_PARITY, ERRID_NVM_PARITY, ERRID_BUSERR_PARITYD,

ERRID_BUSERR_CH, ERRID_OPC_OPC, ERRID_OPC_PARITYI, ERRID_OPC_CH, ERRID_SPLIM_CH, ERRID_RAM2_ECC2, ERRID_RAM2_COMP, ERRID_RAM2_CH, ERRID_FLASH2_ECC2, ERRID_FLASH2_COMP, ERRID_FLASH2_CH, ERRID_RAM1_CH, ERRID_FLASH1_CH, ERRID_EEPROM_ECC1, ERRID_EEPROM_ECC2, ERRID_EEPROM_CH, ERRID_VREGFAIL_VOV, ERRID_VREGFAIL_VUV, ERRID_VREGFAIL_CH, ERRID_VREGWARN_VDENTER, ERRID_VREGWARN_VDEXIT, ERRID_VREGWARN_VERR, ERRID_VREGWARN_VSLP, ERRID_VREGWARN_VDIS, ERRID_VREGWARN_SERR, ERRID_VREGWARN_CH, ERRID_SWDT_BADPC, ERRID_SWDT_BADC, ERRID_SWDT_UC, ERRID_SWDT_EXP, ERRID_SWDT_CH, ERRID_EVSYS0_CH, ERRID_EVSYS0_CLEAR, ERRID_EVSYS1_CH, ERRID_EVSYS1_CLEAR

Here is the call graph for this function:

T_HandleSyncWatchdog()

void T_HandleSyncWatchdog

(

uint32_t

newTimeout

)

Waits until the current Synchronous Watchdog timeout is completed before clearing and setting the next timeout.

This function handles the Synchronous Watchdog Timer (SWDT) by pre-clearing and clearing it in the correctly timed sequence, and setting a new timeout period value. With this, the SWDT is restarted with a new initial counter value after waiting until the previous timeout has ended.

It is also responsible for executing the optional MW_DiagSwdtCount diagnostic, if enabled compile-time. See DIAG_PERIODIC_SWDT_COUNT for more details. Any detected diagnostic faults and input parameter errors are reported to the Error Handler.

Note

The 'newTimeout' value is the closed window for the SWDT. Adding the configured SWDT_OPEN_WINDOW yields the SWDT RESET value. Once the SWDT window has opened, the SWDT can be cleared and hence, restart immediately. This ensures that the SWDT period is always 'newTimeout' clock cycles.

Warning

This Task will busy wait until the SWDT can be cleared in its open window. If the SWDT expires while waiting or the SWDT is already expired, an error is reported and the function returns.

Warning

A 'newTimeout' value resulting in a calculated SWDT RESET that overflows 32 bits or exceeds 24 bits is reported as an error and discarded, and the current SWDT RESET value is re-used for the next period.

Parameters

newTimeout

Number of clock cycles until the SWDT can be pre-cleared after the current timeout period is completed.

The following Error IDs may be reported to the Error Handler by this Task:

• ERRID_SWDT_RESET_VAL Invalid SWDT configuration
• ERRID_DIAG_SWDT_COUNT The MW_DiagSwdtCount diagnostic reported an error
• ERRID_SWDT_EXP SWDT already expired before attempting to clear it

Here is the call graph for this function:

Here is the caller graph for this function:

T_HandleWatchdog()

void T_HandleWatchdog

(

void

)

Clears the Watchdog Timer (WDT) while performing the WDT count diagnostic.

This function is responsible for clearing the Watchdog timer. It is intended to be called at a set interval to ensure that the Watchdog is cleared within the Fault Detection Time Interval (FDTI) of the device. The function is also responsible for optionally executing the MW_DiagWdtCountEnd diagnostic, which detects whether the WDT counter is stuck and reports any detected faults to the Error Handler. See DIAG_PERIODIC_WDT_COUNT for enabling or disabling this feature.

Warning

It is assumed that this function is called at the correct time to clear the Watchdog. If called while the Watchdog is in the closed window, the device will be reset by the Watchdog.

Note

See WWDT_CLOSED_WINDOW, WWDT_OPEN_WINDOW and INIT_WDT_DURATION for configuration of the watchdog timeout.

The following Error IDs may be reported to the Error Handler by this Task:

• ERRID_DIAG_WDT_COUNT The MW_DiagWdtCountEnd diagnostic reported an error

Here is the call graph for this function:

Here is the caller graph for this function: