Introduction
This document contains API documentation for the diagnostic tests included in the MPLAB® Code Configurator PIC16/18 ISO26262 Diagnostic Library.
1 Software Requirements: PIC16
2 Software Requirements: PIC18
3 PIC16 Diagnostic Test APIs
4 PIC18 Diagnostic Test APIs
- 4.1 SW_CPU_REGISTER_RESET_STATE_CHECK_01.
  This module contains functional safety diagnostics APIs for CPU Registers .
- 4.2 SW_CLOCK_PERIODIC_MONITOR_01
  This module contains APIs to calculate and validate the frequency of the CPU clock using a reference Secondary Oscillator Crystal. The Clock test implements the SW_CLOCK_PERIODIC_MONITOR_01 SW REQ. ID by using time-slot monitoring technique.. It verifies the reliability of the system. clock (i.e., the system clock should be neither too fast nor too slow)
- 4.3 SW_CLOCK_PERIODIC_MONITOR_02
  This module contains APIs to calculate, store and validate the frequency of the CPU clock using a reference line frequency.
- 4.4 SW_CPU_REGISTER_TEST_01
  This module contains functional safety diagnostics APIs for CPU Registers .
- 4.5 SW_EEPROM_MEMORY_CHECKSUM_CRC_TEST_01 - CRC16
  This module contains APIs to calculate, store and validate 16-bit CCITT CRC for a given EEPROM region. .
- 4.6 SW_EEPROM_MEMORY_CHECKSUM_CRC_TEST_01 - CRC32
  This module contains APIs to calculate, store and validate 32-bit CCITT CRC for a given EEPROM region.
- 4.7 SW_FLASH_MEMORY_CHECKSUM_CRC_TEST_01 - CRC16
  This module contains APIs to calculate, store and validate 16-bit CCITT CRC for a given FLASH region .
- 4.8 SW_FLASH_MEMORY_CHECKSUM_CRC_TEST_01 - CRC32
  This module contains APIs to calculate, store and validate 32-bit CCITT CRC for a given FLASH region. .
- 4.9 SW_INTERRUPT_FREQUENCY_TEST_01
  This module contains functional safety diagnostics API for Interrupt Frequency Test.
- 4.10 SW_SRAM_MARCH_TEST_01 - MarchB
  This module contains functional safety diagnostics API for SRAM March-B. .
- 4.11 SW_SRAM_MARCH_TEST_01 - MarchC
  This module contains functional safety diagnostics APIs for SRAM March-C. .
- 4.12 SW_SRAM_MARCH_TEST_01 - MarchC_Minus
  This module contains functional safety diagnostics APIs for SRAM March-C Minus. .
- 4.13 SW_WATCHDOG_SIMPLE_TIMER_STARTUP_TEST_01
  This module contains functional safety diagnostics APIs for WatchDog Timer Test. .
- 4.14 SW_WATCHDOG_WINDOWED_TIMER_STARTUP_TEST_01
  This module contains functional safety diagnostics APIs for WatchDog Timer Test .
  - 4.14.1 Defines
  - 4.14.2 Enums
  - 4.14.3 Functions
    - 4.14.3.1 configure_TMR0_for_time_taking
      This is API to Set period so that TMR0 overflows approximately every 1ms.
    - 4.14.3.2 restart_TMR0
      This is a macro to reset TMR0 to zero and start counting from zero.
    - 4.14.3.3 watchdog_delay
      This is a macro to create a fixed delay for the watchdog timer test.
    - 4.14.3.4 DIAG_WDT_WindowedTimer
      **Software Requirement Reference ID : SW_WATCHDOG_WINDOWED_TIMER_STARTUP_TEST_01 GUID-B79C2521-47FE-432B-B985-F25AC86DE1F8.html#GUID-B79C2521-47FE-432B-B985-F25AC86DE1F8__GROUP__DIAG__WDT__WINDOWED__TIMER_1GGAA4770A6B5F28FCC3DD8C7106BD16DC40ABD9E97509B55E5A7C9BE32311AB6FCFF and GUID-B79C2521-47FE-432B-B985-F25AC86DE1F8.html#GUID-B79C2521-47FE-432B-B985-F25AC86DE1F8__GROUP__DIAG__WDT__WINDOWED__TIMER_1GGAA4770A6B5F28FCC3DD8C7106BD16DC40A061212985A780264DBC20D9764CED008**.
    - 4.14.3.5 DIAG_WDT_WindowedTimer_GetStatus
      Software Requirement Reference ID : SW_WATCHDOG_WINDOWED_TIMER_STARTUP_TEST_01.
- 4.15 File List
  Here is a list of all documented files with brief descriptions
- 4.16 Class List
  Here is a list of all documented files with brief descriptions

4.14.3.4 DIAG_WDT_WindowedTimer

**Software Requirement Reference ID : SW_WATCHDOG_WINDOWED_TIMER_STARTUP_TEST_01 DIAG_WDT_WINDOW_FSM_1 and DIAG_WDT_WINDOW_FSM_2**.

This API checks the WDT reset in window mode either the timer being cleared too early or too late.

This test should not be called from main. The test will be executed before main is entered as long as diag_wdt_windowed_timer.h/.c is included in the compilation.

This diagnostics tests that window mode works by attempting to clear the WDT counter in the closed part of the WDT counter window. The correct response of the device should be to reset the device. The next step will test that WDT will issue a system reset in window mode if no WDR instruction is executed. If the device and WDT was reset correctly in each step of the test, then the diag_wdt_window_teststate is set to DIAG_WDT_WINDOW_FSM_OK and diag_wdt_window_status is set to DIAG_WDT_WINDOW_PASS, otherwise the diag_wdt_window_teststate is set to DIAG_WDT_WINDOW_FSM_FAULT and diag_wdt_window_status is set to DIAG_WDT_WINDOW_FAIL thereby indicating fault.

Error reporting:

DIAG_WDT_WindowedTimer_GetStatus should be called from main to know the status of Windowed Timer WDT diagnosis

void DIAG_WDT_WindowedTimer(
    void
)

Returns


void	See DIAG_WDT_WindowedTimer_GetStatus