TA Lifecycle

4.1.7

Test the lifecycle of a TA.

See Test Networking.

1. The TrustZone kit has been burnt into the server and the TrustZone license has been activated.
2. The REE patch has been loaded to the server. The CA and TA can be loaded and can communicate with each other properly.

1. Log in to the REE OS and load the TrustZone REE patch. (See Expected Result 1.)

   insmod tzdriver

   /usr/bin/teecd &

2. Write the test CA and TA. Ensure that print information must be added to each entry API of the TA code, and before and after each GP client API of the CA code. Run the test CA and TA. (See Expected Result 2.)
3. Write the test CA and TA. Ensure that the TA code proactively calls the TEE_Panic API. Run the test CA and TA. (See Expected Result 3.)
4. Write the test CA and TA. Run the kill command to stop the CA process during the running. (See Expected Result 4.)

1. The REE patch is loaded and no error information is displayed.
2. The correct time sequence information is displayed on the CA terminal and can be viewed in the tlogcat security logs. After the CA calls the OpenSession API, the TA instance is created and loaded. After the CA closes the session, the TA instance is destroyed and the resources are reclaimed by the TEE OS.
3. After the TA calls the TEE_Panic API, the TA instance is destroyed and the resources are reclaimed by the TEE. The CA can re-initiate requests to the TA and the TA functions properly.
4. The TA is executed successfully. The TA instance is destroyed and the resources are reclaimed by the TEE due to a timeout (30s).