i.MX ProcessorsのトピックRe: [i.MX8M Plus] Secure JTAG Operation Issue Inquiry

[i.MX8M Plus] Secure JTAG Operation Issue Inquiry

dhj — Mon, 16 Oct 2023 07:34:15 GMT

We have previously inquired about this issue:

https://community.nxp.com/t5/i-MX-Processors/i-MX8M-Plus-Is-secure-jtag-a-trace32-demo-script-executed/m-p/1688753#M209348

Following the support from NXP technical team, we received a Trace32 script, and it seemed to work correctly when executed with this script. However, this operation was successful only when the secure JTAG-related efusing was performed (SJC_RESP, SJC_RESP_LOCK, JTAG_SMODE).

We added efusing specific to our product as follows:

/* SRK_HASH[255:0] - SRK write */ fuse prog -y 6 0 <confidential> fuse prog -y 6 1 <confidential> fuse prog -y 6 2 <confidential> fuse prog -y 6 3 <confidential> fuse prog -y 7 0 <confidential> fuse prog -y 7 1 <confidential> fuse prog -y 7 2 <confidential> fuse prog -y 7 3 <confidential> /* SEC_CONFIG[1] - 0x470[25] - Closed device */ /* BOOT_MODE_FUSE - 0x470[15:12] - eMMC Boot */ /* BT_FUSE_SEL - 0x470[28] - enable eFuse BOOT_MODE */ /* JTAG_SMODE[1:0] - 0x470[23:22] */ fuse prog -y 1 3 0x12402000 /* WDOG_EN - 0x480[10] - Watchdog reset counter enable * fuse prog -y 2 0 0x400 /* USDHC_PWR_EN - 0x490[7] - eMMC reset enable */ /* IMG_CNTN_SET1_OFFSET - 0x490[22:19] - Secondary Image Boot Offset (8mb) */ fuse prog -y 2 1 0x180080 /* SJC_RESP[63:0] - 0x600-0x610 */ /* SJC_RESP[127:64] - 0x7D0-0x7E0 */ fuse prog -y 8 0 0x12345678 fuse prog -y 8 1 0x9abcdef0 fuse prog -y 15 1 0x12345678 fuse prog -y 15 2 0x9abcdef0 /* SJC_RESP_LOCK - 0x400[10] */ /* SRK_LOCK - 0x400[9] */ /* BOOT_CFG_LOCK - 0x400[3:2] */ fuse prog -y 0 0 0x604

trace32 area log:

Are there any other values besides the secure JTAG-related efusing that might have an impact? Or could there be another reason? We are looking forward to your prompt response.

Thank you.

Re: [i.MX8M Plus] Secure JTAG Operation Issue Inquiry

joanxie — Mon, 16 Oct 2023 09:21:11 GMT

let me double checked this from script owner, any update, I will post here

Re: [i.MX8M Plus] Secure JTAG Operation Issue Inquiry

dhj — Tue, 17 Oct 2023 02:41:55 GMT

Upon further investigation, we have confirmed that when proceeding with SEC_CONFIG[1] - 0x470[25] - Closed device, we are unable to perform the attach. It seems that HAB is affecting the SJC in this case.

Re: [i.MX8M Plus] Secure JTAG Operation Issue Inquiry

joanxie — Tue, 17 Oct 2023 05:44:18 GMT

so you have found the root cause, right? do you still need further help?

Re: [i.MX8M Plus] Secure JTAG Operation Issue Inquiry

dhj — Tue, 17 Oct 2023 05:58:20 GMT

The issue has not been resolved. We require secure boot functionality, and for this, we need to use the device closed state (SEC_CONFIG[1] - 0x470[25]).

We mentioned that among several efusing data we applied, SEC_CONFIG[1] - 0x470[25] was the issue. We hoped for a quicker response as the NXP technical support team is aware of this and has looked into it.

Please provide guidance on how to use Secure JTAG while using our efusing.

Re: [i.MX8M Plus] Secure JTAG Operation Issue Inquiry

joanxie — Wed, 18 Oct 2023 06:26:57 GMT

the expert team has issue on another case this week, they will help you next week, do you mind if I put you in the group, and you can contact them directly? maybe call is better

Re: [i.MX8M Plus] Secure JTAG Operation Issue Inquiry

dhj — Wed, 25 Oct 2023 00:41:02 GMT

I can directly contact them via email.

and...

Has my inquiry been forwarded to them? Do I need to send a separate email to them, or should I wait for a response

Re: [i.MX8M Plus] Secure JTAG Operation Issue Inquiry

joanxie — Wed, 01 Nov 2023 03:48:14 GMT

I have already forward your new request to them before, you also can send to them again for save