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 at beta status:
The following features are deprecated and might be removed in a future release:
Information about the full set of target platforms supported by DS-5 can be found on http://ds.arm.com/developer-resources/supported-devices/.
The list of changes in this and previous releases can be found on http://ds.arm.com/developer-resources/ds-5-development-studio-changelog/.
Visit the DS-5 web resources at http://ds.arm.com 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://ds.arm.com/developer-resources/ds-5-technical-support/ 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 requires a minimum specification of computer with a dual core 2GHz processor (or equivalent) and 2GB of RAM. 4GB or more of RAM is recommended to improve performance when debugging large images, or when using the simulation models. A full installation requires approximately 1.5GB of hard disk space. A minimum screen resolution of 1024x768 is required.
DS-5 is supported on the following host platforms and service packs:
DS-5 Ultimate Edition, including ARM Compiler 6, is supported on 64-bit host platforms only.
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/).
DS-5 can co-exist with the earlier ARM RVDS toolchain provided that they are installed into separate directories.
Android and ARM Linux application debug require gdbserver be available on your target. Depending on your chosen connection type, DS-5 Debugger might be able to copy gdbserver to the target for you, but otherwise you must copy it yourself. 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/gdbserver 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.
Linux application rewind requires undodb-server to be available on your target. DS-5 Debugger copies undodb-server to the target for you in the Download and Debug connection type, but for all other connection types you must copy it yourself. The undodb-server binary can be found in the <installdir>/arm/undodb/linux directory within your installation. Application rewind does not follow forked processes or allow modification of register values.
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, RVI, ULINKpro and ULINKpro D debug units allow connection to physical hardware targets. VSTREAM allows connection to RTL simulators and hardware emulators. ARMv8 bare-metal debugging is only supported when using DSTREAM and VSTREAM.
The minimum supported firmware version for DSTREAM, RVI and VSTREAM is 4.18.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.
Separate installable products are provided for 32-bit and 64-bit Linux. Although you can install the 32-bit product on 64-bit Linux, it is recommended to install the 64-bit product instead. The 64-bit product is for use on 64-bit Linux only, and is capable of processing larger data sets and suffers from fewer operating system compatibility issues than the 32-bit product.
To install DS-5 on Linux, run (not source) install.sh and follow the on-screen instructions. The installer unpacks DS-5 into your chosen directory, and optionally installs device drivers and desktop shortcuts. 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 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. The ARM Knowledgebase contains further information about the required DS-5 dependencies: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.faqs/ka14522.html.
The installer includes device drivers to allow USB connection to DSTREAM, RVI, ULINKpro and ULINKpro D 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.
Separate installable products are provided for 32-bit and 64-bit Windows. Although you can install the 32-bit product on 64-bit Windows, it is recommended to install the 64-bit product instead. The 64-bit product is for use on 64-bit Windows only, and is capable of processing larger data sets than the 32-bit product.
To install DS-5 on Windows, run setup.exe and follow the on-screen instructions. 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, ULINKpro, ULINKpro D and Energy Probe hardware units. 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.
After installation, you can start Eclipse for DS-5, which includes C/C++ project management, DS-5 Debugger, ARM Streamline Performance Analyzer, examples and documentation from the 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. Note: to use ARM Compiler 6 you must use <installdir>/bin/suite_exec_ac6 <shell> instead.
On Windows the Start menu contains DS-5 Command Prompt. This console is preconfigured with the bin directory added to the PATH environment variable. Note: to use ARM Compiler 6 you must use ARM Compiler 6 Command Prompt instead.
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 find further instructions on installation, licensing and tutorials on-line at: http://ds.arm.com/developer-resources/tutorials/working-with-arm-ds-5/.
You must obtain a valid license before using DS-5.
You can use the License Manager dialog in Eclipse for DS-5 to obtain and install node-locked licenses on both Windows and Linux. You can open this dialog by selecting ARM License Manager in the Eclipse for DS-5 Help menu. You must also select a toolkit. The toolkit identifies which specific license you are using in the event that you have multiple licenses installed.
Alternatively, floating and commercial (paid-for) node-locked licenses can be obtained and installed manually. Further instructions on this can be found in the ARM DS-5 License Management Guide document in the <installdir>/documents directory.
When the license and toolkit are configured within Eclipse then all license managed components will pick up the license and toolkit settings correctly, both within Eclipse and within the provided DS-5 Command Prompt (Windows) or suite_exec shell (Linux). If you use a different console then you must configure the tools manually. To do this set the environment variable ARMLMD_LICENSE_FILE to point at your license file, and ensure that the license managed compilation tools (armcc, armasm, armlink and fromelf) are passed the option --tool_variant=<toolkit> on each invocation. The argument to tool_variant is the type of license to use and corresponds to the prefix used by the license features in your license file up to the first '_' character. For example, if your license file contains a feature named "ds5eval_compiler5" then you must pass the compilation tools the --tool_variant=ds5eval option. Failure to set either the license location or the toolkit can result in errors reporting a failure to checkout a license, for example "Cannot obtain license for..."
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.
DS-5 is supplied with two versions of ARM Compiler for compiling bare-metal applications. ARM Compiler 5 supports all ARM architectures except ARMv8. ARM Compiler 6 supports architecture ARMv8 as well as alpha support for architecture ARMv7-A. Use of ARMv8 requires a DS-5 Ultimate Edition license.
Both versions of ARM Compiler are license managed and not all editions of DS-5 include a license for it. If your edition of DS-5 does not include a license for ARM Compiler, or you are developing applications for a non-bare-metal case, such as Linux applications, then you might require the use of a third-party compiler.
Linaro GCC Toolchain 4.8-2014.04 is provided for Linux applications and Linux kernel development targeting the AArch32 architecture. Other releases of GCC are available at https://launchpad.net/linaro-toolchain-binaries/.
To uninstall DS-5 on Windows, use Add or Remove Programs in Control Panel, select ARM DS-5 and click the Remove button.
To uninstall DS-5 on Linux, run remove_menus_for_ARM_DS-5.sh in the root directory of your installation to remove desktop menu entries, and then 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.
The following known issues and limitations exist in this release:
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.