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
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.
Hello,
I am experiencing the same issue in the same environment.
Could you please share the file with me as well? I would really appreciate your help.
Thank you!
Dear NewbieNerd,
I am facing the same issue in a similar environment.
If you were able to resolve it, could you please share the solution and explain what changed compared to the previous setup?
Your experience would be greatly appreciated and would be very helpful for troubleshooting this issue on my side.
Thank you for your time and support.
Please create new ticket and I will send it to you. Thanks for understanding.
https://www.nxp.com/support/support:SUPPORTHOME
Thank you for your response.
I have already created a support ticket (Case#00994181), which is currently being handled by another support engineer. If possible, would you be able to take a look at the ticket or provide additional support?
Thank you again for your support.