S32K debug password usage without HSE

[BhushanM]

Hello Team,

Is it possible to secure the JTAG usage by setting password inside "CUST_DB_PSWD_A" register without installing or enabling HSE FW?

If yes, then could you also provide steps how to take secure access for same by providing password over SEGGER.

Thanks,

Bhushan Mahale

[petervlna]

Hello,

Is it possible to secure the JTAG usage by setting password inside "CUST_DB_PSWD_A" register without installing or enabling HSE FW?

Yes, it is.

If yes, then could you also provide steps how to take secure access for same by providing password over SEGGER.

We do not use segger here, but you can follow the general steps for any programmer.

1. Set up ADKP (Application Debug Key/Password).
2. Make sure the password mode or challenge-response mode.
3. Move the lifecycle to the IN-FIELD stage.

Please see the following thread where it is explained in details:

https://community.nxp.com/t5/S32K-Knowledge-Base/S32K3-Restrict-the-debug-access-with-a-password-whe...

Best regards,

Peter

[BhushanM]

Thanks for the reply.
Once Password is set and LC is moved to In-FIELD,
1. Is it possible to flash Binaries over JTAG again by providing password? If yes, then how?
2. Debug can be done in same LC state or it needs to be moved to other state?

[petervlna · Accepted solution]

Hello,

1. Is it possible to flash Binaries over JTAG again by providing password? If yes, then how?

Yes. This is question for your debugger vendor.

For example PE Micro:

To unlock the MCU, PEmicro provides some Python scripts (PEmicro support files package) to facilitate the authentication of the debugger when the password is set.

Once the debug session is established, you will do simple programming to device as normal.

2. Debug can be done in same LC state or it needs to be moved to other state?

Debug can be done in any lice cycle. You advance life cycle to mature security.

Best regards,

Peter

[BhushanM]

Please do reply.