Specifications

ManualsBrandsEmbest ManualsComputer equipmentAM3517

SOC8200

AM3517 Based 32-Bit Microprocessor

Quick Start Guide

Version 2.1

Jan 2014

Summary of content (98 pages)

PAGE 1
SOC8200 AM3517 Based 32-Bit Microprocessor Quick Start Guide Version 2.
PAGE 2
Copyright Statement:  SOC8200, CAN8200, SD8200-X, CAN8200-X, AU8200, VGA8200, USB8200-X, NET8200, ECOM-4, ECOM-8, E100 Module and their related intellectual property are owned by Shenzhen Embest Technology Co., Ltd.  AM3517 is a trademark of the TI Corporation.  Sourcery G++ Lite for ARM GNU/Linux is trademark of Codesourcery.  Microsoft, MS-DOS, Windows, Windows95, Windows98, Windows2000, and Windows embedded CE 6.0 are trademarks of the Microsoft Corporation.
PAGE 3
Table of Contents 1 Product Overview .............................................................. 1 1.1 Introduction ....................................................................1 1.2 Kit Contents ....................................................................1 1.3 Board Interfaces ..............................................................2 1.4 System Block Diagram .....................................................3 1.5 Physical Dimensions ...............................................
PAGE 4
3.2.10 PC104-40 .............................................................................. 16 3.2.11 Multifunctional Expansion Interface .......................................... 19 3.2.12 Can/485 Interface .................................................................. 20 3.2.13 UART (TTL) Interface .............................................................. 21 3.2.14 JTAG Interface ....................................................................... 22 4 Linux System .......................
PAGE 5
4.5 Linux System Deveplopment ........................................... 48 4.5.1 Install the cross compilation environment ................................... 48 4.5.2 The installation of other tools .................................................... 48 4.5.3 Adding environment variable ..................................................... 49 4.5.4 System complation .................................................................. 49 4.6 Linux System Customization .....................................
PAGE 6
Appendix 1: Driver Installation Of Linux USB Ethernet/RNDIS Gadget 73 Appendix 2: Making a Linux Boot Disk ................................ 76 Appendix 3: TFTP Server Setup .......................................... 81 Appendix 4: WinCE related resource links .......................... 83 Appendix 5: Expansion Board ............................................. 85 5.1 SOC8200-M Evaluation Suite........................................... 85 Appendix 6: Interface Board ......................................
PAGE 7
1 Product Overview The document details development with the SOC8200, the hardware specification, features, and software development. 1.1 Introduction The SOC8200 is an industrial evaluation kit designed and manufactured by Embest Technology Co., Ltd. The SOC8200 is based on the Texas Instruments AM3517 processor. This processor is integrated with a 600Mhz ARM Cortex-A8 Core which is used as a dedicated industrial signal processor.
PAGE 8
1.
PAGE 9
1.
PAGE 10
1.
PAGE 11
2 Hardware Features 2.1 SOC8200 Single Board Computer 2.1.1 Processor  AM3517 industrial applications processor  600MHz ARM Cortex-A8 Core  NEON SIMD Coprocessor  POWERVR SGX Graphics Accelerator  16KB I-Cache，  16KB D-Cache，  256KB L2-Cache，  112KB ROM，  64KB Shared SRAM 2.1.2 Memory  256MB DDR2 SDRAM，32bit  256MB NAND Flash，8bit  4MB NOR Flash，16bit 2.1.3 Signals Routed to Pins  5-wire Debug serial port (RS232)  5-wire serial port (TTL)  Two USB 2.
PAGE 12
 1-channel CAN bus  10/100Mbps Ethernet port  SD/MMC card  Multi-functional expansion interface (McBSP, IIC, McSPI, TV-OUT)  PC104 expansion interface (GPMC Bus, MMC, USB, McSPI, UART1, Clock, HDQ)  JTAG interface 2.2 SOC8200 Expansion Board 2.2.1 Audio/Video Interfaces  Audio input port  Stereo audio output port  15-pin standard VGA output interface  Buzzer 2.2.
PAGE 13
 Input Voltage: +5V (Core board)  +12V (Expansion board)  Layers: 8  Working Temperature: -40 ~ 85°C Page | 7
PAGE 14
3 Hardware Details 3.1 Hardware Introduction The SOC8200 board has onboard:  256MB DDR2 SDRAM,  256MB Nand Flash, and  4MB Nor Flash It extends various functions through pins including:  Serial port,  Ethernet,  CAN,  RS485,  SD/MMC card,  CF card,  Audio In/Out,  Camera,  LCD,  USB Host,  USB Device,  Expansion connector and  JTAG. Embest has designed an expansion board and several function interface boards for the SOC8200.
PAGE 15
For a detailed schematic of the SOC8200 please refer to:  http://www.armkits.com/download/soc8200sch.pdf Note:  The schematic is only for reference, we do not offer any technical support related to its use or development. 3.2 Hardware Interfaces 3.2.
PAGE 16
3.2.2 Network interface SOC8200 is a 10M/100M adaptive network interface PIN Description 1 GND 2 VCC_IO 3 TXN 4 TXP 5 GND 6 RXN 7 RXP 8 LED2/NINTSEL 9 LED1/REGOFF 10 GND 3.2.
PAGE 17
PIN Description 12 GND 13 CAM_PCLK 14 GND 15 CAM_HS 16 CAM_VS 17 VCC_IO 18 IIC3_SDA 19 IIC3_SCL 20 GND 3.2.4 MMC Interface PIN Description 1 VCC_IO 2 MMC1_CLK 3 MMC1_CMD 4 MMC1_D0 5 MMC1_D1 6 MMC1_D2 7 MMC1_D3 8 MMC1_CD 9 MMC1_WP 10 GND 3.2.
PAGE 18
2 N/A 3 R1IN 4 T2OUT 5 T1OUT 6 R2IN 7 N/A 8 N/A 9 GND 10 N/A 3.2.6 Analog IO Interface PIN Description 1 CH7 2 CH6 3 CH5 4 CH4 5 CH3 6 CH2 7 CH1 8 CH0 9 GND 10 VCC_IO 3.2.
PAGE 19
3 CH5 4 CH4 5 CH3 6 CH2 7 CH1 8 CH0 9 GND 10 VCC_IO 3.2.
PAGE 20
PIN Description 18 DSS_D10 19 GND 20 N/A 21 DSS_D0 22 DSS_D1 23 DSS_D2 24 DSS_D3 25 DSS_D4 26 GND 27 DSS_DEN 28 VCC_IO 29 VCC_IO 30 N/A 31 N/A 32 Y+ 33 X- 34 Y- 35 X+ 36 LCD_PEN 3.2.
PAGE 21
PIN Description 5 VCC_IO 6 VCC_IO 7 GND 8 SYS_RST 9 POWER_RST 10 SYS_CLKOUT2 11 SYS_CLKOUT1 12 HDQ_SIO 13 SYS_32K 14 GND 15 IRQ 16 GPIO58 17 GPIO57 18 GPIO56 19 GPT11 20 GPT10 21 GPT9 22 IIC1_SDA 23 IIC1_SCL 24 GND PIN Description 25 UART4_RX 50 MMC2_D6 26 RS485_TXEN 51 MMC2_D5 27 RS485_RXEN 52 MMC2_D4 28 UART4_TX 53 MMC2_D3 29 GND 54 MMC2_D2 30 MCBSP4_DX 55 MMC2_D1 56 MMC2_D0 57 MMC_CMD 58 MMC2_CLK Page | 15
PAGE 22
PIN Description 31 MCBSP4_DR 32 MCBSP4_CLKX 33 MCBSP4_FSX 34 MCBSP_CLKS 35 GND 36 GPIO157 37 GPIO162 38 SPI4_CS0 39 SPI4_SOMI 40 SPI4_SIMO 41 SPI4_CLK 42 GND 43 SPI1_CS3 44 SPI1_CS2 45 SPI1_SOMI 46 SPI1_SIMO 47 SPI1_CLK 48 GND 49 MMC2_D7 3.2.
PAGE 23
PIN Description 4 GPMC_NCS2 5 GPMC_A10 6 GPMC_A9 7 GPMC_A8 8 GPMC_A7 9 GPMC_A6 10 GPMC_A5 11 GPMC_A4 12 GPMC_A3 13 GPMC_A2 14 GPMC_A1 15 GPMC_NBE1 16 GPMC_WAIT3 17 SYS_RST 18 GPMC_CLE 19 GND 20 GPMC_ALE 21 GPMC_CLK 22 GPMC_WE 23 GPMC_OE 24 GPMC_D15 25 GPMC_D14 26 GPMC_D13 27 GPMC_D12 28 GPMC_D11 29 GPMC_D10 Page | 17
PAGE 24
PIN Description 30 GPMC_D9 31 GPMC_D8 32 GPMC_D7 33 GPMC_D6 34 GPMC_D5 35 GPMC_D4 36 GPMC_D3 37 GPMC_D2 38 GPMC_D1 39 GPMC_D0 40 GND Page | 18
PAGE 25
3.2.
PAGE 26
3.2.
PAGE 27
Power Interface PIN Description 1 VCC_5V 2 GND 3.2.
PAGE 28
3.2.
PAGE 29
4 Linux System 4.1 Linux system Overview This chapter provides an overview of the software system of the SOC8200, including the introduction of pre-installed software, specifications of the SOC8200 BSP (Board Support Package) and various specifications contained on the SOC8200 CD. The SOC8200 software system includes: pre-compiled images, application system source code, cross compilation tools, auxiliary tools for development.
PAGE 30
Figure 4: Software System Structure The features and functions of each part of the system are: 1. x-loader is a first level bootstrap program. After the system start-up, the ROM inside the CPU will copy the x-loader to internal RAM and perform work. Its main function is to initialize the CPU, copy u-boot into the memory and give the control power to u-boot; 2. u-boot is a second level bootstrap program. It is used for interacting with users and updating images and leading the kernel; 3. The latest 2.6.32.
PAGE 31
4.1.2 BSP Features The SOC8200 BSP is used for customizing and generating a Linux operating system applicable to the SOC8200 hardware platform. Users can conduct a secondary development on the basis of this BSP. The BSP in the CD included with the SOC8200 contains the following: Item Description NAND / ONENAND x-loader MMC / SD FAT Bootloader NAND / ONENAND MMC / SD u-boot FAT NET Kernel Device Driver Linux-2.6.
PAGE 32
Item Description audio Sound driver (supports audio Play) buzzer Buzzer driver can CAN driver led LED driver rs485 RS485 driver Watch dog Watch dog driver Analog Input 8 channel analog input Digital output Control independently 4.2 Linux System Quick Operation 4.2.
PAGE 33
4.2.2 SOC8200 Hardware Environment Preparation Before turning on the power and booting the Linux system, you should ensure the following: 1. Confirm that you have connected the LCD/VGA if required; 2. Insert the SD card; 3. Connect the serial port to both the SOC8200 and a PC; 4. Start up a HyperTerminal window on the PC; 5. Connect the 12V power supply; Figure 5: SOC8200 Interface Locations 6.
PAGE 34
NAND Flash without connecting the jumper cap. If you do not wish to use VGA, please refer to: Update the image in the NAND Flash on p46. SD card Boot If you need to boot from the SD card, please refer to the following section 4.2.4 Display Options To enable display on LCDs (4.3”, 7”, 10.4”) or VGA, use the instructions below: 1. Replace the SD card uImage file Copy the required image to the SD card and delete the previous uImage. Rename the “uImage_xx” to “uImage” on the SD card.
PAGE 35
Net: davinci_emac_initialize Ethernet PHY: GENERIC @ 0x00 DaVinci EMAC Hit any key to stop autoboot: 3 Once at this point, the system will count down for 3 seconds. Then press any key to enter the u-boot shell. 3. U-boot parameter settings Input the following (input characters in bold) into the u-boot shell.
PAGE 36
1. Input the following command to calibration procedure: begin the touchscreen [root@OMAP3EVM /]# ts_calibrate Follow the prompts on the screen, click the "+" icon five times to complete the calibration. 2. After the calibration is complete, enter the following command for the touch-screen test [root@OMAP3EVM /]# ts_test Follow the prompts on the screen to complete testing. 4.3.
PAGE 37
mmcblk1: mmc0:0001 000000 122 MiB mmcblk1: p1 2. Mount the MMC/SD card to directory /mnt: [root@OMAP3EVM /]# mount -t vfat /dev/mmcblk1p1 /mnt/ [root@OMAP3EVM /]# ls /mnt MLO u-boot.bin ubi.img flash-uboot.bin uImage x-load.bin.ift_for_NAND 3. Umount the SD card: [root@OMAP3EVM /]# umount /mnt 4.3.5 USB OTG Test Use the SOC8200 as a DEVICE and the USB OTG as a slave： 1. The user can connect the development board and the pc via a USB mini B to USB A cable after the system runs.
PAGE 38
Figure 8: IP Configuration 4. Ensure that the IP network segment of the SOC8200 board is the same as the virtual network card: [root@OMAP3EVM /]# ifconfig usb0 192.168.1.105 [root@OMAP3EVM /]# ifconfig usb0 Link encap:Ethernet HWaddr CA:A3:26:97:50:A8 inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.
PAGE 39
64 bytes from 192.168.1.15: seq=1 ttl=128 time=0.549 ms 64 bytes from 192.168.1.15: seq=2 ttl=128 time=0.488 ms 64 bytes from 192.168.1.15: seq=3 ttl=128 time=0.458 ms Note:  The IP address of the OTG should not be the same as the virtual network adaptor, you may need to change it. 4.3.6 USB HOST Test Connect the SOC8200 to a USB device: 1. Insert USB-disk into the USB-HOST interface, when the SOC8200 board runs the system shows the detection information automatically. [root@OMAP3EVM /]# usb 1-1.
PAGE 40
flash-uboot.bin uImage 4. Umount the USB-host. [root@OMAP3EVM /]# umount /mn 4.3.7 Network Test The board has a 10/100M self-adapting network card (DM9000); users can connect the board to the LAN and enter the following commands to test: [root@OMAP3EVM /]# ifconfig eth0 192.192.192.201 eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, id=7c0f1) [root@OMAP3EVM /]# PHY: ffffffff:00 - Link is Up - 100/Full [root@OMAP3EVM /]# ping 192.192.192.90 PING 192.192.192.90 (192.192.192.
PAGE 41
Display: Opened Channel Display: Capable of streaming Display: Number of requested buffers = 3 Display: Init done succetvp514x 3-005d: tvp5146 (Version - 0x03) found at 0xba (OMAP I2C adapter) ssfully Display: Stream on... Capture: Stream on... The LCD shows the image collected by the camera. (Press ctrl+c to quit the test) 4.3.9 CAN Test If the user wants to connect a CAN device, please use the CAN8200. The steps for CAN connection are below: 1.
PAGE 42
[root@OMAP3EVM /]# adc_test -d /dev/adc7 The channel: /dev/adc0 0x0fff data: 3.2990 V The channel: /dev/adc0 0x0fff data: 3.2990 V The channel: /dev/adc0 0x0fff data: 3.2990 V Note:  For pin2, the command is "adc_test -d /dev/adc6". When the pin is empty, the digit voltage is 2.2V. 4.3.11 SD Card Test 1. Connect to the SD card to the SOC8200 board, if the following information appears on the debug port, the SD card has been detected.
PAGE 43
[root@OMAP3EVM /]# arecord -t wav -c 2 -r 44100 -f S16_LE -v k Recording WAVE 'k' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo Plug PCM: Hardware PCM card 0 'omap3evm' device 0 subdevice 0 Its setup is: stream : CAPTURE access : RW_INTERLEAVED format : S16_LE subformat : STD channels : 2 rate exact rate msbits : 44100 : 44100 (44100/1) : 16 buffer_size : 22052 period_size : 5513 period_time : 125011 tstamp_mode : NONE period_step : 1 avail_min : 5513 period_event : 0 start_threshold :
PAGE 44
msbits : 16 buffer_size : 22052 period_size : 5513 period_time : 125011 tstamp_mode : NONE period_step : 1 avail_min : 5513 period_event : 0 start_threshold : 22052 stop_threshold : 22052 silence_threshold: 0 silence_size : 0 boundary : 1445199872 appl_ptr : 0 hw_ptr : 0 Page | 38
PAGE 45
4.3.14 Full-function Serial Port Test The SOC8200-M has 3 serial ports: Interface Type Extended Full-functi serial port on 0 port Extended Full-functi serial port on 1 port Debug port Encapsulation serial serial Three-wir e port serial Interface for DB9 Interface IDC nodes /dev/ttySCM A0 for IDC Interface Device /dev/ttySCM A1 for /dev/ttyS2 dBm Test program 3 line com_norts 9 line com_rts 3 line com_norts 9 line com_rts RS232 TTL RS232 System Integration 1.
PAGE 46
The steps for connection: The serial settings for the PC:  Baud rate: 115200  Data bit: 8  Stop bit: 1  Parity bit: None  Control flow: Hardware  DTR: On  RTS: On 2. Communication Test: Connect the extended serial port 0 and PC via 3-wire mode: Input the following commands, the SOC8200 board will send the data “1234567890" to the PC. If the PC has sent the data to SOC8200 board, the board will receive the data too.
PAGE 47
Input the following commands, the SOC8200 board will send the data "1234567890" to the PC. If the PC has sent the data to the SOC8200 board, the board will receive the data too. [root@OMAP3EVM ]# com_rts -d /dev/ttySCMA0 SEND: 1234567890 RECV: SOC8200 RECV: SOC8200 SEND: 1234567890 RECV: SOC8200 RECV: SOC8200 SEND: 1234567890 RECV: SOC8200 RECV: SOC8200 SEND: 1234567890 Note:  For the test program com_rts and com_norts, the user can add the " -s " to change the send content.
PAGE 48
4.3.15 Digital Output Test Pins 1 to 8 on the connector J6 can output the digital voltages 0V and 3.3V, the default output is 3.3v. 1. Device introduction: [root@OMAP3EVM /]# cd /sys/class/misc/digital/ [root@OMAP3EVM digital]# ls dev out2 out4 out6 out8 power out1 out3 out5 out7 outall subsystem uevent As above, out1 corresponds to the pin1; the outall corresponds to pins 1 to 8. 2.
PAGE 49
 Insert the TF card into the card reader of the PC.  Open the HP USB Disk Storage Format Tool, the following window will be displayed. Figure 9: HP USB Disk Storage Format Tool Settings  Select “FAT32” from the file system drop down box.  Click “Start”.  When formatting is completed, click “OK”. Note:  HP USB Disk Storage Format Tool will erase the partitions of TF card.  Use other format tool may cause the failure of the TF card booting.
PAGE 50
 Copy the all the files from the directory: disk/linux/image to the SD card.  Depending on your display device LCD (4.3” or 7”) or VGA, rename “uImage_xx” as uImage Update the image 1. Enter u-boot Insert the SD card into the SOC8200 board, and make sure you have connected the jumper cap on J24 (see Figure 10) J24 Figure 10: J24 Location Note:  Regardless of whether you are updating the image for the SD card or NAND Flash, you must start the image from the SD card.
PAGE 51
The user has to enter u-boot command line mode first: 40X Texas Instruments X-Loader 1.45 (Mar 19 2010 - 16:09:58) Starting X-loader on MMC Reading boot sector 213544 Bytes Read from MMC Starting OS Bootloader from MMC... Starting OS Bootloader... U-Boot 2009.11-svn ( 3 鏈?19 2010 - 16:14:31) OMAP34xx/35xx-GP ES1.
PAGE 52
Save the env and boot the kernel: OMAP3517EVM # saveenv OMAP3517EVM # boot 4.4.2 Update the image in the NAND Flash Preperation Refer to NAND Flash Boot on p27 Update system image Figure 11: NAND Flash Update Principles To update the image in the NAND Flash you must input the commands into the u-boot shell, please refer to the following steps: Updating the x-loader boot image Input the following commands into the u-boot shell to update images on the SD card: mmc init fatload mmc 0 80000000 x-load.bin.
PAGE 53
Input the following commands into the u-boot shell to update images on the SD card: mmc init fatload mmc 0 80000000 flash-uboot.bin nand erase 80000 160000 nandecc sw nand write.i 80000000 80000 $filesize Updating the kernel boot image Input the following commands into the u-boot shell to update images on the SD card: mmc init fatload mmc 0 80000000 uImage nand erase 280000 300000 nandecc sw nand write.
PAGE 54
4.5 Linux System Deveplopment This section will introduce how to establish a Linux system development platform to run on the SOC8200 hardware platform with the use of the SOC8200 BSP. Details to be provided contain the formation of a cross compilation environment, the generation of a system image and a demonstration of how to customize the system.
PAGE 55
cp /media/cdrom/linux/tools/mkfs.ubifs /home/embest/tools cp /media/cdrom/linux/tools/ubinize /home/embest/tools cp /media/cdrom/linux/tools/ ubinize.cfg /home/embest/tools 4.5.3 Adding environment variable After installation of the above tools, those tools can be added into environment variable with the following command: export PATH=/home/embest/arm-2009q1/bin:/home/embest/tools:$PATH Note:  Users can add this to the .barsrc file, allowing the environment variable to be finished as the system starts.
PAGE 56
cd x-load-03.00.00.04 make distclean make am3517evm_config make signGP x-load.bin mv x-load.bin.ift MLO When the above steps are finished, the current directory will contain the required MLO file. 2. To generate the x-load.bin.ift_for_NAND start-up To alter the file x-loader-1.4.1/include/configs/am3517evm.h and annotate the following: vi x-loader-03.00.00.04/include/configs/am3517evm.h //#define CONFIG_MMC 1 Cross compilation cd x-load-1.41 make distclean make am3517evm _config make signGP x-load.
PAGE 57
panel-sharp-lq043t1dg01.c, the default display is VGA. //#define LCD_43inch 1 //#define LCD_7inch 1 #define VGA 1 Compilation cd linux-03.00.00.04/ make distclean cp arch/arm/configs/omap3_soc8200_defconfig .config make make uImage When the above steps are finished, the arch/arm/boot directory will contain the required uImage file. ubifs image generation cd /home/embest/work sudo /home/embest/tools/mkfs.ubifs -r rootfs -m 2048 -e 129024 -c 812 -o ubifs.img sudo /home/embest/tools/ubinize -o ubi.
PAGE 58
The example that we use to introduce the system customization is a usb gadget simulating a usb mass storage device: 1. Select Device drivers Symbol: USB_FILE_STORAGE [=m] Prompt: File-backed Storage Gadget Defined at: drivers/usb/gadget/Kconfig:713 Depends on: && BLOCK [=y] Location:  Device Drivers  USB support (USB_SUPPORT [=y])  USB Gadget Support (USB_GADGET [=y])  USB Gadget Drivers ( [=m]) 2. Select the following option: (File-backed Storage Gadget). 3.
PAGE 59
4.6.2 Compilation Save the configuration and execute the following command to recompile the kernel: make make uImage After the above steps are finished, the arch/arm/boot directory will contain a new kernel image uImage; and drivers/usb/gadget directory will contain a new module file g_file_storage.ko. 4.6.3 Test Update the kernel image file ulmage on the SD card, copy the file g_file_storage.ko to the SD card and reboot the system from the SD.
PAGE 60
Page | 54
PAGE 61
4.7 Linux Application Development This section will introduce how to conduct application development on the SOC8200 hardware platform, including the formation of an SOC8200 software environment. Examples will be taken to show the general process of the development of SOC8200 applications. 4.7.1 LED application development 1. Coding Led_acc.c source code is shown below, The led lamps on the development board will flash. #include #include #include #include
PAGE 62
2. Cross compilation arm-none-linux-gnueabi-gcc led_acc.c -o led_acc 3. Download and run Resources can be put into the SOC8200 board system via SD card or U flash card or download. Then enter the directory containing the file led_acc exists, and input the following commands and enter, then the led_acc will run in the background. .
PAGE 63
5 WinCE System 5.1 WinCE System Overview The SOC8200 software system includes: pre-compiled images and applications and their corresponding static library, dynamic link library, header file and source code; cross compilation tools, auxiliary tools for development. Images, applications, Cross compilation tools used for generating image and applications can be downloaded from Microsoft.
PAGE 64
control to the operating system. EBOOT also can provide related functions to manage the basic hardware and set the shared data in the operating system. Windows Embedded CE 6.0 provides multimedia modules, industry modules, PDA modules, mobile modules and micro kernel modules, the user can choose the module that they want.
PAGE 65
5.1.2 Board Support Package (BSP) The SOC8200 BSP is used to customize the boot image and Windows Embedded CE 6.0 OS image to run on SOC8200 hardware platform. It supports the following: Module Feature NAND X-Loader module ONENAND SD NAND EBOOT module ONENAND SD ILT REBOOT OAL module Watchdog RTC KITL module RNDIS KITL NLED driver GPIO/I2C/SPI/MCBSP driver Series port driver 6X6 keyboard driver Audio driver Driver module NAND (K9F1G08) driver Display driver (LCD/DVI.
PAGE 66
VRFB driver DSPLINKK/CMEMK driver GPIO keyboard driver PWM (TPS65930) driver ADC (TPS65930) driver ONENAND driver SMSC911X network card driver CAN driver Buzzer driver Backlight driver Power management module Battery driver Sleep / wake-up button driver Expansion of power management Flash Plug-in and Flash player MP3/MPEG4/H264 DSP Hardware decoder Application module BSPINFO (control panel) CETK Page | 60
PAGE 67
5.2 WinCE System Quick Start 5.2.1 System boot When you boot the board and operate the system, you may use Hyper terminal software with the following settings:  Baud rate: 115200  Data bit: 8  Parity check: no  Stop bit: 1  Flow control: no 5.2.2 Boot from NAND Flash Please refer to p67 5.2.3 Boot from SD card Copy the image files MLO, EBOOTSD.nb0, and NK.bin from the CD:\WinCE\image\ VGA_1024x768(lcd_800x480 or lcd_480x272)\SD directory to the SD card.
PAGE 68
5.3 WinCE System Development 5.3.1 Development environment building Install the cross compilation environment Developing applications requires the installation and updating of the following software in the order listed:  Visual Studio 2005  Visual Studio 2005 SP1  Visual Studio 2005 SP1 Update for Vista (if applicable)  ActiveSync 4.5 The development of Windows Embedded CE 6.
PAGE 69
to re-customize the system and rebuild the image. This section describes how to use the SOC8200 Board Support Package (BSP) to create the ideal Windows Embedded CE 6.0 system image to run on your SOC8200 hardware platform. 5.4.1 Preparation Embest Technology Co., Ltd., has integrated drivers and their related resources into the SOC8200. In order to customise the SOC8200s embedded security you need to undertake the following preperation: Decompress [SOC8200\WinCE\BSP\AM35x_BSP.
PAGE 70
#define lcd_43inch 1 //#define lcd_vga_1024x768 1 //-------------------------------------------- For the 7” LCD Modify C:\wince600\platform\am35x_bsp\src\bsp_common\display\Lcd_cfg.h //------------------------------------------#define lcd_7inch 1 //#define lcd_43inch 1 //#define lcd_vga_1024x768 1 //-------------------------------------------- For the VGA Modify C:\wince600\platform\am35x_bsp\src\bsp_common\display\Lcd_cfg.
PAGE 71
 Set the Embest SOC8200 BSP in the BSP list.  Continue to finish the Wizard. 2. Select submenu [Build-> Global Build Settings]  Copy Files to the Release Directory After Build  Make Run-Time Image After build 3. If KITL is needed, set Enable Kernel Debugger and Enable KITL in the Build Options page [Project-> Properties]. 4. Select [Build-> Build Solution] to build the BSP. These operations cover the whole compilation including sysgen operating system’s components.
PAGE 72
Component Path Framework 3.5 Core OS Dependencies for .NET Compact Framework 3.5 Services OS->CEBASE->Applications Development->.NET and Compact Framework 3.5-> OS Dependencies for .NET Compact Framework 3.
PAGE 73
Component Path Core Video/Image Compression Manager OS->CEBASE->Graphics Multimedia and Technologies->Media->Video Codecs and Renderers Console Window SD Memory serial Windows Embedded CE Test Kit Core OS->CEBASE->Shell and User Interface->Shell->Command Shell Device Drivers->SDIO->SDIO Memory Device Drivers->USB Function->USB Function Clients Device Drivers Note:  Components can be added or deleted in the window Catalog Items View of the Visual Studio 2005 (VS2005) integrated developme
PAGE 74
2. Copy the image files:  MLO  XLDRNAND.nb0  EBOOTSD.nb0  NK.bin from the CD :\winCE\image\ VGA_1024x768 (lcd_800x480 or lcd_480x272) \NAND directory to the SD card. Image update 1. Set J24 to boot from SD card and insert the SD card then restart your system. HyperTerminal will start printing the output information, at the same time press [SPACE] to enter the EBOOT menu. 2. Press [5] to enter the Flash manage menu. 3.
PAGE 75
 The installation of the Windows Mobile 6 Professional SDK is advised. You can obtain this software from the Microsoft Download Center at: [http://www.microsoft.com/downloads/details.aspx?familyid=06111A3A-A65 1-4745-88EF-3D48091A390B&displaylang=en].  The development example in this manual is based on the development of the Windows Mobile 6 Professional SDK.
PAGE 76
5.6.1 API and Application Demonstrations The Application Programming Interface (API) used for SOC8200 application development employs the standard application interface of Windows Embedded CE 6.0. The SOC8200 has an additional GPIO interface based on standard API. Note:  For interface definitions of Windows Embedded CE 6.0 standard applications, please refer to related help documents for the MSDN Windows Embedded CE 6.0 API.  Some interfaces are only used by drivers. They can’t be used by applications.
PAGE 77
pInBuffer[0] = id; pInBuffer[1] = mode; DeviceIoControl(hFile, IOCTL_GPIO_SETMODE, pInBuffer, sizeof(pInBuffer), NULL, 0, NULL, NULL); Read the working mode of the GPIO: DeviceIoControl(hFile, IOCTL_GPIO_GETMODE, &id, sizeof(DWORD), &mode, sizeof(DWORD), NULL, NULL); "id" is the GPIO Pin number, "mode" is GPIO mode, including: Mode definition Description GPIO_DIR_OUTPUT Output mode GPIO_DIR_INPUT Input mode GPIO_INT_LOW_HIGH Rising edge trigger mode GPIO_INT_HIGH_LOW Falling edge trigger mod
PAGE 78
DeviceIoControl(hFile, IOCTL_GPIO_GETIRQ, &id, sizeof(DWORD), &irq, sizeof(DWORD), NULL, NULL); Where "id" is GPIO pin number, "irq" returns IRQ number 5. Close GPIO device CloseHandle(hFile); Note:  GPIO pin definition: 0~191 MPU Bank1~6 GPIO pin, 192~209 TPS65930 GPIO 0~17.  GPIO interrupt mode is used for drivers, applications cannot set this mode.  For definition of the IOCTL code and GPIO modes, please refer to the CD file [\wince_6\inc\gpio.h] User should include the header file.
PAGE 79
Appendix 1: Driver Installation Of Linux USB Ethernet/RNDIS Gadget 1. If you don’t install drivers for the Linux USB Ethernet/RNDIS Gadget, the PC will find the new hardware and give you a hint on the screen, please select “From list or designated location”, then click “Next” 2.
PAGE 80
3. When the following appears, select “Continue” 4.
PAGE 81
Page | 75
PAGE 82
Appendix 2: Making a Linux Boot Disk The following content will show you how to create a dual-partition flash disk for booting up a Linux system from the first partition, while saving the root filesystem in the second one; 1. Insert a TF card into a TF card reader and then connect the reader to your PC; execute the following instruction in an Ubuntu system to view the device name of the TF card; $ dmesg | tail Device Information: ... [ 6854.215650] sd 7:0:0:0: [sdc] Mode Sense: 0b 00 00 08 [ 6854.
PAGE 83
Note:  If TF card has two or more partitions, there would be multiple paths such as /dev/sdc1, /dev/sdc2 and /dev/sdc3 corresponding to the partitions. 3. Execute the following instruction to unmount the device; $ umount /media/disk 4. Execute an fdisk instruction; $ sudo fdisk /dev/sdc Please make sure you type the device path for the whole device, not one of the partitions such as /dev/sdc1 or /dev/sdc2; 5.
PAGE 84
Command (m for help): [ x ] (type x to enter expert mode) Expert Command (m for help): [ h ] (type h to set heads) Number of heads (1-256, default xxx): [ 255 ] (set heads to 255) Expert Command (m for help): [ s ] (type s to set sectors) Number of sectors (1-63, default xxx): [ 63 ] (set sector to 63) 8.
PAGE 85
Selected partition 1 Hex code (type L to list codes): [ c ] (type c to set partition type) Changed system type of partition 1 to c (W95 FAT32 (LBA)) 11. Type a and 1 to set the TF card to bootable mode; Command (m for help): [ a ] Partition number (1-4): [ 1 ] 12.
PAGE 86
Command (m for help): [ w ] The partition table has been altered! Calling ioctl() to re-read partition table. WARNING: Re-reading the partition table failed with error 16: Device or resource busy. The kernel still uses the old table. The new table will be used at the next reboot. WARNING: If you have created or modified any DOS 6.x partitions, please see the fdisk manual page for additional information. Syncing disks. 15. Execute the following instructions to form the new partitions; $ [sudo mkfs.
PAGE 87
Appendix 3: TFTP Server Setup 1. Install client $>sudo apt-get install tftp-hpa $>sudo apt-get install tftpd-hpa 2. Install inet $>sudo apt-get install xinetd $>sudo apt-get install netkit-inetd 3. Configure the server First, create tftpboot under root directory, and set the properties as “a random user can write and read” $>cd / $>sudo mkdir tftpboot $>sudo chmod 777 tftpboot Secondly, add in /etc/inetd.conf: $>sudo vi /etc/inetd.
PAGE 88
wait = yes user = root server = /usr/sbin/in.tftpd server_args = -s /tftpboot -c per_source = 11 cps = 100 2 } 4. Reboot the server: $>sudo /etc/init.d/xinetd restart $>sudo in.tftpd -l /tftpboot 5. Test the server Conduct a test; create a file under folder /tftpboot $>touch abc Enter into another folder $>tftp 192.168.1.15 (192.168.1.15was the server IP) $>tftp> get abc If the download is successful, this means the server has been installed.
PAGE 89
Appendix 4: WinCE related resource links 1. Visual Studio 2005 SP1 Update for Vista (if applicable)  http://download.microsoft.com/download/c/7/d/c7d9b927-f4e6-4a b2-8399-79a2d5cdfac9/VS80sp1-KB932232-X86-ENU.exe 2. Windows Embedded CE 6.0 Platform Builder Service Pack 1  http://www.microsoft.com/downloads/details.aspx?familyid=BF0D C0E3-8575-4860-A8E3-290ADF242678&displaylang=en 3. Windows Embedded CE 6.0 R2  http://www.microsoft.com/downloads/details.
PAGE 90
 http://download.microsoft.com/download/f/2/3/f232f773-7edc-43 00-be07-d3b76a5b3a91/Windows%20Mobile%206%20Professional %20SDK%20Refresh.msi 8. Windows Embedded CE 6.0 USB Camera Driver.msi  http://download.microsoft.com/download/f/a/1/fa1aaef1-6ae3-4cf 3-ab95-b01d3e428403/Windows%20Embedded%20CE%206.0%20 USB%20Camera%20Driver.
PAGE 91
Appendix 5: Expansion Board The customer can evaluate the AM3517 via the SOC8200 expansion board(SOC8200-M), to experience the full functionality of the AM3517 processor. The customer can use both the single board computer and the function Interface board to add the product functions, thus reducing product development cycles and achieving a faster time to market. 5.
PAGE 92
Transport interface:  1 line, 5 lines serial connectors, RS232 level, DB9 male head  1 line, 9 line, RS232 serial port level, DB9 male head  1 line, 9 line, TTL level, serial port 2x5 (2.54 mm) row needles interface  2 line, USB 2.0 HOST connectors, High-school, 480 Mbps  1 line, USB 2.
PAGE 93
Appendix 6: Interface Board For the convenience of our customers and to allow rapid customization of the product, TianMo introduces several interface boards based on the SOC8200 motherboard, each modular function can be connected to the SOC8200 motherboard. ECOM-4/ECOM-8 (shown below), requires a connection to the E100 communication board for use . Note:  The interface board is not available through retail, 100PCS minimum.
PAGE 94
Appendix 7: ESD Precautions & Handling Procedures Please note that the board comes without any case/box and all components are exposed. Therefore, extra attention must be paid to ESD (electrostatic discharge) precautions. To effectively prevent electrostatic damage, please follow the steps below:  Avoid carpets in cool, dry areas. Leave development kits in their anti-static packaging until ready to be installed.
PAGE 95
Appendix 8: Technical support & Warranty Embest Technology Co., Ltd. established in March of 2000, is a global provider of embedded hardware and software. Embest aims to help customers reduce time to market with improved quality by providing the most effective total solutions for the embedded industry.
PAGE 96
 Customers encounter issues related to their own applications.  Customers experience problems caused by unauthorised alteration of our software source code 8.2 Maintenance service clause 1. Product warranty will commence on the day of sale and last 12 months provided the product is used under normal conditions 2.
PAGE 97
 Embest Technology takes no responsibility for fulfilling any warranty (verbal or written) that is not made by Embest Technology and not included in the scope of our warranty. 3. Within the period of warranty, the cost for sending products to Embest should be paid by the customer. The cost for returning the product to the customer will be paid by Embest. Any returns in either direction occurring after the warranty period has expired should be paid for by the customer. 4.
PAGE 98
8.4 Value Added Services We will provide following value added services:  Driver development based on Embest embedded platforms for devices such as: serial ports, USB interface devices, and LCD screens.  Control system transplantation, BSP driver development, API software development.  Other value added services including supply of power adapters and LCD parts.  Other OEM/ODM services.  Technical training. Please contact Embest with any technical support queries:  http://www.embest-tech.