Abort Exception means almost always corrupted memory, especially if it happens in system code and not in your own. Are you able to reproduce this in the debugger?
in that case:
You can put breakpoint in inti.s– use DIGI ESP debugger’s console (it’s a regular gdb console actually and it accepts regular gdb commands)
etc to set breakpoints
Once you will get an exception , you will hit one of those breakpoints and you will know what exception did you get. Once this happens, look at the link register (LR) - go to the instruction that is on address pointed by the LR - you may have to switch to mixed mode where both C and assembly language instructions are displayed. Once you there, put a breakpoint on the previous instruction - this is the line that caused look and try to figure what this instruction is doing. If it is not HW exception, you can look at the call stack when you hit your breakpoint at customizeExceptionHandler() and try looking at the call stack at this point in DIGI ESP.