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
Use this import button to open the solution in Keil Studio Cloud: [](https://studio.keil.arm.com/?import=https://github.com/Arm-Examples/mlek-cmsis-pack-examples.git)
48
47
49
-
##Overview
48
+
# Overview
50
49
51
50
The examples presented in this repository showcase how to build and deploy end-to-end Machine
52
51
Learning applications using existing code from various CMSIS-packs. These examples are built
@@ -62,33 +61,45 @@ Therefore, the neural network model files used for Corstone™-300 and Corstone
62
61
pre-optimised by the [Vela compiler](https://pypi.org/project/ethos-u-vela/) while the files
63
62
used for pure CPU targets are used as they are.
64
63
65
-
###Object detection
64
+
## Object detection
66
65
67
66
This example uses a neural network model that specialises in detecting human faces in images.
68
67
The input size for these images is 192x192 (monochrome) and the smallest face that can be
69
68
detected is of size 20x20. The output of the application will be co-ordinates for rectangular
70
69
bounding boxes for each detection.
71
70
72
-
###Keyword spotting
71
+
## Keyword spotting
73
72
74
73
This example can detect up to twelve keywords in the input audio stream. The
75
74
[audio file used](./resources/sample_audio.wav) contains the keyword "down" being spoken.
76
75
77
76
More details about the input for this example can be found [here](https://review.mlplatform.org/plugins/gitiles/ml/ethos-u/ml-embedded-evaluation-kit/+/refs/heads/main/docs/use_cases/kws.md#preprocessing-and-feature-extraction).
78
77
79
-
## Building the examples
80
78
81
-
We recommend using [Keil Studio Cloud](https://studio.keil.arm.com/?import=https://github.com/Arm-Examples/mlek-cmsis-pack-examples.git) for building these examples.
82
-
This is by far the easiest way to get started. However, it is possible to build these projects
83
-
locally too and the following sections cover the requirements for such a set up.
79
+
# Prerequisites
84
80
85
-
### Prerequisites
81
+
We recommend using [Visual Studio Code IDE](https://code.visualstudio.com/) with the
82
+
[Keil Studio Pack Extension](https://marketplace.visualstudio.com/items?itemName=Arm.keil-studio-pack).
83
+
Alternatively, [Keil Studio Cloud](https://studio.keil.arm.com/?import=https://github.com/Arm-Examples/mlek-cmsis-pack-examples.git) can also be used.
84
+
85
+
These are the easiest ways to get started. However, it is also possible to build these projects
86
+
locally via CLI and the following sections cover the requirements for such a set up.
87
+
88
+
## Support for Visual Studio Code
89
+
90
+
The [tools required](#tools) can also be used in addition to an extension pack for Visual Studio Code.
91
+
See [Arm Keil Studio Pack](https://marketplace.visualstudio.com/items?itemName=Arm.keil-studio-pack)
92
+
for details on installation and how to use it.
93
+
94
+
Once the IDE has been set up with the extension, it presents an easy to use interface to build
95
+
applications for specific configurations of the different projects and targets from within VS Code,
96
+
and also helps with debugging and flashing.
86
97
87
98
For developing on a local host machine, we recommend a Linux based system as we test
88
99
the flow of the instructions in that environment, but a Windows based machine should
89
100
also work.
90
101
91
-
####Tools
102
+
## Tools
92
103
93
104
The following tools are required if building on a local machine (and not using the project via
94
105
Keil Studio Cloud):
@@ -99,9 +110,15 @@ Keil Studio Cloud):
99
110
- Access to Arm Virtual Hardware for Corstone™-300 (or Corstone™-310) v11.18.1 or a local
100
111
installation of the equivalent Fixed Virtual Platform.
101
112
102
-
> **NOTE**: For Linux, we recommend using the script installer as this sets up the
103
-
> basic paths required the the tools. Otherwise, paths like CMSIS_ROOT_PATH and the
104
-
> toolchain root paths in the toolchain CMake files will need to be set manually.
113
+
> **NOTE**: For Visual Studio Code, the project contains a
114
+
> [vcpkg configuration file](./vcpkg-configuration.json) that helps the required tools to
115
+
> be installed without user having to install them manually. We recommend letting the IDE
116
+
> handle the installation and environment set up at start up.
117
+
>
118
+
> If you need to use the CLI tools locally, we recommend using the script
119
+
> installer as this sets up the basic paths required for the tools. Otherwise, paths like
120
+
> CMSIS_ROOT_PATH and the toolchain root paths in the toolchain CMake files will need to be
121
+
> set manually.
105
122
> The script installer will prompt for the different paths:
0 commit comments