Eddy DK Programmer Guide
94
cp -f ../src/Eddy_APPs/com_redirect root/sbin
cp -f ../src/Eddy_APPs/tcp_server root/sbin
cp -f ../src/Eddy_APPs/tcp_client root/sbin
cp -f ../src/Eddy_APPs/tcp_broadcast root/sbin
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/net-snmp-5.4.1/agent/snmpd
root/usr/local/sbin
List of task on the “Makefile” options are as follows;
Make release
; Copy modules registered on the release to Ramdisk area.
Make install
; Create a Filesystem to a firmware image for using on Eddy.
If the modification of “Makefile” is completed, execute “make release and “make install” in turns and create a
Firmware image.
Created firmware is stored on the “FIRMWARE_DIR” directory stated on the “Makefile”.
On Windows, use cmd(command prompt) to carry out procedures explained on Linux.
[shlee@localhost ramdisk]$
make release
.
.
[shlee@localhost ramdisk]$
make install
.
.
[shlee@localhost ramdisk]$ ls ../firmware
-rwxr-xr-x -----------------------------------------eddy-bl-2.x.x.x.bin
-rwxr-xr-x -----------------------------------------eddy-bs-2.x.x.x.bin
-rwxr-xr-x -----------------------------------------eddy-os-2.x.x.x.bin
-rwxr-xr-x -----------------------------------------
eddy-fs-2.x.x.x.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.
[shlee@localhost ramdisk]$
make release
.
.
[shlee@localhost ramdisk]$
make install
.
.
