These instructions assume you have already followed these instructions to initialize and build an Arm Platforms workspace software stack.
These instructions are for running the Arm Platforms deliverables on one of the following FVPs:
For System Guidance for Infrastructure (SGI) platforms, see Run BusyBox on an SGI platform or Run Fedora Server on an SGI platform.
Note paths for environment variables must be absolute; relative paths are not supported.
To run the software, first make the FVP binary visible to the model scripts, for example SGI-575:
$ export MODEL=/path/to/where/you/separately/installed/FVP_CSS_SGI-575
If you chose to use Android, Fedora, or one of the OpenEmbedded filesystems, the workspace initialization script will have placed the user-space filesystem image in the root of `<workspace>'. You will need to make this filesystem image writeable, and also make it visible to the model scripts:
`<workspace>'
$ export DISK=<workspace>/<filesystem>.img $ chmod a+w $DISK
How you then proceed will depend on whether you built from source or are using a prebuilt configuration.
Simply run the script in the `<workspace>/<prebuilt>/' directory.
`<workspace>/<prebuilt>/'
For example for a `latest-armlt' + BusyBox prebuilt configuration:
`latest-armlt'
$ cd <workspace>/fvp-latest-busybox-uboot/ $ ./run_model.sh
Note: legacy 32-bit software stack users will also need to pass the `--aarch32' flag to `run_model.sh'.
`--aarch32'
`run_model.sh'
You will need to run the script found in the `<workspace>/<model-scripts>/' directory, pointing it at the binaries in `<workspace>/<output>/' corresponding to your chosen configuration.
`<workspace>/<model-scripts>/'
`<workspace>/<output>/'
For example for a `latest-armlt' + BusyBox configuration:
$ <workspace>/model-scripts/run_model.sh <workspace>/output/fvp/fvp-busybox/uboot/