Unable to Debug dio_ToggledLED_S32K144 Example – Debug Error After Flashing

[KAVIN7]

Hi,

I am working with S32K144 using S32 Design Studio 3.4.

I tried debugging the dio_ToggledLED_S32K144 example project.
The code flashes successfully, and I can see the LED toggling output initially. However, after some time, an error window appears, and after that, I am not able to continue debugging.

Due to this issue, I am unable to debug the application properly.

Could you please help with the following:

1. What could be the possible reason for this debug error appearing after flashing?

2. Is this related to debugger connection (J-Link / PEMicro), watchdog, or clock configuration?

3. Are there any known issues with the dio_ToggledLED_S32K144 example in S32 Design Studio 3.4?

4. What are the recommended steps to resolve this issue and debug the project correctly?

Any guidance to resolve this issue would be very helpful.

Thank you for your support.

[Julián_AragónM]

Hi @KAVIN7,

No, there should not be any problems with the Dio example, as the project only toggles a LED.

Could you provide a bit more information about how to reproduce your issue?

1. How long are you running the project before the issue appears?

2. When the issue happens, are you able to reload the debug session and flash the MCU again?

3. Can you confirm you have the latest Pemicro version available?

4. Have you modified the project in any way?

This issue seems to point to PEmicro drivers or debug configuration, as the Dio example does not configure anything related to watchdog or power modes.

Best regards,
Julián

[KAVIN7]

Hi Julián,

Thank you for your response.

Please find the details below:

1. The issue appears after running the project for a few seconds to about one minute. Initially, the code runs correctly and the LED toggles, but after some time, a debug error window appears, and the debug session stops.

2. When the issue occurs, I am not able to continue debugging. In some cases, I need to terminate the debug session and restart S32 Design Studio to flash the MCU again.

3. I will recheck and confirm the PEmicro driver version. Currently, I am using the default PEmicro version installed with S32 Design Studio 3.4.

4. To clarify, this issue is not only with the Dio example code.
   I created a separate user application (custom GPIO project) from scratch.

   In this user-created project, I enabled the following MCAL components:

   • Mcu

   • Port

   • Dio

   • Dem

   • Ecuc

   In the Dio configuration, I selected RED LED (Dio channel 15).
   When I debug this user-created GPIO application, I face the same debug issue, similar to the one shown in the attached image.

Based on this, the problem seems to be related to the debug configuration or PEmicro connection, rather than the Dio example logic itself.

Please let me know if you need any additional details or logs from my side.

[Julián_AragónM]

Hi @KAVIN7,

Looking through your configuration, I can see you do not have any pins configured in the "UnTouchedPortPin" container. In order to be able to use the debug capabilities, the JTAG and Reset pins need to be configured in the Port driver using mechanism B. This means that the following pins/functionalities need to be added in the UnTouchedPortPin list: 4, 5, 10, 68 & 69.

This may not be your root cause, since your issue appears after running the project for some time, but it does not hurt to try.

Like I've said in my previous response, you can also try updating your SW. Latest versions are:

• S32DS: 3.6.5
• S32K1 RTD: 3.0.0
• Pemicro: 6.1.7 

Lastly, please try sharing a log form the debug interface, as well as debug configuration, as it is very difficult to pinpoint an issue like this, as it cannot be reproduced on my side. Here is my debug configuration which seems to work correctly:

Best regards,
Julián

[KAVIN7]

Hi,

Thank you for the information.

However, I believe the issue discussed in this thread (Unable to Debug dio_ToggledLED_S32K144 Example — Debug Error…) is not the exact problem I’m facing.

My issue is described in this other ticket instead, where I’m getting a PE Micro Connection Assistant error due to missing port configuration:

https://community.nxp.com/t5/S32K/PE-Micro-Connection-Assistant-Error-Due-to-Missing/m-p/2303757#M56...

In my case:

• I created a custom GPIO application for LED toggle.

• I enabled only the RED LED pin in Dio/Port configuration.

• I did not enable the “UntouchedPortPin” debug pins (JTAG/RESET/XTAL/EXTAL).

• This results in the PE Micro connection failure, as shown in the attached image in that ticket.

I believe the issue is related to missing port pin configuration required for debug interfaces (JTAG/RESET/XTAL/EXTAL), and not a problem with the dio example itself.

I need this resolved because I cannot proceed with further implementation until the basic debug connection works.

Could someone please review the linked ticket and advise on the correct pin configuration or steps to fix the debug connection issue?

Thank you.