Issue facing during flashing code on NXPS32k144

[Shubham3]

Subject: S32K144 EVB - PEmicro Connection Assistant Error During Debug in S32 Design Studio 3.5

Hello NXP Support Team,

I am facing an issue while debugging an application on an S32K144 evaluation board using S32 Design Studio 3.5.

Environment:

• Board: S32K144 EVB (please update with exact board part number if needed)

• IDE: S32 Design Studio 3.5

• Debug Probe: On-board OpenSDA (PEmicro)

• Operating System: Windows (please specify version)

• Connection Type: OpenSDA USB

Issue Description:
When I start a debug session, the PEmicro Connection Assistant appears with the following message:

"An error occurred while connecting to the interface hardware or target specified in the Launch Configuration Dialog."

The Connection Assistant detects the OpenSDA probe correctly:

• OpenSDA on USB1

• Name = FDC46E50

However, the debugger cannot establish communication with the target MCU.

Observations:

1. OpenSDA is detected successfully by the PC.

2. The board power LED is ON.

3. The issue occurs during debug launch.

4. I have already tried:

   • Pressing the RESET button before debugging.

   • Disconnecting and reconnecting USB.

   • Using a different USB cable.

   • Using a different laptop/PC.

   • Restarting S32 Design Studio.

5. The same issue persists.

Application Information:
The application is based on:

• Pin configuration generated through Pins Tool.

• SDK drivers (PINS_DRV).

• RearWiperControl_Fn generated model code.

Example code executed in main():

• PINS_DRV_Init()

• RearWiperControl_Fn_initialize()

• RearWiperControl_Fn_step()

Questions:

1. What could cause OpenSDA to be detected while target communication fails?

2. Is there any known issue between S32DS 3.5 and the current OpenSDA firmware?

3. Should the OpenSDA firmware be updated or reflashed?

4. Is there a recommended procedure for mass erase or "connect under reset" on S32K144?

5. Are there any jumper settings on the S32K144 EVB that should be verified for debugging?

6. Could incorrect pin mux settings interfere with SWD communication after programming?

Attached:

• Screenshot of the PEmicro Connection Assistant error dialog.

Any guidance on troubleshooting this issue would be appreciated.

Thank you.

[Shubham3]

After flashing below code from example the issue arrives

Uses ADC PAL for a series of SW and HW triggered groups of conversions. Displays on LPUART the average value for each conversion group execution.
The example documentation can be found in the S32 SDK documentation at Examples and Demos section. (/doc/Start_Here.html)

[PavelL]

Hello @Shubham3 ,

Did the board debug correctly before programming this application/example? 

Please check whether your application reconfigures PTA4, PTC4, or PTA5 in Pins Tool / PORT registers. These pins are related to SWD/reset on S32K144.

If yes, this can indeed prevent the debugger from attaching afterwards. Similar cases have already been reported on NXP Community. Please refer to the threads below for possible recovery methods and additional background:

Device is secure , erase to unsecure - NXP Community

Solved: S32K144 -Conflict in PORTA PIN5 CFG vs RESET signal - NXP Community

Solved: Can't use PEmicro debugger with S32K118EVB2-Q048 - NXP Community

Best regards,

Pavel