S32K3 Unlock Secure Debug with Trace32

[NewbieNerd]

Hello S32K3 Team,

I am currently experiencing an issue with secure debug unlock.

The debugger I am using is Trace32 and autosar os using....
The Life Cycle (LC) has been switched to OEM, and secure debug is configured in password mode (not challenge–response).

The configured TEST password is:

0xFFEEDDCCBBAA99887766554433221100

Before switching the LC, I confirmed that the HASH value matched correctly.

I have tried the following two methods to unlock secure debug:

Using the Trace32 command:

SYStem.Option KEYCODE %Byte 0xFF 0xEE 0xDD 0xCC 0xBB 0xAA 0x99 0x88 0x77 0x66 0x55 0x44 0x33 0x22 0x11 0x00

Using the S32_JTAG_WRITE.cmm script

However, both methods failed to unlock secure debug.

I would appreciate your guidance on what I should check next or any potential causes I might be overlooking.

I have attached my script for reference.

Best regards,

#HSE #secureDebug

[davidtosenovjan · Accepted solution]

I have recently test it. See attached scripts

debug_authorization.cmm shows how to enter the password and then it calls other scripts.

I am sending you attachment directly.