Part Number: AM62P-Q1
Hello TI Experts,
During analysis debugging of K3 security, there is a table to describe DOM:
Q1: As our understanding, the "DOM" decribes the debug operation with 2 dimensions access:
"Secure/Non-secure":
- non-secure: only can attach normal world, e.g. normal OS, APPL..., cannot attach the secure world, e.g. TEE, HSM...
- secure: can attach secure world, e.g. TEE, HSM...
"Privileged/User":
- privileged: high level access, can attach the core register, memory, ...
- user: low level access, only can attach user data, cannot attach core register and memory.
Am I correct?
Q2: And in the table, Why only said "SECURE bit in Debug SS" and "PRIV bits in DebugSS register"? but not direct use "1"?
for example, "Secure User" mode, in Debug SS register, PRIV[1:0] = 00, but SECURE bit = 0 or 1?
but if it is 0, then "Secure User" mode will be same with "Strict Public Debug" mode.
A little confused for us.
Q3: The“PRIV bits” have 2 bits, that means it have values of "00/01/10/11", what means of them? if only means User or Privileged, why use 2 bits?
Q4: How to map this SECURE Bit and PRIV bits to DEBUGSS_DOM register? in the register, it only mentioned "DOM value as per DebugSS spec".
Q5: In user side, we can config the debug_type as below, and map it with DOM, is it correct?
Thanks in advance!
B.R
