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:
NXP Knowledge Base articles:
-
HOWTO: Build a Project and Setup Debugging with GDB PEmicro (S32DS 3.x)
-
HOWTO: Build a Project and Setup a Debug Configuration for debugging in S32 Design Studio
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.
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
.png){kind=link}
.png){kind=link}