diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/documentation.md | 6 | ||||
| -rw-r--r-- | docs/quick_start.md | 2 | ||||
| -rw-r--r-- | docs/sections/building.md | 2 | ||||
| -rw-r--r-- | docs/sections/customizing.md | 2 | ||||
| -rw-r--r-- | docs/sections/deployment.md | 8 | ||||
| -rw-r--r-- | docs/sections/memory_considerations.md | 2 | ||||
| -rw-r--r-- | docs/sections/timing_adapters.md | 5 | ||||
| -rw-r--r-- | docs/sections/troubleshooting.md | 2 |
8 files changed, 20 insertions, 9 deletions
diff --git a/docs/documentation.md b/docs/documentation.md index 0476418..41c0642 100644 --- a/docs/documentation.md +++ b/docs/documentation.md @@ -329,9 +329,9 @@ For further information, please see: - [Deployment](./sections/deployment.md#deployment) - [Fixed Virtual Platform](./sections/deployment.md#fixed-virtual-platform) - - [Setting up the MPS3 Corstone-300 FVP](./sections/deployment.md#setting-up-the-mps3-arm-corstone_300-fvp) - - [Deploying on an FVP emulating MPS3](./sections/deployment.md#deploying-on-an-fvp-emulating-mps3) - - [MPS3 board](./sections/deployment.md#mps3-board) + - [Installing an FVP](./sections/deployment.md#installing-an-fvp) + - [Deploying on an FVP](./sections/deployment.md#deploying-on-an-fvp) + - [MPS3 FPGA board](./sections/deployment.md#mps3-fpga-board) - [Deployment on MPS3 board](./sections/deployment.md#deployment-on-mps3-board) ## Implementing custom ML application diff --git a/docs/quick_start.md b/docs/quick_start.md index daef495..35bb35f 100644 --- a/docs/quick_start.md +++ b/docs/quick_start.md @@ -71,7 +71,7 @@ mkdir resources_downloaded && cd resources_downloaded python3 -m venv env env/bin/python3 -m pip install --upgrade pip env/bin/python3 -m pip install --upgrade setuptools -env/bin/python3 -m pip install ethos-u-vela==3.10.0 +env/bin/python3 -m pip install ethos-u-vela==3.12.0 cd .. curl -L https://github.com/ARM-software/ML-zoo/raw/7c32b097f7d94aae2cd0b98a8ed5a3ba81e66b18/models/anomaly_detection/micronet_medium/tflite_int8/ad_medium_int8.tflite \ diff --git a/docs/sections/building.md b/docs/sections/building.md index 7854c6a..775f71a 100644 --- a/docs/sections/building.md +++ b/docs/sections/building.md @@ -486,7 +486,7 @@ cmake .. \ Default CMake configuration behaviour looks for input samples, for each use case, in the default directory. All these inputs are baked-in into the application. If the number of files baked in is greater than one, a user menu is displayed on the application output, where the user is expected to enter their chosen option. See more here: -[Deploying on an FVP emulating MPS3](./deployment.md#deploying-on-an-fvp-emulating-mps3). +[Deploying on an FVP emulating MPS3](./deployment.md#deploying-on-an-fvp). To configure the project to use single input for each use case, CMake option `USE_SINGLE_INPUT` can be set to `ON`. This will result in each use case automatically running with predefined input data, thus removing the need for the diff --git a/docs/sections/customizing.md b/docs/sections/customizing.md index 2a946aa..1a5e3ce 100644 --- a/docs/sections/customizing.md +++ b/docs/sections/customizing.md @@ -672,7 +672,7 @@ Platform build configuration script must have 2 functions: The function `set_platform_global_defaults` must set `PLATFORM_DRIVERS_DIR` variable ```cmake - set(PLATFORM_DRIVERS_DIR "${HAL_PLATFORM_DIR}/mps3" PARENT_SCOPE) + set(PLATFORM_DRIVERS_DIR "${MLEK_HAL_PLATFORM_DIR}/mps3" PARENT_SCOPE) ``` location of the platform library sources. diff --git a/docs/sections/deployment.md b/docs/sections/deployment.md index d51d912..e556eb9 100644 --- a/docs/sections/deployment.md +++ b/docs/sections/deployment.md @@ -179,6 +179,14 @@ the application output can be directed to standard output by using an FVP option - `-C mps3_board.uart0.out_file='-'` for MPS3 based FVPs, OR - `-C mps4_board.uart0.out_file='-'` for MPS4 based FVPs. +> **NOTE**: Dockerfile, provided within the repository, contains useful environment variables pre-assigned with +> above arguments. These can be used directly from command-line. For example, to run MPS4 Arm® Corstone™-315 based +> application within the Docker container, the following command can be used to run the FVP in headless mode. +> +> ```commandline +> ${FVP_315_U65} -a <path/to/ethos-u-<use_case>.axf> ${FVP_315_ARGS} +> ``` + ## MPS3 FPGA board > **Note:** Before proceeding, make sure that you have the MPS3 board powered on, and a USB A to B cable connected diff --git a/docs/sections/memory_considerations.md b/docs/sections/memory_considerations.md index b8d1c25..30b36ac 100644 --- a/docs/sections/memory_considerations.md +++ b/docs/sections/memory_considerations.md @@ -290,6 +290,6 @@ used by a Vela optimized neural network model, then the Arm® *Ethos™-U* NPU w A bigger region of memory for storing the neural network model is placed in the DDR, or flash, region under `LOAD_REGION_1`. The two load regions are necessary as the motherboard configuration controller of the MPS3 limits the load size at address `0x00000000` to 1MiB. This has implications on how the application **is deployed** on MPS3, as -explained under the following section: [Deployment on MPS3](./deployment.md#mps3-board). +explained under the following section: [Deployment on MPS3](./deployment.md#mps3-fpga-board). The next section of the documentation covers: [Troubleshooting](troubleshooting.md). diff --git a/docs/sections/timing_adapters.md b/docs/sections/timing_adapters.md index b5d6e98..24f2fc9 100644 --- a/docs/sections/timing_adapters.md +++ b/docs/sections/timing_adapters.md @@ -161,4 +161,7 @@ not support the feature. Additionally - base addresses of timer adapters blocks | 3 | User memory | 0x4170_3000/0x5170_3000 | 4KB | This is why the evaluation kit is configured with timing adapters disabled altogether (parameter -`ETHOS_U_NPU_TIMING_ADAPTER_ENABLED` set to `OFF`) for Corstone-310 target platform. +`ETHOS_U_NPU_TIMING_ADAPTER_ENABLED` set to `OFF`) for Corstone-310 target platform. + +> **NOTE**: Arm® Corstone™-315 reference platforms do not use timing adapters. Therefore, like for +Arm® Corstone™-310, they are force-disabled in the CMake configuration. diff --git a/docs/sections/troubleshooting.md b/docs/sections/troubleshooting.md index 6841e62..180f62d 100644 --- a/docs/sections/troubleshooting.md +++ b/docs/sections/troubleshooting.md @@ -51,7 +51,7 @@ For example, if the `accelerator-config` from the Vela command was `ethos-u55-12 `ethos-u55-256`, the FVP must be executed with additional command line parameter to instruct it to emulate the 256 MACs configuration instead. -The [deploying on an FVP emulating MPS3](./deployment.md#deploying-on-an-fvp-emulating-mps3) page provides guidance +The [deploying on an FVP](./deployment.md#deploying-on-an-fvp) page provides guidance on how to instruct the FVP to change the number of MACs units. Note that when the FVP is launched and the application starts executing, various parameters about the system are |