The DS-5 web resources include a graphical quick-start guide and detailed instructions to get started with an OMAP3 Beagle Board. It also contains links to the forums for general discussion of DS-5, to the knowledgebase where hints, tips and workarounds are documented, and to any software updates that are provided during the trial period.
Feedback on DS-5, including bug reports and suggestions for improvement, can be emailed to feedback-ds5@arm.com. 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.
DS-5 is supported on the following platforms and service packs:
All tools support both 32-bit and 64-bit versions of these operating systems where available.
Android and ARM Linux application debug require gdbserver to be available on your target. The recommended version of gdbserver is 6.8. gdbserver 6.8 executables built for ARMv4T, ARMv5T and Thumb2 architectures for ARM Linux that are compatible with DS-5 Debugger are provided in the <installdir>/arm directory. DS-5 Debugger is unable to provide reliable multi-threaded debug support with gdbserver versions prior to 6.8.
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 plugin such as the Adobe SVG Viewer (http://www.adobe.com/svg/viewer/install/).
To install DS-5, run setup.exe on Windows or run (not source) install.sh on Linux and follow the on-screen instructions.
After installation, all tools can be found within the <installdir>/bin directory, for example:
The installer does not modify any environment variables on your system. You may optionally wish to add the <installdir>/bin directory to your PATH environment variable, so that you can run the tools more easily from a console. To do this consult the documentation for your operating system or console.
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 the tools can be found in the on-line help within Eclipse. To access the on-line help, start Eclipse and select Help Contents from the Help menu. 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/index.html document, which is also linked to from the Examples Index entry in the Keil DS-5 Windows Start menu.
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%\Keil\DS-5 and also in %USERPROFILE%\.ds-5, and for Linux they are in $HOME/.ds-5.
Problem: Some applications may fail to run on Linux when Security
Enhanced Linux (SELinux) is enabled, as is the case by default on Red Hat
Enterprise 5 and Fedora 10 systems, for example. When the failure occurs
you may see an error message stating "cannot restore segment prot after
reloc: Permission denied" when trying to run an application. This error
occurs because some of the shared libraries used by the applications require
text relocation, but the SELinux policy on your computer prohibits this.
[DE710068]
Workaround: Change the SELinux policy for your applications and shared
libraries to allow text relocation. This can be done by opening a super user
account and modifying the execution context for the installation directory
with the command: chcon -R -t texrel_shlib_t <installdir>
Problem: DS-5 Debugger is slow to load images and shared objects
containing large quantities of debug data and may run out of memory.
Workaround: Restrict the quantity of debug data by enabling debug
data generation in the compiler only for those source files that you wish
to debug.
Workaround: Restrict the quantity of debug data by stripping the
images and shared objects that you do not need to debug.
Workaround: When debugging Linux applications, disable autoloading
of shared object symbols using the set auto-solib-add false
command, and then load symbols for only those shared objects that you
want to debug using the sharedlibrary <libname> command.
Workaround: The memory available to the debugger is reduced when
running within Eclipse, because Eclipse needs some memory for itself. Using
the command line debugger from a console allows slightly larger images to be
loaded.
Workaround: Try increasing the size of the Java™ heap. Instructions
are given below in the release notes for Eclipse on how to change the
maximum heap size, but in this case you should try increasing the heap size
rather than decreasing it. You will need to experiment to find a heap size
that works on your computer.
Problem: Support for C++ is limited. There is no ability to mangle
and demangle C++ symbols.
Workaround: Refer to C++ symbols using their fully mangled name.
Problem: DS-5 Debugger does not support big endian targets. [DE727014]
Workaround: There is no workaround. Support for big endian targets
will be added in a future release.
Problem: DS-5 Debugger does not support accessing NEON registers.
[SDDEBUG-5674]
Workaround: There is no workaround. Support for NEON registers will
be added in a future release.
Problem: DS-5 Debugger and Eclipse IDE fail to start, reporting
the error "JVM terminated".
Workaround:
This problem is often caused by a lack of memory to run the application.
Both DS-5 Debugger and Eclipse IDE are implemented using Java™ technology
and the virtual machine needs to allocate a large contiguous area of virtual
address space for the heap. The maximum heap size is configured to 768MB
but some computers are unable to allocate this amount of memory. To
workaround this you can try reducing the maximum heap size by editing
the following files:
Problem: A number of Eclipse plug-ins, including the Scatter File Editor,
ELF Content Editor and Target Register Editor are not installed, even though the
documentation refers to them. [DE727382]
Workaround: These plug-ins are not included in the trial.
Problem: The warning "Error launching external scanner info
generator" appears in the Problems view when building using the DS-5 GCC
toolchain. [SDAPPS-46]
Workaround: The scanner is used by Eclipse to index your project to
provide source navigation features and content assist. Eclipse tries to
invoke gcc in order to determine the location of the system includes,
but in DS-5 the name of the gcc executable is actually
arm-none-linux-gnueabi-gcc. To correct the toolname:
Problem: When cleaning an Eclipse project using the DS-5 GCC toolchain
on Windows the makefile tries to invoke rm. This program cannot be
found, so the clean operation fails. [SDAPPS-48]
Workaround: Manually delete the object files and executables belonging to
your project to force them to rebuild correctly. You can delete these files in
Eclipse as follows: