MCU Stuck at b Infinite_Loop startup file, with FreeRTOS

Possibly a bus fault or other fault (there are several types of faults, each with its own interrupt vector). All interrupt/fault vectors that are not explicitly initialized point to that code. @Community member​ has posted several (many) versions of fault handler code. Search the forums. This will allow you to see what caused the fault. Maybe an uninitialized pointer that the interrupt handler accesses. I haven't used CubeIDE yet, but that screen shot doesn't look like an decoding of the actual, current stack contents (the "static" in "static stack analyzer" implies that this is a compile-time analasys of which functions call which other functions. I may be wrong though - like I said, I have not yet used that IDE.

Hi.. thanks for your feedback

Cube IDE has the facility to trace the any hard-fault or fault

I have added the hard-fault handler

However, I haven't found any fault withing the fault analyzer

Find the run-time call stack display (not the static stack analasys). Again, I don't know CubeIDE, but in Eclipse it is usually displayed in the "Debug" window/tab. It is shown as a tree structure, with the project name at the top, then a series of function names and (maybe) line numbers. Starting with main(). Something like this: