You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,12 +13,12 @@ For more information, visit the [PSA webpage](https://developer.arm.com/products
13
13
API specifications are placed in [PSA API github site](https://github.com/ARM-software/psa-api/).
14
14
15
15
### PSA Certified API Compliance
16
-
The [PSA Certified API tests](api-tests/dev_apis) are the basis for validating compliance with PSA Certified APIs. For more information on the certification program, see [psacertified.org](https://www.psacertified.org/functional-api-certification/)
16
+
The [PSA Certified API tests](api-tests/dev_apis) are the basis for validating compliance with PSA Certified APIs. For more information on the certification program, see [psacertified.org](https://www.psacertified.org/functional-api-certification/)
17
17
18
18
## GitHub branch
19
19
- For API certification, use the release branch and pick the appropriate release tag.
20
20
- To get the latest version of the code with bug fixes and new features, use the master branch.
21
-
21
+
22
22
## Architecture test suite
23
23
24
24
The current implementation of the Architecture test suite contains tests for following PSA Certified specifications. Arm licensees may contact their partner manager to obtain a copy of this specification. <br />
@@ -46,7 +46,7 @@ Arm PSA test suite is distributed under Apache v2.0 License.
46
46
- For feedback, use the GitHub Issue Tracker that is associated with this repository.
47
47
- For support, send an email to support-psa-arch-tests@arm.com with details.
48
48
- Arm licensees can contact Arm directly through their partner managers.
49
-
- Arm welcomes code contributions through GitHub pull requests.
49
+
- Arm welcomes code contributions through GitHub pull requests.
Copy file name to clipboardExpand all lines: secure-debug/README.md
+12-22Lines changed: 12 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
6
6
### ADAC Specification
7
7
8
-
The [ADAC specification](https://developer.arm.com/documentation/den0101/0001) defines the protocol that allows a target to securely authenticate a debug host. The specification targets software-only layers that are above the physical debug link.
8
+
The [ADAC specification](https://developer.arm.com/documentation/den0101/1) defines the protocol that allows a target to securely authenticate a debug host. The specification targets software-only layers that are above the physical debug link.
9
9
10
10
### ADAC test suite
11
11
@@ -17,10 +17,10 @@ The ADAC test suite checks if a device-side implementation conforms to the behav
17
17
- And the corresponding abstraction layers are available with an Apache v2.0 license allowing for external contribution.
18
18
19
19
## Release details
20
-
- Release Version - 0.8
21
-
- Code Quality: Beta <br/>
20
+
- Release Version - 1.0
21
+
- Code Quality: EAC <br/>
22
22
23
-
- The ADAC tests are written for version beta of the ADAC specification.
23
+
- The ADAC tests are written for EAC version of the ADAC specification.
24
24
- This test suite is not a substitute for design verification.
25
25
26
26
## Layers
@@ -34,7 +34,7 @@ These tests are written on top of VAL and PAL.
34
34
35
35
The abstraction layers provide platform information and runtime environment to enable execution of the tests.
36
36
37
-
In this release, PAL implementation for the 'emulation' target uses Unix sockets as the link layer to send commands and receive responses. Arm also provides support for executing the test suite on the 'Musca-b1' hardware board by adding a 'musca_b1' target which uses memory window protocol as the link layer.
37
+
In this release, Arm provides support for executing the test suite on the 'Musca-b1' hardware board by adding a 'musca_b1' target which uses memory window protocol as the link layer.
38
38
39
39
You can also write your own abstraction layer implementations to allow ADAC tests to run on other host platforms and support the debug link layer.
40
40
@@ -46,7 +46,7 @@ The mapping of the rules to the test cases and the steps followed in the tests a
46
46
47
47
48
48
Follow the instructions in the subsequent sections to get a copy of the source code on your local machine and build the tests. <br/>
49
-
See [Arm Authenticated Debug Access Control Test Suite User guide](docs/Arm_Authenticated_Debug_Access_Control_Test_Suite_User_Guide.pdf) to get details on the steps involved in porting the test suite to your platform.
49
+
See [Arm Authenticated Debug Access Control Test Suite User guide](docs/Arm_Authenticated_Debug_Access_Control_Test_Suite_User_Guide.pdf) to get details on the steps involved in running the test suite on your platform.
50
50
This test suite is provided as a separate directory within the psa-arch-tests repository.
51
51
52
52
### Prerequisites
@@ -60,18 +60,11 @@ Before starting the test suite build, ensure that the following requirements are
60
60
61
61
62
62
## Download source
63
+
This repository uses git submodules. Either add the --recurse-submodules argument when running git clone, or run git submodule update --init after cloning.
63
64
To download the main branch of the repository, type the following command:
@@ -95,7 +87,7 @@ To build ADAC test suite for a given host platform, execute the following comman
95
87
"MinGW Makefiles" - to generate Makefiles for cmd.exe on Windows
96
88
- <target-name> target to build, as created in the platform/hosts directory
97
89
- <suite-selection> ADAC - specify the ADAC suite
98
-
- <link-layer> link layer for the host platform, optional for emulation target
90
+
- <link-layer> "memw_pyocd" - link layer protocol used by host, more options can be specified if supported by host platform
99
91
100
92
To build project
101
93
cmake --build .
@@ -113,12 +105,9 @@ The following ADAC test suite build outputs are available under host build direc
113
105
- psa_adac_test executable
114
106
- val and platform layer libraries
115
107
116
-
For running the test suite on the emulation platform, see the [Readme](platform/hosts/emulation/unix_socket/README.md).<br/>
117
108
For running the test suite on the Musca-b1 hardware platform, see the [Readme](platform/hosts/musca_b1/memw_pyocd/README.md).<br/>
118
109
119
110
Note:
120
-
- See the psa-adac directory for information on other target platforms.
121
-
- The keys and the certificate credentials for a supported cryptosystem can be generated using the tools provided in the psa-adac repository.
122
111
- The test suite is designed to run once per supported cryptosystem. Ensure that the device must be provisioned with the correct certificates installed in the device's RoT.
123
112
124
113
## Security implication
@@ -129,6 +118,7 @@ ADAC test suite may run at higher privilege level. An attacker can utilize these
129
118
130
119
Arm ADAC Architecture test suite is distributed under Apache v2.0 license.
131
120
The psa-adac code repository is distributed under BSD-3-Clause license.
121
+
The mbedtls code repository is distributed under Apache v2.0 license.
132
122
133
123
## Feedback, contributions, and support
134
124
@@ -139,4 +129,4 @@ The psa-adac code repository is distributed under BSD-3-Clause license.
139
129
140
130
--------------
141
131
142
-
*Copyright (c) 2021-2022, Arm Limited and Contributors. All rights reserved.*
132
+
*Copyright (c) 2021-2023, Arm Limited and Contributors. All rights reserved.*
0 commit comments