Hard Fault with USART & Ethernet

parisa · ‎2016-10-22

Posted on October 22, 2016 at 09:08

The original post was too long to process during our migration. Please click on the attachment to read the original post.

Tesla DeLorean · ‎2016-10-22

Posted on October 22, 2016 at 16:08

Use a proper Hard Fault handler and identify the code that is faulting so you can ascertain why.

You can use the .MAP file to identify functions/code by address, and you can understand register usage/content by reviewing the code disassembly at and immediately before the faulting instructions.

Review if the code you are calling is thread/interrupt safe, and if you need to implement some mutex/semaphore to prevent re-entry.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

parisa · ‎2016-10-22

Posted on October 22, 2016 at 16:22

Thanks dear clive1

I'm newbie in debugging. Could you introduce me with some good references (such as video or pdf ,...) to debug and ascertain very well in keil?

Thanks