ARM® RealView® Developer Suite v2.2 Evaluation Version Release Notes

Please read through the following release notes before completing install of the ARM RealView Developer Suite version 2.2 Evaluation Version (RVDS).

Contents

General Information
What's New In This Release
How Can I Purchase RVDS 2.2?
Installation Information
Obtaining and Installing Your Licence
Typical and Custom Installations
Supported Browsers for Online Help
Uninstalling the Evaluation Version Before Installing RVDS 2.2
RealView Compilation Tools v2.2 (RVCT) Release Notes
Changes to ARM/Thumb Assembler Language
RealView Debugger v1.8 (RVD) Release Notes
Should I use RealView Debugger Project Manager or CodeWarrior for RVDS?
Which RealView ICE Version should I use?
Which Multi-ICE Version should I use?
Which MultiTrace Version should I use?
CodeWarrior for RVDS Release Notes (Windows only)

 RealView ARMulator ISS 1.4.1 (RVISS) Release Notes
New Processor Models Supported In This Release
 Installing Exception Handlers
Extensions to the Pagetables Module
 ARM11 Models Release Notes
ARM eXtended Debugger 1.3.1 (AXD) Release Notes (Windows only)


General Information

What's New In This Release

For details of the new features available in this release, together with information about Add-On Options, Frequently Asked Questions and other products in the ARM RealView range, read the product pages at http://www.arm.com/products/DevTools/RealViewDevSuite.html.

Return to Top

How can I purchase RVDS 2.2?

The licence for this evaluation version of RVDS will time out after 45 days. At that point, you can order the product from one of the ARM regional sales processing offices, or via a worldwide network of authorized distributors who offer local knowledge and technical support for the RealView product range. For further information about the ARM RealView development tools please visit www.arm.com or email realview@arm.com.

Return to Top


Installation Information

This release has been tested on the following list of platforms and service packs. Return to Top

Obtaining and Installing Your Licence

Before you can use RVDS, you must obtain a valid license file using the License Wizard found in the ARM section of the Start Menu. This provides step-by-step instructions on installing your license file.

For more assistance with the installation of your license, please consult the ARM FLEXlm License Management Guide in the product documentation, or read our License Management FAQ within the Technical Support area of the ARM web site at http://www.arm.com/support/licensemanagement.html.

Return to Top

Typical and Custom Installations

You can install either a Typical or a Custom installation. In a Custom installation, the "RealView Developer Suite - Utilities (required)" component should always be installed, otherwise the Uninstaller and other utilities will not be installed.

The following components of the "custom" installation are installed by a "typical" installation Return to Top

Supported Browsers for Online Help
The Online Help supplied with the product will function incorrectly with browsers pre-dating the following releases:
- Opera 6 and earlier
- Netscape 4 and earlier
- Konqueror 3.0.3 and earlier
- Internet Explorer 4 and earlier
 
Please upgrade to later versions of these browsers to use the online help.

Return To Top

Uninstalling the Evaluation Version Before Installing RVDS 2.2
You must uninstall RVDS 2.2 Evaluation before installing a full version of RVDS 2.2

During the uninstall process, a dialog box will be displayed indicating the number of days left in your evaluation period. If the evaluation period has expired, the only way to close this dialog box is to click the Cancel button. Please do so - the uninstallation process will continue normally.

Return to Top


RealView Compilation Tools 2.2 Release Notes

The RVCT Essentials Guide describes differences between RVCT 2.2 and previous releases, and can be found in the supplied product documentation.

Changes to ARM/Thumb Assembler Language
Significant additions have been made to the ARM assembly language, primarily to accommodate the new Thumb2 architecture. This is documented in the RVCT Assembler Guide. In addition to the Assembler Changes listed in Section 2.11 of the RVCT Assembler Guide, the mnemonic SWI ("Software Interrupt") has been renamed SVC ("Supervisor Call"). The disassemblers in the compiler (armcc) and fromelf by default now show, for example:
        SVC      0x123456  ; formerly SWI

To produce disassembly in the old syntax (similar to RVCT2.1) use the switch --no_unified_syntax. This option will not be supported in future releases.

The old mnemonic, SWI, is still accepted by the assembler and is the only syntax displayed by the debuggers.

Return to Top

--dwarf3
This release introduces the new option --dwarf3.  The size of the debug tables produced by this option is larger than those produced by the --dwarf2 option.  --dwarf2 remains the default option for the default debug table format.

Linker Relocations
The RVCT 2.2 linker relocations have been enhanced to support the ABI for the ARM Architecture. The linker will attempt to diagnose ABI incompatibilities in the relocation information. Furthermore the linker will attempt to diagnose range and interworking problems with short range 2-byte sized branches. The extra diagnostics are listed here:
Error 6802 if it detects a 2-byte sized branch to a symbol defined in the same section but of different state
Warning 6803 if it detects a 2-byte sized branch to a symbol defined in a different section
Downgradeable Error 6805 if it detects a branch to an absolute symbol which is not of type STT_FUNC
Warning 6806 if it detects a Branch to a symbol defined in a different section which is not of type STT_FUNC
Downgradeable Error 6807 if it detects a 4-byte sized branch to a symbol defined in the same section but of different state
Warning 6830 if it detects a difference between the state implied by the type of the symbol and the state implied by the closest previous mapping symbol.
You are most likely to see these diagnostics for objects produced by older versions of the tools. They can also be triggered by assembly language.

Return to Top


RealView Debugger v1.8 Release Notes

The RVD Essentials Guide describes differences between RVD 1.8 and previous releases, and can be found in the supplied product documentation.

Should I use RealView Debugger Project Manager or CodeWarrior for RVDS?
To ease migration from ADS to RVDS, the CodeWarrior IDE has been re-introduced to RVDS2.2 including provision of conversion utilities for ADS users with existing projects
 
The RVD Project Manager is now not recommended for new designs - developers should use CodeWarrior (for Windows hosts only) or make files
 
The RVD Project Manager will continue to be supported in RVDS2.2 and any service pack releases to allow developers to plan migration of existing projects.

Return to Top

Which RealView ICE Version Should I Use? 
RVDS 2.2 has been tested for use with RVI 1.2 and later releases. If you do not have RealView ICE v1.2, please contact your supplier to obtain this free upgrade.

Return to Top

Which Multi-ICE Version Should I Use? 
Users of Multi-ICE are recommended to upgrade to the latest patch release of Multi-ICE software, available from http://www.arm.com/support/downloads/index.html.

Return to Top

Which MultiTrace Version should I Use? 
Install the MultiTrace patch from the ARM website, http://www.arm.com/support/downloads/index.html, otherwise you may receive the following error when programming the ETM:

"Error calling a trace capture device function"

This can result in unexpected behavior.

Return to Top


CodeWarrior for RVDS Release Notes (Windows Only)
  1. CodeWarrior v5.6.1 is supplied with this release of RVDS. You can read release notes for this product at the following location:
    <Install Directory>\ARM\IDEs\CodeWarrior\5.6\1592\win_32-pentium\Release Notes\
  2. By default code and data sizes are not shown beside the source files in the project window to speed up build times (they appear as -1). To re-enable this feature, go to the RealView Target panel and select Show Object Sizes.
  3. The makefile exporter is not fully functional in this release
  4. The output directory in the project stationary is based on the target name. By default for the supplied stationary it is Debug and Release. If you rename your target you may wish to also rename your output directory (DE 326608)
  5. The batch file runner may occasionally report the following error message after successfully executing: "Link Error   : An error occurred trying to execute batch file." This can be safely ignored (DE 327479).
Return to Top


RealView ARMulator ISS 1.4.1 Release Notes

New Processor Models Supported In This Release
RVDS 2.2 includes new models for ARM968E-S, ARM1156T2-S and ARM1176JZ-S.

Return to Top

Installing Exception Handlers
The RVISS peripheral models can add new exception handlers to the core using the function ARMulif_InstallExceptionHandler. This allows the peripheral model to handle an exception itself. An example of this is the semihosting model handling the SWI vector. The RVISS models store exception handlers as a linked list that is iterated over from start to end when an exception occurs.

On ARM7 / ARM9 and StrongARM models: The new exception handler is added to the end of the list. The list is iterated over and all exception handlers are called. If any return true the built in exception handlers are not taken.

On ARM10 / ARM11 / XScale models: The new exception handler is added to the start of the list. When an exception occurs the core iterates over the list from the beginning so the handler installed last will be called first. It stops iterating if a handler returns TRUE.

Return to Top

Extensions to the Pagetables Module
The pagetables module has been extended to support the memory protection unit used by ARM1156T2-S and ARM1156T2F-S processors.

The memory regions are defined in peripherals.ami in a similar way to the existing regions. The regions are defined as MPURegions[n]. Up to16 regions are supported. For more details about these please consult the ARM1156T2-S Technical Reference Manual.

An example of a 4GB, cacheable and bufferable region is shown below.

{ MPURegion[0]
PhysicalBase=0
Size=4GB
Cacheable=Yes
Shareable=No
Bufferable=Yes
AccessPermissions=3
TEX=0
Execute_Never=0
}

PhysicalBase defines the base address for the region, Size the size of the region, and the remaining variables are used to create the access control register for that region.

Return to Top

ARM11 Models Release Notes
Running images linked using BE32 on ARM11 processors
Images linked using the BE32 option should be run on the _BE32 variant of any ARM11 processor model. All other images should be run on the ordinary model.

Use of Vector Floating Point
The ARM1136JF-S, ARM1156T2F-S and ARM1176JZF-S models already include a built-in VFP11.  No further FPU selection needs to be made for these - i.e. the FPU selection should be left as "No FPU". The ARM1136J-S, ARM1156T2-S and ARM1176JZ-S models do not include a VFP and should not be used with any VFP option as it will potentially produce incorrect results - i.e. again the FPU selection should be left as "No FPU".

ARM1136JF-S and ARM1136J-S Models
The following restrictions apply to ARM1136JF-S and ARM1136J-S models:
1. The caches are not modelled accurately enough to show aliasing effects for cache sizes greater than 16kB.
2. Under RVD the Invalidate by Range operations that are new to the v6 Architecture are shown as 64 bit registers. The high 32 bits of this register is the start address and the low 32 bits are the end address.
3. The following registers are unmodelled:
Register Debugger symbol in RVD
Data Memory Remap Register @CP15_D_MEM_REMAP
Instruction Memory Remap Register @CP15_I_MEM_REMAP
DMA Memory Remap Register @CP15_DMA_MEM_REMAP
Peripheral Port Memory Remap Register @CP15_PERPH_MEM_REMAP
Instruction Cache Master Valid Register @CP15_ICACHE_MASTER_VALID_REGISTER_0/7
Instruction SmartCache Master Valid Register @CP15_ISMARTCACHE_MASTER_VALID_REGISTER_0/7
Data Cache Master Valid Register @CP15_DCACHE_MASTER_VALID_REGISTER_0/7
Data SmartCache Master Valid Register @CP15_DSMARTCACHE_MASTER_VALID_REGISTER_0/7
Main TLB VA Register @CP15_TLB_MAIN_VA
Main TLB PA Register @CP15_TLB_MAIN_PA
Main TLB Attribute Register @CP15_TLB_MAIN_ATT


Return to Top

Accessing RVISS through AXD 1.3.1 (DE 316342)
Under some circumstances, it is possible to get "DBE Warning 0041: an unspecified debug toolbox call failed." after re-configuring RVISS. You can recover by choosing restart in the error box. If you wish to reload the current image, you will have to do this manually, for example by pressing the "reload" button.

Return to Top


AXD 1.3.1 Release Notes (Windows Only)

Running Multiple Versions of AXD
It is possible to install multiple versions of AXD, for example the RVDS 2.2 AXD and the ADS 1.2.1 AXD, but only one version of AXD can be "active" on a single machine at any one time. ARM provides a utility called SuiteSwitcher which allows you to easily switch between different versions of AXD on the same machine. You can download the utility here:
http://www.arm.com/support/downloads/info/4627.html

Alternatively if you wish to use two different versions of AXD on the same machine, it is necessary to manually activate the appropriate version of AXD by running "register.bat" in the directory containing the particular AXD.EXE that you wish to activate. Failure to do this can result in a dialog containing the following: "remote_a.sdi has unexpected Product Version. Expected 2.0, got 1.2. Please contact your supplier."

Using vbscript.dll
The AXD command line interface (CLI) requires the system library vbscript.dll to be registered. This should be registered automatically on all Windows systems, but if you get the error "Script Engine has not been registered" when trying to use the AXD CLI, you can register it manually by typing the following at a Windows command prompt:

    %SystemRoot%\system32\regsvr32.exe %SystemRoot%\system32\vbscript.dll

Return to Top


Release Notes End