[Warning li2040] "./uclinux-2008r1-rc8.ldf":690 Due to memory fragmentation, output section '.init' in processor 'p0' was mapped discontinuously.
Use FORCE_CONTIGUITY command to ensure that output section is mapped continuously.
Use NO_FORCE_CONTIGUITY command if contiguity does not matter in this output section.
For most mapping operations, code and data from an object file are mapped contiguously, and input sections are mapped in the order specified inside the output section. If you have mapped an object into a location that causes a fragmentation of memory, the linker may map an object into the gap in such a way that code or data is no longer contiguous. Because of the fragmentation, the linker may also place input sections into memory in an order that is different from the order in which they appear in the output section. The linker warns that the mapping is not contiguous.
An additional (and probably more common) case of non-contiguous placement is when the sections are not mapped in the order specified in the LDF. Such a case might have nothing to do with internal fragmentation.
How to Fix
The LDF command FORCE_CONTIGUITY forces the linker to keep the variables contiguous. Using the FORCE_CONTIGUITY command may result in unused space in the output section.
You can indicate that it is not important that code and data objects are contiguous by using the LDF command NO_FORCE_CONTIGUITY. In the first example above, if the LDF file contained the NO_FORCE_CONTIGUITY command, the linker would not issue the warning.
If contiguous placement is not important in any of the output section, disable the warning by using the -w2040 command-line switch.
___init_begin = .;
. = (. + 4095) / 4096 * 4096;
__sinittext = .;
__einittext = .;
} > MEM_SDRAM