Flashing Code on S32K144 EVB – Debug Works but Run Causes Error

[KAVIN7]

Hello,

I am using S32 Design Studio Platform v3.4 with the S32K144 EVB for application development.

Currently, I am able to debug the application successfully using the debugger in S32 Design Studio. However, whenever I try to Run the application, an error window appears, and the application does not execute as expected.

Additionally, after power cycling the board, the previously loaded code does not run automatically, which indicates that the code might not be getting flashed permanently into the MCU and is only running during the debug session.

I would like to understand:

1. Why debugging works, but running the application results in an error.

2. Whether additional configuration is required to flash the code permanently to the S32K144 MCU.

3. If any linker settings, debugger settings, or flash programmer configuration need to be modified.

4. Whether an external flash programmer (such as PEMicro Flash Programmer) is required, or if S32 Design Studio alone is sufficient.

My goal is to properly flash the application into the internal flash memory so that the code runs automatically after reset or power cycling.

Please let me know the correct procedure to resolve this issue.

[VaneB]

Hi @KAVIN7 

Based on the information you provided, I understand that you first flash the application using Debug Configurations, where the code runs correctly, and afterward you attempt to flash it again using a Run Configuration.

Since the application behaves as expected when launched in Debug mode, a possible cause of the issue could indeed be an incorrect Run Configuration.

Another important point to consider is what happens after resetting the MCU. If the program runs only while debugging but stops working after a reset, it is possible that the code is being loaded into RAM instead of Flash. When code is placed in RAM, it does not persist after a reset or power cycle, which would explain why it works immediately after flashing in Debug mode but not afterward.

Lastly, because you are using an EVB and, as I understand, relying on the onboard debugger (OpenSDA), please keep in mind that OpenSDA uses PEmicro firmware. This is important because, as you can see in your project’s Run Configurations, there is no existing Run Configuration for PEmicro, unlike the default Debug Configuration automatically generated for the PEmicro interface.

BR, VaneB