summaryrefslogtreecommitdiff
path: root/docs/sections
diff options
context:
space:
mode:
authorIsabella Gottardi <isabella.gottardi@arm.com>2022-03-08 15:27:49 +0000
committerIsabella Gottardi <isabella.gottardi@arm.com>2022-03-11 10:57:23 +0000
commit1716efd0b35889b580276e27c8b6f661c9858cd0 (patch)
tree1c014d324fec1695d4f5bb8e26f9c4fdb795ee82 /docs/sections
parente7f512592818574d98c4b3ba09b4d3315fe025bd (diff)
downloadml-embedded-evaluation-kit-1716efd0b35889b580276e27c8b6f661c9858cd0.tar.gz
MLECO-3006: Fixing some minor errors in documentation
Change-Id: I24cd544780f46fcec8f154b440f7bb959c20a459 Signed-off-by: Isabella Gottardi <isabella.gottardi@arm.com>
Diffstat (limited to 'docs/sections')
-rw-r--r--docs/sections/building.md12
-rw-r--r--docs/sections/customizing.md8
-rw-r--r--docs/sections/deployment.md2
-rw-r--r--docs/sections/troubleshooting.md6
4 files changed, 14 insertions, 14 deletions
diff --git a/docs/sections/building.md b/docs/sections/building.md
index 2f122f9..4f4e6dd 100644
--- a/docs/sections/building.md
+++ b/docs/sections/building.md
@@ -184,7 +184,7 @@ The build parameters are:
- `Sram_Only`
> **Note:** The `Shared_Sram` memory mode is available on both *Ethos-U55* and *Ethos-U65* NPU, `Dedicated_Sram` only
- > for *Ethos-U65* NPU and `Sram_Only` only for Ethos-U55* NPU.
+ > for *Ethos-U65* NPU and `Sram_Only` only for *Ethos-U55* NPU.
- `ETHOS_U_NPU_CONFIG_ID`: This parameter is set by default based on the value of `ETHOS_U_NPU_ID`.
For Ethos-U55, it defaults to the `H128` indicating that the Ethos-U55 128 MAC optimised model
@@ -259,7 +259,7 @@ The build process uses three major steps:
- Some files such as neural network models, network inputs, and output labels are automatically converted into C/C++
arrays, see: [Automatic file generation](./building.md#automatic-file-generation).
-3. Build the application.\
+3. Build the application.
Application and third-party libraries are now built. For further information, see:
[Building the configured project](./building.md#building-the-configured-project).
@@ -271,12 +271,12 @@ Certain third-party sources are required to be present on the development machin
repository to link against.
1. [TensorFlow Lite Micro repository](https://github.com/tensorflow/tensorflow)
-2. [Ethos-U55 NPU core driver repository](https://review.mlplatform.org/admin/repos/ml/ethos-u/ethos-u-core-driver)
+2. [Ethos-U NPU core driver repository](https://review.mlplatform.org/admin/repos/ml/ethos-u/ethos-u-core-driver)
3. [CMSIS-5](https://github.com/ARM-software/CMSIS_5.git)
+4. [Ethos-U NPU core driver repository](https://review.mlplatform.org/admin/repos/ml/ethos-u/ethos-u-core-platform)
> **Note:** If you are using non git project sources, run `python3 ./download_dependencies.py` and ignore further git
> instructions. Proceed to [Fetching resource files](./building.md#fetching-resource-files) section.
->
To pull the submodules:
@@ -290,7 +290,7 @@ This downloads all of the required components and places them in a tree, like so
dependencies
├── cmsis
├── core-driver
- ├── core-software
+ ├── core-platform
└── tensorflow
```
@@ -391,7 +391,7 @@ mkdir build && cd build
#### Using GNU Arm Embedded toolchain
On Linux, if using `Arm GNU embedded toolchain`, execute the following command to build the application to run on the
-Arm® *Ethos™-U55* NPU when providing only the mandatory arguments for CMake configuration:
+Arm® *Ethos™-U* NPU when providing only the mandatory arguments for CMake configuration:
```commandline
cmake ../
diff --git a/docs/sections/customizing.md b/docs/sections/customizing.md
index ef90e5e..2302809 100644
--- a/docs/sections/customizing.md
+++ b/docs/sections/customizing.md
@@ -21,7 +21,7 @@
This section describes how to implement a custom Machine Learning application running on Arm® *Corstone™-300* based FVP
or on the Arm® MPS3 FPGA prototyping board.
-the Arm® *Ethos™-U55* code sample software project offers a way to incorporate more use-case code into the existing
+The Arm® *Ethos™-U* code sample software project offers a way to incorporate more use-case code into the existing
infrastructure. It also provides a build system that automatically picks up added functionality and produces
corresponding executable for each use-case. This is achieved by following certain configuration and code implementation
conventions.
@@ -679,7 +679,7 @@ in the root of your use-case. However, the name of the file is not important.
> - `use_case` – The name of the current use-case.
> - `UC_SRC` – A list of use-case sources.
> - `UC_INCLUDE` – The path to the use-case headers.
-> - `ETHOS_U_NPU_ENABLED` – The flag indicating if the current build supports Ethos-U55.
+> - `ETHOS_U_NPU_ENABLED` – The flag indicating if the current build supports *Ethos™-U* NPU.
> - `TARGET_PLATFORM` – The target platform being built for.
> - `TARGET_SUBSYSTEM` – If target platform supports multiple subsystems, this is the name of the subsystem.
> - All standard build options.
@@ -691,9 +691,9 @@ so:
```cmake
if (ETHOS_U_NPU_ENABLED)
- set(DEFAULT_MODEL_PATH ${DEFAULT_MODEL_DIR}/helloworldmodel_uint8_vela_${DEFAULT_NPU_CONFIG_ID}.tflite)
+ set(DEFAULT_MODEL_PATH ${DEFAULT_MODEL_DIR}/helloworldmodel_vela_${DEFAULT_NPU_CONFIG_ID}.tflite)
else()
- set(DEFAULT_MODEL_PATH ${DEFAULT_MODEL_DIR}/helloworldmodel_uint8.tflite)
+ set(DEFAULT_MODEL_PATH ${DEFAULT_MODEL_DIR}/helloworldmodel.tflite)
endif()
```
diff --git a/docs/sections/deployment.md b/docs/sections/deployment.md
index 034fb19..045bda0 100644
--- a/docs/sections/deployment.md
+++ b/docs/sections/deployment.md
@@ -25,7 +25,7 @@ The FVP is available publicly from the following page:
Please ensure that you download the correct archive from the list under Arm® *Corstone™-300*. You need the one which:
- Emulates MPS3 board and *not* for MPS2 FPGA board,
-- Contains support for Arm® *Ethos™-U55*.
+- Contains support for Arm® *Ethos™-U55* and *Ethos-U65* processors.
### Setting up the MPS3 Arm Corstone-300 FVP
diff --git a/docs/sections/troubleshooting.md b/docs/sections/troubleshooting.md
index 612e40e..8b2646a 100644
--- a/docs/sections/troubleshooting.md
+++ b/docs/sections/troubleshooting.md
@@ -42,7 +42,7 @@ It shows that the configuration of the Vela compiled `.tflite` file doesn't matc
The Vela configuration parameter `accelerator-config` used for producing the .`tflite` file that is used
while building the application should match the MACs configuration that the FVP is emulating.
For example, if the `accelerator-config` from the Vela command was `ethos-u55-128`, the FVP should be emulating the
-128 MACs configuration of the Ethos-U55 block(default FVP configuration). If the `accelerator-config` used was
+128 MACs configuration of the Ethos™-U55 block(default FVP configuration). If the `accelerator-config` used was
`ethos-u55-256`, the FVP must be executed with additional command line parameter to instruct it to emulate the
256 MACs configuration instead.
@@ -56,8 +56,8 @@ logged over UART. These include the MACs/cc configuration of the FVP.
INFO - MPS3 core clock has been set to: 32000000Hz
INFO - CPU ID: 0x410fd220
INFO - CPU: Cortex-M55 r0p0
-INFO - Ethos-U55 device initialised
-INFO - Ethos-U55 version info:
+INFO - Ethos-U device initialised
+INFO - Ethos-U version info:
INFO - Arch: v1.0.6
INFO - Driver: v0.16.0
INFO - MACs/cc: 128