Part Number: AM263P2
Hello Team,
The secure debug for AM263Px SitaraMCU processor information is spread across multiple sections of the technical documentation. The SDK has been helpful in understanding the concept—thank you for that.
However, we have a few follow-up questions:
Permanent Debug Disable: Our requirement is to permanently disable debug access. In the SDK, we noticed the API: SecMgr_isJTAGDisabled()
1. Is checking this status sufficient to confirm that JTAG/debug access is fully and permanently locked?
Alternate Debug Access Paths
2. Are there any other possible interfaces or mechanisms through which debug access could still be enabled, even if JTAG is reported as disabled.
OTP / eFuse-Based Disable
While looking for clarification, we came across a presentation stating (: https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1531676/mcu-plus-sdk-am263px-method-to-enable-secure-debug-on-r5f-and-hsm-core/5893756?tisearch=e2e-quicksearch&keymatch=Secure%20debug ):“Permanent disable via JTAG using OTP KW is currently not supported.” Could you please clarify:
3. Does this mean that permanent debug disable using OTP/eFuse is not supported?
