ページ1に含まれる内容の要旨
1
User’s Manual for the
Boundary Devices
Neon
R board
December 28, 2005
December 28, 2005 Revision 2.8
ページ2に含まれる内容の要旨
2 1 Revision History Date Revision Description 2005-03-20 1.0 First draft 2005-04-03 1.3 Added minidebug instructions 2005-06-11 2.0 Added display config, networking notes 2005-06-27 2.1 Added connector pin-outs (Figure 2) 2005-07-23 2.2 Updated U-Boot version 2005-08-09 2.3 Added notes on mac address command 2005-09-15 2.4 Bumped BSP revision 2005-10-21 2.5 Bumped U-Boot revision 2005-11-07 2.6 Added userland build notes 2005-11-09 2.7 Added rootfs usage notes and list of supported li- braries 2
ページ3に含まれる内容の要旨
CONTENTS 3 Contents 1 Revision History 2 2 Intended Audience 5 3 Overview of features 5 4 Hardware feature 5 4.1 Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.2 Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.3 Connector reference . . . . . . . . . . . . . . . . . . . . . . . 6 4.4 Electrical characteristics . . . . . . . . . . . . . . . . . . . . . 8 5 Software features 9 5.1 Das U-Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5
ページ4に含まれる内容の要旨
CONTENTS 4 6.2.3 Control Keys . . . . . . . . . . . . . . . . . . . . . . . 30 6.2.4 Blast protocol . . . . . . . . . . . . . . . . . . . . . . . 30 6.2.5 Quick-start download and burn . . . . . . . . . . . . . 30 6.3 TeraTerm blast extensions . . . . . . . . . . . . . . . . . . . . 32 6.4 Using U-Boot Networking . . . . . . . . . . . . . . . . . . . . 33 7 Configuration Notes 34 7.1 Display configuration . . . . . . . . . . . . . . . . . . . . . . . 34 7.1.1 What display is currently selected? .
ページ5に含まれる内容の要旨
5 2 Intended Audience This document aims to provide the information needed to integrate the Neon
R board into your application. As such, it addresses both hardware and software integration. 3 Overview of features The following are highlights of the Neon
R board. • Available with Windows Ce or Linux Operating Systems • Full featured Boot Loader for custom startup • 400 MHz Intel PXA-255 CPU • 32 or 64MB SDRAM • 8 or 32MB Intel StrataFlash (tm) EEPROM • Silicon Motion SM 501 Graphics Controller
ページ6に含まれる内容の要旨
4.2 Mounting 6 Figure 1: Neon board 4.2 Mounting R R TheNeon
boardmeasures2.75”by6.75”,slightlylargerthantheHitachi
6.2” display, to allow for easy mounting. There are four mounting holes 1/4” from each edge in each of the four corners, and the holes are 1/8” in diameter. 4.3 Connector reference The following is a list of all connector part numbers used on the Neon
R platform for use in identifying mating parts for your application. Note that Boundary Deviceswill periodically switch vendors f
ページ7に含まれる内容の要旨
4.3 Connector reference 7 1 Figure 2: Connector Pin-outs December 28, 2005 Revision 2.8 A B C D E 5 WIRE TOUCH SCREEN J16 AND J16 ARE RGB OUTPUT FOR TFT PANEL PIN1 TOP RIGHT PIN2 TOP LEFT PIN3 BOTTOM LEFT PIN4 BOTTOM RIGHT PIN 5 SENSE JTAG CONNECTOR HD15 R,G,B ANALOG CONNECTOR INVERTER CONNECTOR 4 4 UART2 PIN 1 IS GPO(GENERAL PURPOSE OUTPUT) PIN 1 POWER PIN 2 DRY CONTACT OUTPUT PIN2 DATA OUT PIN 3 DRY CONTACT OUTPUT PIN3 DATA IN PIN 4 GPI(GENERAL PURPOSE INPUT) PIN4 GROUND PIN 5 GPI(GENERAL PURP
ページ8に含まれる内容の要旨
4.4 Electrical characteristics 8 Description Manufacturer Part USB Master FCI 87520-0010B USB Slave SINGATRON KS-001-BNW I2C FCI 68897-001 Ethernet Halo HFJ11-2450E Stereo Audio Singatron 2SJ-43723N13 Backlight inverter Molex 53048-0210 MMC/SD AVX 14 5638 009 511 862 TFT Display Touch Screen Molex 52207-0590 Serial Port FCI 68897-001 JTAG Molex 53048-0810 4.4 Electrical characteristics December 28, 2005 Revision 2.8
ページ9に含まれる内容の要旨
9 5 Software features As provided by Boundary Devices, the Neon
R board supports either Win- dows CE 5
R or Linux. To simplify the installation of either, the Das U-Bootboot loader is in- stalled on our evaluation boards, and two MMC cards are shipped to allow the use of either operating system. 5.1 Das U-Boot The Das U-Boot Boot Loader is a full-featured loader for either Linux or Windows CE that supports a wide variety of options for loading your Op- erating System and application. Boundary
ページ10に含まれる内容の要旨
5.1 Das U-Boot 10 Base/diffutils Devel/binutils Devel/gcc Devel/make Devel/patchutils Utils/bzip2 Web/wget The second requirement for building is the X-Scale cross-compiler itself. The GNUARM project provides a wealth of information needed to build a cross-compilerforARMprocessors. Thankfully, italsoprovidesaninstaller. As of this writing, Boundary Devices currently uses the GCC-3.4.3 package for Cygwin. 5.1.3 General build steps Quick start: wget http://easynews.dl.sourceforge.net/sourceforge/u-
ページ11に含まれる内容の要旨
5.1 Das U-Boot 11 your application. Ingeneral,thefileu-boot-1.1.2/include/configs/neon.hdefinesthese choices. In particular, the distributed copy currently expects a Windows BMP file named bdlogo.bmp to be present on the MMC card and writes it to the display, then loads an operating system image from a file named nk.nb0 to RAM address 0xa0030000 and executes it. Both of these are defined by the lines which resemble this: #define CONFIG_BOOTCOMMAND "mmcinit; " \ "fatload mmc 0 a0000000 init.scr ; " \
ページ12に含まれる内容の要旨
5.1 Das U-Boot 12 5.1.5 U-Boot Memory layout ThefollowingdiagramshowsthegenerallayoutofRAMwithinDas U-Boot. 32K segment used for page tables. 0xA4000000 Page Tables 0xA3FF8000 Unused RAM 0xA3FF7FFF Unused High 0xA2000000 Extra space between Das U-Boot and 32MB 0xA1FFFFFF boundary Tail of 32MB The Das U-Boot image is loaded 1MB below 0xA1F00000+ the 32MB boundary Das U-Boot image 0xA1F00000 The heap and stack are allocated in space 0xA1EFF
ページ13に含まれる内容の要旨
5.1 Das U-Boot 13 5.1.6 U-Boot Init Script The Das U-Boot boot loader comes with scripting facilities in the form of the Hush parser and the autoscript command. You should notice when first compiling the package that the Boundary Devices sample uses this to defer most board initialization to the MMC card. It does this by setting the CONFIG BOOTCOMMAND environment variable as follows. #define CONFIG_BOOTCOMMAND "mmcinit; fatload mmc 0 a0000000 init.scr ; autoscr a0000000 " In English, this instruc
ページ14に含まれる内容の要旨
5.2 Windows CE 14 5.2 Windows CE As mentioned earlier, the Neon
R board ships with a runnable Windows CE 5.0 image on MMC card. A Board Support Package is also available and necessary to tailor the operating system for a given application. Thefollowingsectionsdescribetheprocessofproducinganimagematch- ing the one shipped with the Neon
R board. 5.2.1 Prerequisites and components R Most of the tools needed to create a bootable Windows CE 5
application fortheNeon
R boardareprovidedbyMicrosoft.
ページ15に含まれる内容の要旨
5.2 Windows CE 15 5.2.3 Building the demo The Platform Builder project used to construct our sample image may be found on the Boundary Devices web site. After installation of the BSP, this project may be copied to a new direc- tory within the WINCE500 PBWorkspaces directory and built using Plat- form Builder. C:\WINCE500\PBWorkspaces>md bdWeb C:\WINCE500\PBWorkspaces>cd bdWeb C:\WINCE500\PBWorkspaces\bdWeb>wget http://boundarydevices.com/bdWeb.pbxml --17:37:40-- http://boundarydevices.com/bdWeb.
ページ16に含まれる内容の要旨
5.3 Linux Support 16 5.3 Linux Support The Linux Environment for Boundary Devices boards consists of four pri- mary pieces, a toolchain, the kernel and device drivers, a user-space build tool based on PTXDist and a Javascript runtime used to demostrate the capabilities of the hardware. 5.3.1 Crosstool Linux Toolchain Before the kernel and applications can be built, it is first necessary to have a cross-compiler toolchain. The following examples show how we at Boundary Devices set up our toolchain
ページ17に含まれる内容の要旨
5.3 Linux Support 17 2 Notethatthiswilltakealooong time . Findsomethingelsetodowhile you wait. When complete, you should find a whole slew of programs in your /opt/crosstool/gcc-3.4.3-glibc-2.3.5/arm-xscale-linux-gnu/bin/di- rectory: -rwxr-xr-x 1 username cvsd 1900724 Jul 18 20:48 arm-linux-addr2line -rwxr-xr-x 2 username cvsd 1960214 Jul 18 20:48 arm-linux-ar -rwxr-xr-x 2 username cvsd 3339533 Jul 18 20:48 arm-linux-as -rwxr-xr-x 2 username cvsd 331791 Jul 18 21:35 arm-linux-c++ -rwxr-xr-x 1 use
ページ18に含まれる内容の要旨
5.3 Linux Support 18 GCC_DIR=gcc-3.4.3 GCC_EXTRA_CONFIG= Then, create a shell script named crosstool-0.37/contrib/newlib/arm-elf.sh with the following content. #!/bin/sh set -ex TARBALLS_DIR=/armArchives RESULT_TOP=/opt/crosstool export TARBALLS_DIR RESULT_TOP GCC_LANGUAGES="c,c++" export GCC_LANGUAGES # You should do the mkdir before running this, # and chown /opt/crosstool to yourself so you # don’t need to run as root. mkdir -p $RESULT_TOP # Build the toolchain. # Takes a couple hours and a c
ページ19に含まれる内容の要旨
5.3 Linux Support 19 5.3.4 Kernel 2.4.19 Arm-Linux kernel version 2.4.19 Linux kernel patches for ARM processors PXA Patches Intel PXA support for ARM-Linux Boundary Devices patches Boundary Devices support 5.3.5 Kernel 2.6 wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.11.11.tar.bz2 bzcat linux-2.6.11.11.tar.bz2 | tar xvf - wget http://boundarydevices.com/boundary-2.6.11.11-2005-11-17.patch.bz2 cd linux-2.6.11.11 bzcat ../boundary-2.6.11.11-2005-11-25.patch.bz2 | patch -p1 cp arch/a
ページ20に含まれる内容の要旨
5.3 Linux Support 20 5.3.6 Userland build tool As mentioned before, we at Boundary Devices use a variant of an older version of the PTXDist tool to keep track of the cross-compilation needs for various libraries. This allows inter-library dependencies to be expressed, and also allows the canonical source locations to be used during a build. This should really be better documented, but the short and simple build instructions are as follows. $ wget http://boundarydevices.com/userland_20051126.tar.
