Skip to main content
Electrical Engineering

Return to Answer

added 75 characters in body
Source Link
Alan Samet
Alan Samet
  • 138
  • 1
  • 7

YouFor future reference, you need to define DEBUG_DEFAULT_INTERRUPT_HANDLERS in your preprocessor macros to capture the real cause of the hardfault interrupt.

Unfortunately, I don't know how to do this with the STM32CubeIDE. Here is a tutorial on how to do it with VisualGDB and hopefully this points you in the right direction: https://visualgdb.com/tutorials/arm/tracing/traceback/

You need to define DEBUG_DEFAULT_INTERRUPT_HANDLERS in your preprocessor macros.

Unfortunately, I don't know how to do this with the STM32CubeIDE. Here is a tutorial on how to do it with VisualGDB and hopefully this points you in the right direction: https://visualgdb.com/tutorials/arm/tracing/traceback/

For future reference, you need to define DEBUG_DEFAULT_INTERRUPT_HANDLERS in your preprocessor macros to capture the real cause of the hardfault interrupt.

Unfortunately, I don't know how to do this with the STM32CubeIDE. Here is a tutorial on how to do it with VisualGDB and hopefully this points you in the right direction: https://visualgdb.com/tutorials/arm/tracing/traceback/

Source Link
Alan Samet
Alan Samet
  • 138
  • 1
  • 7

You need to define DEBUG_DEFAULT_INTERRUPT_HANDLERS in your preprocessor macros.

Unfortunately, I don't know how to do this with the STM32CubeIDE. Here is a tutorial on how to do it with VisualGDB and hopefully this points you in the right direction: https://visualgdb.com/tutorials/arm/tracing/traceback/