S32G3 – Debug with S32 Debug Probe when JTAG is password protected (memory dump)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S32G3 – Debug with S32 Debug Probe when JTAG is password protected (memory dump)

1,549 Views
dtejada02
Contributor I

Hello,

I am working with an S32G3 device using an S32 Debug Probe and S32 Design Studio.
The device has JTAG protected with a password (debug authentication enabled).

I have authorization to access this device. My goal is to attach the debugger and dump internal memory (Flash/RAM) for analysis.

At the moment, JTAG access is blocked due to the password, and I would like to know:

  • What is the correct procedure to authenticate/unlock JTAG on S32G3 using the debug password

  • How this is done in practice with S32 Design Studio and the S32 Debug Probe

  • Once authenticated, whether full memory access / memory dump is supported or if there are restrictions

0 Kudos
Reply
2 Replies

1,511 Views
Joey_z
NXP Employee
NXP Employee

Hi,dtejada02

Thank you for contacting us.

Do you do the secure debug? you can refer to this link for your using.

HOWTO: Secure Debugging from S32DS IDE with S32 Debugger and S32 Debug Probe

Technically, memory read/dump can be performed, but the secure memory/HSE protected area may still be unreadable.

BR

Joey

0 Kudos
Reply

1,503 Views
dtejada02
Contributor I
Hi Joey_z,

Thank you for your answer. I followed all the steps of the link you shared and after introducing the password i get the following error:

"Failure during execution of python script. Reason: "[CCS: secure debug attempt failed]\r\n" error has occured during starting debug for launch: 'PROJECT_M7_0_Debug_RAM_S32Debug'. Error code is 1340. See GDB traces console for additional information.

BR,
Diego Tejada
0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2298805%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ES32G3%20%E2%80%93%20Debug%20with%20S32%20Debug%20Probe%20when%20JTAG%20is%20password%20protected%20(memory%20dump)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2298805%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI%20am%20working%20with%20an%20%3CSTRONG%3ES32G3%3C%2FSTRONG%3E%20device%20using%20an%20%3CSTRONG%3ES32%20Debug%20Probe%3C%2FSTRONG%3E%20and%3CSTRONG%3E%20S32%20Design%20Studio.%3C%2FSTRONG%3E%3CBR%20%2F%3EThe%20device%20has%20%3CSTRONG%3EJTAG%20protected%20with%20a%20password%3C%2FSTRONG%3E%20(debug%20authentication%20enabled).%3C%2FP%3E%3CP%3EI%20have%20authorization%20to%20access%20this%20device.%20My%20goal%20is%20to%20%3CSTRONG%3Eattach%20the%20debugger%20and%20dump%20internal%20memory%20(Flash%2FRAM)%3C%2FSTRONG%3E%20for%20analysis.%3C%2FP%3E%3CP%3EAt%20the%20moment%2C%20JTAG%20access%20is%20blocked%20due%20to%20the%20password%2C%20and%20I%20would%20like%20to%20know%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3EWhat%20is%20the%20%3CSTRONG%3Ecorrect%20procedure%20to%20authenticate%2Funlock%20JTAG%3C%2FSTRONG%3E%20on%20S32G3%20using%20the%20debug%20password%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EHow%20this%20is%20done%20in%20practice%20with%20%3CSTRONG%3ES32%20Design%20Studio%3C%2FSTRONG%3E%20and%20the%20%3CSTRONG%3ES32%20Debug%20Probe%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EOnce%20authenticated%2C%20whether%20%3CSTRONG%3Efull%20memory%20access%20%2F%20memory%20dump%3C%2FSTRONG%3E%20is%20supported%20or%20if%20there%20are%20restrictions%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2299207%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20S32G3%20%E2%80%93%20Debug%20with%20S32%20Debug%20Probe%20when%20JTAG%20is%20password%20protected%20(memory%20dump)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2299207%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EHi%20Joey_z%2C%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20you%20for%20your%20answer.%20I%20followed%20all%20the%20steps%20of%20the%20link%20you%20shared%20and%20after%20introducing%20the%20password%20i%20get%20the%20following%20error%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%22Failure%20during%20execution%20of%20python%20script.%20Reason%3A%20%22%5BCCS%3A%20secure%20debug%20attempt%20failed%5D%5Cr%5Cn%22%20error%20has%20occured%20during%20starting%20debug%20for%20launch%3A%20'PROJECT_M7_0_Debug_RAM_S32Debug'.%20Error%20code%20is%201340.%20See%20GDB%20traces%20console%20for%20additional%20information.%3CBR%20%2F%3E%3CBR%20%2F%3EBR%2C%3CBR%20%2F%3EDiego%20Tejada%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2299050%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20S32G3%20%E2%80%93%20Debug%20with%20S32%20Debug%20Probe%20when%20JTAG%20is%20password%20protected%20(memory%20dump)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2299050%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2Cdtejada02%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20contacting%20us.%3C%2FP%3E%0A%3CP%3EDo%20you%20do%20the%20secure%20debug%3F%20you%20can%20refer%20to%20this%20link%20for%20your%20using.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2FS32-Design-Studio-Knowledge-Base%2FHOWTO-Secure-Debugging-from-S32DS-IDE-with-S32-Debugger-and-S32%2Fta-p%2F1964462%22%20target%3D%22_blank%22%3EHOWTO%3A%20Secure%20Debugging%20from%20S32DS%20IDE%20with%20S32%20Debugger%20and%20S32%20Debug%20Probe%3C%2FA%3E%3C%2FP%3E%0A%3CP%3ETechnically%2C%20memory%20read%2Fdump%20can%20be%20performed%2C%20but%20the%20secure%20memory%2FHSE%20protected%20area%20may%20still%20be%20unreadable.%3C%2FP%3E%0A%3CP%3EBR%3C%2FP%3E%0A%3CP%3EJoey%3C%2FP%3E%3C%2FLINGO-BODY%3E