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.
Subscribe to the Changelog RSS feed to receive alerts when future Fast Models releases become available.
What's new in 11.5
New features and enhancements
- General release of the Iris debug API, which replaces the CADI debug API.
- Fast Models now uses SystemC 2.3.2.
- Support for the ARMv8.5 (Beta) architecture.
- The PCI subsystem now includes an AHCI controller model that can be used to load disk images.
- The FVP_Base_RevC-2xAEMv8A example platform now contains an AHCI controller.
- Timing annotation latency fields have been added to cache MTI trace sources.
- DMI regions greater than 4GB in size are now used correctly inside the AMBA-PV bridges.
- A problem with local time when using VFP instructions with Cortex-M models has been fixed.
Deprecated and removed features
- Support for GCC-4.8.3, GCC-4.8.4, and VC2013 has been removed.
- CADI is deprecated but continues to exist alongside Iris as an optional debug API until end-of-life and removal in May 2020.
- The FVP_Base_AEMv8A-AEMv8A-DP550-V61 example platform has been removed.
Release Note for Release History 11.5
Detailed documentation can be found in the 'Docs' subfolder for Fast Models Portfolio.
A significant number of the examples in Fast Models Portfolio 11.5 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 will mean that examples that require Dhrystone or the Linux images will not be functional, as well as examples using Accellera SystemC 2.3.1.
Enhancements and Changes in Fast Models Portfolio 11.5
Fast Models now uses SystemC 2.3.2. Refer to Accellera SystemC 2.3.2 release notes for more information.
Support for GCC-4.8.3, GCC-4.8.4, and VC2013 has been removed. For a full list of supported platforms, see the list below entitled "Compilers and Operating Systems supported by Fast Models".
Support for ARMv8.5 features is provided at beta quality. The Memory Tagging extension feature is a work in progress. It is disabled by default.
A component, AHCI_PCI, exists for the PCI subsystem, that may be used to load disk images.
The FVP_Base_AEMv8A-AEMv8A-DP550-V61 example platform has been removed.
The FVP_Base_RevC-2xAEMv8A example platform now contains an AHCI controller. For more information on loading a disk image, see https://developer.arm.com/docs/100964/latest/base-platform/base-platform-revc/baseplatformpcirevc-component.
We are pleased to announce the release of the Iris debug API. Iris has been at Beta stage with ongoing testing for more than a year and has now reached a quality level suitable for general release. The Iris debug API is a replacement for the CADI debug API. CADI is now deprecated but will continue to exist alongside Iris as an optional debug API until end-of-life and removal in May 2020.
In addition to the debug functionality that was available in CADI, the Iris API also provides support for event tracing with similar functionality to the existing MTI API. This feature is currently at Beta quality because the in-process performance of Iris trace is significantly slower than MTI. Plans are in place to improve performance of Iris trace in a later release. The out-of-process trace that Iris supports was not possible with MTI or CADI so performance cannot be compared.
Timing annotation latency fields have been added to cache MTI trace sources.
DMI regions greater than 4GB in size are now used correctly inside the AMBA-PV bridges.
A problem with local time when using VFP instructions with Cortex-M models has been fixed.
The folder structure in FastModelsPortfolio 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 Fast Models in a future release.
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.
Fast Models limitations
This section contains information on model limitations for models that are new in this release or new limitations that have been identified for previously released models.
For more information, refer to the Fast Models Reference Manual at: https://developer.arm.com/docs/100964/latest.
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 1st subcluster are configured to be less than 4. CADI targetNames and parameters for cpu[0-3] are always shown from Cortex-A55 subcluster, when viewed by CADI clients.
- 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.
- The model implements version r1p1 of the RTL specification and does not include functionality added by r2p0 or r3p0.
- There are limitations in the CAL (Component Integration Layer) feature, which does not yet function properly with more than 4 devices.
For the InOrder PipelineModel source example plugin, "libtinfo-dev" needs to be installed on Ubuntu 16.04.
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 14.04
- Ubuntu 16.04
- Windows 7
- Windows 10
- Visual Studio 2015 - Update 3
- The following warning is produced when compiling Fast Models with Visual Studio
Unknown compiler version - please run the configure tests and report the results. This occurs due to the Accellera SystemC library using an older version of the Boost library which is not aware of any versions after Visual Studio 2013.
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.5 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 184.108.40.206 (or later) of the FLEXnet license management utilities. Prior versions are not compatible.
License queueing support
When using floating licenses, if all available licenses are in use, models and tools can be configured to queue until a license is available. This is enabled by setting the environment variable FM_LICENSE_QUEUE_TIMEOUT to a timeout value in seconds. The default value of 0 disables this feature.
Note that enabling this feature may cause model initialisation to take a long time, as models will wait for a license to become available until the timeout period expires, rather than failing immediately.
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 16.12 for v8-A platforms and Android 15.03 for v7-A platforms.
The command lines tested are:
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)
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)
- 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 may not clearly indicate that the breakpoint type is unsupported.
CADI methods deprecated for use in Fast Models 11.5:
When attempting to debug an ISIM system, if you launch Model Debugger from System Canvas and then specify an application to load this causes an error in Model Debugger (Error using application...), and the model and application fail to load.
Workaround: Launch Model Debugger without specifying an application, and then load the application from within Model Debugger itself using File -> Load Application Code.
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.
Cache models may output debug messages on stderr even with --quiet.
The Watchpoint mask does not have the expected effect.
When writing to MDSCR_EL1.SS on AEMv8A, it does not change status until an ERET is executed. This should be consistently managed by the has_delayed_sysreg parameter.
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.
The shareable override functionality of CCI400 does not work. The slave interface shareable override register exists and may be read and written but has no functionality.
The value of cpu.register_reset_data and cpu.scramble_unknowns_at_reset should be reflected in the bits of CNTHCTL_EL2 which reset value is UNKNOWN.
When EL3 == AArch32 and executing in AArch32 Secure EL1 (SVC_s), an update of the CNTP_CTL_S causes the tarmac log to print an update of CNTPS_CTL_EL1.
Breakpoints must be set after loading the image to be run, otherwise these will not be hit during execution even if the addresses are accessed.
Cortex-A53, A35, and A32 lack the Advanced SIMD Engine-present parameter.
A17 BROADCAST parameters should be at cluster level, not cpu level.
DynamIQ does not support all cluster models.
On Linux, a program which 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
ModelDebugger 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.
Notice of planned change to licensing terms
The calendar year Q1 2019 release of Fast Models will include a revised End User License Agreement (EULA). If you would like to preview the new EULA prior to the next release, contact your supplier.
Feedback on this product
If you have any comments or suggestions about this product, contact email@example.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.