PE Micro Programming Issue

sharathkumar2026 — Thu, 27 Aug 2026 05:44:17 GMT

Hey NXP

I am using an S32K344 EVB Custom Board with a PEmicro Multilink Universe FX Rev-D
10-pin JTAG/SWD debug probe and S32 Design Studio (S32DS) version 3.6.8.

I would like to flash an application into the normal internal Program Flash of the S32K344.

I am not using HSE Secure Boot, Secure Debug, or any other security features which is not in our scop and not required for our Debug requirements.

currently I am facing the attached Issue while debugging so Your Immidiate guidence will help to resolve the issue in required fields

Could you someone please provide the detailed steps for:

Connecting the PEmicro 10-pin JTAG/SWD debugger to the 10 Pin - S32K344 Custom EVB.
Creating the correct Debug/Run configuration in S32DS 3.6.8.
Selecting the proper interface (SWD or JTAG).
Configuring flash programming settings (Erase, Program, Verify).
Setting the correct target device and connection mode.
Any required linker or memory configuration for standard internal flash programming.
Recommended settings to avoid Secure Debug/HSE-related issues.
Troubleshooting steps if the debugger detects the device but fails during flash programming.

I am looking for a complete flashing procedure and the exact S32DS configuration required for successful programming and debugging of the S32K344 EVB using a PEmicro probe.

Re: PE Micro Programming Issue

danielmartynek — Mon, 31 Aug 2026 07:26:08 GMT

Hi @sharathkumar2026,

The error you are seeing (the PEmicro "Secure Debug" warning) does not necessarily mean HSE firmware is active. Secure Debug can also be enabled purely through UTEST OTP, by programming the debug password at 0x1B000080 and advancing the lifecycle state — without any HSE firmware involvement. I assume you have not done this either, but it is worth mentioning.

Additionally, this error could appear as a false positive when the MCU resets unexpectedly during the debugger's initial connection handshake. Could you please:

Monitor the RESET_B pin with an oscilloscope or logic analyzer while the debugger is disconnected — is it toggling or held low?
Confirm whether the board was working before this failure, or if this is a new board that has never been programmed successfully.
Let us know how many boards are in this state — is this isolated to one unit, or are multiple boards affected?

Note on the PEmicro algorithm

The PEmicro debugger uses a proprietary flash algorithm, so the exact meaning of internal error codes is not publicly documented. I would recommend also reaching out directly to PEmicro support.

1 & 2. S32DS uses the PEmicro GDB Server plugin. The complete plugin documentation is available here:

S32DS uses the PEmicro GDB Server plugin. The complete plugin documentation is available here:

PEmicro GDB Server for Eclipse-based IDEs

NXP Knowledge Base articles:

3. Either interface will work for the S32K344.

4. These settings are handled automatically by the PEmicro flash algorithm.

5. Simply select the derivative in the debug configuration.

6. Any of the RTD (Real-Time Drivers) example projects for S32K344 include a ready-to-use linker file and memory configuration targeting internal flash.

7. If HSE firmware is not installed on your device, ensure that the hse_disabled flash algorithm variant is selected in the PEmicro debugger settings.

danielmartynek_0-1788161026086.png

8. Please check the following:

Is the RESET_B signal stable after power-on reset or does it toggle? An unexpected reset during the flash operation could be the root cause.

Is the power supply clean and stable throughout the operation?

After a power-on reset, does a previously programmed application execute normally, or does the device appear to hang or reset repeatedly?

Do you have access to another PEmicro probe (or a probe from a different vendor, such as a J-Link) to rule out a probe-specific issue?

Is the failure consistent across all boards, or limited to one unit?

Regards,

Daniel

S32K中的主题 Re: PE Micro Programming Issue

PE Micro Programming Issue

Re: PE Micro Programming Issue