Introduction
This document contains API documentation for the diagnostic tests included MPLAB® Code Configurator AVR® IEC60730 Class B Diagnostic Library.
1 Software Requirements
2 Clock Frequency Test
This module contains functional safety diagnostics APIs for Clock Frequency test.
3 CPU Program Counter
This module contains functional safety diagnostics APIs for CPU Program counter test.
4 CPU Registers
This module contains functional safety diagnostics APIs for CPU Registers.
5 EEPROM - 16-bit CRC
This module contains APIs to calculate, store and validate 16-bit CCITT CRC for a given EEPROM region.
6 EEPROM - 32-bit CRC
This module contains APIs to calculate, store and validate 32-bit CCITT CRC for a given EEPROM region.
7 FLASH - 16-bit CRC
This module contains APIs to calculate, store and validate 16-bit CCITT CRC for a given FLASH region.
8 FLASH - 32-bit CRC
This module contains APIs to calculate, store and validate 32-bit CCITT CRC for a given FLASH region.
9 Interrupt Frequency Test
This module contains functional safety diagnostics API for Interrupt Frequency Test.
10 SRAM - Checkerboard Algorithm
This module contains functional safety diagnostics APIs for SRAM Checkerboard Test.
11 SRAM - March C-Minus Algorithm
This module contains functional safety diagnostics APIs for SRAM March-C Minus.
12 Simple Watchdog Timer
This module contains functional safety diagnostics APIs for WatchDog Timer Test.
13 Windowed Watchdog Timer
This module contains functional safety diagnostics APIs for WatchDog Timer Test.
14 File List
Here is a list of all documented files with brief descriptions
15 Class List
Here is a list of all documented files with brief descriptions

1.10 Windowed Watchdog Timer

Test Name: Windowed WDT Test.

Purpose of test: The watchdog timer (WDT) is a system function for monitoring correct program operation that allows recovering from error situations such as runaway or deadlocked code.

Acceptable Measure (Annex. H): Time-slot monitoring of the program sequence (H.2.18.10.4)

Description: This diagnostic tests the following:

WDT issues a system reset if it is untimely reset (WDT window mode)
- This consists of configuring the WDT in window mode and the test state is set accordingly, and then an early reset of the WDT is performed. When the window is closed the WDT should issue a system reset. If a system reset does not occur the error state is set. After this step, a check is performed to see that the WDT reset works when the WDT window is open.
WDT issues a system reset if no WDR is executed (WDT window mode)
- The WDT is expected to issue a system reset without any dependencies with WDR instruction. Upon timely reset, the WDT sets to the appropriate error-free test state

API Documentation: Windowed Watchdog Timer