SPRADI6 May   2024 TMS320F2800132 , TMS320F2800133 , TMS320F2800135 , TMS320F2800137 , TMS320F2800152-Q1 , TMS320F2800153-Q1 , TMS320F2800154-Q1 , TMS320F2800155 , TMS320F2800155-Q1 , TMS320F2800156-Q1 , TMS320F2800157 , TMS320F2800157-Q1 , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Overview of C2000™ MCU Devices in Appliances
  6. 3Introduction of IEC/UL 60730-1/60335-1 Standards
  7. 4Diagnostic Libraries for UL/IEC 60730-1/60335-1 Provided by C2000™
    1. 4.1 Stack Overflow Detection
    2. 4.2 Watchdog
    3. 4.3 CPU and FPU Registers
    4. 4.4 Program Counter (PC)
    5. 4.5 Clock
    6. 4.6 RAM
    7. 4.7 Flash
    8. 4.8 ADC
    9. 4.9 Cycle Time and Memory Usage
  8. 5References

Program Counter (PC)

Traditionally, the detection of the PC pointer is achieved by jumping to a specified function address through the self-test program and then comparing the returned address with the preset address. If the addresses are the same, the self-check passes. The essence of this check is to verify the correctness of function jumps.

In actual applications, watchdogs are enabled and watchdog feeding operations are performed in fixed-frequency interrupts. Therefore, entering the watchdog interrupt to perform feeding indicates that the PC pointer is functioning properly. If the PC pointer fails, a reset caused by watchdog timer overflow occurs, achieving the same protective purpose. Therefore, the PC pointer is usually not individually self-checked. The detection of the PC pointer can be combined with enabling the watchdog and explained in the documentation provided to the certification agency.