W5300E01-ARM is the test board to evaluate the function of W5300 based on ARM920T.
1.1. Products Introduction
W5300E01-ARM is composed of the base board and WZ830MJ module. In the base boa rd, ARM920T based
Samsung S3C2410A-200MHz processor is built in, and W5300, the hardware TCP/IP chip is used.
By using serial port of base board and Ethernet port of WIZ830MJ, the communication environment can be
easily set up. You can also test external devices having USB interface through USB Host and Device port.
W5300E01-ARM operates on Linux OS. By installing 64MB SDRAM, various applications can operate
without any problem.
Samsung S3C2410A processor supports NAND Flash Booting. By installing 64MB NAND Flash memory,
enough space is provided for bootloader, OS and user application.
By using extension connector (40pin * 3, total 120pin), the easy extension is supported for the functions that
the base board does not support.
MCU 200MHz Samsung S3C2410A ARM RISC Processor ARM920T
RAM SDRAM 64MB
ROM NAND Flash ROM 64MB
Serial RS-232C 1Port
USB Host USB Host 1Port
USB Device USB Device 1Port
Ethernet Supported by WIZ830MJ Module Basic ITEM
LCD 16Character * 2Line Character LCD Port Basic ITEM
LED LED 2Ea for Debugging
Button Tact Switch 2Ea for Debugging
JTAG On board JTAG Socket
WIZ830MJ Module
Connector
Expansion Port 120Pin (40pin * 3) 2.54mm Pitch Pin-Header
Power DC 5V / 2A Adapter Basic ITEM
PCB 118mm * 97mm Size
56Pin (28Pin * 2) 2.54mm Pitch Pin -Header S ocket
In order to support NAND Flash boot loader, Samsung S3C2410A processor contains SRAM buffer called as
Steppingstone.
W5300E01-ARM Platform uses NAND Flash ROM for Booting memory. It is designed to be initialized with
NAND Flash booting by pull-down OM0 and OM1 pins of S3C2410A to GND.
As power-on reset IC is installed for user manual reset, it is possible to manually reset the board by using
tact switch during board operation.
3.2.2. SDRAM
64MByte SDRAM is used for external memory of S3C2410A processor, and provides enough space for
operation of O/S and User application.
3.2.3. NAND Flash ROM
64MByte NAND Flash ROM is used for external programming memory of S3C2410A and non-volatile
storage device. Basically, Linux bootloader, Kernel, and File System are programmed in this Flash ROM.
Additionally, embedded web server (utilizing W5300 TCP/IP) is also saved in NAND Flash ROM. Extra space
can be used for user data field.
.
WIZ830MJ is the Ethernet module having W5300 TCP/IP chip and RJ-45 connector (having Transformer).
The connection of WIZ830MJ and base board is supported through 2.54mm Pitch Pin Header typed
connector as shown in < Fig 3>
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
Figure 3-3 : WIZ830MJ Module Interface PIN Map
For more detail, refer to WIZ830MJ Module Datasheet.
Figure 3-4 : W5300 Data Bus Width Setting Port
By using J8 3Pin header, it is possible to configure data bus width(8bit or 16bit) of W5300 in WIZ830MJ.
By connecting pin 1 and 2 of J8 by using 2 pin jumper, 16 bit data bus width is configured. By connecting pin
2 and 3, 8 bit bus width is configured.
It is the interface for UART 0, one of 3 channel UARTs that S3C2410A processo r is supporting.
The rest of 2 channels are used for extenstion through expansion port.
W5300E01-ARM platform basically uses 9 pin DSUB male typed connector.
3.2.6. USB Host / Device Port
A-Type Host Connector and Mini-Type Device Connector are provided for testing USB Host interface and
USB Device (Slave) interface that S3C2410 supports.
As USB Host driver is basically supported by Linux, it is possible to test various USB devices by connecting
to W5300E01-ARM platform. Through USB device driver, the connection with PC is supported.
3.2.7. JTAG Interface
Through JTAG Interface, it is possible to write the Bootloader to the NAND Flash ROM. Debugging is
available through JTAG debugging equipment. As 20 pin JTAG connector is installed, general JTAG
equipments can be connected without any problem.
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
Figure 3-5 : JTAG Interface Part Schematic
3.2.8. LED & Tact Switch for Debugging
By using 2 LEDs and 2 Tact Switches connected to EINT/GPIO, simple deb ugging is supported.
3.2.9. Character LCD
Character LCD is used for displaying debugging and system staus.
The pin description of character LCD interface (J7) is as below.
1 GND / VSS Signal Ground
2 5V / VDD I LCD Power Supply
3 V0 / V0 I Voltage for LCD drive
4 A1 / RS I Data / Instruction register select
5 A2 / RW I Read / Write
6 LCD_E / E I Enable signal,start data read / write
7 ~ 14 D0 / DB0 ~ D7 / DB7 I/OData Bus Line
15 5V / LED A O LED Anode, power supply+
16 GND / LED K O LED Cathode,ground 0V
74LBC4245 Bidirectional Level shifter is installed between I/O interface voltage level, 3.3V and LCD
operational voltage level, 5V, for stable operation.More reliable opration is available by checking LCD Busy
W5300E01-ARM B/D PIN NAME
DIR.Description
/ LCD PIN NAME
Table 3-1 : LCD PIN Description
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
Flag through bi-directional buffer.
Low active chip select signal of S3C2410A is passed through inverter and changed to High active.And it is
used for LCD Enable singal
For more detail related to LCD operation, refer to LCD datasheet. (LC1624(R2).pdf).
3.2.10. Power Block
The power of W5300E01-ARM is supplied by 5V/2A adaptor. The internal power is 5V, 3.3V and 1.8V. For
the detail of each power, refer to referen ce sch ematic or ‘3.1.2 Power Block Diagram’.
The input of 5V adaptor can be controlled by power switch (SW1). In order to prevent the damage by overpower when the switch is on, Poly-Fuse(F1) is applied.
Low Drop Out Regulator (5V -> 3.3V, 3.3V -> 1.8V) is applied for power efficiency and heat minimization.
Expansion port interface is designed for user to add the functions that S3C2410A provides (but W5300E01ARM does not).
Function Pin # Pin Name Dir.Description
J3 Port
Power 1 3V3D 3.3V System power
System
Data Bus
System
Address
Bus
3 5V0D 5V System power
39 GND System ground
2,4,6,8,10,12,
14,16,18,20,22,
24,26,28,30,32
5,7,9,11,13,15,
17,19,21,23,25,
27,29,31,33,35
D0 ~ D15
A0 ~ A15
IO Data bus
O Address bus
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
System
Control
Signal
J4 Port
Power 1 3V3D 3.3V System power
DMA 2 nXDACK0 O External DMA acknowledge
I2S
Interface
34 nGCS0 O General chip select 0
36 nOE O Output enable
37 nRESET I System reset input
38 nWE O Write enable
40 EINT0 IO External interrupt request / GPIO
3 5V0D 5V System power
39 GND System ground
38 VDDA_ADC 3.3V ADC power
40 VSSA_ADC ADC ground
4 nXDREQ0 I External DMA request
5 I2SLRCK IO I2S bus channel select clock
7 I2SSCLK IO I2S bus serial clock
9 CDCLK O CODEC system clock
11 I2SSDI I I2S bus serial data input
13 I2SSDO O I2S bus serial data output
UART
Interface
SDDAT3
24 SPICLK0 IO SPI clock
26 SPIMOSI0 IO SPI master data output line
28 SPIMISO0 IO SPI master data input line
30 EINT10 / nSS0 I SPI chip select (for slave mode)
I2C
Interface
27 IICSDA IO I2C bus data
29 IICSCL IO I2C bus clock
ADC 32 AIN1 AI ADC analog input 1
34 AIN0 AI ADC analog input 0
36 Vref AI ADC voltage reference
GPIO
18 EINT6 IO External interrupt request / GPIO
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
/ Interrupt
System
Control
Signal
37 EINT1 IO External interrupt request / GPIO
6 nXBREQ I Bus hold request
8 nXBACK O Bus hold acknowledge
20 PWREN
22 nRSTOUT
31 nWAIT
33 nGCS4 General chip select 4
35 nGCS5 General chip select 5
J5 Port
Power 1 3V3D
3 5V0D
39 GND
LCD
Data Bus
5,7,9,11,13,15,
17,19,21,23,25,
27,29,31,33,35,
VD0 ~ VD23
STN / TFT / SEC TFT LCD
data bus
37,2,4,6,8,10,
12,14
LCD
Control
Signal
16 LEND Line end signal
18 VCLK LCD clock signal
20 VLINE LCD line signal
22 VM VM alternates the polarity of the row
Execute the Hyper Terminal of Windows and configu re the po rt as below.
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
Figure 4-1 : Hyper Terminal Port Configuration
Configure the port as above.
In order to check the operation of the board, turn on the power after connecting the serial cable and
executing Hyper Terminal prog ram.
Below booting message means normal operation of the board. Below screen means that the booting is
processed to Bootloader and Linux Kernel, and user can use the Linux.
z If below booting message is not displayed, check if power adaptor or serial cable is normally
At the Linux, the booting can be checked by using minicom.
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
Figure 4-3 : Minicom Port Configuration
Execute ‘minicom –s’ and select ‘Serial port setup’ menu, and configure the port as above.
Select ‘Save setup as dfl’ menu to save serial configuration. By selecting ‘Exit’ menu, exit the configuration
menu.
z The device file of ‘Serial Device’ can be different acco rding to the Linux version.
Turn on the board after connecting the board to PC by using serial cable, and executing the Hyper Terminal
program. If below booting message is displayed on the Terminal screen, the bo ard normally operates.
Below screen means that the booting is processed to Bootloader and Linux Kernel, and user can use the
Linux.
z If below booting message is not displayed, check if power adaptor or serial cable is normally
W5300E01-ARM board supports Hybrid mode of W5300 linux driver – simultaneous use of S/W & H/W
TCP/IP stack. By configuring channel 0 as MAC_RAW mode, it is possible to utilize Hybrid mode for
compatibility with existing network program. Channel 1 is configured for testing looback test through H/W
TCP/IP stack.
By configuring channel 0 as MAC_RAW mode, existing network program can be supported without any
change. And, if there is any network application requiring higher performance, you can use other H/W
TCP/IP channels.
According to the requirement of your products, Hybrid mode can be useful. For more detail, refer to ‘W5300
Datasheet’.
When W5300E01-ARM board is booted, FTP server, HTTP server and Telnet server are automatically
loaded.
4.2.1. Testing FTP Server
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
1. Supply the power to W5300E01-ARM and check booting is normally processed.
2. Execute FTP Client program.
z Windows : Start -> ‘Run’ -> input ‘ftp’
z Linux : Input ‘ftp’ at the terminal
3. Input ‘open 192.168.1.53’ and connect to FTP server of W5300E01-ARM.
1. Supply the power to W5300E01-ARM board and check booting.
2. Execute TELNET Client program.
z Windows : Start -> ‘Run’ -> Input ‘telnet’
z Linux : Input ‘telnet’ at the terminal
3. Log in with ‘id > wiznet, password > wiznet’.
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
Figure 4-7 : TELNET Server Test
4.2.4. Testing Loopback
With the loopback program in W5300E01-ARM, it is possible to test both of S/W & H/W TCP/IP stack.
Loopback program is installed in ‘/root’ directory of 5300E01-ARM board.
1. Install AX1 provided by CD. (Software/Tools/AXInstallV3.1.exe)
For the detail of AX1, refer to ‘Documents/Menual/AX1 Menual V3.1’ provided by CD.
2. Supply the power to W5300E01-ARM and check booting.
3. Log in with ‘root’.
4. Execute the Loopback server with ‘./loopback –t -w’ command. The option of Loopback is as below.
6. For the exact testing, calculate CPU T ick by selecting ‘CPUTICK’ -> ‘CPUTICK’ of AX1.
7. Select ‘TCP’ -> ‘Connect’ of AX1.
8. Input ‘IP > 192.168.1.53’ and ‘PORT > 5001’ and click ‘OK’ button.
The IP address of PC in which AX1 is installed, should be set as 192.168.1.xxx (Ex> 192.168.1.2).
9. Check if ‘Connected’ message is shown. If PC and W5300E01-ARM board is connected, ‘loopback start!’
message is displayed at the loopback program of W5300E01-ARM. If connection is not normal, check
below.
z Is UTP cable correctly connected?
z Is IP address correctly configured as 192.168.1.xxx?
z Is loopback program normally executed at the W5300E01-ARM?
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
Figure 4-8 : Loopback Connection Check
10. Select ‘∞’ Toolbar of AX1, and select any image file. (Size : 10~50Mb)
Development environment is same as one which is generally usede. Programming is done at the Host PC.
Execution file for target board is created by using cross compiler. The file is sent to target board for execution.
5.1. Cable Connection
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
Figure 5-1 : Cable Connection Example 1
As shown in <Figure 5-1>, connect the Host PC and W5300E01-ARM board. The Linux should be installed
in the Host PC. Serial cable is used for system console, debugging and data transmission. UTP cable is for
data transmission. The data communication through UTP cable is faster than serial cable. In order to transfer
big-sized file, use UTP cable for more efficien cy.
If you are not familiar with Linux, it is possible to develop at the Windows, and compile the source code by
sending to Host PC as shown in <Figure 5-2>.
Toolchain is included in CD. Log in with ‘root’ at the Host PC, and install as below steps.
1. Mount the CD on the CD-ROM.
2. Copy the compressed Toolchain file into ‘/’.
3. Extract the Toolchain compressed file.
After mounting CD, input below commands in the terminal window.
As the CD contents are automatically mounted in the latest Linux version, you don’t need to input ‘mount’
# mount /dev/cdrom /media/cdrom
# cp /media/cdrom/Software/Tools/arm-toolchain-3.4.3.tar.gz /
# cd /
# tar zxvf arm-toolchain-3.4.3.tar.gz
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
command in the most cases. When you mount the CD manually, check device file and mounting directory.
5.3. Network Configuration of Host PC
In order to transfer files between Host PC and target board by using UTP cable, server programs should be
installed in the Host PC. Virtual IP address can be used for this networking. As server program installation is
processed by package management system, the board should be conneted to the WAN. In order to use LAN
and WAN together, add the virtual IP with below command.
# ifconfig eth0 add 192.168.1.2
5.3.1. TFTP(Trivial File Transfer Protocol) Server Configuration
In order to transmit Linux Kernel image, Ramdisk image or other files, tftp server should be installed in Host
PC. In here, we will install the tftp server of Red Hat and Debian.
If Host PC is using Debian Linux, install tftpd-hpa package by using apt-get package management system.
# apt-get install tftpd-hpa
At the Red Hat Linux, install tftpd-server package by using yum package management system.
Make the directory to be used for tftp server, and execute tftp server.
# mkdir /tftpboot
# in.tftpd –l –s /tftpboot
Now, it is possible to download the files in ‘/tftpboot’ of Host PC into the target board by usig tftp.
When executing tftp server by using xinetd, open ‘/etc/xinetd.d/tftp’ file at the editor, and change the ‘disable
= yes’ into ‘disable = no’. If you don’t have ‘/etc/xinetd.d/tftp’ file, create the file and include below.
service tftp
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -c –s /tftpboot
per_source = 11
cps = 100 2
flags = IPv4
}
When using ‘xinetd’, ‘xinetd’ package should be installed. If ‘xinetd’ package is not installed, install it by using
apt-get or yum package management system.
5.3.2. NFS(Network FileSystem) Server Configuration
When transmitting big-sized file from Host to target board, serial is not efficient. For this case, NFS (Network
File System) can be used. Binary image is created after programming and compiling at the Host PC. If you
install the the binary image at the directory configured by NFS, you can execute it at the target board.
If nfs server is not installed in the Host PC, install the nfs server. If you are using Debian Linux, install the nfskernel-server package with apt-get package management system.
# apt-get install nfs-kernel-server
In case of Red Hat, install nfs-utils package with yum package management system.
# yum install nfs-utils
Create a directory to share NFS between Host PC and Target board.
# mkdir /nfs
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
Open ‘/etc/’exports’ file and add below.
/nfs 192.168.1.0(rw, insecure)
Re-start the NFS. (In case of using Debian, input ‘/etc/init.d/nfs-kernel-server’ instead of ‘/etc/init.d/nfs’.)
It is possible to transmit a file by using Zmodem of terminal program.
Serial transmission is simple and easy, but slow in speed. It is appropriate to transmit small-sized files.
For the testing, program ‘Hello World’ in the ‘test.c’ source file.
#include <stdio.h>
int main(void)
{
printf(“Hello World!\n”);
return 0;
}
Compile the source code into execute file for ARM.
In order to use NFS, NFS Server should be installed in the Host PC. For the detail of NFS server installation,
refer to ‘5.3.2 NFS Server Configuration’.
W5300E01-ARM supports NFS Client. In order to use the directory of NFS at the Host PC, input below
command at the target board.
# mount –t nfs –o nolock 192.168.1.2:/nfs /mnt/nfs
# ls /mnt/nfs
In the ‘/root’ directory, the script to mount NFS is included. By using this script, NFS directory can be simply
mounted.
#./nfsmnt 192.168.1.2:/nfs
# ls /mnt/nfs
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
5.4.3. Others
In the W5300E01-ARM, FTP server and client are built in. By using FTP, file transmission is available.
1. Copy Linux kernel source patched to W5300E01-ARM from CD.
# cd /media/cdrom/Software/LinuxKernel
# cp linux-2.6.24.4-w5300e01.tar.gz /usr/src/
2. Extract the compression and compile it.
# cd /usr/src
# tar zxvf linux-2.6.24.4-w5300e01.tar.gz
# cd linux-2.6.24.4
# make wizImage
3. Copy the created kernel image into the directory set as tftp server.
# cp wizImage /tftpboot/
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
4. Input ‘tftp 31000000 wizImage’ at the bootloader of the Target board, and download the kernel image.
(For the detail of bootloader , refer to ‘8. Bootloader’)
6. Input ‘nand write 31000000 40000 2eb958’ to write the kernel image of RAM into the NAND Flash kernel
area. In here, ‘2eb958’ is size of kernel image downloaded from tftp.
7. By inputting ‘printenv’, check bootcmd.
8. When kernel image size is changed, re-configure environment variable ‘bootcmd’
Ex > If changed kernel image size is 300000.
Root File system is the file system mounted in ‘/’.
Root File system should include dynamic library, device file, and indispensable utilities basically used for
system operation.
W5300E01-ARM uses Ramdisk for Root File system. NAND Flash area is used by mounting JFFS2 file
system at the Ramdisk
7.1. Ramdisk
Ramdisk uses a part of memory as like disk drive. Ramdisk is volatile because the file system exists on RAM.
If power is off, the saved data disappears.
If data should be preserved, the data should be written in NAND Flash area.
(For the detail, refer to ‘7.2 JFFS2’.)
You can change the Ramdisk composition. However, the size of Ramdisk cant’ be over 12M (the maximum
size of Ramdisk)
NAND Flash is non-volitile storage device. For storing data, use NAND Flash area. JFFS2 is the file system
only for Flash. When W5300E01-ARM accesses NAND Flash area, mount and use the JFFS2 file system.
NAND Flahs area can be divided as below
z 0x00000000 – 0x00020000 : Bootloader
z 0x00020000 – 0x00040000 : Boot Param
z 0x00040000 – 0x00400000 : Kernel
z 0x00400000 – 0x01400000 : Ramdisk
z 0x01400000 – 0x04000000 : JFFS2 FileSystem
Bootloader field has bootloader firstly operating when power is supplied to the system.
The Boot Param field is the space where boot parameter value is saved when kernel is booted at the
bootloader. Linux kernel field includes kernel images. At the bootloader, the kernel image of this field is
loaded to RAM and booted to kernel.
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
In the Ramdisk area, the Ramdisk used for current root file system is included.
JFFS2 File System area does not have any image. This area can be used after formatting as JFFS2.
7.2.1. JFFS2 File System Mount
1. After completing the boot, log in with ‘root’.
2. In case of using JFFS2 area for the first time, it should be formatted in JFFS2 type.
# flash_eraseall –j /dev/mtd4
3. Mount JFFS2 file system.
# mount –t jffs2 /dev/mtdblock4 /mnt/jffs2
4. If data is written in the directory - ‘/mnt/jffs2’, the data is saved in NAND Flash.
Now, JFFS2 file system can be automatically mounted.
In the W5300E01-ARM, the bootloader that u-boot is modified, is included. The usage of u-boot is almost
same as exisiting one.
For the detail of each command, refer to http://www.denx.de/wiki/DULG/Manual
information of each command through ‘help [command]’
Below is the description of frequently used commands.
printenv It shows environment variables currently set.
setenv <name> <value> It configures <name> environment variables as <value>. Some
important variables should be configured in accordace with system.
z ipaddr : It shows IP address of the target board during current
bootloader operates. Defalut value is ‘192.168.1.3’.
z serverip : It is the IP address of Host PC. The default value is
‘192.168.1.2’.
z gatewayip : It is the Gateway IP address. The default value is
‘192.168.1.1’.
. You can also see the
W
W
5
5
3
3
0
0
0
0
E
E
0
0
1
1
-
-
A
A
R
R
M
M
U
U
s
s
e
e
r
r
’
’
s
s
M
M
a
a
n
n
u
u
a
a
l
l
z netmask : It is the Network mask value. The default value is
‘255.255.255.0’.
z bootcmd : It is the environment variables automatically
executed when booting at the bootloader.
tftpboot <address> <bootfilename> Download the <bootfilename> image file of Host PC of which IP
address is set as ‘serverip’ into <address> of the target board.
At this time, tftp server should be installed in the Host PC. For the
configuration method of tftp server, refer to ‘5.3.1. tftp server
configuration’. If download is not normally processed, check
environment variable ‘ipaddr’ and ‘serverip’.
bootm <address> Boot with application image saved in <address>.
nand erase [clean] [off size] Erase Nand Flast as much as [size] at the [off] address. Be careful
that all value of NAND Flash can be removed if ‘nand erase clean’ is
used.
nand read <addr> <off> <size> Read the data of <off> address of NAND Flash as much as <size> to
<addr> address.
nand write <addr> <off> <size> Write the data of <addr> of RAM as much as <size> into <off> of
NAND Flash. It is used when writing new bootloader, kernel and