Comtrol eCos - Manual (Page 337)

Chapter 11. Porting Guide
$(OBJCOPY) -O srec $< $(@:.bin=.srec)
$(OBJCOPY) -O binary $< $@
}
}
}
The important part here is the make command in the CYGBLD_BUILD_REDBOOT_BIN option which emits makefile
commands to translate the .elf file generated by the link phase into both a binary file and an S-Record file. If a
different format is required by a PROM programmer or ROM monitor, then different output formats would need to
be generated here.
Platform Memory Layout
The platform memory layout is defined using the Memory Configuration Window in the Configuration Tool.
Note: If you do not have access to a Windows machine, you can hand edit the .h and .ldi files to match the
properties of your platform. If you want to contribute your port back to the eCos community, ask someone on
the list to make proper memory map files for you.
Layout Files
The memory configuration details are saved in three files:
.mlt
This is the Configuration Tool save-file. It is only used by the Configuration Tool.
.ldi
This is the linker script fragment. It defines the memory and location of sections by way of macros defined in
the architecture or variant linker script.
.h
This file describes some of the memory region details as C macros, allowing eCos or the application adapt the
memory layout of a specific configuration.
These three files are generated for each startup-type, since the memory details usually differ.
Reserved Regions
Some areas of the memory space are reserved for specific purposes, making room for exception vectors and various
tables. RAM startup configurations also need to reserve some space at the bottom of the memory map for the ROM
monitor.
These reserved areas are named with the prefix "reserved_" which is handled specially by the Configuration Tool:
instead of referring to a linker macro, the start of the area is labeled and a gap left in the memory map.
233