docs: Add Corstone-320

Signed-off-by: Gergely Korcsák <[email protected]>

Author: gergelykarm

README.md

@@ -29,6 +29,8 @@ is used to run the application artefacts.
 The [currently released version <11.24.22>](https://developer.arm.com/downloads/-/arm-ecosystem-fvps)
 of FVP is supported by the FRI.
 
+* [Corstone-320](https://developer.arm.com/Processors/Corstone-320)
+  * Arm Cortex-M85 CPU, Ethos-U85 NPU and Mali-C55 ISP
 * [Corstone-315](https://developer.arm.com/Processors/Corstone-315)
   * Arm Cortex-M85 CPU, Ethos-U65 NPU and Mali-C55 ISP
 * [Corstone-310](https://developer.arm.com/Processors/Corstone-310)

docs/applications/blinky.md

@@ -19,19 +19,19 @@ setup correctly before proceeding.
 
 To build the blinky example, run the following command:
 ```bash
-./tools/scripts/build.sh blinky --target <corstone300/corstone310/corstone315> --toolchain <ARMCLANG/GNU>
+./tools/scripts/build.sh blinky --target <corstone300/corstone310/corstone315/corstone320> --toolchain <ARMCLANG/GNU>
 ```
 
 Run the command below to perform a clean build:
 ```bash
-./tools/scripts/build.sh blinky --target <corstone300/corstone310/corstone315> --toolchain <ARMCLANG/GNU> -c
+./tools/scripts/build.sh blinky --target <corstone300/corstone310/corstone315/corstone320> --toolchain <ARMCLANG/GNU> -c
 ```
 
 ## Running the application
 
 To run the blinky example, run the following command:
 ```bash
-./tools/scripts/run.sh blinky --target <corstone300/corstone310/corstone315>
+./tools/scripts/run.sh blinky --target <corstone300/corstone310/corstone315/corstone320>
 ```
 
 ### Expected output

docs/applications/device_advisor/running_aws_iot_core_device_advisor_tests.md

@@ -65,15 +65,15 @@ Save and close the file.
 To build the application, run the following command:
 
 ```bash
-./tools/scripts/build.sh ${APPLICATION_NAME} --certificate_path <certificate pem's path> --private_key_path <private key pem's path> --target <corstone300/corstone310/corstone315> --toolchain GNU --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS>
+./tools/scripts/build.sh ${APPLICATION_NAME} --certificate_path <certificate pem's path> --private_key_path <private key pem's path> --target <corstone300/corstone310/corstone315/corstone320> --toolchain GNU --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS>
 ```
 
 * The `certificate pem's path` and `private key pem's path` should be the downloaded key's and certificate's paths during the Thing creation.
 
 Or, run the command below to perform a clean build:
 
 ```bash
-./tools/scripts/build.sh ${APPLICATION_NAME} --certificate_path <certificate pem's path> --private_key_path <private key pem's path> --target <corstone300/corstone310/corstone315> --toolchain GNU --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS> -c
+./tools/scripts/build.sh ${APPLICATION_NAME} --certificate_path <certificate pem's path> --private_key_path <private key pem's path> --target <corstone300/corstone310/corstone315/corstone320> --toolchain GNU --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS> -c
 ```
 
 ## Running the application
@@ -87,7 +87,7 @@ to start the [previously created](#creating-aws-iot-core-qualification-test-suit
 Now run the application by running the following command:
 
 ```bash
-./tools/scripts/run.sh ${APPLICATION_NAME} --target <corstone300/corstone310/corstone315>
+./tools/scripts/run.sh ${APPLICATION_NAME} --target <corstone300/corstone310/corstone315/corstone320>
 ```
 
 Once the device advisor has completed all the tests, you can download the AWS

docs/applications/keyword_detection.md

@@ -47,7 +47,7 @@ Follow the instructions described in [Setting Up AWS Connectivity](./aws_iot/set
 To build the Keyword-Detection example, run the following command:
 
 ```bash
-./tools/scripts/build.sh keyword-detection --certificate_path <certificate pem's path> --private_key_path <private key pem's path> --target <corstone300/corstone310/corstone315> --inference <ETHOS/SOFTWARE> --audio <ROM/VSI> --toolchain <ARMCLANG/GNU> --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS>
+./tools/scripts/build.sh keyword-detection --certificate_path <certificate pem's path> --private_key_path <private key pem's path> --target <corstone300/corstone310/corstone315/corstone320> --inference <ETHOS/SOFTWARE> --audio <ROM/VSI> --toolchain <ARMCLANG/GNU> --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS>
 ```
 * The `certificate pem's path` and `private key pem's path` should be the downloaded key's and certificate's path if you chose the **Auto-generate a new certificate** during the Thing creation. If you chose **Skip creating a certificate at this time** then these paths should locate the generated credential files that were created by the `./tools/scripts/generate_credentials.py` script in the previous step.
 
@@ -63,7 +63,7 @@ implementation, please refer to [Mbed TLS document](../components/security/mbedt
 Or, run the command below to perform a clean build:
 
 ```bash
-./tools/scripts/build.sh keyword-detection --certificate_path <certificate pem's path> --private_key_path <private key pem's path> --target <corstone300/corstone310/corstone315> --inference <ETHOS/SOFTWARE> --audio <ROM/VSI> --toolchain <ARMCLANG/GNU> --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS> -c
+./tools/scripts/build.sh keyword-detection --certificate_path <certificate pem's path> --private_key_path <private key pem's path> --target <corstone300/corstone310/corstone315/corstone320> --inference <ETHOS/SOFTWARE> --audio <ROM/VSI> --toolchain <ARMCLANG/GNU> --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS> -c
 ```
 
 ## Provisioning the device credentials into Protected Storage
@@ -82,7 +82,7 @@ If you would like to run the keyword detection application using VSI configurati
 To run the Keyword-Detection example, run the following command:
 
 ```bash
-./tools/scripts/run.sh keyword-detection --target <corstone300/corstone310/corstone315> --audio <ROM/VSI>
+./tools/scripts/run.sh keyword-detection --target <corstone300/corstone310/corstone315/corstone320> --audio <ROM/VSI>
 ```
 
 ### Expected output

docs/applications/object_detection.md

@@ -25,7 +25,7 @@ Follow the instructions described in [Setting Up AWS Connectivity](./aws_iot/set
 
 To build the Object-Detection example, run the following command:
 ```bash
-./tools/scripts/build.sh object-detection --certificate_path <certificate pem's path> --private_key_path <private key pem's path> -t corstone315 --toolchain GNU --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS>
+./tools/scripts/build.sh object-detection --certificate_path <certificate pem's path> --private_key_path <private key pem's path> -t <corstone315/corstone320> --toolchain GNU --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS>
 ```
 - The `certificate pem's path` and `private key pem's path` should be the downloaded key's and certificate's path if you chose the **Auto-generate a new certificate** during the Thing creation. If you chose **Skip creating a certificate at this time** then these paths should locate the generated credential files that were created by the `./tools/scripts/generate_credentials.py` script in the previous step.
 
@@ -38,7 +38,7 @@ implementation, please refer to [Mbed TLS document](../components/security/mbedt
 
 Or, run the command below to perform a clean build:
 ```bash
-./tools/scripts/build.sh object-detection --certificate_path <certificate pem's path> --private_key_path <private key pem's path> -t corstone315 --toolchain GNU --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS> -c
+./tools/scripts/build.sh object-detection --certificate_path <certificate pem's path> --private_key_path <private key pem's path> -t <corstone315/corstone320> --toolchain GNU --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS> -c
 ```
 
 ## Provisioning the device credentials into Protected Storage
@@ -48,7 +48,7 @@ Check [Device Provisioning](./device_provisioning/device_provisioning.md) for de
 ## Running the application
 
 ```bash
-./tools/scripts/run.sh object-detection -t corstone315 --frames applications/object_detection/resources/test.frm
+./tools/scripts/run.sh object-detection -t <corstone315/corstone320> --frames applications/object_detection/resources/test.frm
 ```
 - The `frames` is used to select the input frames file.
 

docs/applications/speech_recognition.md

@@ -27,7 +27,7 @@ Follow the instructions described in [Setting Up AWS Connectivity](./aws_iot/set
 To build the Speech-Recognition example, run the following command:
 
 ```bash
-./tools/scripts/build.sh speech-recognition --certificate_path <certificate pem's path> --private_key_path <private key pem's path> --target <corstone300/corstone310/corstone315> --inference ETHOS --audio <ROM/VSI> --toolchain <ARMCLANG/GNU> --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS>
+./tools/scripts/build.sh speech-recognition --certificate_path <certificate pem's path> --private_key_path <private key pem's path> --target <corstone300/corstone310/corstone315/corstone320> --inference ETHOS --audio <ROM/VSI> --toolchain <ARMCLANG/GNU> --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS>
 ```
 * The `certificate pem's path` and `private key pem's path` should be the downloaded key's and certificate's path if you chose the **Auto-generate a new certificate** during the Thing creation. If you chose **Skip creating a certificate at this time** then these paths should locate the generated credential files that were created by the `./tools/scripts/generate_credentials.py` script in the previous step.
 
@@ -41,7 +41,7 @@ implementation, please refer to [Mbed TLS document](../components/security/mbedt
 Or, run the command below to perform a clean build:
 
 ```bash
-./tools/scripts/build.sh speech-recognition --certificate_path <certificate pem's path> --private_key_path <private key pem's path> --target <corstone300/corstone310/corstone315> --inference ETHOS --audio <ROM/VSI> --toolchain <ARMCLANG/GNU> --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS> -c
+./tools/scripts/build.sh speech-recognition --certificate_path <certificate pem's path> --private_key_path <private key pem's path> --target <corstone300/corstone310/corstone315/corstone320> --inference ETHOS --audio <ROM/VSI> --toolchain <ARMCLANG/GNU> --conn-stack <FREERTOS_PLUS_TCP/IOT_VSOCKET> --psa-crypto-implementation <TF-M/MBEDTLS> -c
 ```
 
 ## Provisioning the device credentials into Protected Storage
@@ -60,7 +60,7 @@ If you would like to run the speech recognition application using VSI configurat
 To run the Speech-Recognition example, run the following command:
 
 ```bash
-./tools/scripts/run.sh speech-recognition --target <corstone300/corstone310/corstone315> --audio <ROM/VSI>
+./tools/scripts/run.sh speech-recognition --target <corstone300/corstone310/corstone315/corstone320> --audio <ROM/VSI>
 ```
 
 ### Expected output