Release History

The latest Fast Models release version is reported at the top right of this page.

Details on What's New, and links to the Release Notes are provided below.

 

Fast Models

Version 11.9

Released: November 27, 2019

What's new in 11.9

New features and enhancements

  • Support for Armv8.6-A features
  • Beta support for GCC 7.3
  • Wayland client support has been added to GGA/GRM
  • Python support policy has been aligned with the official Python release schedule
  • FVPs are built with compilers gcc-6.4 and VisualStudio 2017.

Deprecated and removed features

  • Windows 7 support is deprecated
  • Accellera SystemC version 2.3.1 support is deprecated
  • Ubuntu 14.04 support is deprecated
  • GCC 5.x compiler support is deprecated

Release Note for Release History 11.9

Detailed documentation can be found in the Docs subfolder for Fast Models Portfolio and at https://developer.arm.com/products/system-design/fast-models/docs.

A significant number of the examples in Fast Models Portfolio 11.9 make use of images containing third party IP. These have been split out into a separate 'Third Party IP' package that can be downloaded from:

Not installing these images means that examples that require Dhrystone or the Linux images will not be functional, as well as examples using Accellera SystemC 2.3.2.

Enhancements and changes in Fast Models Portfolio 11.9

  • Fast Models supports Armv8.6-A features

  • We have added beta support for GCC 7.3

  • We have added Wayland Client support to GGA/GRM

  • As part of our licensing simplification project, Fast Models from 11.7 onwards updates the End User License Agreement (EULA). The new EULA aligns with other Arm software products, giving a consistent set of terms and conditions across products.

  • Fast Models support policy with regard to Python is aligned with the official Python support. See the following link for the schedule of Python releases: Status of Python branches

    In particular, Fast Models does not guarantee support for any Python version that has reached end of life according to the schedule of the Python community.

  • We have deprecated support for Windows 7 and will remove support in the Q1 2020 release

  • We have deprecated support for Accellera SystemC version 2.3.1 and will remove support in the Q1 2020 release

  • We have deprecated support for Ubuntu 14.04 and will remove support in the Q1 2020 release

  • We have deprecated support for GCC 5.X compilers and will remove support in the Q1 2020 release

  • We are shipping FVPs built with compilers gcc-6.4 and VisualStudio 2017. This change is applied to build system projects SysGen:Models, SysGen:SubSystemModels and SysGen:ModelPackages

  • New tutorial added to Fast Models User Guide: Building Fast Models

  • Graphics Acceleration in Fast Models chapter in Fast Models User Guide has been rewritten

Notice

  • The planned deprecation of GCC 4.9.2 has been extended to Q4 2020 Fast Models release.

  • We plan to update ffmpeg to 4.1.3. This will only affect users of the Mali video processor models.

  • The folder structure in Fast Models Portfolio will be refactored in a future release.

  • The default parameter values for HostBridge and VirtioNet will change in a future release.

  • Model Shell and the related SimGen target (TARGET_MAXVIEW) are deprecated. They will be removed from the Fast Models releases no earlier than Nov 2019.

  • The zstdint.h and zinttypes.h supplied headers are deprecated and will be removed from the product in the future. Use the standard cstdint and cinttypes files instead.

  • The TxThread.h and TxRunnable.h supplied headers, and the TxThread and TxRunnable types, are deprecated and will be removed from the product in the future. Use the standard library thread facilities instead.

  • Support for MxScript will be removed from Model Debugger in a future release. Use Iris Python Debug Scripting instead.

Fast Models limitations

This section contains information on limitations for models that are new in this release or new limitations that have been identified for existing models.

For more information, refer to the Fast Models Reference Manual at: https://developer.arm.com/docs/100964/latest.

  • Improvements to ClockTimer[64] component to ensure clocks run correctly when switching frequencies:

    Previously, it was possible for a Clock component to run even if the connection to the clk_in input was missing. This is no longer possible and designs that erroneously relied on the old behavior might not function correctly. For example, software running on the design might hang.

  • DynamIQ (FCM):

    For flexible Cortex-A55+Cortex-A75 clusters, there is a known issue related to presentation of parameters and CADI targetNames to CADI clients when cpu instances in the first subcluster are configured to be less than 4. CADI targetNames and parameters for cpu[0-3] are always shown from the Cortex-A55 subcluster, when viewed by CADI clients.

  • DMC-620 Dynamic Memory Controller Fast Model:

    • No support for address striping.
    • Works with linear addresses and not in rank,bank,row,column form.
    • Includes error injection and detection mechanisms and syndrome registers support only for 2 out of the 6 RAS error types.
    • Scrubbing functionality is not provided.
    • Does not implement direct read or write commands.
    • Does not implement any performance counters.
  • CMN-600 Coherent Mesh Network:

    • The model implements version r1p1 of the RTL specification and includes CAL (Component Aggregation Layer) functionality that was added in r3p0.
    • The model supports a new revision parameter to select between r1p1 and r3p0 implementations.
    • CAL r2 and r3 features are supported. Further testing of these features is planned.
    • The following CML (Coherent Multi-chip Links) r3 features are supported:
      • LDID-based CML routing
      • CCIX port aggregation support
      Further testing of these features is planned.
  • Pipeline Model plug-in:

    For the InOrder PipelineModel source example plugin, libtinfo-dev needs to be installed on Ubuntu 16.04.

  • The cp15sdisable port/parameter is removed from some cores that do not support AArch32 at EL3.

Compilers and Operating Systems supported by Fast Models

  • RedHat 6
  • RedHat 7
  • Ubuntu 16.04
  • Windows 7
  • Windows 10
  • GCC-4.9.2
  • GCC-5.4.0
  • GCC-6.4.0
  • GCC-7.3
  • Visual Studio 2015 - Update 3
  • Visual Studio 2017. The following Visual Studio 2017 components are required:
    • Visual C++ ATL for x86 and x64.
    • Visual C++ MFC for x86 and x64.

Hardware requirements for Generic Graphics Accelerator (GGA)

GGA has been validated on the NVIDIA GT 730 or later graphics cards with the following driver versions:

  • 390.77 and above for Ubuntu.
  • 390.77 and above for Windows.

FLEXnet license management utilities

FLEXnet server binaries are no longer shipped with the product; if you need them, download them from https://developer.arm.com/products/software-development-tools/license-management/downloads.

Release 11.9 of Fast Models requires a newer version of the FLEXnet license management utilities. If you are using floating licenses, you need to upgrade to version 11.14.1.0 (or later) of the FLEXnet license management utilities. Earlier versions are not compatible.

Linaro images and command lines tested in this release

All A-profile platforms available in this release have been validated against the following Linaro images: Android 18.07 for v8-A platforms and Android 15.03 for v7-A platforms.

The command lines tested are:

  • v8-A (examples):

    FVP_Base_AEMv8A-AEMv8A \
    -C pctl.startup=0.0.0.0 -C bp.secure_memory=0 -C cache_state_modelled=0 -C bp.pl011_uart0.untimed_fifos=1 \
    -C bp.secureflashloader.fname=bl1.bin -C bp.flashloader0.fname=fip.bin \
    -C bp.ve_sysregs.mmbSiteDefault=0 -C bp.virtioblockdevice.image_path=fvp.img \
    --data cluster0.cpu0=Image@0x80080000 \
    --data cluster0.cpu0=fdt.dtb@0x82000000 \
    --data cluster0.cpu0=ramdisk.img@0x84000000
    EVS_Base_AEMv8A-AEMv8A.x \
    -C Base.pctl.startup=0.0.0.0 -C Base.bp.secure_memory=0 -C Base.cache_state_modelled=0 -C Base.bp.pl011_uart0.untimed_fifos=1 \
    -C Base.bp.secureflashloader.fname=bl1.bin -C Base.bp.flashloader0.fname=fip.bin \
    -C Base.bp.ve_sysregs.mmbSiteDefault=0 -C Base.bp.virtioblockdevice.image_path=fvp.img \
    --data Image@0x80080000 \
    --data fdt.dtb@0x82000000 \
    --data ramdisk.img@0x84000000
    (This command line is also valid for SVPs)
  • v7-A (examples):

    FVP_VE_Cortex-A15x1-A7x1 \
    -C motherboard.flashloader0.fname=boot/rtsm/uefi_rtsm_ve-ca15.bin -C motherboard.flashloader1.fname=uefi-vars.fd \
    -C motherboard.flashloader1.fnameWrite=uefi-vars.fd -C motherboard.mmc.p_mmc_file=linaro.img \
    -C motherboard.pl011_uart0.unbuffered_output=true -C motherboard.smsc_91c111.enabled=1 \
    -C motherboard.hostbridge.userNetworking=1
    EVS_LinuxBoot_Cortex-A15x2 \
    -C Base.motherboard.flashloader0.fname=boot/rtsm/uefi_rtsm_ve-ca15.bin -C Base.motherboard.flashloader1.fname=uefi-vars.fd \
    -C Base.motherboard.flashloader1.fnameWrite=uefi-vars.fd -C Base.motherboard.mmc.p_mmc_file=linaro.img \
    -C Base.motherboard.pl011_uart0.unbuffered_output=true -C Base.motherboard.smsc_91c111.enabled=1 \
    -C Base.motherboard.hostbridge.userNetworking=1
    (This command line is also valid for SVPs)

Outstanding issues

  • GGA issues:

    • GGA-only mode is not supported on Linux targets in this release

    • On Windows hosts, only Android targets are supported. To simulate Linux (non-Android) distributions, you must be running a Linux host

  • There is a performance issue with in-process trace using Iris compared to trace using MTI.

  • Models only support some types of memory breakpoints. Currently the error message returned if an unsupported type is used might not clearly indicate that the breakpoint type is unsupported.

  • CADI methods deprecated for use in Fast Models 11.9:

    • CADICallbackObj
      • appliOpen()
      • appliClose()
      • cycleTick()
      • killInterface()
  • A15 bus transactions are not bus accurate.

  • CADI and MTI names for CP15 registers are different.

  • When semihosting is enabled on a SystemC model and a read from stdin is done within the target software, the semihosting call from CADI does not originate from the SystemC thread. Consequently the complete simulation becomes blocked if the semihosting call cannot complete due to no user input.

  • In some circumstances, the model will boot more slowly when an operating system filesystem image is used in read-only mode. The workaround is to make sure that the image is writeable.

  • Cortex-A53, Cortex-A35 and Cortex-A32 lack the Advanced SIMD Engine-present parameter.

  • A17 BROADCAST parameters should be at the cluster level, not at the cpu level.

  • DynamIQ does not support all cluster models.

  • On Linux, a program that dynamically loads a model shared object file using dlopen() must be linked with the pthread library (-lpthread), even if the program is otherwise single-threaded. Failure to do so may result in a segmentation fault, or other abnormal termination, possibly with the message 'Enable multithreading to use std::thread: Operation not permitted', depending on the libstdc++ version. The underlying defect is a libstdc++ bug (#67791) which has been exposed by migrating the model to C++11 threads.

Outstanding tools issues

  • Model Debugger does not display the correct values for wTasKMaskId.

  • The Cortex-M0 model exposes a VTOR register via CADI, but this register in not present in hardware.

  • On Windows, .bmp files are copied into the top Build folder for FVP_MPS2 models. They are not accessible to the isim_system generated in the internal platform/flavor dependent folder. An easy workaround is to manually copy them into that folder.

  • Neoverse-N1/Neoverse-E1 Fast Models:

    • DBGEN, SPIDEN, NIDEN, and SPIDEN signals in the model have per-core instances instead of per-cluster.
    • The cfgsdisable signal will be removed in a future release.

Feedback on this product

If you have any comments or suggestions about this product, contact support-esl@arm.com and give:

  • The product name.

  • The product revision or version.

  • An explanation with as much information as you can provide. Include symptoms and diagnostic procedures if appropriate.