Arm Community
Arm Community
  • Site
  • User
  • Site
  • Search
  • User
  • Groups
    • Arm Research
    • DesignStart
    • Education Hub
    • Graphics and Gaming
    • High Performance Computing
    • Innovation
    • Multimedia
    • Open Source Software and Platforms
    • Physical
    • Processors
    • Security
    • System
    • Software Tools
    • TrustZone for Armv8-M
    • 中文社区
  • Blog
    • Artificial Intelligence
    • Automotive
    • Healthcare
    • HPC
    • Infrastructure
    • Innovation
    • Internet of Things
    • Machine Learning
    • Mobile
    • Smart Homes
    • Wearables
  • Forums
    • All developer forums
    • IP Product forums
    • Tool & Software forums
  • Activity
  • Support
    • Open a support case
    • Documentation
    • Downloads
    • Training
    • Arm Approved program
    • Arm Design Reviews
  • More
  • Cancel
Open Source Software and Platforms
  • Developer Community
  • Tools and Software
  • Open Source Software and Platforms
  • Jump...
  • Cancel
Open Source Software and Platforms
Wiki Run the Arm Platforms deliverables on an FVP
  • Android blog
  • Forums
  • Help
  • Jump...
  • Cancel
  • New
  • About this wiki
  • Supported platforms
  • Obtaining support
  • +Arm Reference Platforms deliverables
  • -A-class platforms
    • +Juno
    • -FVPs
      • Run the Arm Platforms deliverables on an FVP
      • Using pre-"Rev C" AEM FVPs
    • +System Guidance for Infrastructure (SGI)
    • +System Guidance for Mobile (SGM)
    • Corstone-700
    • Cortex-A5 DesignStart
    • Neoverse N1 SDP
    • Neoverse Reference Designs
    • +Legacy platforms
  • +M-class platforms
  • +FPGA prototyping boards
  • +Open source software

Run the Arm Platforms deliverables on an FVP

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.

Running the deliverables on an 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.

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/
$ ./run_model.sh

Note: legacy 32-bit software stack users will also need to pass the `--aarch32' flag to `run_model.sh'.

Built from source

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/

Note: legacy 32-bit software stack users will also need to pass the `--aarch32' flag to `run_model.sh'.

  • Share
  • History
  • More
  • Cancel
Related
Recommended