Moxa Technologies UC-8410-LX User manual

UC-8410/8416/8418/8430-LX
User’s Manual
Sixth Edition, June 2011
www.moxa.com/product
© 2011 Moxa Inc. All rights reserved.
Reproduction without permission is prohibited.

UC-8410/8416/8418/8430 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 ©2011 Moxa Inc.
All rights reserved.
Reproduction without permission is prohibited.
Trademarks
The MOXA logo 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
1. Introduction...................................................................................................................................... 1-1
Overview ...........................................................................................................................................1-2
Software Architecture..........................................................................................................................1-2
Journaling Flash File System (JFFS2) .............................................................................................1-3
Software Features .......................................................................................................................1-3
2. Getting Started.................................................................................................................................. 2-1
Powering on the UC-8410/8416/8418/8430 ...........................................................................................2-2
Connecting the UC-8410/8416/8418/8430/8430 to a PC .........................................................................2-2
Serial Console.............................................................................................................................2-2
Telnet Console ............................................................................................................................2-2
SSH Console...............................................................................................................................2-3
Configuring the Ethernet Interface ........................................................................................................ 2-4
Modifying Network Settings with the Serial Console .........................................................................2-4
Modifying Network Settings over the Network .................................................................................2-6
Test Program─Developing Hello.c.........................................................................................................2-6
Installing the Tool Chain (Linux)....................................................................................................2-6
Checking the Flash Memory Space.................................................................................................2-7
Compiling Hello.c ........................................................................................................................ 2-7
Uploading and Running the “Hello” Program ...................................................................................2-8
3. Managing Embedded Linux................................................................................................................ 3-1
System Version Information.................................................................................................................3-2
Firmware Upgrade ..............................................................................................................................3-2
Upgrading the Firmware...............................................................................................................3-2
Loading Factory Defaults .............................................................................................................. 3-4
Enabling and Disabling Daemons ..........................................................................................................3-5
Setting the Run-Level..........................................................................................................................3-7
Setting the System Time .....................................................................................................................3-8
TZ variable .................................................................................................................................3-8
etc/timezone ..............................................................................................................................3-8
Adjusting the System Time .................................................................................................................. 3-8
Setting the Time Manually ............................................................................................................3-8
NTP Client .................................................................................................................................. 3-9
Updating the Time Automatically ...................................................................................................3-9
Cron—Daemon to Execute Scheduled Commands ................................................................................. 3-10
Connecting Peripherals ...................................................................................................................... 3-11
USB Mass Storage ..................................................................................................................... 3-11
CF Mass Storage ....................................................................................................................... 3-11
4. Managing Communication ................................................................................................................. 4-1
Telnet/FTP .........................................................................................................................................4-2
DNS ..................................................................................................................................................4-2
Web Service—Apache..........................................................................................................................4-3
IPTABLES ..........................................................................................................................................4-4
NAT ..................................................................................................................................................4-8
NAT Example ..............................................................................................................................4-9
Enabling NAT at Bootup ...............................................................................................................4-9
Dial-up Service—PPP ......................................................................................................................... 4-10
PPPoE.............................................................................................................................................. 4-13
NFS (Network File System) Client ....................................................................................................... 4-15
Setting up the UC-8410/8416/8418/8430/8430 as an NFS Client .................................................... 4-15
Mail ................................................................................................................................................ 4-15
SNMP .............................................................................................................................................. 4-16
OpenVPN ......................................................................................................................................... 4-17
Package Management—ipkg ............................................................................................................... 4-24
Audio Playing and Recording .............................................................................................................. 4-24
Volume Control ......................................................................................................................... 4-24
Playing a WAVE File ................................................................................................................... 4-25
Recording a WAVE file................................................................................................................ 4-25
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-5
WDT (Watch Dog Timer)...................................................................................................................... 5-5
Digital I/O..........................................................................................................................................5-8
UART .............................................................................................................................................. 5-13

SRAM .............................................................................................................................................. 5-15
Make File Example ............................................................................................................................ 5-16
Moxa CAN Programming Guide ........................................................................................................... 5-17
Introduction.............................................................................................................................. 5-17
Programming Guide................................................................................................................... 5-17
Software Lock .................................................................................................................................. 5-19
Qt-embedded................................................................................................................................... 5-20
Compile and Test the QT Program on an X86 Machine.................................................................... 5-21
Set up Qt development .............................................................................................................. 5-21
Cross-compile the Qt application and run with Dual-display ............................................................ 5-21
Upload the binary to target and run it with following command ....................................................... 5-22
A. Firmware Upgrade Procedure............................................................................................................ A-1
B. System Commands ............................................................................................................................ B-1
Linux Normal Command Utility Collection...............................................................................................B-1
File Manager ...............................................................................................................................B-1
Editor ........................................................................................................................................B-1
Network .....................................................................................................................................B-2
Process ......................................................................................................................................B-2
Modules .....................................................................................................................................B-2
Other.........................................................................................................................................B-2
Special Moxa Utilities ...................................................................................................................B-3

1
1. Introduction
Welcome to the Moxa UC-8400 Series of RISC-based communication platforms.
The UC-8410/8416/8418/8430 embedded computer comes with 8 RS-232/422/485 serial ports, 3 Ethernet
ports, 4 digital input channels, 4 digital output channels, (12 digital input channels and 12 digital output
channels for UC-8418), 8 10/100 Mbps switch ports (UC-8416 only), a CompactFlash socket, and 2 USB 2.0
ports. In addition, the UC-8430 comes with 2 VGA outputs, making it the perfect solution for applications that
require HMI for field site monitoring.
The UC-8410/8416/8418/8430 computer uses the Intel XScale IXP435 533 MHz RISC CPU. This powerful
computing engine supports several useful communication functions, but will not generate too much heat. The
built-in 16 MB NORFlash ROM can be used to store the operating system, and 256 MB SDRAM gives you enough
memory to run your application software directly on the UC-8410/8416/8418/8430. Moreover, the 32 MB
NAND Flash provides the capacity for data storage.
The UC-8410/8416/8418/8430 computer supports RS-232/422/485 serial ports, digital I/O, and has three LAN
ports, making it ideal as a communication platform for industrial applications that require network redundancy.
Pre-installed with the Linux 2.6 platform, the UC-8410/8416/8418/8430 provides an open software operating
system for software program development. Software written for a desktop PC can be easily ported to the
UC-8410/8416/8418/8430 platform by using a GNU cross compiler, without needing to modify the code. This
makes the UC-8410/8416/8418/8430 an optimal solution for your industrial applications with the minimal cost
and effort.
In addition to the standard model, a wide temperature version (-40 to 75°C) of the UC-8410/8416/8418/8430
is also available for use in harsh industrial environments.
The following topics are covered in this chapter:

Overview

Software Architecture
Journaling Flash File System (JFFS2)
Software Features

UC-8410/8416/8418/8430 Introduction
1-2
Overview
The UC-8410/8416/8418/8430 computer, which features a RISC CPU, RAM memory, serial ports for
connecting RS-232/422/485 devices, and 3 10/100 Mbps Ethernet ports, is designed for embedded
applications.
The UC-8410/8416/8418/8430 uses an Intel XScale IXP435 533 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. The built-in 16
MB NOR Flash ROM can be used to store the operating system, and 256 MB of SDRAM gives you enough
memory to run your application software directly on the UC-8410/8416/8418/8430. Moreover, the 32 MB
NAND Flash provides the capacity for data storage. In addition, the network capability provided by the 3 LAN
ports built into the RISC CPU combined with the ability to control connected serial devices makes the
UC-8410/8416/8418/8430/8430 an ideal communication platform for data acquisition and industrial control
applications.
The UC-8410/8416/8418/8430’s pre-installed open source Linux operating system can run software written for
desktop PCs, provided the software is ported to the computer with a GNU cross compiler. The process is easy,
straightforward, and your programmer will not need to modify the source code. The OS, device drivers (e.g.,
Ethernet, SRAM, watchdog, and Buzzer control) and your own applications, can all be stored in the NOR Flash
memory.
Software Architecture
The Linux operating system that comes pre-installed on the UC-8410/8416/8418/8430/8430 follows the
standard Linux architecture, making it easy to run programs that follow the POSIX standard. Program porting
is done with the GNU Tool Chain provided by Moxa. In addition to Standard POSIX APIs, device drivers for the
buzzer, SRAM and watchdog controls, and UART are also included in the Linux OS.
The UC-8410/8416/8418/8430’s built-in Flash ROM is divided into Boot Loader, Linux Kernel, Root File
System, and User Root File System partitions.
In order to prevent user applications from crashing the Root File System, the UC-8410/8416/8418/8430/8430
uses a specially designed Root File System with Protected Configuration for emergency use. This Root
File System comes with serial and Ethernet communication capability for users to load the Factory Default
Image file. The user directory saves the user’s settings and application.
To improve system reliability, the UC-8410/8416/8418/8430/8430 has a built-in mechanism that prevents the
system from crashing. When the Linux kernel boots up, the kernel will mount the root file system for read only,

UC-8410/8416/8418/8430 Introduction
1-3
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 Root File System to boot up the system. The Root File System is protected, and
cannot be changed by the user, providing a “safe” zone.
For more information about memory map and programming, 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 by Axis Communications in Sweden, puts 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 (which
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:
•Targets the Flash ROM directly
•Robustness
•Consistency across power failures
•No integrity scan (fsck) is required at boot time after normal or abnormal shutdown
•Explicit wear leveling
•Transparent compression
Although JFFS2 is a journaling file system, this does not preclude the loss of data. The file system will remain
in a consistent state after power failures and will always be mountable. However, if the board is powered down
during a write then the incomplete write will be rolled back on the next boot, but writes that have already been
completed will not be affected.
Additional information about JFFS2 is available on the following websites:
http://sources.redhat.com/jffs2/jffs2.pdf
http://developer.axis.com/software/jffs/
http://www.linux-mtd.infradead.org/
Software Features
Linux
Kernel Version: 2.6.23
Protocol Stack:
TCP, UDP, IPv4, SNMP V1, ICMP, ARP, HTTP, CHAP, PAP, SSH 1.0/2.0, SSL, DHCP, NTP, NFS,
Telnet, FTP, PPP, PPPoE, OpenVPN
File System: JFFS2, NFS, Ext2, Ext3
System Utilities: bash, busybox, tinylogin, telnet, ftp, ssh, scp
telnetd: telnet Server daemon
ftpd: FTP server daemon
sshd: secure shell server
Apache: web server daemon, supporting PHP and XML

UC-8410/8416/8418/8430 Introduction
1-4
openvpn: virtual private network service manager
pppd: dial in/out over serial port daemon
snmpd: snmpd agent daemon
openssl: open SSL
Application Development Software: Moxa Linux API device control
Linux Tool Chain:
Firmware v1.X:
• GCC (V4.2.1): C/C++ PC Cross Compiler
• Glibc (V2.2.5): POSIX standard C Library
Firmware v2.X:
• GCC (V4.4.2): C/C++ PC Cross Compiler
• Glibc (V2.10.1): POSIX standard C Library
Software Encryption Lock:
BINEncryptor: Encryption tool for binary files (based on patented Moxa technology)

2
2. Getting Started
In this chapter, we explain how to connect the UC-8410/8416/8418/8430, turn on the power, and then get
started with programming and using other functions.
The following topics are covered in this chapter:

Powering on the

Connecting the UC-8410/8416/8418/8430/8430 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

UC-8410/8416/8418/8430 Getting Started
2-2
Powering on the UC-8410/8416/8418/8430
Connect the SG wire to the Shielded Contact located in the upper left corner of the UC-8410/8416/8418/8430,
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.
ATTENTION
After connecting the UC-8410/8416/8418/8430/8430 to the power supply, it
will take about 16 seconds for
the operating system to boot up. The green Ready LED will not turn on until the operating system is ready.
Connecting the
UC-8410/8416/8418/8430/8430 to a PC
There are two ways to connect the UC-8410/8416/8418/8430/8430 to a PC: directly through the serial console
port, or by Telnet over the network. For the UC-8430, you can connect the display with the display cable. Once
you turn on the power, you will be able to access the computer and conduct additional configurations.
Serial Console
The serial console port gives users a convenient way of connecting to the UC-8410/8416/8418/8430’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, so you do not need to know either of its 3 IP addresses in order to connect to
the UC-8410/8416/8418/8430.
Use the serial console port settings shown below.
Baudrate 115200 bps
Parity None
Data bits 8
Stop bits 1
Flow Control None
Terminal VT100
Once the connection is established, you can start using UC-8410/8416/8418/8430.
Telnet Console
If you know at least one of the IP addresses and netmasks, you can use Telnet to connect to the
UC-8410/8416/8418/8430’s console utility. The default IP address and Netmask for each of the 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
LAN 3 192.168.5.127 255.255.255.0
*Please note that the LAN1 of the UC-8430 uses DHCP for both IP Address and Netmask.
Use a cross-over Ethernet cable to connect directly from your PC to the UC-8410/8416/8418/8430. You should
first modify your PC’s IP address and netmask so that your PC is on the same subnet as one of the
UC-8410/8416/8418/8430’s 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 LAN 2, you can set your PC’s IP address to
192.168.4.126 and netmask to 255.255.255.0.

UC-8410/8416/8418/8430 Getting Started
2-3
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 when you reach the bash command
shell. Configuration instructions are given in the next section.
ATTENTION
Serial Console Reminder
Remember to choose VT100 as the terminal type. Use cable CBL-4PINDB9F-100, which comes with the
UC-8410/8416/8418/8430, to connect to the serial console port.
Telnet Reminder
When connecting to the UC-
8410/8416/8418/8430/8430 over a LAN, you must configure your PC’s Ethernet
IP address to be on the same subnet as the UC-8410/8416/8418/8430/8430 you wish to connect to. If y
ou do
not get connected on the first try, re-check the IP settings, and then unplug and re-plug the
UC-8410/8416/8418/8430’s power cord.
SSH Console
The UC-8410/8416/8418/8430/8430 supports an SSH console to provide users with better security options.
Windows Users
Click on 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 UC-8410/8416/8418/8430/8430 in a Windows environment.
The following figure shows a simple example of the configuration that is required.

UC-8410/8416/8418/8430 Getting Started
2-4
Linux Users
From a Linux machine, use the “ssh” command to access the UC-8410/8416/8418/8430’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 UC-8410/8416/8418/8430
’s console utility
over the network.
Configuring the Ethernet Interface
The network settings of the UC-8410/8416/8418/8430/8430 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 network settings of the target computer.
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 directory.
root@Moxa:# cd /etc/network/
root@Moxa:/etc/network/#
Type #vi interfaces to edit the network configuration file with vi editor. You can configure the
UC-8410/8416/8418/8430’s Ethernet ports for static or dynamic (DHCP) IP addresses.

UC-8410/8416/8418/8430 Getting Started
2-5
Static IP addresses:
As shown below, 3 network addresses need to be modified: address, network, netmask, and broadcast.
The default IP addresses are 192.168.3.127 for LAN1, 192.168.4.127 for LAN2, and 192.168.5.127 for LAN3,
with default netmasks of 255.255.255.0.
# We always want the loopback interface.
auto eth0 eth1 eth2 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
# embedded ethernet LAN3
iface eth2 inet static
address 192.168.5.127
network 192.168.5.0
Dynamic IP Addresses:
By default, the UC-8410/8416/8418/8430 is configured for “static” IP addresses. To configure 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
*Please note that the default value for LAN1 of the UC-8430 is DHCP.
Auto eth0 eth1 lo
iface lo inet loopback
iface eth0 inet dhcp
iface eth1 inet dhcp
After the boot settings of the LAN interface have been modified, issue the following command to activate the
LAN settings immediately:
#/etc/init.d/networking restart
ATTENTION
After changing the IP settings, use the networking restart command to activate the new IP address.

UC-8410/8416/8418/8430 Getting Started
2-6
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:/etc/network/#
Test Program─Developing Hello.c
1. Connect the UC-8410/8416/8418/8430/8430 to a Linux PC.
2. Install the Tool Chain (GNU Cross Compiler & glibc).
3. Set the cross compiler and glibc environment variables.
4. Code and compile the program.
5. Download the program to the UC-8410/8416/8418/8430
/8430 via
FTP or NFS.
6. Debug the program
If bugs are found, return to Step 4.
If no bugs are found, continue with Step 7
7. Back up the user directory (distribute the program to additional
UC-8410/8416/8418/8430/8430 units if needed).
Installing the Tool Chain (Linux)
The PC must have the Linux operating system pre-installed before installing the
UC-8410/8416/8418/8430/8430 GNU Tool Chain. Redhat 7.3/8.0, Fedora core, and compatible versions are
recommended. The Tool Chain requires about 600 MB of hard disk space on your PC. The
UC-8410/8416/8418/8430/8430 Tool Chain software is located on the UC-8410/8416/8418/8430/8430 CD. To
install the Tool Chain, insert the CD into your PC and then issue the following commands:
With v1.x firmware:
#mount /dev/cdrom /mnt/cdrom#/mnt/cdrom/tool-chain/Linux/arm-linux_2.3.sh
With v2.x firmware:
#mount /dev/cdrom
/mnt/cdrom#/mnt/cdrom/tool-chain/Linux/arm-linux_3.0_Build_YYMMDDHH.sh
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.
With v1.x firmware and arm-linux 2.x.sh:
PATH=/usr/local/arm-linux/bin:$PATH
With v2.x firmware and arm-linux 2.x.sh and arm-linux_3.0_Build_YYMMDDHH.sh:
PATH=/usr/local/arm-linux-4.4.2/bin:$PATH
Setting the path allows you to run the compiler from any directory.

UC-8410/8416/8418/8430 Getting Started
2-7
ATTENTION
If you have an older version of Linux Tool Chain on your Moxa embedded computer (such as the W300 Series,
IA240/241, and UC-7112-LX Plus) and would like to install the new Linux Tool Chain for the
UC-8410/8416/8418/8430
, the old Linux Tool Chain files will be immediately overwritten, and the programs
compiled by this new Tool Chain may not work on your old models. We strongly suggest you rename the
directory of the old Linux Tool Chain before installing the new one if you would like to use the old Linux Tool
Chain for other embedded computers.
Checking the Flash Memory Space
The UC-8410/8416/8418/8430/8430 uses a specially designed root file system. Only /tmp, /etc, /home,
/usr/local/bin, /usr/local/sbin, /usr/local/libexec, and /usr/local/lib directories are writable. Others are
read-only. The writable directories are mounted on /dev/mtdblock4. If the /dev/mtdblock4 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
root@Moxa:/# df -h
Filesystem Size Used Available Use% Mounted on
rootfs 13.4M 9.8M 3.5M 74% /
/dev/root 13.4M 9.8M 3.5M 74% /
/dev/ram15 1.7M 19.0k 1.6M 1% /dev
/dev/ram0 499.0k 18.0k 456.0k 4% /var
/dev/mtdblock4 32.0M 1.9M 30.1M 6% /tmp
/dev/mtdblock4 32.0M 1.9M 30.1M 6% /home
/dev/mtdblock4 32.0M 1.9M 30.1M 6% /etc
tmpfs 252.5M 0 252.5M 0% /dev/shm
/dev/sdb1 483.4M 57.9M 425.5M 12% /var/sdb
root@Moxa:/#
If there isn’t enough “Available” space for your application, you will need to delete some existing files. To do
this, connect your PC to the UC-8410/8416/8418/8430/8430 with the console cable, and then use the console
utility to delete the files from the UC-8410/8416/8418/8430’s flash memory.
Compiling Hello.c
The CD contains several sample programs. Here we use Hello.c 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:

UC-8410/8416/8418/8430 Getting Started
2-8
[root@localhost hello]# make
xscale-linux-gcc –o hello-release hello.c
xscale-linux-strip –s hello-release
xscale-linux-gcc –ggdb -o hello-debug hello.c
[root@localhost hello]# _
Next, execute hello.exe to generate hello-release and hello-debug, which are described below:
hello-release—an IXP platform execution file (created specifically to run on the UC-8410/8416/8418/8430)
hello-debug—an IXP platform GDB debug server execution file (see Chapter 5 for details about the GDB
debug tool).
ATTENTION
Be sure to type the #make command from within the /tmp/example/hello directory, since the
UC-8410/8416/8418/8430’s tool chain puts a specially designed Makefile in that directory. This special
Makefile uses the xscale-linux-gcc
compiler to compile the hello.c source code for the Xscale environment. If
you type the #make com
mand from any other directory, Linux will use the x86 compiler (for example, cc or
gcc). Refer to Chapter 5 to see a Make file example.
Uploading and Running the “Hello” Program
Use the following command to upload hello-release to the UC-8410/8416/8418/8430/8430 via FTP.
From the PC, type:
#ftp 192.168.3.127
Use the bin command to set the transfer mode to binary mode, and then put command to initiate the file
transfer:
ftp> cd /home
ftp> bin
ftp> put hello-release
From the UC-8410/8416/8418/8430, type:
# chmod +x /home/hello-release
# ./home/hello-release
The word Hello will be printed on the screen.
root@Moxa:~# ./home/hello-release
Hello

3
3. Managing Embedded Linux
This chapter includes information about version control, deployment, updates, and peripherals.
The following topics are covered in this chapter:

System Version Information

Firmware Upgrade
Upgrading the Firmware
Loading Factory Defaults

Enabling and Disabling Daemons

Setting the Run-Level

Setting the System Time
TZ variable
/etc/timezone

Adjusting the System Time
Setting the Time Manually
NTP Client
Updating the Time Automatically

Cron—Daemon to Execute Scheduled Commands

Connecting Peripherals
USB Mass Storage
CF Mass Storage

UC-8410/8416/8418/8430 Managing Embedded Linux
3-2
System Version Information
To determine the hardware capability of your UC-8410/8416/8418/8430/8430 and what kind of software
functions are supported, check which version of the firmware your UC-8410/8416/8418/8430/8430 is running.
Contact Moxa to determine the hardware version. You will need the Production S/N (Serial number), which
is located on the UC-8410/8416/8418/8430’s bottom label.
To check the kernel version, type:
#kversion
192.168.3.127 – PuTTY
root@Moxa:~# kversion
UC-8410/8416/8418/8430 version 1.0
root@Moxa:~#
root@Moxa:/# kversion -a
UC-8410/8416/8418/8430 version 1.0 Build 08091716
root@Moxa:~#
Firmware Upgrade
Upgrading the Firmware
The UC-8410/8416/8418/8430’s kernel, and root file system are combined into one firmware file, which can be
downloaded from Moxa’s website (www.moxa.com). The name of the file has the form
FWR_uc8400_Va.b.c_Build_YYMMDDHH.hfm, with “a.b.c” indicating the firmware version and
YYMMDDHH indicating the build date. To upgrade the firmware, download the firmware file to a PC, and then
transfer the file to the UC-8410/8416/8418/8430/8430 unit via a serial console or Telnet console connection.
ATTENTION
Upgrading the firmware will erase all data on the Flash ROM
If you are using the ramdisk
to store code for your applications, beware that updating the firmware will erase
all of the data on the Flash ROM. You should back up your application files and data before updating the
firmware.
Since different Flash disks have different sizes, it’s a good idea to check the size of your Flash disk before
upgrading the firmware, or before using the disk to store your application and data files. Use the #df –h
command to list the size of each memory block, and how much free space is available in each block.
192.168.3.127 – PuTTY
root@Moxa:/# df -h
Filesystem Size Used Available Use% Mounted on
rootfs 13.4M 9.8M 3.5M 74% /
/dev/root 13.4M 9.8M 3.5M 74% /
/dev/ram15 1.7M 19.0k 1.6M 1% /dev
/dev/ram0 499.0k 18.0k 456.0k 4% /var
/dev/mtdblock4 32.0M 1.9M 30.1M 6% /tmp
/dev/mtdblock4 32.0M 1.9M 30.1M 6% /home
/dev/mtdblock4 32.0M 1.9M 30.1M 6% /etc
tmpfs 252.5M 0 252.5M 0% /dev/shm
/dev/sdb1 483.4M 57.9M 425.5M 12% /var/sdb
root@Moxa:/# /dev/s

UC-8410/8416/8418/8430 Managing Embedded Linux
3-3
root@Moxa:/# upramdisk
root@Moxa:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/mtdblock2 14.0M 11.2M 2.8M 80% /
/dev/ram15 1.7M 18.0k 1.6M 1% /dev
/dev/ram0 499.0k 34.0k 440.0k 7% /var
/dev/mtdblock3 15.8M 2.6M 13.1M 17% /tmp
/dev/mtdblock3 15.8M 2.6M 13.1M 17% /home
/dev/mtdblock3 15.8M 2.6M 13.1M 17% /etc
/dev/ram1 38.7M 13.0k 36.7M 0% /mnt/ramdisk
root@Moxa:/# cd /mnt/ramdisk/
root@Moxa:/mnt/ramdisk#
The following instructions give the steps required to save the firmware file to the UC-8410/8416/8418/8430’s
RAM disk, and then upgrade the firmware.
1. Type the following commands to enable the RAM disk:
#upramdisk
#cd /mnt/ramdisk
2. Type the following commands to use the UC-8410/8416/8418/8430’s built-in FTP client to transfer the
firmware file (FWR_uc8400_Va.b.c_Build_YYMMDDHH.hfm ) from the PC to the
UC-8410/8416/8418/8430:
/mnt/ramdisk> ftp <destination PC’s IP>
Login Name: xxxx
Login Password: xxxx
ftp> bin
ftp> get FWR_uc8400_Va.b.c_Build_YYMMDDHH.hfm
192.168.3.127 – PuTTY
root@Moxa:/mnt/ramdisk# ftp 192.168.3.193
Connected to 192.168.3.193 (192.168.3.193).
220 TYPSoft FTP Server 1.10 ready…
Name (192.168.3.193: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> cd newsw
250 CWD command successful. “/C:/ftproot/newsw/” is current directory.
ftp> bin
200 Type set to I.
ftp> ls
200 Port command successful.
150 Opening data connection for directory list.
drw-rw-rw- 1 ftp ftp 0 Nov 30 10:03 .
drw-rw-rw- 1 ftp ftp 0 Nov 30 10:03 .
-rw-rw-rw- 1 ftp ftp 12904012 Nov 29 10:24
FWR_uc8400_Va.b.c_Build_YYMMDDHH.hfm
226 Transfer complete.
ftp> get FWR_uc8400_Va.b.c_Build_YYMMDDHH.hfm
local: FWR_uc8400_Va.b.c_Build_YYMMDDHH.hfm remote:
FWR_uc8400_Va.b.c_Build_YYMMDDHH.hfm
200 Port command successful.

UC-8410/8416/8418/8430 Managing Embedded Linux
3-4
150 Opening data connection for FWR_uc8400_Va.b.c_Build_YYMMDDHH.hfm
226 Transfer complete.
12904012 bytes received in 2.17 secs (5925.8 kB/s)
ftp>
3. Next, use the upgradehfm command to upgrade the kernel and root file system:
#upgradehfm FWR_uc8400_Va.b.c_Build_YYMMDDHH.hfm
192.168.3.127 – PuTTY
root@Moxa:/mnt/ramdisk# upgradehfm FWR_uc8400_Va.b.c_Build_YYMMDDHH.hfm
Moxa UC-8400 Upgrade firmware utility version 1.0.
To check source firmware file context.
The source firmware file conext is OK.
This step will upgrade firmware. All the data on flash will be destroyed.
Do you want to continue? (Y/N) :
Now upgrade the file [redboot].
Format MTD device [/dev/mtd0] ...
MTD device [/dev/mtd0] erase 128 Kibyte @ 60000 -- 100% complete.
Wait to write file ...
Completed 100%
Now upgrade the file [kernel].
Format MTD device [/dev/mtd1] ...
MTD device [/dev/mtd1] erase 128 Kibyte @ 1a0000 -- 100% complete.
Wait to write file ...
Completed 100%
Now upgrade the file [root-file-system].
Format MTD device [/dev/mtd2] ...
MTD device [/dev/mtd2] erase 128 Kibyte @ e00000 -- 100% complete.
Wait to write file ...
Completed 100%
Now upgrade the file [directory].
Format MTD device [/dev/mtd5] ...
MTD device [/dev/mtd5] erase 128 Kibyte @ 20000 -- 100% complete.
Wait to write file ...
Completed 100%
Now upgrade the new configuration file.
Upgrade the firmware is OK. Rebooting
Loading Factory Defaults
Press the reset button for more than 5 seconds to force the system to load the factory default settings. All files
in the /home, /etc, /usr/local/bin, /usr/local/sbin, /usr/local/lib, /usr/local/libexec, and /tmp directories will be
deleted. While pressing the reset button, during the first 5 seconds the ready-light will blink once each second.
If you continue pressing the button after 5 seconds have passed, the ready-light will turn off, indicating that the
factory defaults have been loaded.