Posted on November 18, 2017 at 07:02
You could try this hardfault handler. It reads the CPU registers and saves them in a bunch of variables.
The PC variable contains the program counter and points to the code address that failed (actually, one after it).
Using the disassembly, you can then at least get an idea of where the problem happened.
Add/change this in your stm32fxx_it.c :
void prvGetRegistersFromStack(uint32_t *pulFaultStackAddress) {
/* These are volatile to try and prevent the compiler/linker optimising them
away as the variables never actually get used. If the debugger won't show the
values of the variables, make them global my moving their declaration outside
of this function. */
__unused volatile uint32_t r0;
__unused volatile uint32_t r1;
__unused volatile uint32_t r2;
__unused volatile uint32_t r3;
__unused volatile uint32_t r12;
__unused volatile uint32_t lr; /* Link register. */
__unused volatile uint32_t pc; /* Program counter. */
__unused volatile uint32_t psr;/* Program status register. */
r0 = pulFaultStackAddress[0];
r1 = pulFaultStackAddress[1];
r2 = pulFaultStackAddress[2];
r3 = pulFaultStackAddress[3];
r12 = pulFaultStackAddress[4];
lr = pulFaultStackAddress[5];
pc = pulFaultStackAddress[6];
psr = pulFaultStackAddress[7];
/* When the following line is hit, the variables contain the register values. */
Error_Handler();
}
/**
* @brief This function handles Hard fault interrupt.
*/
void HardFault_Handler(void) {
/* USER CODE BEGIN HardFault_IRQn 0 */
__asm volatile
(
' tst lr, #4
'
' ite eq
'
' mrseq r0, msp
'
' mrsne r0, psp
'
' ldr r1, [r0, #24]
'
' ldr r2, handler2_address_const
'
' bx r2
'
' handler2_address_const: .word prvGetRegistersFromStack
'
);
/* USER CODE END HardFault_IRQn 0 */
while (1) {
}
/* USER CODE BEGIN HardFault_IRQn 1 */
/* USER CODE END HardFault_IRQn 1 */
}�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?
