E.3.6. Rebuilding the Boot Monitor or platform library

All firmware components are built using either RVDS running under either Windows or Unix/Linux:

After rebuilding the Boot Monitor, load it into NOR flash, see Loading Boot Monitor into NOR flash.

After rebuilding the platform library, you can link platform.a from the target build subdirectories with your application (see Building an application with the platform library).

Build options

You can specify the following build options after the make command:

  • BIG_ENDIAN=1/0, defining image endianness (Default 0, little endian)

  • THUMB=1/0, defining image state (Default 0, ARM)

  • DEBUG=1/0, defining optimization level (Default 0, optimized code)

  • VFP=1/0, defines VFP support (Default 0, no VFP support).


The Boot Monitor must be built as a simple image. Scatter loading is not supported.

The build options define the subdirectory in the Builds directory that contains the compile and link output:

<Debug>_<State>_<Endianness>_Endian + further component specific options

For example, Release_ARM_Little_Endian or Debug_Thumb_Big_Endian.

The makefile creates a directory called Builds if it is not already present. The Builds directory contains subdirectories for the specified make options (for example, Debug_ARM_Little_Endian). To delete the objects and images for all targets and delete the Builds directory, type make clean all.

Copyright © 2008-2011 ARM Limited. All rights reserved.ARM DUI 0417D