Hi Team,
I'm facing an issue while running the bootloader code from the D-Flash region on the S32K118. When I run the code, it unexpectedly jumps to the DefaultISR, and I’m unable to identify the root cause.
The same code works fine when the linker script is configured to run from P-Flash, so the issue seems specific to executing from D-Flash.
Here are some observations:
While waiting for data via UART (using blocking mode with 0xFFFFFFFF timeout or polling), the code proceeds to the next step even if no data is received from the host (I confirmed this by testing without any physical UART connection).
I suspect this could be contributing to the problem, but even when UART functionality is disabled, the code still enters DefaultISR.
Occasionally, the system crashes when trying to write new firmware into P-Flash.
Debugging is also difficult as I’m using -O1 optimization, which might be causing the debug view to behave unpredictably. when I try with -O0 also it jumps to DefaultISR.
This is a high-priority issue, and I would appreciate your help in identifying possible causes and providing a solution at the earliest.
Thank you.
