You are currently reviewing an older revision of this page.
NOTICE: The Arm Reference Platforms are now hosted on this git repository.The instructions on this page assume you have followed the instructions in the user guide to fetch, build, and package the deliverables for FVP.
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:
$ 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.
For example for a `latest-armlt' + BusyBox prebuilt configuration:
$ cd <workspace>/fvp-latest-busybox-uboot/
Note: legacy 32-bit software stack users will also need to pass the `--aarch32' flag to `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.
For example for a `latest-armlt' + BusyBox configuration:
$ <workspace>/model-scripts/run_model.sh <workspace>/output/fvp/fvp-busybox/uboot/