I have locked my S32K344 with a password. I can still connect to it through the JTAG interface by providing the password in jlink scripts. However, when using Ozone the connection is not granted.
Case 1: not providing the password in the jdebug file.
In this case a window pops up, where I add the password. In the console window I see that unlocking was successful and RAM is being initialized by Ozone. Then the core enable sequence fails and Ozone shows "J-Link reports an unspecific download error".
The USB LED of j-Trace is red.
Case 2: providing the password in the jdebug file in function "BeforeTargetConnect" (Exec.Command("SetCPUConnectIDCODE <my password>");).
Unlocking is not successful.
Case 3: providing the password in the jdebug file in function "BeforeTargetConnect" (Exec.Command("SetCPUConnectIDCODE <my password>");).
The connection procedure hangs in the unlock step.
Has anybody successfully used Ozone with a locked S32K device?
Hi @arx
The issue appears to be related to Segger's tool. Since this falls outside the scope of our support, I would recommend reaching out to Segger directly for further assistance.
BR, VaneB