TDA4AL-Q1: On this chip platform M4F, it is said to support Vector HSM. What is the actual range between the key and certificate?

已咨询e2e产品线工程师，因为这周感恩节美国放假，所以回复会慢些，请关注下面帖子的回复。
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1295789/tda4al-q1-what-is-the-actual-range-between-the-key-and-certificate

能否详细描述一下您的问题？请看下面e2e工程师的回复。

The question is not clear to me can you elaborate more on your usecase?

Hi shine：

The problem summary is as follows:

Question 1: TDA4AL has the WKUP SMS M4F core, which can support third-party Vertor HSM software packages. However, TDA4AL does not have a built-in HSM security chip. Therefore, if the certificate and public key passed by OEM have efuse intervals in EMMC, there is a problem. The problem is that efuse is readable, so the confidentiality of the key and certificate cannot be guaranteed? Or you may have a better recommended solution here

Question 2: If the certificate and key are stored in efuse, what is the current efuse space size of the TDA4AL board? Here, I can evaluate whether efuse memory is sufficient.

已跟进！