CCSTUDIO: dbgauth for AM625

Hello,

Hust biter said:

For HS-FS type, is it possible to lock the JTAG for all cores(A53s, M4F) except the SMS core, and then unlock it by "dbgauth"? If yes, how to lock the cores (A53s, M4F)? If no, does that mean only for the HS-SE type JTAG of the cores(A53s, M4F)  can be locked?

There is no procedure to lock the cores on either HSFS or HSSE device types. The JTAG is automatically locked for all the cores out of SoC reset on HSSE while the JTAG is always unlocked for all the cores except HSM and TIFS on HSFS.

Hust biter said:

For HS-FS and HS-SE type, the JTAG of SMS core is locked by default. can I unlock  the JTAG of SMS through "dbgauth" or other means on HS-FS/SE? If yes, how to do that?

The SMS is a subsystem hosting two cores (HSM and TIFS). The JTAG can be unlocked for HSM core but not TIFS on both HSFS and HSSE.

Hust biter said:

coreDbgEn is  used to enable non-secure debug, while coreDbgSecEnis used to enable secure debug. I think both of them specify which cores can be unlocked at run time,

The `coreDbgEn` and `coreDbgSecEn` provide the way to enable the non-secure and secure debug of the core. These are ARM cores specific features. So, for understanding the differences between them, you would have to go through their TRMs.

Normally, setting is the debug level to DEBUG_FULL is sufficient for unlocking all the cores for debugging.

https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/security/sec_cert_format.html#sysfw-x509-ext-doc-debug-levels-table:~:text=of%20values%20for-,debug_priv_level,-%3A

Thank you for your reply!

For the 2nd question——"The SMS is a subsystem hosting two cores (HSM and TIFS). The JTAG can be unlocked for HSM core but not TIFS on both HSFS and HSSE.",  specially, how should I unlock the HSM core of SMS on HSFS, by using TISCI API or dbgauth? Is "dbgauth" available for that?

Hust biter said:

specially, how should I unlock the HSM core of SMS on HSFS, by using TISCI API or dbgauth? Is "dbgauth" available for that?

The procedure is the same as the JTAG unlocking procedure on the HSSE device. The only difference is that the debug certificate can be signed with any random valid key for HSFS device.

For HS-FS type, when generating the debug certificate of HSM core of SMS for "dbgauth", shall I need to set  "coreDbgSecEn" for the HSM core of SMS (debugType = INTEGER:0x00000004 & coreDbgEn = INTEGER:0x0 & coreDbgSecEn = INTEGER:0x80 ), and set allow_jtag_unlock to 0x5A in sciclient_defaultBoardcfg_security.c? Is that correct?

Hust biter said:

(debugType = INTEGER:0x00000004 & coreDbgEn = INTEGER:0x0 & coreDbgSecEn = INTEGER:0x80 ), and set allow_jtag_unlock to 0x5A

This is exactly correct.

Oh, the reply came so fast. Thank you very much. I'll try again.

It's a working day after all :)

Please make sure you are using at least SDK v10.1 (specifically at least TIFS v10.1) as the HSM unlock on HSFS devices was enabled starting this TIFS version only.

OK, I'm using "mcu_plus_sdk_am62x_11_02_00_23".

Thank you!