Fast Models Portfolio 7.1 Release Notes
(version 7.1.45 dated 2012/05/24 12:57:33 GMT)

Introduction

Detailed documentation can be found in the doc subfolder for Fast Models Tools and the Docs subfolder for the Fast Models Portfolio.

A significant number of the examples in the Fast Models Portfolio 7.1 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 any examples that require dhrystone.axf, dhrystone_v7m.axf or the Linux images will not be functional, as well as any example using OSCI System C 2.2 and TLM 2.0.

Enhancements and changes in the Fast Models Portfolio 7.1 release

Fast Models 7.1 includes enhancements/changes in the following since 7.0:

Multiple Instantiation (MI)

Fast Models now adds support for Multiple instantiation to its SystemC export capability.

Overview

'simgen' can be invoked with the --enable-mi option. This enables the new MI SystemC export.

When 'simgen --enable-mi' is used, a new class scx::scx_evs_Dhrystone is generated (Dhrystone is just used as a placeholder for the system name here). The header file for this is '#include <scx_evs_Dhrystone.h>'.

Supported features:

See the Fast Models - SystemC Export with Multiple Instantiation document for more information, $PVLIB_HOME/Docs/GENC-010823_mi_ug.pdf.

SystemC Export with Single Instance (SI) is deprecated and will be removed in a future release of Fast Models. Please contact ARM for advice on moving to Multiple Instantiation (MI).

Outstanding issues

The function sg::SchedulerInterfaceForComponents::SchedulerThread::start() is not required to (and does not for all use cases) behave as specified in the header and in the documentation. The specification will change in future versions of Fast Models regarding this behavior:

The start() function returns immediately without running the threadProc() function of the thread. Calling start() during the elaboration phase adds the thread to the list of threads which will be made runnable once the simulation starts running. Calling start() while the simulation is already running will add the thread to the list of runnable processes for the current scheduler time. Calling start() on an already-started thread has no effect. Calling start() on a thread which already terminated (threadProc() returned) has no effect.

The current SystemC export default scheduler mapping is in line with this new specification. The current Fast Models standalone scheduler requires all threadProc() functions to call wait(0) once initially to produce this behavior. All threads in Fast Models components do this already, so this specification change does not affect any Fast Models component. Future versions of Fast Models will not require this initial wait(0) in threadProc(). This issue only affects users who either implement or call start() directly which is usually not necessary (SDDKW-13039).

Limitations

The following are current known limitations:

Microsoft Visual Studio 2010 support

Support for building models using Microsoft Visual Studio 2010 has been added.

gcc 4.4 support

Support for building models using gcc 4.4.4 has been added.

ARM Cortex-R7

A model of the ARM Cortex-R7 processor is introduced. This is an ARM-v7 R profile core.

There are two variants introduced in the Fast Models 7.1 release, each with supporting periperals:

MTI Plugin Development Kit

The Model Trace Interface plugin development kit (MTIPDK) is now shipped as standard with Fast Models Portfolio.

Deprecated in the Fast Models Portfolio 7.1 Release

The following are deprecated in Fast Models Portfolio 7.1:

Removed from the Fast Models Portfolio 7.1 Release

GCC 3.4 support has been removed.

Platform requirements for Microsoft Windows

When running Microsoft Windows XP or Microsoft Windows 7 it is recommended to use machines with at least 2GB RAM, and preferably at least 4GB for best performance. To use audio a 2GHz, or faster, Intel Core2Duo, or similar-performing, processor is recommended.

Operating system:

Compiler:

Runtime Libraries:

Please email support-esl@arm.com with any comments

To view the documentation, Adobe Acrobat reader (Version 8 or higher) must be installed on the system.

Platform requirements for Linux

When running on Linux it is recommended to use machines with at least 2GB RAM, and preferably at least 4GB for best performance. To use audio a 2GHz, or faster, Intel Core2Duo, or similar-performing, processor is recommended.

Operating system:

Compiler:

When building models for 32-bit hosts, Fast Models 7.1 for Linux supports the following compilers:

When building models for 64-bit hosts, Fast Models 7.1 for Linux supports the following compilers:

64-bit host model support:

Additional project configurations are available for most recently-created System Canvas projects and selected updated example projects. To build for a Linux 64-bit host, start System Canvas and change the 'Active Project Configuration' to one of the 'Linux64-Release-GCC' configurations, then rebuild the project.

To view the documentation, Adobe Acrobat reader (Version 8 or higher) must be installed on the system.

Licence management utilities

If you are using floating licenses, you must use FLEXnet license management utilities version 9.2 or higher. FLEXnet 10.8 license management utilities are available as an optional installable component in the product installer.

Use the highest version of the license management utilities provided with any ARM tools you are using. It is recommended to set up the user environment running applications of the Fast Models product only for one armlmd license server, because spreading Fast Models license features over different servers could result in license denials for certain features.

For more instructions on installing licenses please consult the ARM online documentation:

Installation notes

This section covers installation information for:

Microsoft Windows XP and Microsoft Windows 7

The Fast Models Portfolio installs its examples into the specified install location, which is normally under C:\Program Files\ARM\ On Microsoft Windows 7, without Administrative privileges it is not possible to build and run the examples in situ. It is therefore necessary to copy the file hierarchy under C:\Program Files\ARM\FastModelPortfolio_7.1\examples to a local directory to which the user has read/write permissions. Once this is done, it is necessary to load examples into the System Canvas tool from this new location (TA-588366/SDDKW-3784).

By default, Microsoft Windows 7 does not provide an executable telnet client. For instructions on how to deal with this, please see Chapter 5 of the Fast Models Reference Manual.

Linux

Once you have installed the Fast Models package, it is necessary to source the following script (dependent on shell) to set up up the appropriate environment variables. This should ideally be included such that it is sourced into the user's environment when they log in:

TPIP

The Third-Party IP package (TPIP) must be installed after the Fast Models package.

Using the MPS platform model

This section provides information for loading and running the platform.

Loading and running the platform

The platform model comes with a pre-built flash image that contains a slightly modified version of the MPS BootMonitor and the MPS SelfTests. The platform has a parameter for the name of the file that is loaded into the flash on startup. To use the flash image this parameter needs to be set properly.

Examples:

The BootMonitor can be used to start images from flash:

When running the MPS SelfTests, the following tests are expected to fail on the MPS platform model:

Using the ARM Profiler with Fast Models 7.1

Fast Models version 7.1 supports ARM Profiler version 2.1, as shipped in ARM RealView Development Studio 4.0 SP2, and later. It does not support the use of ARM Profiler 2.0 or earlier, which was shipped in ARM RealView Development Studio 4.0 and 4.0 SP1.

If you currently have ARM Profiler 2.0 and wish to use the ARM Profiler with Fast Models 7.1, it will be necessary to upgrade to ARM RVDS 4.0 SP2. Please contact ARM Support for further details.

Using TAP/TUN-based Model Networking

Fast Models Version 6.0 added a new model-to-host networking implementation based on TAP/TUN. This has a number of advantages compared to the previous version:

Installation instructions for Model Networking can be found in the Fast Models Reference Manual, Sections 5.4.45, 5.6.3, and 5.6.4.

However, due to the different implementation and configuration methods, you may encounter some issues during installation:

Outstanding issues

The following known issues and limitations exist in this release:

CT model issues

CT model issues are as follows:

Model Trace Interface (MTI)

Trace output from the ARM Cortex-M3 fast model has the following known limitations:

CLCD

CLCD has the following known limitations:

PL011 UART

The following parameters of the PL011 UART are being deprecated in the next release of the product (TA-641768/SDDKW-4497):

Model generation issues

There is one known model generation issue:

Networking

There are the following known networking limitations: