LP-AM261: Enabling Debug in HS-SE device

Hi Nithin,

I believe you are asking about enabling the JTAG trace.

Hi Nilabh,

Thank you for the response.

Nilabh Anand said:

I believe you are asking about enabling the JTAG trace.

Yes, I am looking for enabling JTAG debug.

While going through the example, i have few more doubts.

• --dev_dbg_type 2 means what? could you please elaborate? does that mean DBG_PUBLIC_ENABLE?
• What DBG_SOC_DEFAULT really mean?
• Can we interchange between DBG_SOC_DEFAULT, DBG_PUBLIC_ENABLE and DBG_FULL_ENABLE at any point of time?
  • How can we do it?

How is the secure debug flow?

• Once debug authorization is done (HsmClient_openDbgFirewall), can we do debug from there on, and debug is enabled at power cycles?
• Or should we add HsmClient_openDbgFirewall all images we want to debug? or should the image certificate with some specifical field.

In SDK_PATH\devconfig\devconfig.mak file contain the following comments:

# Debug options for HS (DBG_PERM_DISABLE / DBG_SOC_DEFAULT / DBG_PUBLIC_ENABLE / DBG_FULL_ENABLE)
# This option is valid only if DEBUG_TIFS is false
DEBUG_OPTION?=DBG_SOC_DEFAULT

what does that mean?

DEBUG_TIFS  is for what?

Hi Nithin,

Nithin Kurian said:

Can we interchange between DBG_SOC_DEFAULT, DBG_PUBLIC_ENABLE and DBG_FULL_ENABLE at any point of time?

• How can we do it?

This is one time configurable per reset cycle.

Nithin Kurian said:

While going through the example, i have few more doubts.

• --dev_dbg_type 2 means what? could you please elaborate? does that mean DBG_PUBLIC_ENABLE?
• What DBG_SOC_DEFAULT really mean?
• Can we interchange between DBG_SOC_DEFAULT, DBG_PUBLIC_ENABLE and DBG_FULL_ENABLE at any point of time?
  • How can we do it?

Nithin, I will highly encourage you to go through the documentation, it clearly explains what each level means. Attaching the doc path for refernec:

docs/api_guide_am263px/html/HSM_DBG_SRV.html

I cannot share more details here, please navigate to documentation for more  details.

Nithin Kurian said:

How is the secure debug flow?

• Once debug authorization is done (HsmClient_openDbgFirewall), can we do debug from there on, and debug is enabled at power cycles?
• Or should we add HsmClient_openDbgFirewall all images we want to debug? or should the image certificate with some specifical field.

The debug setting are applicable for per reset cycle, once programmed cannot be changed until you reset the soc.

You can use certificate of SBL for debug port configuration.