Phytec phyCORE-LPC3250 Programming manual

A product of a PHYTEC Technology Holding Company
QuickStart Instructions
L-715e_0
April 10, 2009
Document No:
Edition:
phyCORE-LPC3250 Rapid Development Kit for
Linux

In this QuickStart are descriptions for copyrighted products that are not explicitly indicated as such. The
absence of the trademark (™) and copyright (©) symbols does not imply that a product is not protected.
Additionally, registered patents and trademarks are similarly not expressly indicated in this manual.
The information in this document has been carefully checked and is believed to be entirely reliable.
However, PHYTEC America LLC assumes no responsibility for any inaccuracies. PHYTEC America LLC
neither gives any guarantee nor accepts any liability whatsoever for consequential damages resulting from
the use of this manual or its associated product. PHYTEC America LLC reserves the right to alter the
information contained herein without prior notification and accepts no responsibility for any damages which
might result.
Additionally, PHYTEC America LLC offers no guarantee nor accepts any liability for damages arising from
the improper usage or improper installation of the hardware or software. PHYTEC America LLC further
reserves the right to alter the layout and/or design of the hardware without prior notification and accepts no
liability for doing so.
© Copyright 2009 PHYTEC America LLC, Bainbridge Island, WA.
Rights - including those of translation, reprint, broadcast, photomechanical or similar reproduction and
storage or processing in computer systems, in whole or in part - are reserved. No reproduction may occur
without the express written consent from PHYTEC America LLC.
EUROPE NORTH AMERICA
Address: PHYTEC Technologie Holding AG
Robert-Koch-Str. 39
D-55129 Mainz
GERMANY
PHYTEC America LLC
203 Parfitt Way SW, Suite G100
Bainbridge Island, WA 98110
USA
Ordering Information: [phone]
[email protected]
1 [phone]
[email protected]
Technical Support: [phone]
[email protected]
1 [phone]
[email protected]
Fax: [phone] [phone]
Website: http://www.phytec.de http://www.phytec.com
phyCORE-ARM9/LPC3250 Rapid Development Kit for Linux
© PHYTEC America LLC 2009
L-715e_0

Table of Contents
© PHYTEC America LLC 2009 i
L-715e_0
Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Rapid Development Kit Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Professional Support Packages Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Overview of this QuickStart Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.4 Conventions used in this QuickStart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.5 Kit Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.6 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.7 The PHYTEC Kit CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Rapid Development Kit Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Booting the Pre-built Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3 Getting More Involved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1 Installing the Linux Target Image Builder (LTIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2 Building U-Boot, the Linux Kernel, and Root File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3 Setting up TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.4 Setting up NFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.5 Overview of the Boot Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.6 Placing U-Boot into NAND Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.7 Configuring U-Boot to Boot Linux over TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.8 Placing the Kernel into NAND Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.9 Placing the Root File System into NAND Flash. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.10 Placing the Root File System on an SD/MMC Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.11 Building Custom Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.11.1 Building Openssh and the Apache Web Server . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.11.2 Testing Openssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.11.3 Testing the Apache Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.11.4 Adding your Own Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Appendix A: Helpful Hints and Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
A.1 Where to Find More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
A.2 NAND Flash Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
A.3 Using DHCP Instead of a Static IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
A.4 Enabling Ethernet in the Provided Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 1: Introduction
© PHYTEC America LLC 2009 1
L-715e_0
1 Introduction
This QuickStart provides you with the tools and know-how to get the Linux operating system
running on the phyCORE-LPC3250 System on Module. This QuickStart shows you how to do
everything from installing the appropriate tools and source, to building custom kernels, to
deploying the OS, to exercising the software and hardware.
Please refer to the phyCORE-LPC3250 Hardware Manual for specific information on board-level
features such as jumper configuration, memory mapping and pin layout for the phyCORE-
LPC3250 System on Module and Carrier Board.
1.1 Rapid Development Kit Documentation
This rapid development kit (RDK) includes the following electronic documentation on the enclosed
phyCORE-LPC3250 Rapid Development Kit CD:
• The PHYTEC phyCORE®-LPC3250 Hardware Manual
• Controller User’s Manuals and Datasheets
• This QuickStart Instruction guide
1.2 Professional Support Packages Available
PHYTEC backs up our Rapid Development Kits with a Start-Up Guarantee. We invite you to make
use of our free Technical Support concerning installation and setup of QuickStart demos until any
kit start-up problem you might encounter is resolved. For more in-depth questions, we offer
technical support packages for purchase. Please contact our sales team at [email protected] to
discuss the appropriate support option if professional support beyond installation and setup is
required.
1.3 Overview of this QuickStart Instruction
This QuickStart instruction gives a general Rapid Development Kit description, as well as all of the
necessary instructions required to deploy embedded Linux on the phyCORE-LPC3250 in both a
standalone configuration, and a networked development configuration. This QuickStart takes you
from deploying pre-built images provided in the kit on an SD Card, to building a custom image and
deploying everything over the network suitable for the often changing development environment.
The structure of this QuickStart is as follows:
Chapter 1 - Introduction: This chapter provides an overview of this QuickStart instruction, system
requirements, and kit contents.
Chapter 2 - Getting Started: This chapter guides you through installing the PHYTEC Spectrum CD
software and documentation, preparing the phyCORE-LPC3250 hardware and interfacing a host
PC, and booting the pre-built images included on the SD Card that comes with the kit.
Chapter 3 - Getting More Involved: This chapter provides more in-depth instructions on installing
the Linux build tools, building custom images, deploying images via NAND Flash, SD/MMC Card,
TFTP, and NFS.
Appendix A: This chapter provides some additional information that you may find useful while
working with Linux on the phyCORE-LPC3250 SOM. This chapter includes links to the NXP Linux
BSP page, links to learning more about the Linux Target Image Builder, NAND Flash layout, using
DHCP, and enabling Ethernet in the pre-built images.

Chapter 1: Introduction
© PHYTEC America LLC 2009 2
L-715e_0
1.4 Conventions used in this QuickStart
The following is a list of the typographical conventions used in this book.
Pay special attention to the notes set apart from the text with the following icons:
1.5 Kit Contents
The following PHYTEC hardware components are included in the phyCORE-LPC3250 Linux
Rapid Development Kit (part number KPCM-040-Linux) and are necessary for completing the
instructions in this QuickStart:
• The phyCORE-LPC3250 SOM (PCM-040)
• The phyCORE-LPC3250 Carrier Board (PCM-967)
• Bare PCB Expansion Board (PCM-988) (optional)
• AC adapter supplying 5V/3.2A, center positive
• Ethernet patch cable
Bold Commands or other text that should be typed literally by the user
Bold Italic File and directory names
Italic Field and window names or titles, menu items, and other terms that corre-
spond to items on the PC desktop
Underline Blue Hyperlinks to documents, webpage URLs, or FTPs
<bracket red> Replace these entries with the text applicable to your system. For
instance this may be a directory name, or IP address. The entire entry,
including brackets should be replaced by the applicable text.
FixedWidth Source code listings and examples
Completion of an important part of this QuickStart.
Useful supplementary information and tips about the topic.
Estimated completion time for the following chapter.
This warning will help you avoid potential problems.
Helpful information for troubleshooting and resolving potential problems.

Chapter 1: Introduction
© PHYTEC America LLC 2009 3
L-715e_0
• Serial cable (RS-232)
• SOM extraction tool
• Hard copy schematics (optional)
• SD Card with pre-built U-Boot, Linux, and Root File System images
• PHYTEC Kit CD
As an addition the KLCD-011 QVGA (320x240) TFT LCD can be purchased as an add-on for this
kit should you require graphics.
1.6 System Requirements
The following system requirements are necessary to complete this QuickStart without errors and
problems. Deviations from these requirements may suffice, or may have other work-arounds.
• A network enabled Linux host system running OpenSUSE 11.1 or later1
• SD card reader operational under Linux2
• Active internet connection
1.7 The PHYTEC Kit CD
The PHYTEC Kit CD contains documentation, datasheets, and demo files for various OSes and
develoment environments. For Linux, all demo images are provided on the kit SD card. The latest
demo images can be obtained from http://www.phytec.com/products/linux/bsp-LPC3250.html The
remaining components for the Linux kit are all provided from http://www.bitshrine.org and are
installed as part of this QuickStart Instruction.
If you are interested in evaluating the WinCE BSP, or the Keil or IAR BSPs you can install the
PHYTEC Kit CD on a Windows system by running the setup.exe. Please refer to the respective
QuickStart for each BSP by visiting http://www.phytec.com/products/sbc/ARM-XScale/phyCORE-
ARM9-LPC3250.html or by navigating to the QuickStarts folder on the CD under
\PHYTEC\phyCORE-LPC3250\Documentation\QuickStarts.
1. Although other Linux distributions will likely work, this QuickStart is based on working with the openSUSE dis-
tribution. The Fedora Core 9 distribution has also been tested to work with some of this QuickStart.
2. If you do not have SD card access under Linux then mounting the root file system on an SD card will not be
possible. Some parts of this QuickStart require copying files from Linux onto an SD card. Most of these oper-
ations use a FAT32 partition. This can be handled with a Windows machine if SD card access under Linux is
unavailable.

Chapter 2: Getting Started
© PHYTEC America LLC 2009 4
L-715e_0
2 Getting Started
2.1 Rapid Development Kit Setup
To prepare for the subsequent sections of this QuickStart document, complete the following steps:
1. Insert the SD card that came in the kit in to the SD/MMC card slot connector X15 on the
phyCORE-LPC3250 Carrier Board.
2. If you ordered the KLCD-011 add-on, plug this into the LCD connector X26 at this time.
3. Plug the phyCORE-LPC3250 SOM into connector X1 on the Carrier Board if it is not
already plugged into the board.
4. Connect the kit supplied serial cable from a free serial port on your Linux host to the
bottom DB9 connector P1A on the Carrier Board. This is the UART5 communications
channel with the LPC3250 at RS-232 levels.
5. Connect the kit supplied Ethernet cable from the Ethernet connector X7 on the Carrier
Board to your network hub, router, or switch. If you do not have an Ethernet connection
available you can postpone this step until Chapter 3.7. You will be able to boot the Linux
kernel without the need for Ethernet connectivity in this chapter of the QuickStart.
6. Start your favorite terminal software (such as minicom or komport) on your Linux host and
configure it for 115200 baud, 8 data bits, no parity, and 1 stop bit (8n1) with no handshake.
7. Plug the kit supplied 5V power adapter into the power input connector X10 on the Carrier
Board. You will see something similar to the following in the terminal output window:
PhytecLPC3250board
Builddate:Dec4200809:45:09
phy3250>
8. This is the output of the Stage 1 Loader. Test that your terminal session is working
correctly by typing info at the Stage 1 Loader prompt and hitting Enter. You will see a
bunch of system information dumped to the terminal window if everything is working
correctly. If you are unable to type anything at the Stage 1 Loader prompt, check that you
have setup the terminal software correctly per step 6 and that handshaking has been
disabled.
In this chapter you will set up the phyCORE-LPC3250 Rapid
Development Kit to connect to your host Linux PC. Afterwards you will
boot the pre-built images that come shipped on the SD card by
flashing them to the SOM. At the end of this chapter you will have a
fully functioning Linux system on the phyCORE-LPC3250 SOM.
15 min
You are now ready to begin booting the pre-built images that come with your SD card.

Chapter 2: Getting Started
© PHYTEC America LLC 2009 5
L-715e_0
2.2 Booting the Pre-built Images
The following pre-built images are included on the SD card contained in the kit.
1. ubt-qs.bin -- Das U-Boot 1.3.3-1, universal bootloader
2. uimg-qs -- Linux kernel with LCD support
3. rootfs -- Linux root file system in jffs2 format suitable for placement in NAND Flash
(openssh and Apache Web Server installed).
In this part of the QuickStart U-Boot, the Linux kernel image, and the root file system images will all
be written to the on-board NAND Flash.
1. Return to the Stage 1 Loader prompt in your terminal output window and type ls to get a
list of files on the SD card. You should see the files listed above.
2. Execute the following command to load the U-Boot binary image from the SD card into
SDRAM at 0x83fc0000:
phy3250>loadblkubt‐qs.binraw0x83fc0000
3. Execute the following command to save the U-Boot image to NAND Flash:
phy3250>nsave
4. Execute the following command to configure the auto boot settings to automatically fetch
the U-Boot binary from flash into SDRAM at 0x83fc0000 and then execute it:
phy3250>abootflashraw0x83fc0000
5. Execute the following command to change the Stage 1 Loader prompt to “phy3250-linux>”
and the boot delay to 2 seconds:
phy3250>promptphy3250‐linux>2
6. Execute the following command to load the Linux kernel image into SDRAM at
0x80100000:
phy3250‐linux>loadblkuimg‐qsraw0x80100000
7. Now type boot at the Stage 1 Loader prompt. You will see something similar to the
following output:
U‐Boot1.3.3(Feb102009‐15:44:53)
DRAM:64MB
NAND:64MiB
***Warning‐badCRCorNAND,usingdefaultenvironment
In:serial
Out:serial
Err:serial
uboot>
8. The bad CRC warning is normal. This is indicative that the current environment variables
that U-Boot attempted to read from NAND Flash were bad, or non-existent. Since the

Chapter 2: Getting Started
© PHYTEC America LLC 2009 6
L-715e_0
board is new the environment variables haven’t been written to NAND yet, and are non-
existent. This CRC warning will come up until a saveenv command is executed in U-Boot.
This will be done shortly.
9. The next step is to use U-Boot to write the Linux kernel to flash. Execute the flash_kernel
command to write the kernel to flash:
uboot>runflash_kernel
10. Reboot the board by pressing the reset button S1 on the Carrier Board. Press any key in
your terminal window to stop the auto boot process, arriving at a Stage 1 Loader prompt.
11. Load the Linux file system image into SDRAM and boot U-Boot again:
phy3250‐linux>loadblkrootfsraw0x80100000
phy3250‐linux>boot
12. U-Boot will come up again and stop at the prompt. Execute the flash_rootfs command to
write the root file system image to flash:
uboot>runflash_rootfs
13. Configure the boot command to tell U-Boot to boot the Linux kernel image from NAND
Flash:
uboot>setenvbootcmd${boot_nand}
14. Now save the environment variables to NAND Flash. This will get ride of that CRC error
that comes up every time U-Boot boots and tries to read the non-existent environment
variables in NAND Flash.
uboot>saveenv
15. Reboot the board again by pressing the system reset button S1 on the Carrier Board. If
everything was done correctly the board should boot completely into Linux, arriving at a
root prompt. Note that the first time the board is booted it will takes a little while for the
SSH server to generate new keys. Subsequent boots should be faster.
Make sure you wait for the autoboot message to come up in the terminal window before hitting
any key to stop the boot process. This is especially important when the boot jumper (JP21) is
installed and the board attempts to boot over UART5 after reset. Pressing a key during the
UART5 boot will fool the boot loader into thinking a UART boot is occurring, causing an invalid
boot process, and the board will reset.
Note that the loading process will take several seconds. No status messages are printed to the
screen during this time.
You have successfully booted the pre-built images included on the SD card.

Chapter 3: Getting More Involved
© PHYTEC America LLC 2009 7
L-715e_0
3 Getting More Involved
3.1 Installing the Linux Target Image Builder (LTIB)
The Linux Target Image Builder (LTIB) is a tool that integrates the build and configuration of the
mutliple software packages and components required for a typical embedded Linux distribution.
LTIB greatly reduces the complexity of gathering, configuring, and building all of these required
components.
For the phyCORE-LPC3250 Linux package, the primary components are:
• Das U-Boot -- the universal bootloader
• Linux kernel -- the compressed kernel image
• Linux file system -- the filesytem containing modules, executables, configuration files,
etc...
• arm-(vfp)-linux-gnu toolchain -- cross-toolchain built to support the ARM926EJ-S
processor (with VFP)
LTIB is reponsible for building U-Boot, the Linux kernel, and the root file system. The ARM cross-
toolchain is not built by LTIB and must be supplied as a seperate, pre-built component. This
toolchain is supplied with the phyCORE-LPC3250 Linux package.
Installing LTIB is a very easy process. To get started you must download the netinstall script from
http://www.bitshrine.org. This can be done using the wget command. Open a new shell window
and execute the following sequence of commands in your base home directory:
1. Change to your base home directory by typing cd ~ at the shell prompt.
2. Create a subdirectory for LPC3250 related development and change into the new
directory:
~>mkdirlpc3250
~>cdlpc3250
3. Download the netinstall script:
~/lpc3250>wgethttp://www.bitshrine.org/netinstall
In this chapter you will install the tools required to build an embedded
Linux system for the phyCORE-LPC3250 SOM. You will then be
guided through building the boot loader, Linux image, and root file
system. Later on in the chapter you will learn how to deploy the
images to the SOM using a variety of methods. This chapter will also
guide you through configuring your host Linux PC for rapid
development via TFTP and NFS. When you are finished with this
chapter you will know how to build Linux images from scratch, add a
variety of useful software components, and deploy the images using a
variety of methods.
1-3 hr

Chapter 3: Getting More Involved
© PHYTEC America LLC 2009 8
L-715e_0
4. Run the netinstall script:
~/lpc3250>perlnetinstall
5. You will be prompted for an install path. For the purposes of this document the install path
is /home/<username>/lpc3250/ltib-qs/. To avoid confusion later on in this QuickStart you
should use the exact same directory. If you decide to use something else, remember to
change all references to this path when appropriate.
You will likely encounter a build failure notifying you that you do not have sudo permissions to
execute rpm commands as root without a password. For the LTIB install, this is required.
Follow the instructions given in the error output to enable sudo permissions to execute rpm
commands. You must run visudo as root. You can either do this by using sudo:
~/lpc3250>sudo/usr/sbin/visudo
And type in the root password. Or you can do this by opening a root shell and typing:
/home/<username>/lpc3250#visudo
Either method will allow you to edit the sudoers file.
For this QuickStart, the following edit was added to the very end of the sudoers file:
<username>ALL=NOPASSWD:/bin/rpm,/opt/ltib/usr/bin/rpm
Now restart the install process by executing the perlnetinstallscript again.
From here LTIB will download from bitshrine.org and install automatically. Depending on the
speed of your host machine and internet connection, this may take several minutes, or several
hours. Be aware that LTIB will not show its progress while it is installing; be patient. After
install has completed the build will return to a prompt. You are now ready to begin configuring
LTIB for a phyCORE-LPC3250 Linux distribution build.

Chapter 3: Getting More Involved
© PHYTEC America LLC 2009 9
L-715e_0
3.2 Building U-Boot, the Linux Kernel, and Root File System
LTIB completely automates building U-Boot, the Linux kernel, and the root file system. LTIB allows
configuration of the bootloader, kernel, and installed packages through a menu driven system. To
begin the build process:
1. Return to the shell window used to install LTIB. Change directories to the LTIB install path
and execute LTIB like so:
~/lpc3250>cdltib‐qs
~/lpc3250/ltib‐qs>./ltib
2. A menu will come up instruction you to select the platform. Use the cursor keys to navigate
the menu. Choose the Phytec 3250 board with the NXP LPC32XX SoC from the list.
Select Exit and say Yes to saving the new configuration.
3. The LTIB configuration menu will appear allowing you to configure all of the build options
LTIB controls. Scroll down to the Configure the kernel option and unselect this with the
spacebar. Select Exit and say Yes to saving the new configuration.
LTIB will begin to download and build U-Boot, the kernel, and root file system. The entire process
may take several minutes, or several hours depending on the speed of your host system and
internet connection. The build process may pause at several points as package sources are
downloaded from the internet. This is normal.
If all goes well LTIB will return to a prompt with a Build Succeeded message. Once this process
has finished U-Boot, the Linux kernel, and the root file system have all been built and assembled
and are ready to be deployed on the phyCORE-LPC3250 Rapid Development Kit. If you received
a Build Succeeded message you can skip the following paragraphs and table and continue to the
next section.
If the build process fails then restart the LTIB configuration menu and check that the default
settings are correct. See Table 3-1 below for default configuration options. The table only contains
the items which must be checked. To restart the LTIB configuration menu, type the following:
~/lpc3250/ltib‐qs>./ltib‐‐configure
If the build process fails then restart the LTIB configuration menu and check that the default
settings are correct. See Table 3-1 below for default configuration options. The table only
contains the items which must be checked. To restart the LTIB configuration menu, type the
following:
~/lpc3250/ltib‐qs>./ltib‐‐configure
Note that LTIB will only enter the configuration menu the first time after install when typing just
./ltib at the prompt. Thereafter typing just ./ltib at the prompt will rebuild modified source. To
enter the configuration menu the command line switch --configure must be used, as shown
above.

Chapter 3: Getting More Involved
© PHYTEC America LLC 2009 10
L-715e_0
Note that LTIB will only enter the configuration menu the first time after install when typing just ./
ltib at the prompt. Thereafter typing just ./ltib at the prompt will rebuild modified source. To enter
the configuration menu the command line switch --configure must be used, as shown above.
Table 3-1. LTIB Configuration Menu Default Settings
LTIB Option Setting
Systemfeatures [*]cachetargetrpms
TargetClibrarytype (X)glibc
Clibrarypackage (X)fromtoolchainonly
Toolchaincomponentoptions [*]libcsharedlibraries
[*]c++sharedlibraries
[*]libgcc*.so*
Toolchain (X)gcc‐3.4.5‐glibc‐2.3.6(soft‐float)
EnteranyCFLAGSforgcc/g++ ‐fsigned‐char‐msoft‐float‐O3
bootloaderchoice (X)u‐boot1.3.3forthePhytec3250
board
u‐bootflags <empty>
kernel (X)Linux2.6.27.8forLPC3250/Phytec
3250
Alwaysrebuildthekernel [*](checked)
Producecscopeindex [](unchecked)
Kernelpreconfig linux‐2.6.27.8‐phy3250.config
Includekernelheaders [](unchecked)
Configurethekernel [](unchecked)
Leavethekernelsourcesafterbuild‐
ing
[*](checked)
Packagelist Checkonly:
[*]busybox
[*]moduledependencies
[*]mp3play
[*]mtd‐utils
[*]Skeletonbasefiles
TargetSystemConfigurationOptions Checkonly:
[*]startnetworking
[*]startsyslogd/klogd
TargetImageGenerationOptions Targetimage:(NFSonly)

Chapter 3: Getting More Involved
© PHYTEC America LLC 2009 11
L-715e_0
3.3 Setting up TFTP
TFTP is a “trivial” file transfer protocol used to transfer files across networks. Although TFTP is not
absolutely required for working with Linux on the phyCORE-LPC3250, it is highly recommended
during the building and development phase. TFTP allows the phyCORE-LPC3250 to be
configured to always load the latest build of the Linux kernel image from your host machine,
without the need to continually reflash the target board or update kernel image in some other time
consuming fashion.
The setup of the TFTP server will only be described for the openSUSE 11.1 distribution, although
it will likely apply to earlier versions of openSUSE. Because of the vast number of Linux
distributions out there, describing the setup of a TFTP server for other Linux distributions is out of
the scope of this document. Please refer to one of the many guides available on the internet for
your particular distribution.
To begin setup:
1. Start YaST and enter the root password.
2. Under the Software section on the left in the YaST Control Center, click Software
Management.
3. In the Search field, type tftp and click Search.
4. Check tftp and yast2-tftp-server under the Package list.
5. Click Accept in the lower right hand corner to install the packages.
6. After installation has completed close the Software Management window wand click on
the Network Services section on the left in the YaST Control Center.
7. Click the TFTP Server component to being configuring the TFTP server.
8. Click the Enable radio button and leave the Boot Image Directory as /tftpboot.
9. Check the Open Port in Firewall checkbox to prevent the firewall from blocking the TFTP
server access.
10. Click OK to accept the configuration.
Make sure you resolve dependencies required to complete the package install if prompted to
do so.
Your TFTP server should now be enabled and ready to use.

Chapter 3: Getting More Involved
© PHYTEC America LLC 2009 12
L-715e_0
3.4 Setting up NFS
NFS allows you to mount a remote network disk as if it were a local disk thus providing easy
sharing of files over a network. For this QuickStart NFS is used to access the root file system on
the host Linux machine. That is, the root file system for the phyCORE-LPC3250 SOM will actually
be located on the remote host Linux machine. This enables easy access and modificatios to the
root file system during development. Although NFS is not absolutely required for working with
Linux on the phyCORE-LPC3250, it will greatly decrease development time.
The setup of the NFS server will only be described for the openSUSE 11.1 distribution, although it
will likely apply to earlier versions of openSUSE. Because of the vast number of Linux distributions
out there, describing the setup of a NFS server for other Linux distributions is out of the scope of
this document. Please refer to one of the many guides available on the internet for your particular
distribution.
To begin setup:
1. Start YaST.
2. Under the Software section on the left in the YaST Control Center, click Software
Management.
3. In the Search field, type nfs and click Search.
4. Check the nfs-kernel-server, yast2-nfs-common, and yast2-nfs-server packages and click
Accept to install.
5. Close the Sofware Management interface and return to YaST. In the Network Services
section, click the NFS Server to begin configuration.
6. Under NFS Server choose Start.
7. Under Firewall choose Open Port in Firewall. Click Next.
8. Click the Add Directory button and type the complete path to your LTIB root file system.
For this QuickStart the following path was used: /home/cday/lpc3250/ltib-qs/rootfs.
9. If the Add Host window does not appear automatically, then click the Add Host button and
type the IP address of the phyCORE-LPC3250 SOM into the Host Wild Card box. Make
sure you select a free IP address available on your network. Ask your network
administrator for assistance if you are unsure of how to obtain a free IP address.
10. In the Options box type the following configuration options:
rw,no_root_squash,sync,no_subtree_check
11. Click OK and then click Finish for the settings to take effect. Close the YaST Control
Center.
Make sure you resolve dependencies required to complete the package install if prompted to
do so.
Your NFS is ready to be accessed by the SOM.

Chapter 3: Getting More Involved
© PHYTEC America LLC 2009 13
L-715e_0
3.5 Overview of the Boot Process
Before proceeding into the following sections it is helpful to first have an understanding of the
entire boot process and the software components required to boot and run Linux on the
phyCORE-LPC3250.
There are six software components that are involved in bringing Linux to life on the phyCORE-
LPC3250. A brief description of each is given below.
1. LPC3250 on-chip bootstrap software -- This software component is part of the LPC3250
SoC itself. It is the very first piece of software that is executed after a system reset/power
cycle. The bootstrap software is capable of booting code from several sources, including
UART, SPI, external memory bus, and NAND Flash.
2. Kickstart Loader (KS) -- This software component is stored in the NAND Flash at block 0
and is loaded into IRAM and executed by the on-chip bootstrap software. The Kickstart
Loader does some GPIO initialization and then proceeds to load the Stage 1 Loader into
IRAM and transfer execution to it.
3. Stage 1 Loader (S1L) -- This software component is stored in the NAND Flash and is
loaded into IRAM and executed by the Kickstart Loader. The S1L does additional low level
initiaization, including SDRAM, and allows interaction with the outside world via a
command line driven interface over a terminal session. The S1L is responsible for loading
U-Boot into SDRAM and transfering execution to it.
4. Das U-Boot -- This software component is one of the leading bootloaders used to boot the
Linux kernel. It is feature rich supporting environment variables, NAND Flash, and
Ethernet (TFTP) to name a few. U-Boot is responsible for loading the Linux kernel into
SDRAM and transfering execution to it.
5. Linux Kernel -- This is the monolithic kernel that is the Linux Operating System.
6. Root File System -- This software component contains all of the data associated with
particular software components installed on the system, configuration files, device nodes,
etc... that are available to a user when the operating system is running.
After a reset the normal boot procedure becomes:
1. On-chip bootstrap executes and boots the Kickstart Loader.
2. Kickstart Loader executes and boots the Stage 1 Loader.
3. Stage 1 Loader executes and boots Das U-Boot.
4. Das U-Boot executes and boots the Linux kernel.
The Kickstart Loader, Stage 1 Loader, and Das U-Boot are relatively stable components that do
not require frequent modifications or rebuilds. During development these components are always
flashed to the SOM because of their static, stable nature.
The Linux kernel and root file system can change often during system development and debug.
Because of this it is desirable to have these components loaded dynamically onto the target SOM
until they’ve reached a mature, stable status that is unlikely to change. Dynamic loading and
access of the Linux kernel and root file system is done via TFTP and NFS, as explained in the
previous sections of this document.

Chapter 3: Getting More Involved
© PHYTEC America LLC 2009 14
L-715e_0
Now that a better understanding of the boot process and components required to bring Linux up on
the phyCORE-LPC3250 has been presented, you are ready to place U-Boot into the NAND Flash,
followed by booting the Linux kernel for the first time with the newly compiled kernel and root file
system from Chapter 3.2.
3.6 Placing U-Boot into NAND Flash
The phyCORE-LPC3250 SOM comes pre-flashed with the Kickstart and Stage 1 Loaders, so you
do not need to flash these software components. U-Boot does not come pre-flashed to the SOM
and must be flashed in order to boot Linux.
After U-Boot is flashed to the board, the system can be booted by fetching the latest kernel image
(uImage) over TFTP and mounting the latest root file system over NFS.
At later points in this QuickStart you will be provided instructions for flashing the kernel and root file
system to the board. However, during development of your target system the need to rebuild the
kernel and file system will occur frequently. TFTP and NFS accelerate the development process.
Reflashing the newest kernel and root file system to the SOM after every new build would be very
cumbersome and time consuming. Das U-Boot, unlike the kernel and file system, will probably not
need to be reconfigured after it has been built. For this reason U-Boot is the only image that is
initially flashed to the SOM in the development process.
If you followed Chapter 2.2 and booted the pre-built images shipped on the SD Card, then you’ve
already flashed U-Boot to the SOM. Unless you have custom needs for U-Boot it is unlikely that
you need to flash the version you built in Chapter 3.2. If you do have custom U-Boot requirements,
or are interested in seeing the version you built in action, follow the steps below:
To begin flashing U-Boot to the SOM:
1. Copy the u-boot.bin file built in the previous steps of this QuickStart from the root file sys-
tem /boot directory to your SD card. You can use the SD card that came with the kit. For
this QuickStart u-boot.bin is located at the following location: /home/<username>/
lpc3250/ltib-qs/rootfs/boot/u-boot.bin.
2. Place the SD card into the SD/MMC connector X15 on the phyCORE-LPC3250 Carrier
Board.
3. Switch to minicom, or the applicable terminal software you’ve chosen for this QuickStart.
4. Press the reset button S1 on the phyCORE-LPC3250 Carrier Board for a clean reboot. If
you’ve previously flashed U-Boot to the board make sure you hit the space bar to stop the
boot process in the Stage 1 Loader.
5. You will see something similar to the following in your terminal output window:
PhytecLPC3250board
Builddate:Dec4200809:45:09
phy3250>
6. Type ls at the prompt to get a list of the files on the SD card. You should see the U-
BOOT.BIN binary that you copied to the SD card in the list of files.
7. Type the following at the prompt to load the u-boot.bin binary into SDRAM for subsequent
writing to NAND Flash:

Chapter 3: Getting More Involved
© PHYTEC America LLC 2009 15
L-715e_0
phy3250>loadblku‐boot.binraw0x83fc0000
8. Type nsave to write the image to flash.
9. Configure the autoboot settings by typing the following:
phy3250>abootflashraw0x83fc0000
10. Configure the prompt string and boot delay (2 seconds) by typing the following:
phy3250>promptphy3250‐linux>2
11. Erase the environment variables that were saved to NAND Flash (stored in blocks 90
through 99) when you flashed the U-Boot binary that was included on the SD Card:
phy3250>erase90100
12. Cycle power, or press the RESET button S1 to reset the board. You should see something
similar to the output below on your terminal window.
PhytecLPC3250board
Builddate:Dec4200809:45:09
Autobootinprogress,pressanykeytostop...
U‐Boot1.3.3(Feb102009‐15:44:53)
DRAM:64MB
NAND:64MiB
***Warning‐badCRCorNAND,usingdefaultenvironment
In:serial
Out:serial
Err:serial
uboot>
The bad CRC warning is normal. This is indicative that the current environment variables
that U-Boot attempted to read from NAND Flash were bad, or non-existent. Since you
erased the environment variables that were stored in the previous step, they are non-
existent. This CRC warning will come up until a saveenv command is executed in U-Boot.
This will be done shortly in the next section when U-Boot is configured to boot the Linux
kernel.
You have successfully placed U-Boot into the NAND Flash and booted the system.

Chapter 3: Getting More Involved
© PHYTEC America LLC 2009 16
L-715e_0
3.7 Configuring U-Boot to Boot Linux over TFTP
With U-Boot flashed to the board you are ready to boot the system over TFTP and NFS for the first
time. To do this U-Boot must be configured with several environment variable parameters to direct
it where to boot the Linux images from, and to tell Linux how to mount the root file system.
Execute the following steps to configure U-Boot:
1. Reset the board by cycling power or pressing the reset button S1 on the Carrier Board.
2. At the U-Boot prompt execute the following set of commands:
uboot>setenvbootfileuImage
uboot>setenvbootcmd‘tftpboot;bootm’
uboot>setenvbootdelay1
uboot>setenvloadaddr0x80100000
3. Execute the following U-Boot commands to configure the TFTP server IP address:
uboot>setenvserverip<tftpserverIP>
4. Now configure the boot arguments that are passed to the Linux kernel during boot:
uboot>setenvbootargs‘console=ttyS0,115200n81root=/dev/nfsrw
nfsroot=<NFSserverIPaddress>:/home/<username>/lpc3250/ltib‐qs/rootfs
ip=<SOMIPaddress>init=/sbin/init’
5. Set the IP address of the SOM to whatever IP you’ve chosen from the free pool of IP
addresses:
uboot>setenvipaddr<SOMIPaddress>
6. Now type saveenv at the U-Boot prompt to save the environment variables to NAND
Flash. This will prevent you from having to type the environment variables into U-Boot
after every reset and it will also remove the CRC warning error that you received the first
time U-Boot was booted.
7. At this point the system is almost ready to boot. The last step is to copy the kernel image
built in Chapter 3.2 to the tftpboot directory. Since the /tftpboot directory is likely owned by
root and restricted to writes only by the owner you will need to modify this to allow writing
by normal users. Do this by executing the following commands as root:
#chown<username>/tftpboot
#chgrpusers/tftpboot
8. Now copy the kernel image to the tftpboot directory by executing the following command:
~/lpc3250>cp/home/<username>/lpc3250/ltib‐qs/rootfs/boot/uImage/
tftpboot
Note that after LTIB completes the build process the kernel image is placed in the root file
system under the boot/ directory as the file uImage.

Chapter 3: Getting More Involved
© PHYTEC America LLC 2009 17
L-715e_0
9. You are now ready to boot the system for the first time. If everything has been set up
correctly the system should boot all the way to a root prompt upon reset. Press the reset
button S1 on the Carrier Board to boot the system into Linux.
3.8 Placing the Kernel into NAND Flash
Placing the kernel into NAND Flash allows booting the system without the need for the TFTP
hosted kernel image. This is the most common place to put the kernel in a standalone application.
Normally development is done using a TFTP hosted kernel image until the configuration has
become more stable and is unlikely to change frequently. Once stable, the kernel image can be
moved to NAND Flash.
Placing the kernel image into the NAND Flash is accomplished using the U-Boot NAND write
commands. The kernel is loaded into SDRAM using TFTP and then flashed to the board. To begin:
1. Copy the uImage kernel image file from the LTIB rootfs/boot directory to your TFTP-
BOOT directory. For this QuickStart the uImage file is located at /home/<username>/
lpc3250/ltib-qs/rootfs/boot/uImage.
2. Reboot your board by pressing the reset button and stop the boot process in U-Boot by
hitting any key at the Hit any key to stop autoboot message.
3. Load the kernel image into SDRAM using the tftpboot command in U-Boot as follows:
uboot>tftpboot0x80100000uImage
4. Erase the area of NAND Flash reserved for the kernel image partition:
uboot>nanderase0x1900000x270000
The 0x190000 is the offset of the beginning of kernel image partition, and the 0x270000 is
the size of the partition.
5. The next step is to write the kernel image into NAND Flash. This is done using the nand
write.jffs2 command in U-Boot. This command takes three parameters:
nandwrite.jffs2<addr><offset><size>
Where <addr> is the address of the source data (0x80100000 in this case), <offset> is
the offset in NAND Flash to begin writing data, and <size> is the amount of data to write.
The offset will always be 0x190000. The size will depend on the size of your kernel image
you’ve created. The U-Boot tftpboot command will report the size of the image transfered
after it is completed. You should see something similiar to the following when the tftpboot
tranfer is completed:
Bytestransferred=1701080(19f4d8hex)
Given that you are likely to rebuild the kernel several times during your development process it
is a good idea to add a command to the LTIB configuration menu that copies the newly built
kernel image to your TFTP boot directory after every build. You can do this by entering the
LTIB configuration menu (typing ./ltib --configure in the base LTIB directory) and selecting the
Target Image Generation Options menu item, and then the Run a command after building the
target image option and using cp /home/<username>/lpc3250/ltib-qs/rootfs/boot/uImage /
tftpboot as the argument.