S32K358 SECURE DEBUG

[abunayeeem]

We have designed a custom board using the NXP S32K358 microcontroller. While trying to upload the first code using the S32 Design Studio (S32DS) IDE, we are encountering the following error:

"Secure Debug might be enabled on this device. If so, please unlock the device via PEmicro scripts before attempting to connect again."

We suspect that the MCU’s debug interface is locked, preventing us from uploading code or debugging. Could you please provide a step-by-step guide to unlock the debug interface??

[abunayeeem]

Hi @VaneB ,

We are still unable to debug the MCU.
Our support ticket is closed without any resolution and your feedback is appreciated.

BR, Nayeem

[VaneB]

Hi @abunayeeem 

I have reviewed your previous cases and noticed that you are using an FS26. As mentioned earlier, this issue is typically related to communication problems. It is possible that the SBC is not powering correctly, which could prevent the MCU from being programmed.

Please review the following thread, which contains information that could be useful.

FS26

[abunayeeem]

Hi @VaneB ,
The FS26 power rails are working fine.
We have checked the voltages of the physical pins of both FS26 and MCU.

We have applied
> VDD_HV_A & VDD_HV_B - (+5V)
> Vcore - (+1.5V)
>Vref - (+5V)
We have also checked V11 and V25 which are also fine. We have used the same board with previous MCUs (P32K358HVS 0P14E CTAB2335A ) which was working just fine.

Current MCU part number is - S32K358GHMPCS 1P14E CTAG2428B

[VaneB]

Hi @abunayeeem 

I have consulted with the internal team regarding your situation. We need your assistance to verify a few details to determine whether the issue is related to the MCU or the software.

Firstly, if possible, could you replace the MCU with the one that previously showed no issues? Does exhibit the same problem, or is it functioning properly?

Also, the part number you initially used has custom firmware for VW. Were the PEMicro scripts you used also customized?

Lastly, did your project include any modifications to the lifecycle?"

[abunayeeem · Accepted solution]

Hi @VaneB ,

Thank you for your support. We have found the issue. RST_B pin of FS26 was low and it was resetting the MCU which restricted us from debugging the MCU. After isolating the the RST_B from MCU pin, we are now able to debug the MCU.

[VaneB]

Hi @abunayeeem 

I am checking the situation with the internal team and will let you know the response as soon as I have an update.

Thank you for your patience.

[VaneB]

Hi @abunayeeem 

When programming the MCU for the first time, secure debug should be disabled, and this error message is usually related to communication issues. Please verify that the chip is powered correctly and that you are using the latest version of the PEMicro plugin. To update, go to Help > Install New Software, then select the PEMicro page.

Additionally, could you provide information about your programming algorithm?

BR, VaneB

[abunayeeem]

Hi @VaneB ,
We have updated the PEmicro plugin and the chip is powered correctly.

Please find attached the flash algorithm information.

BR, Nayeem