Solvline LemonIDE Ver 1.0e - Manual (Page 37)

LemonIDE TM User’s Guide
5.6 Creating a Firmware Image
Application program which has been compiled and executed on the target (with the instructions of previous
chapters) will now be made into a firmware image to be loaded to the target. This chapter will outline the
process of creating a firmware image and loading it to its target.
5.6.1 Changing Makefile
Changes to Makefile will be made to make a firmware image.
Makefile resides under “Ramdisk”( /DK Source/ Ramdisk) which is registered as a project.
Version information, amount of Ramdisk to be used, application information to be copied can be configured in
Makefile.
Example below shows a newly created “hello” binary file which is included in Makefile (under “Ramdisk” project
under “ramdisk” directory) being added to firmware image file.
Note
DK Source is distributed in Linux compatible format.
Thus some commands in Makefile may not be recognized in Windows environment. In such
cases, add .exe to unrecognized utilities in Makefile as shown below.
../tool/genext2fs Æ ../tool/genext2fs .exe
../tool/mkimage Æ ../tool/mkimage .exe
IMAGE=ramdisk
FW_NAME = eddy-fs-2.1.x.x.bin Æ Firmware image name and Version info
FIRMWARE_DIR = ../firmware Æ Directory to store created firmware
## Check environments
#include ../Make.check
install:
#@echo "Making ramdisk image..."
#$(TOOL) -b 8192 -d root -D device_table.txt ramdisk
#../tool/genext2fs -U -b 5110 -d root -D device_table.txt ramdisk
#../tool/genext2fs -U -b 7158 -d root -D device_table.txt ramdisk
#../tool/mkcramfs -q -D device_table.txt root ramdisk
../tool/genext2fs.exe -U -b 10240 -d – N 1024 root -D device_table.txt ramdisk Æ Make size
of Ramdisk to 10,240 K and register the device of Eddy/dev as indicated on Devide_table.txt.
gzip -vf9 ramdisk
test -f ramdisk.gz
5-13