I am working on stm32f769 project, running freeRTOS task, with stm32cubeIDE(1.7.0) debugger.
The debugger does not hit hard faults inside the faulty task , but later, reporting scheduler restart in debug calling stack.
That way I completely miss the error source. how can I locate the error inside the task, while debugging?
I have fitted the task with fault code: illegal_instruction_execution(); which You can found on
" How to debug a HardFault on an ARM Cortex-M MCU" to issue the handler, which in my case issues “MemManage_Handler(void)” , but when the debugger hit this handler, the scheduler is just restarted, and the debugger tab calling stack reports the lastest scheduler restart, no task calling stack before fault code…
How to avoid scheduler restart, or just hit the handler inside and on task running? any help will be appreciated, thanks