ARM^® RealView^® ICE v4.1 Release Notes

RealView ICE v4.1 (RVI 4.1) adds support for the Cortex-M4 processor. It also adds support for several new platforms.

You are strongly advised to read through the following release notes before using the software, as they contain the most recent information for RVI 4.1.

Please note, if viewing the release notes using the installer under Linux, links to external web pages may not be operational. If this is the case you can view the release notes after the installation has completed using your normal browser. This readme.html can also be found at the root of the installation CD.

• New features in RVI v4.1
• Installation
• Debug
  • Supported Hardware Development Platforms
  • Supported Processors
  • Notes on Marvell core support
• GDB support
• Known issues
• Obtaining further support information
• Third Party notices

New features in RVIv4.1

Support for DSTREAM

RVI v4.1 adds support for debugging the ARM Cortex-M4.

RVI v4.1 now supports USB on supported 64-bit Linux and Microsoft Windows Operating Systems.

Installation

New RealView ICE software and firmware

This release of RealView ICE includes new firmware as well as new host software and drivers. Please refer to Chapter 7 of the "RealView ICE and RealView Trace User Guide", version 4.1 for instructions on how to upgrade the firmware on a RealView ICE unit. The firmware can be found in the installation directory in the RVI/Firmware sub-directory.

Supported Operating Systems

RealView ICE v4.1 supports the following Operating Systems:

• Windows XP Professional service pack 3
• Windows Vista Business service pack 2
• Windows Vista Enterprise service pack 2
• Windows 7 Professional Edition
• Windows 7 Enterprise Edition
• Red Hat Enterprise Linux WS version 4 for x86 using GNOME Window Manager and Bash Shell
• Red Hat Enterprise Linux WS version 5 for x86 using GNOME Window Manager and Bash Shell

Compatible RealView Debugger versions

RealView ICE v4.1 is compatible with RealView Debugger (RVD) Version 4.1 as supplied with RealView Development Suite version (RVDS) 4.1 SP1.

Online Help Notes

The Adobe SVG Viewer is required to display online help images. To test whether your PC has the SVG plug-in correctly installed, access the following link to the SVG plug-in test: http://www.adobe.com/svg/viewer/install/svgtest.html. If the test fails, you must install the Adobe SVG Viewer:

1. Access the Adobe site: http://www.adobe.com/svg/viewer/install
2. On the web page, scroll down to the "Downloads" section.
3. Within this section, under "Installing Adobe SVG Viewer", there is a table of various operating systems.
4. Locate and select the appropriate OS for your platform, for example "Win 98-XP".
5. Follow the on-screen instructions.

Requirements for installing on Windows Operating Systems

The installer for this product must be run with administrator privileges.

Important note for DNS and DHCP network administration

RealView ICE Software uses the hostname of the RealView ICE unit to make a connection. If the RVI software cannot connect to the requested hostname, it performs a local search of the network for RVI units with the same name. If one is found, the IP address of that unit is used. The RVI software will warn you if it is going to use the IP address because, if you are using DHCP, the IP address is likely to change when the unit is power-cycled. Changing the IP address would therefore invalidate the stored connection settings and prevent re-connection.

If your network DHCP and DNS do not work together, then you should apply for a static IP address for your RealView ICE unit from your network administrator: this will isolate you from any problems with changing IP addresses.

Debug

RealView ICE v4.1 supports the following Hardware Development Platforms:

• TI OMAP 1710 (generic)
• TI OMAP 3410 (generic)
• TI OMAP 3420 (generic)
• TI OMAP 3430 (generic)
• TI OMAP 3440 (generic)
• TI OMAP 3450 (generic)
• TI OMAP 3503 (generic)
• OMAP 3530 EVM (Mistral)
• TI OMAP 3515 (generic)
• TI OMAP 3525 (generic)
• TI OMAP 3530 (generic)
• TI OMAP 5912 (generic)
• TI DaVinci (TMS320DM355)
• TI OMAPL138 LogicZoomExpKit
• TI TMS570PSFC61
• ZOOM OMAP34x-II MDP
• Beagleboard
• Freescale i.MX25PDK
• Freescale i.MX28PDK
• Freescale i.MX27 LiteKit
• Freescale i.MX31 (generic)
• Freescale i.MX31 (Zoom LITEKIT)
• Freescale i.MX31 (Phycore RDK)
• Freescale i.MX35 (generic)
• Icytecture i.MX35BaseModule
• Silica Phytec iMX35
• Freescale i.MX51 (generic)
• Freescale i.MX51PDK
• ST u8500
• ARM PB1176
• ARM PB926
• Atmel AT91SAM9261-EK
• Atmel AT91SAM9263-EK
• Atmel AT91SAM9G45-EK
• Atmel AT91SAM9RL-EK
• Keil MCBSTM32
• NXP LPC3250_FDI
• Samsung S5PC100 SMDK

Note: generic support denotes support for the platform and does not include board specific settings such as trace signal calibrations and board reset configurations.

Board Support notes

AT91SAM9261-EK, AT91SAM9263-EK, AT91SAM9RL-EK, AT91SAM9G45-EK-E

The Atmel AT91SAM boards listed above are supported within this release of DSTREAM/RVI and have 2 sets of platform files available, one with JTAG clock speed = 10Mhz and another with JTAG clock speed = 5Khz. If debugging through reset, it is recommended that the user utilises the platform files with JTAG clock = 5Khz otherwise JTAG communication may be lost. Otherwise, if not intending debugging through reset, use the 10Mhz JTAG clock speed for optimal communication speed.

The AT91SAM9G45-EK-ES may not have the in-line resistor R84 fitted in series with the nTRST line from the JTAG connector. If this is the case, then the DSTREAM or RVI unit cannot perform a TAP reset whilst debugging through reset and communication with the target can be lost. If this occurs then the reset type should be set to 'Fake'.

ETM trace on AT91SAM9263-EK

If tracing off-chip via the mictor connector J28, the AT91SAM9263-EK board must have R30 removed; see section 4.1 of "AT91SAM9263-EK Evaluation Board Rev. B User Guide". Failure to remove the resistor when tracing off-chip may result in trace capture failure.

Resets on Icytecture and Silica/Phytec iMX35

Both these boards have their nSRST and nPORST lines tied, so a System reset also results in a Power-on reset occurring, with consequential loss of the debug settings for the target. Consequently, the target runs from the reset vector without intervention by the RVI or DSTREAM unit.

Freescale iMX25 PDK

Should auto-detection of the iMX25 fail, please confirm that the RVI firmware has been upgraded to RVI 4.1. A known issue with auto-detecting this target was identified and fixed within the RVI 4.1 firmware. When attempting to obtain off-chip trace on this target from the ETM, it has been found that if the ARM Core Clock is > 133Mhz (TRACECLK > 66Mhz) then the trace may be corrupt. No work around is known for this, please contact the board vendor if this problem is encountered.

Future Designs Inc. NXP LPC3250

This board does not feature the standard ARM 20 pin JTAG connector. Therefore, in order to connect an RVI or DSTREAM unit to this board, the JTAG adaptor referred to in "LPC3250 User Manual" sec. 10 must be constructed. It is also possible that the 10-way JTAG debug connector J3 pinout may be reversed on this board, please confirm the correct pinout on this connector before making up the adaptor otherwise damage may result to the target hardware and/or debug hardware. ARM cannot be held responsible for such damage.

RealView ICE v4.1 supports the following processors:

• ARM720T
• ARM740T
• ARM7TDMI-S
• ARM7TDMI
• ARM7EJ-S
• ARM9EJ-S
• ARM920T
• ARM922T
• ARM925T
• ARM926EJ-S
• ARM940T
• ARM946E-S
• ARM966E-S
• ARM968E-S
• ARM968E-Srd
• ARM1136JF-S
• ARM1156T2F-S
• ARM1176JZF-S
• ARM11 MPCore
• Cortex-A9
• Cortex-A8
• Cortex-A5
• Cortex-M0
• Cortex-M1
• Cortex-M3
• Cortex-M4
• Cortex-R4
• Cortex-R4F
• SecurCore SC100
• SecurCore SC200
• Marvell 88FR101
• Marvell 88FR111
• Marvell 88FR331
• Marvell 88SV581x-v7 PJ4

The following cores are supported when connected via JTAG-AP in a CoreSight system:

• ARM7TDMI-S
• ARM7EJ-S
• ARM9EJ-S
• ARM926EJ-S
• ARM946E-S
• ARM966E-S
• ARM968E-S
• ARM1136JF-S
• ARM1156T2F-S
• ARM1176JZF-S
• ARM11 MPCore

NOTE: A problem in r2 & r3 ARM7TDMI-S cores can lead to incorrect program execution if two breakpoints are placed immediately after a non-branching multicycle instruction. After this multicycle instruction is executed, the debug hardware generates an incorrect address for the breakpoint entry. RealView ICE may then return control to the wrong address after the breakpoint.

Examples of non-branching multicycle instructions are Data Processing with Register Shift; Multiplies; Load or Store instructions.

Contact your CPU vendor for full errata.

Marvell Core Support

RealView ICE supports the Marvell 88FR101 and Marvell 88FR111 cores. On some early revisions of the Marvell 88FR101 and 88FR111, mode specific breakpoints need to be inverted to work correctly. The behaviour of the RealView ICE when setting these breakpoints can be altered by using a configuration item named "Invert mode specific breakpoints". For more information on setting configuration items please refer to section 4.2.7 "Configuring devices" in RealView ICE 4.1 User Manual.

GDB support

RealView ICE contains functionality to allow the user to use GDB to debug over RealView ICE.

For more information visit the RealView ICE GDB Pages at http://www.arm.com/products/DevTools/RVIGDB.html. Here you can find the latest information about GDB including:

• Later supported GDB versions
• Drivers to enable Ethernet and serial communications over DCC

Known issues with RVI 4.1

Using RVI 4.1 tools from the Linux command line requires correct environment setup

When using RVI 4.1 tools (for example, CSAT) from the linux command line with older editions of RVI or RVDS installed, it is possible for the tools to load incompatible versions of runtime libraries, resulting in failure to connect.

To avoid this issue, run the provided environment setup script before using any RVI 4.1 tools from the command line:

cd <install root>
source rvi_4_1_env.posh

If running any scripts to set up the RVDS toolset for command line use (for example RVDS41env.posh), ensure that rvi_4_1_env.posh is run afterwards.

Performing a system reset (nSRST) on i.MX31 platforms will cause trace data collection in ETB to fail

A system reset on i.MX31 platforms causes the ETB programming to be reset. This results in analyzer connections in RVDS failing to capture any trace. To work around this, disconnect and reconnect the analyzer window after performing a reset.

Range breakpoints not supported for Cortex cores

In RVI 4.1 breakpoints that fire on a range of memory addresses are not supported for the Cortex-A8, Cortex-A9 and Cortex-R4.

CSAT log file creation fails

If CSAT is installed in a directory that does not allow creation of files, then on execution the error message "Error : Failed to open logfile CSAT.LOG" will appear on execution. The logging feature in CSAT will be disabled at this point.

There are three ways to work around this issue...

1) Re-enable logging by providing a logfile name and path that is valid for user creation of files.

This can be done either on the command line if using CSAT interactively using the following command.

   log <writeable-directory>/<filename>

For example,

   log /home/me/log_dir/mylog.txt

Alternatively, if using CSAT batch files, put a similar line at the top of the file.

2) Run the CSAT executable from a location that is writeable. The environment is set up correctly at install time for the RVI tools to run. Simply switch to a writeable directory and type "csat" and the program should run and create a log file in the current directory.

3) Copy the CSAT installation into an alternative directory (set up the environment appropriately for your operating system) and run from there.

On Windows operating systems the following files are required.

• csat.exe
• boost_thread-vc71-mt-1_31.dll
• rvicomms.dll
• rvt_cli_cmds.dll

On Linux operating systems the following files are required.

• csat
• libcli_cmds.so
• libeditline.so
• librvicomms.so
• libboost_thread-gcc-mt-1_31.so.1.31.0

Connecting to boards with both debug and trace connectors with DSTREAM unit

If the target has both debug and trace connectors and the trace connector brings the debug signals out, then it is recommended that debug takes place solely via the trace connector if DSTREAM unit is in use. If debug is being performed without trace being required, then it is recommended that the user disconnects the trace mictor cable from the target. This is because it is possible that conflicting debug signals can be generated due to stubs existing on the trace lead and these can conflict with the debug signals being generated by DSTREAM.

Problems when switching between LVDS Probe and JTAG ribbon cable when previous RealView ICE connection had used SWD

A problem can occur when the user reconfigures their connection to RealView ICE in RVDS when the previous connection used SWD and the RealView ICE unit is no longer reachable. The following sequence happens:

1. RVDS supplies the previous configuration file to RVConfig.
2. RVConfig uses the address of the unit in the configuration file to attempt to connect to that unit.
3. If the unit is no longer reachable, RVConfig will report an error and then let the user attempt to connect to another RealView ICE unit.
4. If the user selects a RealView ICE unit that doesn't have an LVDS cable connected, or has an LVDS cable that does not support SWD, then the connection to the new unit is refused with the "Configuration Error" message, "This configuration requires an SWD connection. The RVI does not support SWD. Please ensure the correct probe is connected between the RVI and the target".

To work around this issue the user can either:

1. Create a new connection in RVDS rather than reconfiguring an existing one. The existing one can be deleted.
2. Use an SWD enabled LVDS cable with the chosen RealView ICE unit.

Problems installing USB drivers under Microsoft Windows 64-bit operating systems

When installing RealView ICE under Microsoft Windows 64-bit operating systems the installation of the USB drivers may fail, resulting in errors being shown in the installation log. It is possible to install the USB drivers manually using Windows Device Manager as follows:

1. Connect RealView ICE via USB, and apply power
2. Open Windows Device Manager by holding down the Windows key and pressing Break, and selecting "Device Manager" from the dialog
3. Select "RealView ICE" from the "Other Devices" section, and choose "Update Driver Software" from the context menu
4. Follow the on-screen instructions, using "Browse my computer for driver software" to navigate to the driver location <install root>\RVI\Drivers\usb_drivers\1.5
5. When prompted that the driver is unsigned, select "Install this driver anyway"

If installing DSTREAM, select "DSTREAM" from the "Other Devices" section of the Device Manager.

Further support information

The latest RealView ICE knowledge base articles can be found on the ARM web site at http://infocenter.arm.com/help/topic/com.arm.doc.faqs/ki9msU6jbMfpa7.html

Third party notices

University of California, Berkeley

This product includes software developed by the University of California, Berkeley and its contributors. The full copyright notice is restated below.

Copyright (c) 1992, 1993 The Regents of the University of California. All rights reserved.

This code is derived from software contributed to Berkeley by Christos Zoulas of Cornell University.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
   • This product includes software developed by the University of California, Berkeley and its contributors.
4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Apache

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

Boost

Elements of RealView ICE software use the Boost portable C++ source libraries. For more information on Boost see http://www.boost.org

The Boost Software License is reproduced here.

Boost Software License - Version 1.0 - August 17th, 2003

Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:

The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

bsdiff/bspatch 4.2

The installer contains code derived from bsdiff/bspatch 4.2, Copyright 2003 Colin Percival. This code comes with the following disclaimer:

NO WARRANTY. THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT, EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Copyright ARM Limited 2010