mirror of
https://github.com/openharmony/tee_tee_dev_kit.git
synced 2026-08-25 09:09:44 -04:00
85896a69f8
Match-id-774de57e557c76bef4abe4940616c1c90427f6c3
2.9 KiB
2.9 KiB
Introduction to ddk capabilities
Introduction
The DDK capabilities include: Driver compilation dependent scripts and header files, driver's ability to issue certificates and sign perm_config signatures, and sec file signatures.
Content
The warehouse directory structure is as follows:
├── build
│ ├── cmake # cmake compile framework capabilities
│ ├── config_tee_private_sample.ini # sec signed and perm_config signed python ini configuration file
│ ├── keytools # Driver certificate issuance, and release type perm_config signature and non-interoperable sec file signature capabilities
│ ├── mk # make compile framework capabilities
│ ├── pack-Config # Signature packaging perm_config capability
│ ├── signtools # sec signature capability python script
│ └── tools # ld file (32-bit and 64-bit) linked by sec file, sec file binary check shell script
├── CHANGELOG # Changelog of DDK version.
├── include # Driver compilation dependent header files
├── README.md # English description file of DDK package
├── README_zh.md # Chinese description file of DDK package
├── demo # Driver development sample
├── rust_drv_apis # Rust FFI interfaces for driver
├── thirdparty
│ └── open_source
│ ├── libboundscheck # Driver compilation depends on the security function library header file archive path
│ └── musl # Driver compile dependent libc header files archive path
└── VERSION # DDK package software version number
Software Installation
Note that this kit can only be used on the linux server and cannot be used on the windows side. And depends on the following software:
- Install python3 software;
- Install the pycryptodomex library of python3
- Export the musl and bounds_checking_function header files, and follow the md instructions under thirdparty\open_source\bounds_checking_function and thirdparty\open_source\musl.