ARM® Development Studio 5 (DS-5™) is the toolkit of choice for software developers who want to fully realize the benefits of the ARM Architecture. The DS-5 installation contains:
This is a summary of the new features and other major changes in this release:
The following features are deprecated and might be removed in a future release:
The following features are removed from this release:
Information about the full set of target platforms supported by DS-5 can be found on http://www.arm.com/products/tools/software-tools/ds-5/supported-platforms.php.
The list of changes in this and previous releases can be found on http://www.arm.com/products/tools/software-tools/ds-5/change-log.php.http://www.arm.com/ds-5 to find to tutorials, knowledgebase articles, and any software updates that are available.
Technical support for DS-5 should be obtained from your supplier. Support issues can be raised directly with ARM at https://silver.arm.com/ (requires registration). Where appropriate, please mention the build of DS-5 that you are using, which can be found at the top of these release notes beneath the title. Refer to http://www.arm.com/support/obtaining-support/index.html for further information on obtaining support.
Queries and support issues relating to DS-5 can also be raised on ARM's public forums at: http://forums.arm.com/.
DS-5 is supported (except where specified) on both 32-bit and 64-bit versions of the following host platforms (and service packs):
Android and ARM Linux application debug require gdbserver to be available on your target. The recommended version of gdbserver is 7.0 or higher. gdbserver executables, built for Android and ARM Linux, that are compatible with DS-5 Debugger are provided in the <installdir>/arm directory. gdbserver executables for Android have been tested against Android Virtual Devices Froyo-v2.2 to ICS-v4.0.
DS-5 Debugger is unable to provide reliable multi-threaded debug support with gdbserver versions prior to 6.8.
DS-5 support for Android and Linux depends upon infrastructure and features introduced in specific kernel versions:
ARM Linux kernel and bare-metal debugging require the use of additional tools (not supplied with DS-5) to connect to your target system. DSTREAM and RVI debug units allow connection to physical hardware targets. VSTREAM allows connection to RTL simulators and hardware emulators.
The minimum supported firmware version for DSTREAM, RVI and VSTREAM is 4.11.0. For DSTREAM and RVI it is recommended that you use the supplied debug hardware update tool to check that you are using the latest firmware and to update it if necessary. Updated firmware is available in the <installdir>/sw/debughw/firmware directory. The firmware for VSTREAM is delivered as part of the VSTREAM software, so you must obtain and install a newer version of this product if the firmware version is too old.
DS-5 can co-exist with the earlier ARM RVDS toolchain provided that they are installed into separate directories.
All line drawings in the online help use SVG format. To view these graphics, your browser must support the SVG format. If your browser does not have native support for SVG, you must install an appropriate plug-in such as the Adobe SVG Viewer (http://www.adobe.com/svg/viewer/install/).
install_x86_32.sh is for use on 32-bit Linux host platforms. It also supports 64-bit Linux host platforms, but it is recommended that you use install_x86_64.sh instead.
install_x86_64.sh is for use on 64-bit Linux host platforms only, and is the recommended installer to use on these platforms. The 64-bit tools that are installed are capable of processing larger data sets and suffer from fewer operating system compatibility issues than those tools in the 32-bit installation.
The tools installed by both 32-bit and 64-bit installers have dependencies on 32-bit system libraries. You must ensure that 32-bit compatibility libraries are installed when using DS-5 on 64-bit Linux host platforms. DS-5 tools might fail to run or report errors about missing libraries if 32-bit compatibility libraries are not installed.
Additionally, several known issues exist when running DS-5 32-bit binaries on 64-bit Ubuntu host platforms. The ARM Knowledgebase contains instructions that might help you to overcome these issues: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.faqs/ka14522.html.
It is recommended that you delete any previous release of DS-5 before installing this release. The installer guides you through this process. Alternatively you can install this release into a different directory.
The installer includes device drivers to allow USB connection to DSTREAM and RVI debug hardware units. It is recommended to install these drivers if you intend to use these features. Installation of these drivers requires that you run the installer with root privileges. If you do not run the installer with root privileges or choose not to install these drivers, then you can still install them after installation by running the <installdir>/run_post_install_for_ARM_DS-5.sh script with root privileges. The installer creates a desktop menu using the freedesktop.org menu system on supported Linux platforms.
If you have an earlier release of DS-5 already installed, then you can install this release on top of it and an upgrade is performed.
During installation you might be prompted to install device drivers. These drivers are to allow USB connections to DSTREAM, RVI and Energy Probe hardware units, and to support networking for the simulation models. It is recommended to install these drivers if you intend to use these features. You might receive warnings such as "Windows can't verify the publisher of this driver software" or "The software you are installing has not passed Windows Logo testing". You can safely ignore these warnings and continue with installation.ARM DS-5 -> Eclipse for DS-5 entry in your desktop menu. Eclipse for DS-5 and other supplied tools can also be found within the <installdir>/bin directory.
Portions of DS-5 are license managed and you must install a license before using them. See the Obtaining and Installing Your License section of these release notes below for further information about this.
The installer does not modify any environment variables on your system. To run the tools more easily from a console you can manually add the <installdir>/bin directory to your PATH environment variable. You should be aware that DS-5 includes copies of gcc and make that might behave differently from any copies that are installed elsewhere on your system. For this reason, if you modify your PATH environment variable, it is recommended that you do this locally within a console rather than globally for your entire system. See your operating system documentation for further information on setting environment variables.
On Linux you can run <installdir>/bin/suite_exec <shell> to open a shell with the PATH environment variable correctly configured. Run this tool with no arguments for more help.
On Windows the Start menu contains DS-5 Command Prompt. This console is preconfigured with the bin directory added to the PATH environment variable.
Further information on using DS-5 can be found in the on-line help within Eclipse for DS-5. To access the on-line help, start Eclipse for DS-5 and select Help -> Help Contents. The main documentation for DS-5 can be found under the DS-5 Documentation section in the contents.
Separate documentation is provided for the supplied examples in the <installdir>/examples/docs/index.html document, which is also linked to from the Examples Index menu entry in the ARM DS-5 Windows Start menu.
You can use the License Manager dialog in Eclipse for DS-5 to obtain and install licenses on both Windows and Linux. You can open this dialog by selecting ARM License Manager in the Eclipse for DS-5 Help menu.
Alternatively you can obtain and install your license manually. Further instructions on this can be found in the ARM DS-5 License Management Guide document in the <installdir>/documents directory.
Consult the License Management FAQ at http://infocenter.arm.com/help/topic/com.arm.doc.faqs/kiLwjCHu92xQmR.html for more assistance with the installation of your license.
Contact firstname.lastname@example.org if you need additional help with registering or obtaining your license. Please provide your serial number, a detailed description of the problem, and your ARM web licensing system username and password.
If you are installing a floating license server then the installation contains binaries for FlexNet 11.x. It is recommended that you use 11.x binaries on your license server in order to match the version of FlexNet that is used within the DS-5 tools.
For information on installing device drivers for USB-Blaster and USB-Blaster II please consult your Altera Quartus tools documentation.
The UEFI source code and Jython scripts are available for download from SourceForge: http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=ArmPlatformPkg/ArmVExpressPkg
For more information, see this blog: http://blogs.arm.com/software-enablement/884-uefi-debug-made-easy/Add or Remove Programs in Control Panel, select ARM DS-5 and click the Remove button.
To uninstall DS-5 on Linux, simply delete the installation directory.
On both Windows and Linux, some per-user configuration is stored outside of the installation directory, which you might optionally choose to delete. For Windows these files are stored in %APPDATA%\ARM\DS-5. For Linux these files are stored in $HOME/.ds-5.
Streamline Performance Analyzer might not fully process shared library symbols if the "soname" is not
Workaround: Streamline Performance Analyzer expects the shared library "soname" (lib<name>.so.<v>) when loading symbols for profiler analysis. If you provide the real name (lib<name>.so.<v>.<m>) of the shared library, you might find that only a subset of symbols are matched from the shared library. In order to correct the issue, you must specify the same library using the "soname". This might involve copying, renaming or symlinking to the library.
When setting up an "APK native library debug" configuration for Android, the
"Load symbols from file" field in the Files tab usually fills in automatically. However,
this field can fail to update if you modify the "Project directory" field before the
update completes. [SDDEBUG-11056]
Workaround: Wait for the "Load symbols from file" field to update before editing the "Project directory" field. This can take several seconds. Alternatively, edit the "Load symbols from file" field manually.
Memory fill is not supported on AHB and APB address spaces when the size of the data is
not 32-bits. [SDDEBUG-11633]
Workaround: Perform a memory fill using 32-bit data, with individual memory writes at the start and end of the fill region to cover any remaining non-32-bit aligned bytes. Alternatively, use the debugger's jython scripting interface to perform repeated memory writes instead of performing a fill operation; this might be slow if the region to be filled is large. Alternatively, create a file containing the desired fill data and use the restore command to write this to memory.
Tooltips in the source code editor showing the value of variables and expressions are
disabled in this release. [SDDEBUG-12821]
Workaround: Right-click on variables or expressions that you want to view and select Inspect from the context menu. Alternatively, enter the variable or register into the Expressions view.
Semihosting settings when using RTSM targets are now configured as arguments to the
model instead of on the debugger command line. [SDDEBUG-12621]
Workaround: Bare metal debug of RTSM targets now uses the RTSM's semihosting implementation with input/output now performed via the Target Console view instead of the App Console. This is more efficient and enables correct semihosting behaviour for TrustZone applications and Cortex-M models. However, semihosting parameters including stack/heap settings and working directory for file I/O must now be specified as parameters to the model. These parameters are set in the Debug Configurations dialog. The parameters are specific to each model, but usually take the form of -C coretile.core.semihosting-XXXX or -C cluster.cpu0.semihosting-XXXX. Multi-core models have semihosting parameters for each core. The full list of parameters can be obtained with the --list-params option to the model.
To re-enable DS-5 Debugger's semihosting support for RTSM connections, the model's semihosting must be disabled by passing appropriate command line parameters. For the Cortex-A8 RTSM platform, add the following to the Model Parameters entry in the Debug Configurations dialog:
For the RTSM_VE_Cortex-A9x4 platform, the following parameters should be set:
-C cluster.cpu0.semihosting-enable=0 -C cluster.cpu1.semihosting-enable=0 -C cluster.cpu2.semihosting-enable=0 -C cluster.cpu3.semihosting-enable=0
The corresponding parameters for other models can be obtained using the model's --list-params option.
Problem: Eclipse fails to start and reports "cannot restore segment
prot after reloc: Permission denied" [SDDEBUG-13327]
Workaround: This error occurs because some of the shared libraries used by the applications require text relocation, but the Security-enhanced Linux (SELinux) policy on your machine prohibits this. To work around this, change the SELinux policy for your DS-5 applications and shared libraries to allow text relocation. This can be achieved with the following command, run under a super user account:
chcon -R -t texrel_shlib_t "<installdir>"
Problem: Eclipse fails to start and reports "JVM terminated" or
outputs a stack backtrace. [SDDEBUG-6433]
Workaround: This problem is often caused by heap settings for Eclipse that are not suitable for the computer that you are running it on. To fix this you must edit <installdir>/sw/eclipse/eclipse.ini to supply alternative heap settings. The following knowledgebase article provides detailed instructions on making this change: http://infocenter.arm.com/help/topic/com.arm.doc.faqs/ka14185.html.