• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 84 subscribers
  • Views 876 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.

TMS320F28388D: Debug hard fault on CM

Sheldon He
Expert 8585 points
Part Number: TMS320F28388D

Hi expert,

My customer entered exception isr when using F28388D.

It seems hard fault happens on cortex-m4 core. When they enlarger the stack, issue will not happen again. Could you provide any method to determine the root cause or whether it is a stack overflow case?

Thanks

Sheldon

  • 0
    TI__Guru** 113205 points

    Sheldon,

    Hard fault on Cortex M4 can happen because of many different reason. There are difference status register which user need to check to know what is causing the fault and take appropriate action to fix that. You can check Configurable Fault Status Register (CFSR - 0xE000ED28)to see what is causing the fault. You can find the detail about this in ARM manual here.Many time it is caused because of Usage Fault.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Guru** 113205 points

    Hi,

    Is this same issue as this one ?

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Expert 8585 points

    Hi Viviek,

    This same case, we have solved by adding stack size and is now working on why stack usage is that much. 

    They are currently not running TIRTOS on CM, do you have any suggestions to idenfity possible risks in stack usage?

    I recommened them to try call graph tool, but it could be very limited in function.

    Thanks

    Sheldon