The HAL code uses a Error_Handler() function which just spins forever in a tight loop. I've seen comments about changing the call to report __FILE__ & __LINE__ which I may do. But I thought setting a breakpoint in the Error_Handler() code would lead me to the caller and failure. I'm using the IAR tools and when the breakpoint is hit, the call stack shows, main, Exception Frame, and Error_Handler. This doesn't tell me what called the Error_Handler() function.
Does anyone know how to track down the caller using the IAR debugger?