Moxa Technologies DA-660 Series User manual

DA-660-8/16-LX User’s Manual
Seventh Edition, February 2009
www.moxa.com/product
©2009 Moxa Inc. All rights reserved.
Reproduction without permission is prohibited.

DA-660-8/16-LX User’s Manual
The software described in this manual is furnished under a license agreement and may be used only in
accordance with the terms of that agreement.
Copyright Notice
Copyright ©2009 Moxa Inc
All rights reserved.
Reproduction without permission is prohibited.
Trademarks
MOXA is a registered trademark of Moxa Inc.
All other trademarks or registered marks in this manual belong to their respective manufacturers.
Disclaimer
Information in this document is subject to change without notice and does not represent a commitment on the
part of Moxa.
Moxa provides this document “as is,” without warranty of any kind, either expressed or implied, including, but
not limited to, its particular purpose. Moxa reserves the right to make improvements and/or changes to this
manual, or to the products and/or the programs described in this manual, at any time.
Information provided in this manual is intended to be accurate and reliable. However, Moxa assumes no
responsibility for its use, or for any infringements on the rights of third parties that may result from its use.
This product might include unintentional technical or typographical errors. Changes are periodically made to the
information herein to correct such errors, and these changes are incorporated into new editions of the
publication.
Technical Support Contact Information
www.moxa.com/support
Moxa Americas:
Toll-free: 1-888-669-2872
Tel: [phone]
Fax: [phone]
Moxa China (Shanghai office):
Toll-free: 800-820-5036
Tel: [phone]
Fax: [phone]
Moxa Europe:
Tel: [phone]
Fax: [phone]
Moxa Asia-Pacific:
Tel: [phone]
Fax: [phone]

Table of Contents
Chapter 1 Introduction..................................................................................................1-1
Overview.................................................................................................................................. 1-2
Software Architecture .............................................................................................................. 1-2
Journaling Flash File System (JFFS2).......................................................................... 1-3
Software Package ......................................................................................................... 1-4
Chapter 2 Getting Started.............................................................................................2-1
Powering on the DA-660......................................................................................................... 2-2
Connecting the DA-660 to a PC .............................................................................................. 2-2
Serial Console............................................................................................................... 2-2
Telnet Console.............................................................................................................. 2-3
SSH Console................................................................................................................. 2-4
Configuring the Ethernet Interface .......................................................................................... 2-5
Modifying Network Settings with the Serial Console.................................................. 2-5
Modifying Network Settings over the Network............................................................ 2-6
Test Program—Developing Hello.c......................................................................................... 2-6
Installing the Tool Chain (Linux)................................................................................. 2-7
Checking the Flash Memory Space.............................................................................. 2-7
Compiling Hello.c ........................................................................................................ 2-8
Uploading and Running the “Hello” Program.............................................................. 2-8
Developing Your First Application .......................................................................................... 2-9
Testing Environment .................................................................................................... 2-9
Compiling tcps2.c......................................................................................................... 2-9
Uploading and Running the “tcps2-release” Program................................................ 2-10
Testing Procedure Summary....................................................................................... 2-13
Chapter 3 Managing Embedded Linux ........................................................................3-1
System Version Information..................................................................................................... 3-2
System Image Backup.............................................................................................................. 3-2
Upgrading the Firmware............................................................................................... 3-2
Loading Factory Defaults............................................................................................. 3-4
Enabling and Disabling Daemons............................................................................................ 3-4
Setting the Run-level ............................................................................................................... 3-6
Adjusting the System Time...................................................................................................... 3-7
Setting the Time Manually ........................................................................................... 3-7
NTP Client.................................................................................................................... 3-8
Updating the Time Automatically ................................................................................ 3-8
Cron—Daemon to Execute Scheduled Commands ................................................................. 3-9
Timezone Setting................................................................................................................... 3-10
Chapter 4 Managing Communications........................................................................4-1
Telnet / FTP ............................................................................................................................. 4-2
DNS ......................................................................................................................................... 4-2
Web Service—Apache............................................................................................................. 4-3
IPTABLES............................................................................................................................... 4-5
NAT.......................................................................................................................................... 4-9
NAT Example............................................................................................................... 4-9
Enabling NAT at Bootup............................................................................................ 4-10
Dial-up Service—PPP............................................................................................................ 4-10

PPPoE.................................................................................................................................... 4-13
NFS (Network File System)................................................................................................... 4-15
Setting up the DA-660 as a NFS Server ..................................................................... 4-15
Setting up the DA-660 as a NFS Client...................................................................... 4-16
Mail........................................................................................................................................ 4-17
SNMP .................................................................................................................................... 4-17
OpenVPN............................................................................................................................... 4-18
Chapter 5 Programmer’s Guide....................................................................................5-1
Flash Memory Map.................................................................................................................. 5-2
Linux Tool Chain Introduction................................................................................................. 5-2
Debugging with GDB..............................................................................................................5-3
Device API............................................................................................................................... 5-4
RTC (Real Time Clock)...........................................................................................................5-4
Buzzer...................................................................................................................................... 5-4
WDT (Watch Dog Timer) ........................................................................................................ 5-5
UART....................................................................................................................................... 5-9
LCM....................................................................................................................................... 5-10
KeyPad....................................................................................................................................5-11
Makefile Example...................................................................................................................5-11
Appendix A System Commands.....................................................................................A-1
Linux normal command utility collection............................................................................... A-1
File Manager................................................................................................................ A-1
Editor........................................................................................................................... A-1
Network....................................................................................................................... A-1
Process.........................................................................................................................A-2
Other............................................................................................................................ A-2
Moxa Special Utilities ................................................................................................. A-2

1
1
Chapter 1 Introduction
Welcome to the DA-660 RISC-based Communication Platforms. Features include RS-232/422/485
serial ports, and dual 10/100 Mbps Ethernet ports, making the DA-660 ideal for your embedded
applications.
The following topics are covered in this chapter:
Overview
Software Architecture
¾Journaling Flash File System (JFFS2)
¾Software Package

DA-660-8/16-LX User’s Manual Introduction
1-2
Overview
The DA-660 computer is ideal for embedded applications. This computer features a RISC CPU,
RAM memory, and communication ports that connect to RS-232/422/485 serial devices and dual
10/100 Mbps Ethernet.
The Da-660 computer uses an Intel XScale IXP-422 266 Mhz RISC CPU. Unlike the X86 CPU,
which uses a CISC design, the RISC architecture and modern semiconductor technology provide
this computer with a powerful computing engine and communication functions, but without
generating a lot of heat. Built-in 32 MB NOR Flash ROM and 128 MB SDRAM give you enough
memory to install your application software directly on the computer. In addition, dual LAN ports
are built right into the RISC CPU. The network capability, in combination with its control over
serial devices, makes the Da-660 an ideal communication platform for data acquisition and
industrial control applications.
DA-660’s pre-installed Linux operating system (OS) provides an open software operating system
for your software program development. Software written for desktop PCs can be easily ported to
the computer with a GNU cross compiler, without needing to modify the source code. The OS,
device drivers (e.g., Keypad, LCM, and Buzzer control) and your own applications, can all be
stored in the NOR Flash memory.
The DA-660 Linux Series (referred to as DA-660, or the target computer) comes in two models:
the DA-660-8-LX has 8 serial ports, and the DA-660-16-LX has 16 serial ports. Both models have
exactly the same software and hardware features.
Software Architecture
The Linux operating system that is pre-installed in the DA-660 follows standard Linux
architecture, making it easy to accept programs that follow the POSIX standard. Program porting
is done with the GNU Tool Chain provided by Moxa. In addition to Standard POSIXAPIs, device
drivers for the LCM, Buzzer and Keypad controls, and UART are also included in the Linux OS.
AP
API
Protocol
Stack
Device
Driver
Microkernel
User Application Daemon (Apache, Telnet, FTPD, SNMP)
Application Interface (POSIX, Socket, Secure Socket)
TCP, IP, UDP, CMP, ARP, HTTP, SNMP, SMTP
PCMCIA, CF, WLAN, USB, UART, RTC, LCM, Keypad
Memory control, Schedule, Process
RS-232/422/485, Ethernet, PCMCIA, CompactFlash, USB
File
System
Hardware
lenreKSO
The DA-660’s built-in Flash ROM is partitioned into Boot Loader, Linux Kernel, Mini Root
File System, and User Root File System partitions.

DA-660-8/16-LX User’s Manual Introduction
1-3
In order to prevent user applications from crashing the
Root File System, the DA-660 uses a specially designed
Mini File System with Protected Configuration for
emergency use. This Mini File System comes with serial
and Ethernet communication capability for users to load
the Factory Default Image file. The Mini File System
will only be activated if the boot loader fails to load the
User Root File System.
User AP
User Directory
(User Configuration) Mini Root File System Configuration
Linux Kernel & Root
HW
Boot Loader
To improve system reliability, the DA-660 has a built-in mechanism that prevents the system from
crashing. The procedure is as follows.
When the Linux kernel boots up, the kernel will mount the root file system, and then enable
services and daemons. During this time, the kernel will start searching for system configuration
parameters via rc or inittab.
Normally, the kernel uses the User Root File System to boot up the system. The Mini Root File
System is protected, and cannot be changed by the user, and thus provides a safe zone. The kernel
will only use the Mini Root File System when the User Root File System crashes.
For more information about the memory map and programming in DA-660, refer to Chapter 5,
Programmer’s Guide.
Journaling Flash File System (JFFS2)
The User Root File System in the flash memory is formatted with the Journaling Flash File
System (JFFS2). The formatting process places a compressed file system in the flash memory,
transparent to the user.
The Journaling Flash File System (JFFS2), which was developed byAxis Communications in
Sweden, places a file system directly on the flash, instead of emulating a block device. It is
designed for use on flash-ROM chips and recognizes the special write requirements of a
flash-ROM chip. JFFS2 implements wear-leveling to extend the life of the flash disk, and stores
the flash directory structure in the RAM. A log-structured file system is maintained at all times.
The system is always consistent, even if it encounters crashes or improper power-downs, and does
not require fsck (file system check) on boot-up.
JFFS2 is the newest version of JFFS. It provides improved wear-leveling and garbage-collection
performance, improved RAM footprint and response to system-memory pressure, improved
concurrency and support for suspending flash erases, marking of bad sectors with continued use of
the remaining good sectors that enhances the write-life of the devices, native data compression
inside the file system design, and support for hard links.
The key features of JFFS2 are:
yTargets the Flash ROM directly
yRobustness
yConsistency across power failures
yNo integrity scan (fsck) is required at boot time after normal or abnormal shutdown
yExplicit wear leveling
yTransparent compression
Although JFFS2 is a journaling file system, it does not exclude the loss of data. The file system
will remain in a consistent state across power failures and will always be mountable. However, if
the board is powered down during a write operation, then the incomplete write operation will be
rolled back on the next boot, but write operations that have already been completed will not be

DA-660-8/16-LX User’s Manual Introduction
1-4
affected.
Additional information about JFFS2 is available at:
http://sources.redhat.com/jffs2/jffs2.pdf
http://developer.axis.com/software/jffs/
http://www.linux-mtd.infradead.org/
Software Package
Boot Loader Redboot (V1.92)
Kernel Monta Vista embedded Linux 2.4.18
Protocol Stack ARP, PPP, CHAP, PAP, IPv4, ICMP, TCP, UDP, DHCP, FTP, SNMP
V1/V3, HTTP, NTP, NFS, SMTP, SSH 1.0/2.0, SSL, Telnet, PPPoE,
OpenVPN
File System JFFS2, NFS, Ext2, Ext3, VFAT/FAT
OS shell command bash
Busybox Linux normal command utility collection
Utilities
tinylogin login and user manager utility
telnet telnet client program
ftp FTP client program
smtpclient email utility
scp Secure file transfer Client Program
Daemons
pppd dial in/out over serial port daemon
snmpd snmpd agent daemon
telnetd telnet server daemon
inetd TCP server manager program
ftpd ftp server daemon
apache web server daemon
sshd secure shell server
nfs-user-server network file system server
openvpn virtual private network
openssl open SSL
Linux Tool Chain
GCC (V3.3.2) C/C++ PC Cross Compiler
GDB (V5.3) Source Level Debug Server
Glibc (V2.2.5) POSIX standard C library

2
2
Chapter 2 Getting Started
In this chapter, we explain how to connect the DA-660, turn on the power, and then get started
using the programming and other functions.
The following topics are covered in this chapter:
Powering on the DA-660
Connecting the DA-660 to a PC
¾Serial Console
¾Telnet Console
¾SSH Console
Configuring the Ethernet Interface
¾Modifying Network Settings with the Serial Console
¾Modifying Network Settings over the Network
Test Program—Developing Hello.c
¾Installing the Tool Chain (Linux)
¾Checking the Flash Memory Space
¾Compiling Hello.c
¾Uploading and Running the “Hello” Program
Developing Your First Application
¾Testing Environment
¾Compiling tcps2.c
¾Uploading and Running the “tcps2-release” Program
¾Testing Procedure Summary

DA-660-8/16-LX User’s Manual Getting Started
2-2
Powering on the DA-660
Connect the SG wire to the Shielded Contact located on the upper left corner of the DA-660, and
then power on the computer by connecting it to the power adaptor. It takes about 30 to 60 seconds
for the system to boot up. Once the system is ready, the Ready LED will light up, and the model
name of the computer will appear on the LCM display.
NOTE After connecting the DA-660 to the power supply, it takes about 30 to 60 seconds for the
operating system to boot up. The green Ready LED will not turn on until the operating system is
ready.
Connecting the DA-660 to a PC
There are two ways to connect the DA-660 to a PC: through the serial Console port or by using
Telnet over the network.
Serial Console
The serial console port gives users a convenient way of connecting to the DA-660’s console utility.
This method is particularly useful when using the computer for the first time. The signal is
transmitted over a direct serial connection, and therefore there is no need to know DA-660’s two
IP addresses in order to connect to the serial console utility.
Use the serial console port settings shown below.
Baudrate 115200 b
p
s
Parit
y
N
one
Data bits 8
Sto
p
bits: 1
Flow Control
N
one
Terminal VT100
Once the connection is established, the following window will open.
To log in, type the Login name and password as requested. The default values are both root:
Login: root
Password: root

DA-660-8/16-LX User’s Manual Getting Started
2-3
Telnet Console
If you know at least one of the two IP addresses and netmasks, then you can use Telnet to connect
to the DA-660’s console utility. The default IP address and netmask for each of the two ports are
given below:
Default IP Address Netmask
LAN 1 192.168.3.127 255.255.255.0
LAN 2 192.168.4.127 255.255.255.0
Use a cross-over Ethernet cable to connect directly from your PC to the DA-660. You should first
modify your PC’s IP address and netmask so that your PC is on the same subnet as one of the
DA-660’s two LAN ports. For example, if you connect to LAN 1, you can set your PC’s IP address
to 192.168.3.126 and netmask to 255.255.255.0. If you connect to the LAN 2, you can set your
PC’s IP address to 192.168.4.126 and netmask to 255.255.255.0.
To connect to a hub or switch connected to your local LAN, use a straight-through Ethernet cable.
The default IP addresses and netmasks are shown above. To log in, type the Login name and
password as requested. The default values are both root:
Login: root
Password: root
You can proceed with configuring network settings of the target computer from the built-in bash
shell. Configuration instructions are given in the next section.
ATTENTION
Serial Console Reminder
Remember to choose VT100 as the terminal type. Use the cable provided, CBL-RJ45F9-150, to
connect to the serial console port.
Telnet Reminder
When connecting to the DA-660 over a LAN, you must configure your PC’s Ethernet IP address
to be on the same subnet as the DA-660 you wish to contact. If you do not get connected on the
first try, re-check the serial and IP settings, and then unplug and re-plug the DA-660’s power
cord.

DA-660-8/16-LX User’s Manual Getting Started
2-4
SSH Console
The DA-660 supports an SSH Console to offer users with better security options.
Windows Users
Click the link http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html to download
PuTTY (free software) to set up an SSH console for the DA-660 in a Windows environment. The
following figure shows a simple example of the configuration that is required.
Linux Users
From a Linux machine, use the ssh command to access the DA-660’s Console utility via SSH.
#ssh 192.168.3.127
Select yes to complete the connection.
[root@bee_notebook root]# ssh 192.168.3.127
The authenticity of host ‘192.168.3.127 (192.168.3.127)’ can’t be established.
RSA key fingerprint is 8b:ee:ff:84:41:25:fc:cd:2a:f2:92:8f:cb:1f:6b:2f.
Are you sure you want to continue connection (yes/no)? yes_
NOTE SSH provides better security compared to Telnet for accessing the DA-660’s Console utility over
the network.

DA-660-8/16-LX User’s Manual Getting Started
2-5
Configuring the Ethernet Interface
The network settings of the DA-660 can be modified with the serial Console, or online over the
network.
Modifying Network Settings with the Serial Console
In this section, we use the serial console to configure the network settings of the target computer.
1. Follow the instructions given in a previous section to access the Console Utility of the target
computer via the serial Console port, and then type #cd /etc/network to change directories.
root@Moxa:# cd /etc/network/
root@Moxa:/etc/network/#
2. Type #vi interfaces to edit the network configuration file with vi editor. You can configure
the Ethernet ports of the DA-660 for static or dynamic (DHCP) IP addresses.
Static IP addresses:
As shown below, 4 network settings need to be modified: address, network, netmask, and
broadcast. The default IP addresses are 192.168.3.127 for LAN1 and 192.168.4.127 for
LAN2, with a default netmask of 255.255.255.0.
# We always want the loopback interface.
auto eth0 eth1 lo
iface lo inet loopback
# embedded ethernet LAN1
iface eth0 inet static
address 192.168.3.127
network 192.168.3.0
netmask 255.255.255.0
broadcast 192.168.3.255
# embedded ethernet LAN2
iface eth1 inet static
address 192.168.4.127
network 192.168.4.0
netmask 255.255.255.0
broadcast 192.168.4.255
# 802.11g Gigabyte Cardbus wireless card
#iface eth2 inet static
address 192.168.5.127
network 192.168.5.0
“/etc/network/interfaces” line 1 of 162 --0%--
Dynamic IP addresses:
By default, the DA-660 is configured for static IP addresses. To configure one or both LAN
ports to request an IP address dynamically, replace static with dhcp and then delete the
address, network, netmask, and broadcast lines.
Default Setting for LAN1 Dynamic Setting using DHCP
iface eth0 inet static
address 192.168.3.127
network: 192.168.3.0
netmask 255.255.255.0
broadcast 192.168.3.255
iface eth0 inet dhcp

DA-660-8/16-LX User’s Manual Getting Started
2-6
Auto eth0 eth1 lo
iface lo inet loopback
iface eth0 inet dhcp
iface eth1 inet dhcp
3. After modifying the boot settings of the LAN interface, issue the following command to
activate the LAN settings immediately:
#/etc/init.d/networking restart
NOTE After changing the IP settings, use the networking restart command to activate the new IP
address. However, the LCM display will still show the old IP address. To update the LCM display,
you will need to reboot the DA-660.
Modifying Network Settings over the Network
IP settings can be activated over the network, but the new settings will not be saved to the flash
ROM without modifying the file /etc/network/interfaces.
For example, type the command #ifconfig eth0 192.168.1.1 to change the IP address of LAN1 to
192.168.1.1.
root@Moxa:~# ifconfig eth0 192.168.1.1
root@Moxa:~#
Test Program—Developing Hello.c
In this section, we use the standard Hello programming example to illustrate developing a program
for the DA-660. In general, program development for DA-660 involves the following seven steps.
Step 1:
Connect the DA-660 to a Linux PC.
Step 2:
Install Tool Chain (GNU Cross Compiler & glibc).
Step 3:
Set the cross compiler and glibc environment variables.
Step 4:
Code and compile the program.
Step 5:
Download the program to the DA-660 via FTP or NFS.
Step 6:
Debug the program
ÆIf bugs are found, return to Step 4.
ÆIf no bugs are found, continue with Step 7.
Step 7:
Back up the user directory (distribute the program to
additional DA-660 units if needed).
68x
Cross
Compiler

DA-660-8/16-LX User’s Manual Getting Started
2-7
Installing the Tool Chain (Linux)
The PC must have the Linux Operating System pre-installed before installing the DA-660 GNU
Tool Chain. Redhat 7.3/8.0, Fedora Core, and compatible versions are recommended. The Tool
Chain requires about 100 MB of hard disk space on your PC. The DA-660 Tool Chain software is
located on the DA-660 CD. To install the Tool Chain, insert the CD into your PC and then issue
the following commands:
#mount /dev/cdrom /mnt/cdrom
#rpm –ivh /mnt/cdrom/mxscaleb-3.3.2-6.i386.rpm
The Tool Chain will be installed automatically on your Linux PC within a few minutes. Before
compiling the program, be sure to set the following path first, since the Tool Chain files, including
the compiler, link, library, and include files are located in this directory.
PATH=/usr/local/mxscaleb/bin:$PATH
Setting the path allows you to run the compiler from any directory.
NOTE Refer to Appendix B for an introduction to the Windows Tool Chain. In this chapter, we use the
Linux tool chain to illustrate the cross compiling process.
Checking the Flash Memory Space
If the flash memory is full, you will not be able to save data to the Flash ROM. Use the following
command to calculate the amount of Available flash memory:
/>df –h
If there is not enough Available space for your application, you will need to delete some existing
files. To do this, connect your PC to the DA-660 with the console cable, and then use the console
utility to delete the files from the DA-660’s flash memory.
NOTE If the flash memory is full, you will need to free up some memory space before saving files to
the Flash ROM.

DA-660-8/16-LX User’s Manual Getting Started
2-8
Compiling Hello.c
The package CD contains several example programs. Here we use Hello.c as an example to show
you how to compile and run your applications. Type the following commands from your PC to
copy the files used for this example from the CD to your computer’s hard drive:
# cd /tmp/
# mkdir example
# cp –r /mnt/cdrom/example/* /tmp/example
To compile the program, go to the Hello subdirectory and issue the following commands:
#cd example/hello #make
You should receive the following response:
[root@localhost hello]# make
/usr/local/mxscaleb/bin/mxscaleb-gcc –o hello-release hello.c
/usr/local/mxscaleb/bin/mxscaleb-strip –s hello-release
/usr/local/mxscaleb/bin/mxscaleb-gcc –ggdb -o hello-debug hello.c
[root@localhost hello]# _
Next, execute the hello.exe file to generate hello-release and hello-debug, which are described
below:
hello-release—an IXP platform execution file (created specifically to run on the DA-660)
hello-debug—an IXP platform GDB debug server execution file (see Chapter 5 for details about
the GDB debug tool).
NOTE Be sure to type the #make command from within the /tmp/example/hello directory, since UC’s
tool chain places a specially designed Makefile in that directory. This special Makefile uses the
mxscale-gcc compiler to compile the hello.c source code for the Xscale environment. If you type
the #make command from any other directory, Linux will use the x86 com
p
iler (for example, cc or
gcc).
Refer to Chapter 5 to see a Makefile example.
Uploading and Running the “Hello” Program
Use the following commands to upload hello-release to the DA-660 via FTP.
1. From the PC, type:
#ftp 192.168.3.127
2. Use the bin command to set the transfer mode to Binary mode, and the put command to
initiate the file transfer:
ftp> bin
ftp> put hello-release
3. From the DA-660, type:
# chmod +x hello-release
# ./hello-release
The word Hello will be printed on the screen.
root@Moxa:~# ./hello-release
Hello

DA-660-8/16-LX User’s Manual Getting Started
2-9
Developing Your First Application
We use the tcps2 example to illustrate how to build an application. The procedure outlined in the
following subsections will show you how to build a TCP server program plus serial port
communication that runs on the DA-660.
Testing Environment
The tcps2 example demonstrates a simple application program that delivers transparent,
bi-directional data transmission between the DA-660’s serial and Ethernet ports. As illustrated in
the following figure, the purpose of this application is to transfer data between PC 1 and the
DA-660 via an RS-232 connection. At the remote site, data can be transferred between the
DA-660’s Ethernet port and PC 2 over an Ethernet connection.
RS-232 LAN
PC 2PC 1
Write data to PC1 Receive LAN data
Read serial data Send data to PC2
tcps2.c
Serial Rx
Buffer
LAN Rx
Buffer
Compiling tcps2.c
The source code for the tcps2 example is located on the CD-ROM at
CD-ROM://example/TCPServer2/tcps2.c. Use the following commands to copy the file to a
specific directory on your PC. We use the directory /home/da660/1st_application/. Note that you
need to copy 3 files—Makefile, tcps2.c, tcpsp.c—from the CD-ROM to the target directory.
#mount –t iso9660 /dev/cdrom /mnt/cdrom
#cp /mnt/cdrom/example/TCPServer2/tcps2.c/home/da660/1st_application/tcps2.c
#cp /mnt/cdrom/example/TCPServer2/tcpsp.c/home/da660/1st_application/tcpsp.c
#cp /mnt/cdrom/example/TCPServer2/Makefile.c/home/da660/1st_application/Makefile.c
Type #make to compile the example code:
You will get the following response, indicating that the example program was compiled
successfully.

DA-660-8/16-LX User’s Manual Getting Started
2-10
root@server11:/home/da660/1st_application
[root@server11 1st_application]# pwd
/home/da660/1st_application
[root@server11 1st_application]# 11
total 20
-rw-r—r-- 1 root root 514 Nov 27 11:52 Makefile
-rw-r—r-- 1 root root 4554 Nov 27 11:52 tcps2.c
-rw-r—r-- 1 root root 6164 Nov 27 11:55 tcps2.c
[root@server11 1st_application]# make_
/usr/local/mxscaleb/bin/mxscaleb-gcc -o tcps2-release tcps2.c
/usr/local/mxscaleb/bin/mxscaleb-strip –s tcps2-release
/usr/local/mxscaleb/bin/mxscaleb-gcc -o tcpsp-release tcpsp.c
/usr/local/mxscaleb/bin/mxscaleb-strip –s tcpsp-release
/usr/local/mxscaleb/bin/mxscaleb-gcc –ggdb -o tcps2-debug tcps2.c
/usr/local/mxscaleb/bin/mxscaleb-gcc –ggdb -o tcpsp-debug tcpsp.c
You have new mail in /var/spool/mail/root
[root@server11 1st_application]# 1s
[root@server11 1st_application]# 11
total 92
-rw-r—-r-- 1 root root 514 Nov 27 11:52 Makefile
-rwxr-xr—x 1 root root 25843 Nov 27 12:03 tcps2-debug
-rwxr—xr-x 1 root root 4996 Nov 27 12:03 tcps2-release
-rw-r—-r-- 1 root root 4554 Nov 27 11:52 tcps2.c
-rwxr—xr-x 1 root root 26823 Nov 27 12:03 tcpsp-debug
-rwxr—xr-x 1 root root 5396 Nov 27 12:03 tcpsp-release
-rw-r—-r-- 1 root root 6164 Nov 27 11:55 tcpsp.c
[root@server11 1st_application]#
Two executable files, tcps2-release and tcps2-debug, are created.
tcps2-release—an IXP platform execution file (created specifically to run on the DA-660).
tcps2-debug—an IXP platform GDB debug server execution file (see Chapter 5 for details about
the GDB debug tool).
NOTE If you get an error message at this point, it could be because you neglected to put tcps2.c and
tcpsp.c in the same directory. The example Makefile we provide is set up to compile both tcps2
and tcpsp into the same project Makefile. Alternatively, you could modify the Makefile to suit
your particular requirements.
Uploading and Running the “tcps2-release” Program
Use the following commands to use FTP to upload tcps2-release to the DA-660.
1. From the PC, type:
#ftp 192.168.3.127
2. Next, use the bin command to set the transfer mode to Binary, and the put command to
initiate the file transfer:
ftp> bin
ftp> put tcps2-release

DA-660-8/16-LX User’s Manual Getting Started
2-11
root@server11:/home/da660/1st_application
[root@server11 1st_application]# ftp 192.168.3.127
Connected to 192.168.3.127 220
Moxa FTP server (Version wu-2.6.1(2) Mon Nov 24 12:17:04 CST 2003) ready.
530 Please login with USER and PASS.
530 Please login with USER and PASS.
KERBEROS_V4 rejected as an authentication type
Name (192.168.3.127:root): root
331 Password required for root.
Password:
230 User root logged in.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> bin
200 Type set to I.
ftp> put tcps2-release
local: tcps2-release remote: tcps2-release
277 Entering Passive Mode (192.168.3.127.82.253)
150 Opening BINARY mode data connection for tcps2-release.
226 Transfer complete
4996 bytes sent in 0.00013 seconds (3.9e+04 Kbytes/s)
ftp> ls
227 Entering Passive Mode (192.168.3.127.106.196)
150 Opening ASCII mode data connection for /bin/ls.
-rw------- 1 root root 899 Jun 10 08:11 bash_history
-rw-r--r-- 1 root root 4996 Jun 12 02:15 tcps2-release
226 Transfer complete
ftp>
3. From the DA-660, type:
# chmod +x tcps2-release
# ./tcps2-release &
192.168.3.127 - PuTTY
root@Moxa:~# ls –al
drwxr—xr-x 2 root root 0 Jun 12 02:14
drwxr—xr-x 15 root root 0 Jan 1 1970
-rw------- 1 root root 899 Jun 10 08:11 .bash_history
-rw-r--r-- 1 root root 4996 Jun 12 02:15 tcps2-release
root@Moxa:~# chmod +x tcps2-release
root@Moxa:~# ls –al
drwxr—xr-x 2 root root 0 Jun 12 02:14
drwxr—xr-x 15 root root 0 Jan 1 1970
-rw------- 1 root root 899 Jun 10 08:11 .bash_history
-rwxr-xr-x 1 root root 4996 Jun 12 02:15 tcps2-release
root@Moxa:~#
4. The program should start running in the background. Use either the #jobs or #ps –ef
command to check if the tcps2 program is actually running in the background.
#jobs // use this command to check if the program is running
192.168.3.127 - PuTTY
root@Moxa:~# ls –al
drwxr—xr-x 2 root root 0 Jun 12 02:14
drwxr—xr-x 15 root root 0 Jan 1 1970
-rw------- 1 root root 899 Jun 10 08:11 .bash_history
-rw-r--r-- 1 root root 4996 Jun 12 02:15 tcps2-release
root@Moxa:~# chmod +x tcps2-release
root@Moxa:~# ls –al
drwxr—xr-x 2 root root 0 Jun 12 02:14
drwxr—xr-x 15 root root 0 Jan 1 1970
-rw------- 1 root root 899 Jun 10 08:11 .bash_history
-rwxr-xr-x 1 root root 4996 Jun 12 02:15 tcps2-release

DA-660-8/16-LX User’s Manual Getting Started
2-12
root@Moxa:~# ./tcps2-release &
[1] 187
start
root@Moxa:~# jobs
[1]+ Running ./tcps2-release &
root@Moxa:~#
NOTE Use the kill command for job number 1 to terminate this program: #kill %1
#ps -ef // use this command to check if the program is running
192.168.3.127 - PuTTY
[1]+ Running ./tcps2-release &
root@Moxa:~# ps –ef
PID Uid VmSize Stat Command
1 root 1296 S init
2 root S [keventd]
3 root S [ksoftirqd_CPU0]
4 root S [kswapd]
5 root S [bdflush]
6 root S [kupdated]
7 root S [mtdblockd]
8 root S [khubd]
10 root S [jffs2_gcd_mtd3]
32 root D [ixp425_csr]
34 root S [ixp425 eth0]
36 root D [ixp425 eth1]
38 root 1256 S stdef
46 root 1368 S /usr/sbin/inetd
52 root 4464 S /usr/sbin/httpd
53 nobody 4480 S /usr/sbin/httpd
54 nobody 4480 S /usr/sbin/httpd
64 nobody 4480 S /usr/sbin/httpd
65 nobody 4480 S /usr/sbin/httpd
66 nobody 4480 S /usr/sbin/httpd
88 bin 1460 S /sbin/portmap
100 root 1556 S /usr/sbin/rpc.statd
104 root 4044 S /usr/sbin/snmpd –s –l /dev/null
106 root 2832 S /usr/sbin/snmptrapd -s
135 root 1364 S /sbin/cardmgr
139 root 1756 S /usr/sbin/rpc.nfsd
141 root 1780 S /usr/sbin/rpc.mountd
148 root 2960 S /usr/sbin/sshd
156 root 1272 S /bin/reportip
157 root 1532 S /sbin/getty 115200 ttyS0
158 root 1532 S /sbin/getty 115200 ttyS1
162 root 3652 S /usr/sbin/sshd
163 root 2208 S -bash
169 root 2192 S ftpd: 192.168.3.110: root: IDLE
187 root 1264 S ./tcps2-release
188 root 1592 S ps -ef
root@Moxa:~#
NOTE Use the kill -9 command for PID 187 to terminate this program: #kill -9 187