Common Error Logs

The config binary used for TA compilation does not match the TA private key.

Check whether the TA private key (.pem) used for TA compilation matches the config binary.

If you cannot determine whether they match, see Applying for a TA Developer Certificate in a Debugging Environment and contact Huawei technical support to apply for a new TA developer certificate.

The configuration information in the manifest.txt file during TA application compilation is different from that in the configs.xml file submitted to Huawei. As a result, the configuration check fails when the TA is loaded.

1. Modify the manifest.txt file to match the configuration information the developer submitted for applying for a TA developer certificate from Huawei, and recompile and deploy the TA.
2. If the TA configuration does not meet the service requirements, you need to modify the manifest.txt file of the TA. Contact Huawei technical support to apply for a new config binary file.

The code of a TA contains a function API that is not supported by iTrustee.

Refer to the iTrustee 6.0.0 SDK Developer Guide or contact Huawei technical support to check whether the APIs are supported by the current iTrustee version. If necessary, modify the code to use the supported APIs.

When a CA establishes a communication link with a TA, the CA sends the disk storage path of the TA to the TEE OS. However, the TA is not correctly deployed and the TEE OS cannot find the TA.

The error information can be viewed in the journalctl log and is printed by the teecd daemon.

Check and deploy the TA, and run the CA again.