Solvline Eddy DK Ver 2.20 - Manual (Page 40)

Chapter 5. Creating Firmware
test -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)/
cfg:
../tool/mkfs.jffs2.exe -q -l -o $(CONFIG_NAME) -d flash -p – f Æ Create image of Eddy’s
initial execution configuration file residing under Flash folder.
test -f $(CONFIG_NAME)
mv $(CONFIG_NAME) $(FIRMWARE_DIR)/
release: Æ Register application to be copied to Eddy so it can be copied to proper directory
cp -f ../src/busybox-1.5.0/busybox root/bin
cp -f ../src/dropbear-0.50/dropbear root/usr/local/sbin
cp -f ../src/dropbear-0.50/dropbearkey root/usr/local/sbin
cp -f ../src/ethtool-6/ethtool root/usr/local/sbin
cp -f ../src/thttpd-2.25b/thttpd root/usr/local/sbin
cp -f ../src/net-snmp-5.4.1/agent/snmpd root/usr/local/sbin
cp -f ../src/net-snmp-5.4.1/agent/snmpd.conf root/etc
cp -f ../src/netkit-ftp-0.18/ftp/ftp root/usr/local/bin
.
Makefile options are as follows.
Make release ; copy module in release to ramdisk area
Make cfg ; create firmware image of Eddy enviromental files in ramdisk/flash
Make install ; create a firmware image of Eddy’s Filesystem
If changes to Makefile are complete, use “make install” command to create firmware image.
Firmware will be created in “FIRMWARE_DIR” directory defined in Makefile.
On Windows, use cmd(command prompt) to carry out procedures explained on Linux.
5-3