ARM Technical Support Knowledge Articles

What does "Error L6000U: out of memory" mean?

Applies to: ARM Developer Suite (ADS), RealView Compilation Tools (RVCT) for BREW, RealView Developer Kit (RVDK) for OKI, RealView Developer Kit (RVDK) for ST, RealView Developer Kit for XScale (RVXDK), RealView Development Suite (RVDS)

This error occurs because the linker does not have enough memory to link your target object. This is not common, but could be triggered for a number of reasons.  For example, this may occur when linking very large objects/libraries together, or if you are generating a large amount of debug information, or if you have very large regions defined in your scatter-file. In these cases, your workstation may run out of (virtual) memory.

This can also occur because of the use of FIXED in a scatter file. FIXED forces an execution region to become a "root region" in ROM at a fixed address. The linker may need to add padding bytes between the end of the previous execution region and the FIXED one, to generate the ROM image. The linker may run out of memory if huge amounts of padding are added where the FIXED region's address is far away from the end of the execution region. The link step might succeed if the gap is reduced.

While the linker can generate images of almost any size, it will require a larger amount of memory in order to run and finish the link. There are several suggestions for improving your performance:

  1. Shut down all nonessential applications and processes when you are linking

    For example, if you are running under CodeWarrior, try running your linker from the command line, or exiting and restarting CodeWarrior between builds. Minimizing the project window will also help.

  2. Use --no_debug command with your linker

    This command will tell the linker to create the object without including any debug information. You cannot carry out source level debugging with that option, however. Note this option is -nodebug for ADS 1.2 and earlier.

  3. Reduce debug information

    If you do not want to use the --no_debug switch (2), there are many ways you can try and reduce debug information.  Please see the FAQ: How can I reduce the amount of debug data in my image? for further information.

  4. Partial linking

    You could also use partial linking to split the link stage over a few smaller operations. Doing so will also stop duplication of the object files in memory in the final link.

If you are still experiencing the same problem, it is recommended that you add some more memory to the host computer.

Article last edited on: 2009-08-18 15:56:30

Rate this article

[Bad]
|
|
[Good]
Disagree? Move your mouse over the bar and click

Did you find this article helpful? Yes No

How can we improve this article?

Link to this article
Copyright © 2008-9 ARM Limited. All rights reserved. External (Open), Non-Confidential