Most embedded applications are initially developed in a prototype
environment with resources that differ from those available
in the final product. As such, it is important to consider the
processes that enable your application to run on your target
The aim of this application note is to examine the processes
involved in moving an embedded application from one that relies
on the facilities of the development/debugging environment to
a system that runs standalone on target hardware. In particular,
this document illustrates some of the features of the ARM Developer
Suite (ADS) v1.2, and suggests how they might be effectively
used in this regard.
What is covered in this application note?
With ADS, several issues must be considered to move from an
“out-of-the-box” build to a standalone embedded application:
- C library use of hardware
- Some C library functionality executes by using debug environment
resources. If used, this functionality must be re-implemented
to make use of target hardware.
- ADS has no inherent knowledge of the memory map of any
given target. The image memory map must
- be tailored to the memory layout of the target hardware.
- An embedded application must perform some initialization
before the main application can be run. A complete initialization
sequence requires user-implemented code as well as ADS C library
This application note addresses each of the above issues. Also,
some further considerations regarding the image memory map are