Solvline Eddy DK - Manual (Page 95)

Eddy DK Programmer Guide
95
Chapter 5. Creating Firmware
On the previous chapter, we explained how to make and compile application program with sample program. This
chapter introduces methods to create a firmware which permanently saves the application into the Eddy module and
apply it to hardware of Eddy.
5.1 How to Create a Firmware
Firmware image can be created on filesystem_2.x.x.x/ramdisk folder.
Modify ‚Makefile‛ on filesystem_2.x.x.x/ramdisk folder to create a firmware image.
Version info, required Ramdisk amount and desired application to copy can be set up on the ‚Makefile‛.
(NOTE)
Provided DK Sources are Linux based. Some commands are not executable on Windows
environment. To prevent this problem, a suffix, ‚exe‛, has to be added for some utilities after
file name as shown below.
../tool/genext2fs  ../tool/genext2fs .exe
../tool/mkimage  ../tool/mkimage .exe
IMAGE=ramdisk
FW_NAME =
eddy-fs-2.x.x.x.bin  Name and Version Info of Firmware Image
FIRMWARE_DIR = ../firmware
 Folder to store created firmware
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 -N 1024 -d 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
est -f ramdisk.gz
./tool/mkimage.exe -A arm -O linux -T ramdisk -C gzip -a 0 -e 0 -n $(FW_NAME) -d ./ramdisk.gz
$(FW_NAME)
test -f $(FW_NAME)
mv $(FW_NAME) $(FIRMWARE_DIR)/
release:
 Register the desired application to the folder for copying to Eddy
cp -f ../src/Eddy_APPs/hello_world root/sbin
cp -f ../src/Eddy_APPs/eddy root/sbin