SSV Embedded Systems eSOM/SK2 User manual

eSOM
/
SK2 eSOM/9263
Embedded Linux Starter Kit
First Steps
SSV Embedded Systems
Dünenweg 5
D-30419 Hannover
Phone: [phone]
Fax: [phone]
E-mail: [e-mail] Document Revision: 1.0
Date: 2010-05-14
F OR FURTHER INFORMATION REGARDING OUR PRODUCTS PLEASE VISIT US AT WWW . SSV - EMBEDDED . DE

eSOM/SK2 eSOM/9263 - First Steps
2
Manual Revision 1.0
CONTENT
1INTRODUCTION...............................................................................................................3
1.1 Safety Guidelines...................................................................................................................3
1.2 Conventions...........................................................................................................................3
1.3 Features and Technical Data..................................................................................................4
2GETTING STARTED.........................................................................................................5
2.1 Serial Link between BB6/eSOM and PC...............................................................................5
2.2 Ethernet Link between BB6/eSOM and PC ..........................................................................6
2.3 Connecting Power Supply and Power-up the Starter Kit............................................................7
2.4 Using Serial Link with Terminal Program ............................................................................8
2.5 Power-up eSOM/9263 with RCM disabled...........................................................................9
2.6 Power-up eSOM/9263 with RCM enabled..........................................................................10
2.7 eSOM/9263 Linux File System ...........................................................................................12
2.8 Checking IP Address of PC.................................................................................................13
2.9 Checking Ethernet-based TCP/IP Communication .............................................................14
2.10 Using a Telnet Connection ..................................................................................................15
2.11 Checking FTP Server...........................................................................................................16
2.12 Checking TFTP Client.........................................................................................................17
2.13 Checking HTTP Server........................................................................................................18
2.14 Changing Ex Factory IP Address ........................................................................................19
3LINUX BOOT MESSAGES..............................................................................................20
4BB6/ESOM HARDWARE REFERENCE .........................................................................22
4.1 BB6/eSOM Board Layout ...................................................................................................22
4.2 Pinout COM1 Connector – J5..............................................................................................23
4.3 Pinout COM2 Connector – J6..............................................................................................23
4.4 Pinout COM3 Connector – J7..............................................................................................24
4.5 Pinout 10/100 Mbps Ethernet Connector – J10...................................................................24
4.6 Pinout Power Connector – J17 ............................................................................................24
5HELPFUL LITERATURE.................................................................................................25
CONTACT..............................................................................................................................25
DOCUMENT HISTORY .........................................................................................................25

eSOM/SK2 eSOM/9263 - First Steps
Manual Revision 1.0
3
1 INTRODUCTION
The Starter Kit eSOM/SK2 contains everything you need to get started with your embedded
networking application. The Starter Kit includes an eSOM/9263 module with a pre-installed
U-Boot boot loader and an embedded Linux, the Evaluation Board BB6/eSOM, power sup-
ply, serial interface (null modem) cable, a CD-ROM with software and documentation and a
printed user manual for the first steps with the Starter Kit.
The Starter Kit CD-ROM comes with a full GNU cross tool chain for C/C++ software de-
velopment. The binary files of this pre build tool chain run on an x86 Linux based host
(SuSE, Red Hat or other) and build executable files for the Atmel AT91SAM9263 ARM9
MCU.
For using the eSOM/SK2 Embedded Linux Starter Kit you need a development system. The
minimal configuration for this system is a Windows based PC with the HyperTerminal ter-
minal emulation program and a free COM port (COM1, COM2 or USB based COMx) for
the RS232 serial link between the eSOM/9263 and HyperTerminal.
For using the Ethernet link, your PC needs an Ethernet adapter with 10 Mbps or
10/100 Mbps LAN interface. This environment allows Web server programming (HTML
pages, Java applets) and Linux shell script programming. For using the GNU C/C++ cross
tool chain, it is necessary to run Linux on the development system.
1.1 Safety Guidelines
Please read the following safety guidelines carefully! In case of property or personal
damage by not paying attention to this document and/or by incorrect handling, we do
not assume liability. In such cases any warranty claim expires.
ATTENTION: Observe precautions for handling – electrostatic sensitive device!
•Discharge yourself before you work with the device, e.g. by touching a heater of
metal, to avoid damages.
•Stay grounded while working with the device to avoid damage through electrostatic
discharge.
1.2 Conventions
Convention Usage
bold
Important terms
italic
User inputs and other specials
monospace Pathnames, internet addresses and program code
Table 1: Conventions used in this Document

eSOM/SK2 eSOM/9263 - First Steps
4
Manual Revision 1.0
1.3 Features and Technical Data
The eSOM/SK2 comes with a pre-installed U-Boot boot loader and an Embedded Linux op-
erating system. The eSOM/9263 Linux consists of two main components: 1. the Linux ker-
nel and 2. the root file system.
The eSOM/9263 U-Boot boot loader allows the downloading of new Linux kernel versions
and root file systems to the eSOM/9263 RAM and Flash. This in-system programming fea-
ture can be used by a simple serial and Ethernet link between the development system and
the eSOM/9263.
•eSOM/9263 with Atmel AT91SAM9263 ARM9 MCU @ 192 MHz
•32 Mbytes NOR Flash and 128 Mbytes SDRAM
•U-Boot boot loader and Embedded Linux pre-installed in Flash memory
•Evaluation Board BB6/eSOM
•Null modem cable
•110 VAC or 230 VAC to 12..24 VDC international power supply
•CD-ROM with user manual and hardware/programmers manuals
•Embedded Linux with source
•GNU cross tool chain for C/C++ software development for Linux-based PCs
•GNU gdb and gdbserver for Ethernet-based remote debugging
•Linux remote login with Telnet
•Web server setup sample
•FTP server setup sample
•TFTP client setup sample
•Many source code samples

eSOM/SK2 eSOM/9263 - First Steps
Manual Revision 1.0
5
2 GETTING STARTED
2.1 Serial Link between BB6/eSOM and PC
Setup the serial link between the Evaluation Board BB6/eSOM and your PC. Use a null mo-
dem cable for this connection.
Figure 1: Serial link between BB6/eSOM and PC
Connect one end of the null modem cable with an unused COM port of your PC. Make sure
that this PC COM port supports 115.200 bps.

eSOM/SK2 eSOM/9263 - First Steps
6
Manual Revision 1.0
2.2 Ethernet Link between BB6/eSOM and PC
Setup the Ethernet LAN link between the Evaluation Board BB6/eSOM and your PC. Use an
Ethernet cross-over cable or a switch-based infrastructure for the LAN connection.
Figure 2: Ethernet link between BB6/eSOM and PC
Please note: The eSOM/9263 comes with the default IP address 192.168.0.126.
Please make sure that your PC can work with the IP address range 192.168.0.x.
Figure 3: Switch-based Ethernet link between BB6/eSOM and PC

eSOM/SK2 eSOM/9263 - First Steps
Manual Revision 1.0
7
2.3 Connecting Power Supply and Power-up the Starter Kit
Connect the 12 VDC power supply with the barrel plug with the Evaluation Board
BB6/eSOM.
Please note: Make sure that all cable connections are OK. Then power-up the Starter
Kit.
Figure 4: Power supply for the BB6/eSOM
CAUTION: Providing the BB6/eSOM with a voltage higher than the regular 12..24 VDC
±10% could resolve in damaged board components!

eSOM/SK2 eSOM/9263 - First Steps
8
Manual Revision 1.0
2.4 Using Serial Link with Terminal Program
Run HyperTerminal on your Windows-PC, minicom or a similar simple terminal emulation
program on your Linux-based PC.
Figure 5: Direct connection setup with HyperTerminal
Setup a direct connection with the parameters of table 2. Make sure, that the PC COM port
supports 115.200 bps.
Figure 6: Parameter setup with HyperTerminal
Parameter Value
Speed 115.200 bps
Data Bits 8
Parity None
Stop Bits 1
Protocol No (Xon/Xoff, RTS/CTS or similar)
Table 2: Setup parameters for the serial link

eSOM/SK2 eSOM/9263 - First Steps
Manual Revision 1.0
9
2.5 Power-up eSOM/9263 with RCM disabled
After power-up the eSOM/9263 starts an automatic boot process from the on-board flash
memory chip. This process consists of two steps:
1. Directly after power-up, the eSOM/9263 runs the U-Boot boot loader program
for some milliseconds. U-Boot initializes the hardware components (hardware
init). With RCM disabled (please see the eSOM/9263 hardware reference man-
ual for details), there is no U-Boot text message output over the eSOM/9263
COM1 serial interface and no boot delay-based
1
wait period. Direct after the
hardware init, the U-Boot boot loader starts the Linux OS image.
2. Linux takes control over the eSOM/9263 hardware and runs all necessary proc-
esses for coming up to live.
Figure 7: Linux booting process with HyperTerminal
Please note: The U-Boot environment variable boot delay does not influence the
eSOM/9263 boot process with RCM (Remote Console Mode) disabled.
The eSOM/9263 Linux supports a serial console. It allows running a Linux-based system
in a headless configuration without a monitor or keyboard. Wait until the Linux boot pro-
cess finishes. Please use the username root and the password root. Then press Enter.
“boot delay” is a U-Boot environment variable. The value defines a wait time before
U-Boot starts the Linux operating system.

eSOM/SK2 eSOM/9263 - First Steps
10
Manual Revision 1.0
2.6 Power-up eSOM/9263 with RCM enabled
The eSOM/9263 boot sequence with RCM enabled is similar to the boot procedure with
RCM disabled. Only the first step is different:
1. The eSOM/9263 runs the U-Boot boot loader program. This software shows a
wait message over the eSOM/9263 COM1 serial interface if RCM is enabled
(please see the eSOM/9263 hardware reference manual for details). It is possible
to interrupt the boot process and switch to the U-Boot command line interface.
Just hit a key of your terminal emulation program.
2. Without interruption the U-Boot boot loader starts a Linux OS image after the
wait period from the eSOM/9263 Flash memory.
Figure 8: U-Boot wait message
Please note: The U-Boot command line interface allows you to change the wait
time of the first step. Please see the U-Boot environment variable boot delay for
details.
Figure 9: Linux booting process after the U-Boot boot delay

eSOM/SK2 eSOM/9263 - First Steps
Manual Revision 1.0
11
Figure 10: After a login the serial console offers a Linux command line interface
Wait until the Linux boot process finishes. Please use the username root and the pass-
word root. Then press Enter.

eSOM/SK2 eSOM/9263 - First Steps
12
Manual Revision 1.0
2.7 eSOM/9263 Linux File System
After booting the eSOM/SK2 all directories in the root file system are read-only. There
are only three exceptions, which are shown in the following table:
Directory Remark
/flash
R/W directory, non-volatile memory within Flash
/home/root
R/W directory, RAM disk, volatile memory
/var/volatile
R/W directory, RAM disk, volatile memory
Table 3: R/W directories in the file system
The read-only restriction protects all files of the file system. Under ordinary operating
conditions it is not possible to overwrite or delete a file which is necessary for the
eSOM/9263. To disable the write protection just login with the username root and the
password root and enter the following command:
mount / -o remount,rw
This command „mounts„ the file system as read/write. All files are now writable and de-
letable. Please pay attention not to damage important system files! With the command
mount / -o remount,ro
the system is set to the read-only initial condition after the boot process.
Figure 11: Disabling the write protection with the mount command

eSOM/SK2 eSOM/9263 - First Steps
Manual Revision 1.0
13
2.8 Checking IP Address of PC
Make sure that your PC is using the right IP address for the Ethernet-based TCP/IP com-
munication with the eSOM/9263.
Please use 192.168.0.1 or 192.168.0.254 for your PC and 192.168.0.126
for the eSOM/9263.
Figure 12: Windows-PC IP address check with ipconfig
Talk to your network administrator if you have problems with the IP address understand-
ing.
Please note: To change the ex factory IP address 192.168.0.126 of the
eSOM/9263 please refer to chapter 2.16.

eSOM/SK2 eSOM/9263 - First Steps
14
Manual Revision 1.0
2.9 Checking Ethernet-based TCP/IP Communication
Check the Ethernet-based TCP/IP communication between the eSOM/9263 and the PC
with a simple ping command.
Figure 13: Windows-PC TCP/IP communication check with ping
First check the cable connections and then the IP addresses if your ping does not work.
Then check the TCP/IP setup of your PC.

eSOM/SK2 eSOM/9263 - First Steps
Manual Revision 1.0
15
2.10 Using a Telnet Connection
Run a Telnet client program on your PC with the IP address of the eSOM/9263. You can use
a Telnet session for remote entering Linux commands.
Figure 14: Run the Windows Telnet client program
Wait until the eSOM/9263 Linux requests a user name. Please use the login name root and
the password root. Then press Enter.
Please note: The eSOM/9263 Linux comes with BusyBox. All Linux command line
commands are implemented in BusyBox. BusyBox combines tiny versions of many
common UNIX utilities into a single small executable. It provides replacements for
most of the utilities you usually find in GNU fileutils, shellutils, etc. The utilities in
BusyBox generally have fewer options than their full-featured GNU cousins; how-
ever, the options that are included provide the expected functionality and behave
very much like their GNU counterparts. BusyBox provides a fairly complete envi-
ronment for any small or embedded system.
Figure 15: Using Linux commands within a Telnet client window

eSOM/SK2 eSOM/9263 - First Steps
16
Manual Revision 1.0
2.11 Checking FTP Server
The eSOM/SK2 Linux comes with a pre-installed FTP server. This server allows the file
transfer via Ethernet between a PC and the eSOM/SK2. Run an FTP client program like
FileZilla on your PC for a test.
Figure 16: FileZilla as FTP client to access the FTP server
Use for the FTP login the IP address 192.168.0.126, the username root and the
password root. With this login you have FTP read/write permission in the file system of
the eSOM/SK2.
Please Note: Before you start an FTP file transfer to the eSOM/SK2, please make
sure you have the read/write permission in the file system. For further information
about the file system please refer to chapter 2.7.

eSOM/SK2 eSOM/9263 - First Steps
Manual Revision 1.0
17
2.12 Checking TFTP Client
The eSOM/SK2 Linux comes with a pre installed TFTP client. This client allows the file
transfer via Ethernet between a PC and the eSOM/SK2. Run a TFTP server like
TFTPD32 on your PC for a test.
To transfer a file with the name autostart.sh into the directory /var of the eSOM/SK2
execute the following commands within a Telnet session:
cd /var
tftp 192.168.0.249
get autostart.sh
quit
With the first command you change into the directory /var of the eSOM/SK2.
The second command establishes a connection to the TFTP server. In this example the
PC with the TFTP server has the IP address 192.168.0.249.
The third command transfers the file with TFTP-GET. After the file transfer Linux shows
how many bytes have been transferred.
The fourth command disconnects the TFTP server. You can now access the new file in
the file system of the eSOM/SK2.
Figure 17: File transfer via TFTP
Please Note: Before you start a TFTP file transfer to the eSOM/SK2, please make
sure you have the read/write permission within the file system. For further infor-
mation about the file system please refer to chapter 2.7.

eSOM/SK2 eSOM/9263 - First Steps
18
Manual Revision 1.0
2.13 Checking HTTP Server
The eSOM/SK2 Linux comes with a pre-installed Web server. Run a Web browser on
your PC for a test and enter the following address
http://192.168.0.126
into the address bar of the browser. The browser shows the file index.html which is stored
in the directory /www of the eSOM/SK2. Into this directory you can load own files.
Figure 18: Checking the Web server of the eSOM/SK2 with a browser

eSOM/SK2 eSOM/9263 - First Steps
Manual Revision 1.0
19
2.14 Changing Ex Factory IP Address
The default IP address of the eSOM/SK2 is 192.168.0.126. The IP address settings
are stored in the file /etc/network/interfaces. Run a Telnet session and start the
editor nano which is part of the Linux with the following command:
TERM=vt102 nano /etc/network/interfaces
Figure 19: The editor nano within a Telnet session
Change the file /etc/network/interfaces to your needs and save it.
The changes of the IP address settings will not be active until a system reboot.
Please Note: To change a file with the editor nano, you need the read/write per-
mission within the file system. For further information about the file system
please refer to chapter 2.7.

IGW/400-UART – Linux Boot Messages
20
Manual Revision 1.0
3 LINUX BOOT MESSAGES
Linux version 2.6.24.7 (mha@hareangle-saturn) 


(gcc version 4.1.2) #2 PREEMPT Thu Jul 2 15:42:14 CEST 2009
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: SSV Hardware 9263/1
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 192 MHz, master 96 MHz, main 16.000 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 


128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 


128 sets
Built 1 zonelists in Zone order, mobility grouping on. 


Total pages: 8128
Kernel command line: mem=32M console=ttyAT0,115200 


noinitrd root=/dev/mtdblock2 rootfstype=jffs2 ro
AT91: 160 gpio irqs in 5 banks
PID hash table entries: 128 (order: 7, 512 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 29356KB available (2740K code, 240K data, 100K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 64 bytes
NET: Registered protocol family 16
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: pit clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
atmel_usart.0: ttyAT0 at MMIO 0xfff8c000 (irq = 7) is a 


ATMEL_SERIAL
console [ttyAT0] enabled
atmel_usart.1: ttyAT1 at MMIO 0xfff90000 (irq = 8) is a 


ATMEL_SERIAL
atmel_usart.3: ttyAT3 at MMIO 0xfeffee00 (irq = 1) is a 


ATMEL_SERIAL
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffbc000 irq 21 (02:80:ad:1f:12:34)
eth0: attached PHY driver [Davicom DM9161E] 


(mii_bus:phy_addr=ffffffff:00, irq=-1)
physmap platform flash device: 02000000 at 10000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank