From a4f45cf04de2ae108c21cc90cfe08caa47aa6aeb Mon Sep 17 00:00:00 2001 From: Colm Donelan Date: Thu, 14 May 2020 07:45:44 +0100 Subject: MLCE-193 README and FAQ updates. * Add FAQ entry about ArmNN and ComputeLibrary mismatch * Add documentation reference to README that dynamically referrs to gh branch on GitHub. * Update ONNXSupport.mb to fix broken links. Signed-off-by: Colm Donelan Change-Id: I6390d87443c57cc43e27ea0a27f830f8fc25244d --- docs/FAQ.md | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) (limited to 'docs') diff --git a/docs/FAQ.md b/docs/FAQ.md index 2f06df62bb..1df82e8a63 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -3,13 +3,20 @@ Frequently asked questions These are issues that have been commonly seen when using ArmNN. +Problems seen when trying to build armnn and ComputeLibrary obtained from GitHub +----------------------------------------------------------------------------- + +Some users have encountered difficulties when attempting to build armnn and ComputeLibrary obtained from GitHub. The build generally fails reporting missing dependencies or fields in aclCommon, backendsCommon, cl or neon. These errors can look like this: + +error: ‘HARD_SWISH’ is not a member of ‘AclActivationFunction {aka arm_compute::ActivationLayerInfo::ActivationFunction}’ + +The most common reason for these errors are a mismatch between armnn and clframework revisions. For any version of ArmNN the coresponding version of ComputeLibrary is detailed in scripts/get_compute_library.sh as DEFAULT_CLFRAMEWORKREVISION + +On *nix like systems running this script will checkout ComputeLibrary, with the current default SHA, into ../../clframework/ relative to the location of the script. + Segmentation fault following a failed call to armnn::Optimize using CpuRef backend. --------------------------------------------------------- -In some error scenarios of calls to armnn::Optimize a null pointer may be -returned. This contravenes the function documentation however, it can -happen. Users are advised to check the value returned from the function as a -precaution. +In some error scenarios of calls to armnn::Optimize a null pointer may be returned. This contravenes the function documentation however, it can happen. Users are advised to check the value returned from the function as a precaution. -If you encounter this problem and are able to isolate it consider contributing -a solution. +If you encounter this problem and are able to isolate it consider contributing a solution. -- cgit v1.2.1