Solvline LemonIDE Ver 1.0c - Manual (Page 37)

LemonIDE TM
Chapter 5. Using IDE
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
../tool/mkfs.jffs2 Æ ../tool/mkfs.jffs2 .exe
IMAGE=ramdisk
FW_NAME = eddy-fs-20a.bin Æ Name & version of Firmware Image
CONFIG_NAME = eddy-cf-20a.bin Æ Environmental information on Eddy’s default
execution status
FIRMWARE_DIR = ../firmware Æ Directory where firmware image is to be stored
## Check environments
#include ../Make.check
config:
@echo -n "Checking ramdisk skeleton files..."
@if [ ! -f "$(ROOT_FS_SKEL)" ] ; then \
echo "fail"; \
exit 0;\
fi
@echo "ok"; \
5-13