Skip to content

Commit

Permalink
Merge pull request #63 from jaypit02/master
Browse files Browse the repository at this point in the history
Add table for Developer APIs test list in README
  • Loading branch information
prasanth-pulla authored Feb 18, 2019
2 parents 9b833f3 + 84782f6 commit ad7cc56
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 10 deletions.
21 changes: 12 additions & 9 deletions api-tests/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,20 +21,23 @@ The test suite for this specification is located in the dev_apis directory of th

## Release Update
- Release Version - 0.8
- Code Quality: Beta. Please use this opportunity to suggest enhancements and point out errors.
- Current release contains following Developer APIs tests:
1. **Crypto tests** that are written for the crypto service APIs defined in the [crypto.h](../api-specs/include/psa/crypto.h)
2. **Protected Storage tests** that are written for the protected storage service APIs defined in the [protected_storage.h](../api-specs/include/psa/protected_storage.h)
3. **Internal Trusted Storage tests** that are written for the internal trusted storage service APIs defined in the [internal_trusted_storage.h](../api-specs/include/psa/internal_trusted_storage.h)
4. **Initial Attestation tests** that are written for the initial attestation service APIs defined in the [initial_attestation.h](../api-specs/include/psa/initial_attestation.h)
- Current release contains following PSA-FF tests:
1. **IPC tests** that are written for version 1.0-Beta-0 of the PSA FF specification.
- Code Quality: Please use this opportunity to suggest enhancements and point out errors.
- Current release contains following tests:
1. Developer APIs test list:

| Test Category | Specification Version | Header File |
|--------------------------|--------------------------------------|-----------------------------------------------------------------------------------|
| Crypto | PSA Crypto API 1.0 Beta-1 | [crypto.h](../api-specs/include/psa/crypto.h) |
| Protected Storage | PSA Protected Storage API 1.0 | [protected_storage.h](../api-specs/include/psa/protected_storage.h) |
| Internal Trusted Storage | PSA Internal Trusted Storage API 1.0 | [internal_trusted_storage.h](../api-specs/include/psa/internal_trusted_storage.h) |
| Initial Attestation | PSA Initial Attestation API 1.0 Beta-0 | [initial_attestation.h](../api-specs/include/psa/initial_attestation.h) |

2. PSA-FF **IPC tests** that are written for version 1.0-Beta-0 of the PSA FF specification.

## License

Arm PSA test suite is distributed under Apache v2.0 License.


## Feedback, contributions, and support

- For feedback, use the GitHub Issue Tracker that is associated with this repository.
Expand Down
3 changes: 2 additions & 1 deletion api-tests/docs/porting_guide_dev_apis.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,8 @@ An example of the input configuration file is as shown.
- Update platform/targets/<platform_name>/target.cfg with your platform detail. Refer val/common/val_target.h for structure details.
- Update platform/targets/<platform_name>/Makefile appropriately to select correct instances of PAL files for compilation. To compile dev_apis suites, you must set PSA_IPC_IMPLEMENTED to 0. This selects the non-secure PAL instances for the driver services and eliminates IPC dependency for dev_apis tests.
- Refer "PAL API list" section to view list of PAL APIs that must be ported for your target platform. These APIs definitions are available in nspe/<suite_name>/pal_\*\_intf.c. These APIs are written for tgt_dev_apis_mbedos_fvp_mps2_m4 platform. You can reuse the code if it works for your platform. Otherwise you must port them for your platform specific peripherals.
- The platform make file is invoked as part of test suite build tool(./setup.sh) step and it creates <build_dir>/BUILD/platform/pal_nspe.a archive.
- Update Crypto configuration file - nspe/crypto/pal_crypto_config.h to enable/disable crypto features selectively for crypto test suite
- The platform make file is invoked as part of test suite build tool(./setup.sh) step and it creates <build_dir>/BUILD/platform/pal_nspe.a archive.

**Note**:
Test suite needs access to the following peripherals:<br \>
Expand Down

0 comments on commit ad7cc56

Please sign in to comment.