|
14 | 14 | - [Prerequisites](#prerequisites)
|
15 | 15 | - [Visual Studio Code](#visual-studio-code)
|
16 | 16 | - [Packs](#packs)
|
| 17 | + - [Virtual Streaming Interface](#virtual-streaming-interface) |
17 | 18 | - [Building the examples](#building-the-examples)
|
18 | 19 | - [Launch project in Visual Studio Code](#launch-project-in-visual-studio-code)
|
19 | 20 | - [Download Software Packs](#download-software-packs)
|
20 | 21 | - [Generate and build the project](#generate-and-build-the-project)
|
21 |
| - - [Execute project](#execute-project) |
| 22 | + - [Execute Project](#execute-project) |
| 23 | + - [Working with Virtual Streaming Interface](#working-with-virtual-streaming-interface) |
22 | 24 | - [Application output](#application-output)
|
23 | 25 | - [Trademarks](#trademarks)
|
24 | 26 | - [Licenses](#licenses)
|
@@ -107,6 +109,33 @@ CMSIS-Pack defines a standardized way to deliver software components, device par
|
107 | 109 | support information and code. A list of available CMSIS-Packs can be found
|
108 | 110 | [here](https://developer.arm.com/tools-and-software/embedded/cmsis/cmsis-packs).
|
109 | 111 |
|
| 112 | +## Virtual Streaming Interface |
| 113 | + |
| 114 | +[Virtual Streaming Interface)](https://arm-software.github.io/AVH/main/simulation/html/group__arm__vsi.html) |
| 115 | +(VSI) is available for certain |
| 116 | +[Fixed Virtual Platform](https://developer.arm.com/Tools%20and%20Software/Fixed%20Virtual%20Platforms) (FVP) or |
| 117 | +[Arm Virtual Hardware](https://developer.arm.com/Tools%20and%20Software/Arm%20Virtual%20Hardware) (AVH) |
| 118 | +targets. For VSI supported examples, you may need to install some dependencies. |
| 119 | + |
| 120 | +For more details and up-to-date requirements, see |
| 121 | +[Python environment setup](https://arm-software.github.io/AVH/main/simulation/html/group__arm__vsi__pyenv.html) |
| 122 | +which mentions: |
| 123 | + |
| 124 | +> The following packages are required on Linux systems (Ubuntu 20.04 and later): |
| 125 | +> - libatomic1 |
| 126 | +> - python3.9 |
| 127 | +> - python3-pip |
| 128 | +
|
| 129 | +In addition to the above, the VSI Python scripts depend on `opencv-python` package. We recommend using |
| 130 | +a virtual environment and installing this with pip. |
| 131 | + |
| 132 | +```shell |
| 133 | +$ pip install opencv-python |
| 134 | +``` |
| 135 | + |
| 136 | +**NOTE**: The requirement for Python version is driven by the FVP executable. Versions <= 11.26 require |
| 137 | +Python3.9 but this may change for future releases. |
| 138 | + |
110 | 139 | # Building the examples
|
111 | 140 |
|
112 | 141 | ## Launch project in Visual Studio Code
|
@@ -181,12 +210,12 @@ Build complete
|
181 | 210 |
|
182 | 211 | The built artifacts will be located under the `out/` directory in the project root.
|
183 | 212 |
|
184 |
| -## Execute project |
| 213 | +## Execute Project |
185 | 214 |
|
186 | 215 | The project is configured for execution on Arm Virtual Hardware which removes the requirement for
|
187 | 216 | a physical hardware board.
|
188 | 217 |
|
189 |
| -- When using a Fixed Virtual Platform installed locally: |
| 218 | +- When using a Fixed Virtual Platform (FVP) installed locally: |
190 | 219 | ```shell
|
191 | 220 | $ <path_to_installed_FVP> -a ./out/kws/AVH-SSE-300-U55/Debug/kws.Debug+AVH-SSE-300-U55.axf -f ./FVP/FVP_Corstone_SSE-300/fvp_config.txt
|
192 | 221 | ```
|
@@ -218,6 +247,21 @@ For example:
|
218 | 247 | $ cp ./out/kws/STM32F746-DISCO/Release/kws.Release+STM32F746-DISCO.bin /media/user/DIS_F746NG/ && sync
|
219 | 248 | ```
|
220 | 249 |
|
| 250 | +### Working with Virtual Streaming Interface |
| 251 | + |
| 252 | +The object detection example for Arm Corstone-300 and Corstone-310 supports Virtual Streaming Interface (VSI). |
| 253 | +This allows the locally installed FVP application (or an AVH instance) to read images in from a camera connected to |
| 254 | +your local machine and stream these over to the application running within the FVP. |
| 255 | + |
| 256 | +To run the VSI application, append the command line with the v_path argument. For example: |
| 257 | + |
| 258 | +```shell |
| 259 | + $ <path_to_installed_FVP> \ |
| 260 | + -a ./out/object-detection-vsi/AVH-SSE-300-U55/Release/object-detection-vsi.axf \ |
| 261 | + -C ethosu.num_macs=256 \ |
| 262 | + -C mps3_board.v_path=./device/corstone/vsi/video/python/ |
| 263 | + ``` |
| 264 | + |
221 | 265 | ## Application output
|
222 | 266 |
|
223 | 267 | Once the project can be built successfully, the execution on target hardware will show output of
|
@@ -378,4 +422,21 @@ spot immediately. Please help us improve this section by reporting them via GitH
|
378 | 422 | Currently Keil Studio Cloud only supports running with the Arm® Ethos™-U55 on AVH
|
379 | 423 | virtual targets.
|
380 | 424 | You can build the project but will have to run it on your local machine on an
|
381 |
| - installation of the equivalent Fixed Virtual Platform containing Arm® Ethos™-U65 NPU. |
| 425 | + installation of the equivalent Fixed Virtual Platform containing Arm® Ethos™-U65 NPU. |
| 426 | + |
| 427 | +7. The newer versions of BSP packs for Arm® Corstone™-300 and Arm® Corstone™-310 require CMSIS 6. |
| 428 | + There are warnings about some unsatisfied requirements because of this. For example: |
| 429 | + ```shell |
| 430 | + MISSING ARM::Device: [email protected] |
| 431 | + |
| 432 | + MISSING ARM::Device:Native Driver: [email protected] |
| 433 | + |
| 434 | + MISSING ARM::Device:Native Driver: [email protected] |
| 435 | + |
| 436 | + MISSING ARM::Device:Native Driver: [email protected] |
| 437 | + |
| 438 | + MISSING ARM::Device:Startup &C [email protected] |
| 439 | + |
| 440 | + ``` |
| 441 | + These are expected to be resolved once we bump up the version of CMSIS core pack. Currently, |
| 442 | + this is blocked by other dependencies. |
0 commit comments