mirror of
https://github.com/ARM-software/workload-automation.git
synced 2025-01-18 20:11:20 +00:00
141 lines
6.8 KiB
ReStructuredText
141 lines
6.8 KiB
ReStructuredText
.. _faq:
|
|
|
|
FAQ
|
|
===
|
|
|
|
.. contents::
|
|
:depth: 1
|
|
:local:
|
|
|
|
---------------------------------------------------------------------------------------
|
|
|
|
|
|
**Q:** I receive the error: ``"<<Workload> file <file_name> file> could not be found."``
|
|
-----------------------------------------------------------------------------------------
|
|
|
|
**A:** Some workload e.g. AdobeReader, GooglePhotos etc require external asset
|
|
files. We host some additional workload dependencies in the `WA Assets Repo
|
|
<https://github.com/ARM-software/workload-automation-assets>`_. To allow WA to
|
|
try and automatically download required assets from the repository please add
|
|
the following to your configuration:
|
|
|
|
.. code-block:: YAML
|
|
|
|
remote_assets_url: https://raw.githubusercontent.com/ARM-software/workload-automation-assets/master/dependencies
|
|
|
|
------------
|
|
|
|
**Q:** I receive the error: ``"No matching package found for workload <workload>"``
|
|
------------------------------------------------------------------------------------
|
|
|
|
**A:** WA cannot locate the application required for the workload. Please either
|
|
install the application onto the device or source the apk and place into
|
|
``$WA_USER_DIRECTORY/dependencies/<workload>``
|
|
|
|
------------
|
|
|
|
**Q:** I am trying to set a valid runtime parameters however I still receive the error ``"Unknown runtime parameter"``
|
|
-------------------------------------------------------------------------------------------------------------------------
|
|
|
|
**A:** Please ensure you have the corresponding module loaded on the device.
|
|
See :ref:`Runtime Parameters <runtime-parameters>` for the list of
|
|
runtime parameters and their containing modules, and the appropriate section in
|
|
:ref:`setting up a device <setting-up-a-device>` for ensuring it is installed.
|
|
|
|
-------------
|
|
|
|
**Q:** I have a big.LITTLE device but am unable to set parameters corresponding to the big or little core and receive the error ``"Unknown runtime parameter"``
|
|
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
|
|
|
|
**A:** Please ensure you have the hot plugging module enabled for your device (Please see question above).
|
|
|
|
|
|
**A:** This can occur if the device uses dynamic hot-plugging and although WA
|
|
will try to online all cores to perform discovery sometimes this can fail
|
|
causing to WA to incorrectly assume that only one cluster is present. To
|
|
workaround this please set the ``core_names`` :ref:`parameter <core-names>` in the configuration for
|
|
your device.
|
|
|
|
|
|
**Q:** I receive the error ``Could not find plugin or alias "standard"``
|
|
------------------------------------------------------------------------
|
|
|
|
**A:** Upon first use of WA3, your WA2 config file typically located at
|
|
``$USER_HOME/config.py`` will have been converted to a WA3 config file located at
|
|
``$USER_HOME/config.yaml``. The "standard" output processor, present in WA2, has
|
|
been merged into the core framework and therefore no longer exists. To fix this
|
|
error please remove the "standard" entry from the "augmentations" list in the
|
|
WA3 config file.
|
|
|
|
**Q:** My Juno board keeps resetting upon starting WA even if it hasn't crashed.
|
|
--------------------------------------------------------------------------------
|
|
**A** Please ensure that you do not have any other terminals (e.g. ``screen``
|
|
sessions) connected to the board's UART. When WA attempts to open the connection
|
|
for its own use this can cause the board to reset if a connection is already
|
|
present.
|
|
|
|
|
|
**Q:** I'm using the FPS instrument but I do not get any/correct results for my workload
|
|
-----------------------------------------------------------------------------------------
|
|
|
|
**A:** If your device is running with Android 6.0 + then the default utility for
|
|
collecting fps metrics will be ``gfxinfo`` however this does not seem to be able
|
|
to extract any meaningful information for some workloads. In this case please
|
|
try setting the ``force_surfaceflinger`` parameter for the ``fps`` augmentation
|
|
to ``True``. This will attempt to guess the "View" for the workload
|
|
automatically however this is device specific and therefore may need
|
|
customizing. If this is required please open the application and execute
|
|
``dumpsys SurfaceFlinger --list`` on the device via adb. This will provide a
|
|
list of all views available for measuring.
|
|
|
|
As an example, when trying to find the view for the AngryBirds Rio workload you
|
|
may get something like:
|
|
|
|
.. code-block:: none
|
|
|
|
...
|
|
AppWindowToken{41dfe54 token=Token{77819a7 ActivityRecord{a151266 u0 com.rovio.angrybirdsrio/com.rovio.fusion.App t506}}}#0
|
|
a3d001c com.rovio.angrybirdsrio/com.rovio.fusion.App#0
|
|
Background for -SurfaceView - com.rovio.angrybirdsrio/com.rovio.fusion.App#0
|
|
SurfaceView - com.rovio.angrybirdsrio/com.rovio.fusion.App#0
|
|
com.rovio.angrybirdsrio/com.rovio.fusion.App#0
|
|
boostedAnimationLayer#0
|
|
mAboveAppWindowsContainers#0
|
|
...
|
|
|
|
From these ``"SurfaceView - com.rovio.angrybirdsrio/com.rovio.fusion.App#0"`` is
|
|
the mostly likely the View that needs to be set as the ``view`` workload
|
|
parameter and will be picked up be the ``fps`` augmentation.
|
|
|
|
|
|
**Q:** I am getting an error which looks similar to ``'CONFIG_SND_BT87X is not exposed in kernel config'...``
|
|
-------------------------------------------------------------------------------------------------------------
|
|
**A:** If you are receiving this under normal operation this can be caused by a
|
|
mismatch of your WA and devlib versions. Please update both to their latest
|
|
versions and delete your ``$USER_HOME/.workload_automation/cache/targets.json``
|
|
(or equivalent) file.
|
|
|
|
**Q:** I get an error which looks similar to ``UnicodeDecodeError('ascii' codec can't decode byte...``
|
|
------------------------------------------------------------------------------------------------------
|
|
**A:** If you receive this error or a similar warning about your environment,
|
|
please ensure that you configure your environment to use a locale which supports
|
|
UTF-8. Otherwise this can cause issues when attempting to parse files containing
|
|
none ascii characters.
|
|
|
|
**Q:** I get the error ``Module "X" failed to install on target``
|
|
------------------------------------------------------------------------------------------------------
|
|
**A:** By default a set of devlib modules will be automatically loaded onto the
|
|
target designed to add additional functionality. If the functionality provided
|
|
by the module is not required then the module can be safely disabled by setting
|
|
``load_default_modules`` to ``False`` in the ``device_config`` entry of the
|
|
:ref:`agenda <config-agenda-entry>` and then re-enabling any specific modules
|
|
that are still required. An example agenda snippet is shown below:
|
|
|
|
.. code-block:: none
|
|
|
|
config:
|
|
device: generic_android
|
|
device_config:
|
|
load_default_modules: False
|
|
modules: ['list', 'of', 'modules', 'to', 'enable']
|