• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 28 subscribers
  • Views 1094 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[FAQ] SW-TM4C: How to debug a program going into FaultISR

Ralph Jacobi
Guru*** 128095 points
Part Number: SW-TM4C

Observed Issue: The program is entering into the FaultISR during normal program execution.

The FaultISR entry has been confirmed to be unrelated to the topic discussed in How to prevent the program from going into FaultISR when using a new peripheral

  • 0
    TI__Guru*** 128095 points

    Typical Root Cause: Fault ISR means that the CPU has hit a condition either internally or externally (w.r.t peripherals) that it cannot resolve.

    Debug Steps:

    1) The Registers that need to be checked to begin analysis are the NVIC_FAULTSTAT and NVIC_FAULTADDR registers at absolute address 0xE000ED28 and 0xE000ED38.

    2) Precise Bus Fault in NVIC_FAULTSTAT would mean that the address of Faulting location is captured in NVIC_FAULTADDR

    3) Similarly every fault type mentioned has a cause associated to it, some being easy to diagnose and some being difficult to diagnose. In order to diagnose faults, refer to the following document that covers the different Fault Types: http://www.ti.com/lit/spma043

    4) If a solution is not found after consulting SPMA043, post on E2E with details including the Fault Type and what steps have been taken to try and resolve the issue.