| Name | Date | Size | #Lines | LOC | ||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| vm/ | 04-Jul-2025 | - | 120 | 112 | ||
| Android.bp | D | 04-Jul-2025 | 2.1 KiB | 88 | 82 | |
| AndroidTest.xml | D | 04-Jul-2025 | 3.9 KiB | 57 | 37 | |
| README.md | D | 04-Jul-2025 | 848 | 27 | 18 | |
| trusty-test_vm-config-arm64.json | D | 04-Jul-2025 | 208 | 9 | 8 | |
| trusty-test_vm-config-x86_64.json | D | 04-Jul-2025 | 185 | 8 | 7 | |
| trusty-ut-ctrl.sh | D | 04-Jul-2025 | 712 | 18 | 1 | |
| trusty-vm-launcher.sh | D | 04-Jul-2025 | 821 | 21 | 4 | |
| trusty-wait-ready.sh | D | 04-Jul-2025 | 1.1 KiB | 40 | 27 |
README.md
1## test_vm 2 3The Trusty test_vm ought to include the test TAs for the Trusted HALs, 4defined under hardware/interfaces/security/see: 5 6- AuthMgr 7- Secure Storage 8- HWCrypto 9- HDCP 10 11The Trusty test_vm also includes the VINTF test which allows to check the vendor 12support of the Trusted HALs (version and API hash), against the expected 13compatibility matrix for a given Android Dessert Release. 14 15### instructions 16 17`atest -s <device-serial-port> VtsSeeHalTargetTest 18 19### test_vm console 20 21The test_vm console can be retrieved from `/data/local/tmp/trusty_test_vm/logs/console.log`. 22The script `trusty-vm-laucher.sh` uses `/apex/com.android.virt/bin/vm run` with the option 23`--console` to store the console log. 24 25This log can be consulted when the tests are running and will be uploaded 26by the Tradefed FilePullerLogCollector runner (see AndroidTest.xml). 27