https://elinux.org/api.php?action=feedcontributions&user=Som2416&feedformat=atomeLinux.org - User contributions [en]2024-03-28T14:11:49ZUser contributionsMediaWiki 1.31.0https://elinux.org/index.php?title=S3C2416&diff=319820S3C24162014-03-20T11:00:24Z<p>Som2416: </p>
<hr />
<div>It's a [http://www.arm.com ARM926EJ] RISC '''SOC'''(System-On-Chip) made by [http://www.samsung.com/global/business/semiconductor Samsung seminconductor].<br><br />
This chip is 14mm x 14mm size, FBGA package with ball pitch of 0.65mm. the S3C2416 chip is a 32/16-bit RISC cost-effective, low power, high performance micro-processor solution for general applications including the GPS Navigation and Mobile Phone markets. Additionally, in order to allow for lower system costs, higher performance and low power, the S3C2416 is fabricated using the 65nm low power CMOS process.<br><br />
All in all, the S3C2416 presents a low-cost, highly embedded solution with upgraded features.<br />
<br />
----<br />
<br />
The S3C2416 carries revolutionary upgrades with respect to the S3C2412. Most notably, an upgrade to the ARM926EJ core, the integration of a 2D Graphics Accelerator, an added low power mode, as well as embedded internal ROM/RAM for secure boot, moviNAND booting and low power audio decoding. Furthermore, peripheral and feature upgrades have also been made to increase performance, as well as flexibility. Examples include a USB 1.1 host, in addition to a USB 2.0 high speed device, dual MMC ports, HSSPI ports as well as other upgraded memory interfaces.<br />
<br />
== Block Diagram ==<br />
<br />
[[File:S3c2416-BlockDiagram.jpg]]<br />
<br />
<br />
== Features ==<br />
<br />
*ARM926EJ CPU 400MHz with 16KB I-cache and 16KB D-cache <br />
*Dual port external memory controller: DRAM/ROM control and chip select logic <br />
*64KB internal general purpose SRAM <br />
*32KB internal ROM for moviNAND booting <br />
*LCD controller with DMA-dedicated: 24bpp, 2-PIP <br />
*2D graphics accelerator <br />
*6-ch DMAs with external request pins <br />
*4-ch UART (3Mbps) with IrDA 1.0 (64B FIFO) <br />
*1-ch HS-SPI (50Mbps) <br />
*1-ch IIC: multi-master <br />
*1-ch IIS: PCM and AC97 I/F <br />
*2-ch SD/SDIO/MMC <br />
*1-port USB Host v1.1 full speed <br />
*1-port USB Device v2.0 high speed <br />
*4-ch PWM timers & 1-ch internal timers <br />
*Real time clock & Watch dog timer <br />
*2 PLLs with on-chip clock generator <br />
*Power modes: Normal, Idle, Stop & Deep Stop, Sleep and Power-off <br />
*10-ch 12-bit ADC (Touch screen interface) <br />
*65nm low-power technology and MtCMOS technology incorporated <br />
*Package - 330-pins FBGA (0.65mm Pitch), 14 x 14 x 1.7mm<br />
<br />
<br />
==Development Board/ODM Provider==<br />
# [http://www.techor.com/ TECHOR's] [http://http://www.techor.com/prod-39.html System-on-Module based on S3C2416]]([[SOM2416]])</div>Som2416https://elinux.org/index.php?title=SOM2416&diff=319814SOM24162014-03-20T10:52:02Z<p>Som2416: Undo revision 314264 by Nandcon (talk)</p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSom2416&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
<br />
This page collects information about [http://www.samsung.com/global/business/semiconductor SAMSUNG semiconductor's] [http://www.arm.com/ ARM926EJ] based 400MHz [[S3C2416]] [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C2416 Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_281.html '''SOM2416'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
<br />
<br />
=Events=<br />
<I><br />
'''2014.1.27''': KIT2416-II will be released in Nov 10, 2009, it's extendable, we will develop Wifi, Bluetooth,GPS, GPRS/3G, FM module, CAN, 4x4 keypad, CMMB, LCD to VGA, LCD to LVDS,and series of Industial Sensors like Toradex Oak : [http://www.toradex.com/En/Products/Oak_USB_Sensors Oak_USB_Sensors] to plug onto the KIT2416-II and KIT3530, KIT6410<br />
[[File:Som2416 developkit.jpg|400px|thumbnail|(default)|som2416 develop kit 2014.01.27]]<br />
<br />
<br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM3530] '''Rev PRELIMINARY''' will be released in Oct 30,2009! [[SOM3530|elinux.org/SOM3530]] is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
<br>[[File:SOM3530msk.jpg|200px|SOM3530, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
<br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM6410] '''Rev PRELIMINARY''' will be released in Oct 30,2009! [[SOM6410|elinux.org/SOM6410]] is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
<br>[[File:SOM6410msk.jpg|200px|SOM6410, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
<br />
'''2009.09.30''': '''SOM2416-I Rev2''' and '''SOM2416-II Rev PRELIMINARY''' ([http://elinux.org/SOM2416#Pinout_definitions 120pin],4x4cm of 1.27mm pin pitch) Released and for Order/Samples<br><br />
'''2009.09.05''': Work together with [http://www.djyos.com/technology/2009-05-24/47.html DJYOS](The first of China Embedded Realtime Operation System) and port the DJYOS to '''SOM2416-I''' <br><br />
'''2009.08.30''': '''SOM2416-I Rev 1.0''' and '''SOM2416-II Rev PRELIMINARY''' annouce to be released on Mid-Sept,2009. '''SOM2416-II''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package <br><br />
'''2009.08.20''': [http://www.techor.com/product_281.html SOM2416-I] '''Rev PRELIMINARY''' released, '''SOM2416-I''' is 4x4cm size, 74pin 2.0mm pitch QFP-like package<br />
</I><br />
<br />
=How to Purchase=<br />
==SOM([[System-on-Module]]) Order Part Number(table items for refer only, Do not reflect the true inventory) ==<br />
True actual modules inventory please refer to: http://www.techor.com/prod-39.html<br />
{|border="0"<br />
!Part Number||Pin#||CPU Freq||DDR2 SDRAM||NAND Flash||Ethernet||Audio||Note<br />
|-<br />
|SOM2416-I-400-64-256M<br>default:'''SOM2416-I'''||74||400MHz||64MB||256MB||LAN9220||WM8731L||For Samples/In stock/no MOQ<ref>Minimum Order Quantity</ref> limited<br />
|-<br />
|SOM2416-I-400-64-256M-9221||74||400MHz||64MB||256MB||LAN9221||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-I-400-64-256M-NENA||74||400MHz||64MB||256MB||No||No||MOQ:10+pcs<br />
|-<br />
|SOM2416-II-400-64-256M<br>default:'''SOM2416-II'''||120||400MHz||64MB||256MB||LAN9220||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-II-400-64-256M-9221||120||400MHz||64MB||256MB||LAN9221||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-II-400-64-256M-NENA||120||400MHz||64MB||256MB||No||No||MOQ:10+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-I-400-32-64M||74||400MHz||32MB||64MB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-I-400-64-1G||74||400MHz||64MB||1GB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-I-400-64-2G-9221||74||400MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-II-400-32-64M||120||400MHz||32MB||64MB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-400-64-1G||120||400MHz||64MB||1GB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-400-64-2G-9221||120||400MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-I-266-64-256M||74||266MHz||64MB||256MB||LAN9220||WM8731L||MOQ:10+pcs<br />
|-<br />
|SOM2416-I-266-32-64M-NA||74||266MHz||32MB||64MB||LAN9220||No||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-266-64-256M-NE||120||266MHz||64MB||256MB||No||WM8731L||MOQ:10+pcs<br />
|-<br />
|SOM2416-II-266-64-2G-9221||120||266MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|}<br />
'''Note:''' <references/><br />
<br><br />
<br />
==Development/Evaluation KIT Order Part Number==<br />
<br />
{|border="1" align="center"<br />
<br />
!Part Number||Note<br />
|-<br />
|'''KIT2416-I'''<br>or<br>'''KIT2416-II'''||''KIT2416-I'' and ''KIT2416-II'' is a '''NECESSARY''' basic evaluation system kit for illustrating the functionality, connectivity of SOM2416-I/SOM2416-II modules on their each '''App Demo Board'''.<br />
; each KIT2416 includes :<br />
:# '''SOM2416-I'''(74pin,4x4cm) or '''SOM2416-II'''(120pin,4x4cm) Embedded Module<br />
:# 4.3" 16:9 '''TFT LCD''', LED backlight digital adjustable, 480 x RGB x 272 pixels, with 4-wire resistance touch screen<br />
:# Theirs corresponding [[SOM2416#App_Demo_Board|App Demo Board]] ''Rev 1.1'', which having USB host and device/Ethernet/3 or 4 UART/IIC/SPI/LCD/touch screen/Stereo Audio out/MIC/Line in/SDMMC/ADC/PWM/GPIO/local bus interfaces<br />
:# '''Cables''' : Ethernet cable, mini USB cable, RS232 Cable<br />
:# '''Power Supply''' AC 110V~220V in DC 5V 1A output<br />
:# '''SDK''': WINCE 5.0 SDK and documents,App Demo Board's SCH, PCB source code; Linux SDK in under developing and planing Nov 2009 release<br />
<br />
[[File:KIT2416-I-4.3-00.JPG|700px|thumbnail|left|SOM2416 kit with wince 6.0 / Linux 3.0]]<br />
<br />
|}<br />
<br><br />
'''3.How to Order? One of the 3 ways:'''<br />
{|<br />
|<br />
# Send Purchase Order mail to ''embed_sales at techor dot com'' and specifying ''Part#/Quantity/Where to Ship/Note'' , we will reply you the Quotation and payment instruction in 2 work days by e-mail<br />
# Add our services MSN: ''cxzeng at msn dot com'' , and chat/talk(in English and Chinese only) with our services to specify what your reqirements online<br />
# or you could refer to the official web page for detailed: [http://www.techor.com/product_281.html SOM2416]<br />
|}<br />
<br />
=Hardware=<br />
<br />
== General Info ==<br />
<br />
{|border="1"<br />
|+'''Two Models of SOM2416'''<br />
|Model||'''SOM2416-I'''<br>74pin 2.0mm pitch,4x4cm outer contour||'''SOM2416-II'''<br>120pin 1.27mm pitch,4x4cm outer contour<br />
|-<br />
|Picture||[[File:SOM2416-watermark.jpg]]||[[File:SOM2416-II-440.JPG]]<br />
|-<br />
|Components||<br />
<br />
{|border="0"<br />
!No.||Name||Comment<br />
|-<br />
|1||DDR2 SDRAM||64MB/32MB optional<br />
|-<br />
|2||LAN9220/LAN9221||High Performance 10/100M Ethernet controller<br />
|-<br />
|3||NAND Flash||2GB/1GB/512MB/256MB/128MB/64MB SLC/MLC optional<br />
|-<br />
|4||WM8731L||IIS Audio codec<br />
|-<br />
|5||S3C2416||400MHz/266MHz optional<br />
|}<br />
|-<br />
|Package||[[File:Som2416-package.gif]]||[[File:som2416-II-package.gif]]<br />
|-<br />
|Layout||[[File:72pin-top.jpg]]||[[File:120pin-top.jpg]]<br />
|}<br />
<br />
==Pinout definitions==<br />
<br />
{|<br />
|-<br />
|<br />
{|border="1"<br />
|+Pinout definition of SOM2416-I(74pin)<br />
!Pin number||Main Function||Note||Alt Function||Note<br />
|-<br />
| 1||style="background:#99FF00" |DP0 ||style="background:#99FF00" |USB Host+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 2||style="background:#80FF80" |ETX-||style="background:#80FF80" |ETH TX-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 3||style="background:#80FF80" |ETX+||style="background:#80FF80" |ETH TX+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 4||style="background:#80FF80" |ERX-||style="background:#80FF80" |ETH RX-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 5||style="background:#80FF80" |ERX+||style="background:#80FF80" |ETH RX+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 6||style="background:#FFAA00" |nOE||style="background:#FFAA00" |bus Read signal||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 7||style="background:#FFAA00" |nWE||style="background:#FFAA00" |bus Write signal||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 8||style="background:#FFAA00" |nCS3||style="background:#FFAA00" |bus Chip Select#3||style="background:#FFFF80" |GPA14||style="background:#FFFF80" |GPIO PA14<br />
|-<br />
| 9||style="background:#FFAA00" |ADDR0||style="background:#FFAA00" |bus addr||style="background:#FFFF80" |GPA0||style="background:#FFFF80"|GPIO PA0<br />
|-<br />
|10||style="background:#FFAA00" |ADDR1||style="background:#FFAA00" |bus addr||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|11||style="background:#FFAA00" |DATA0||style="background:#FFAA00" |bus data0||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|12||style="background:#FFAA00" |DATA1||style="background:#FFAA00" |bus data1||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|13||style="background:#FFAA00" |DATA2||style="background:#FFAA00" |bus data2||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|14||style="background:#FFAA00" |DATA3||style="background:#FFAA00" |bus data3||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|15||style="background:#FFAA00" |DATA4||style="background:#FFAA00" |bus data4||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|16||style="background:#FFAA00" |DATA5||style="background:#FFAA00" |bus data5||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|17||style="background:#FFAA00" |DATA6||style="background:#FFAA00" |bus data6||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|18||style="background:#FFAA00" |DATA7||style="background:#FFAA00" |bus data7||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|19||style="background:#80FF80" |HSYNC||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC2||style="background:#FFFF80" |GPIO PC2<br />
|-<br />
|20||style="background:#80FF80" |PCLK||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC1||style="background:#FFFF80" |GPIO PC1<br />
|-<br />
|21||style="background:#80FF80" |VSYNC||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC3||style="background:#FFFF80" |GPIO PC3<br />
|-<br />
|22||style="background:#80FF80" |VDEN||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC4||style="background:#FFFF80" |GPIO PC4<br />
|-<br />
|23||style="background:#80FF80" |LCD_B0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC11||style="background:#FFFF80" |GPIO PC11<br />
|-<br />
|24||style="background:#80FF80" |LCD_B1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC12||style="background:#FFFF80" |GPIO PC12<br />
|-<br />
|25||style="background:#80FF80" |LCD_B2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC13||style="background:#FFFF80" |GPIO PC13<br />
|-<br />
|26||style="background:#80FF80" |LCD_B3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC14||style="background:#FFFF80" |GPIO PC14<br />
|-<br />
|27||style="background:#80FF80" |LCD_B4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC15||style="background:#FFFF80" |GPIO PC15<br />
|-<br />
|28||style="background:#80FF80" |LCD_G0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD2||style="background:#FFFF80" |GPIO PD2<br />
|-<br />
|29||style="background:#80FF80" |LCD_G1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD3||style="background:#FFFF80" |GPIO PD3<br />
|-<br />
|30||style="background:#80FF80" |LCD_G2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD4||style="background:#FFFF80" |GPIO PD4<br />
|-<br />
|31||style="background:#80FF80" |LCD_G3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD5||style="background:#FFFF80" |GPIO PD5<br />
|-<br />
|32||style="background:#80FF80" |LCD_G4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD6||style="background:#FFFF80" |GPIO PD6<br />
|-<br />
|33||style="background:#80FF80" |LCD_G5||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD7||style="background:#FFFF80" |GPIO PD7<br />
|-<br />
|34||style="background:#80FF80" |LCD_R0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD11||style="background:#FFFF80" |GPIO PD11<br />
|-<br />
|35||style="background:#80FF80" |LCD_R1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD12||style="background:#FFFF80" |GPIO PD12<br />
|-<br />
|36||style="background:#80FF80" |LCD_R2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD13||style="background:#FFFF80" |GPIO PD13<br />
|-<br />
|37||style="background:#80FF80" |LCD_R3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD14||style="background:#FFFF80" |GPIO PD14<br />
|-<br />
|38||style="background:#80FF80" |LCD_R4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD15||style="background:#FFFF80" |GPIO PD15<br />
|-<br />
|39||style="background:#FFFF40" |ALOUT||style="background:#FFFF40" |audio left out ||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|40||style="background:#FFFF40" |AROUT||style="background:#FFFF40" |audio right out||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|41||style="background:#FFFF40" |MIC||style="background:#FFFF40" |audio MIC in||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|42||style="background:#2099FF" |TXD0||style="background:#2099FF" |uart0 tx||style="background:#FFFF80" |GPH0||style="background:#FFFF80" |GPIO PH0<br />
|-<br />
|43||style="background:#2099FF" |RXD0||style="background:#2099FF" |uart0 rx||style="background:#FFFF80" |GPH1||style="background:#FFFF80" |GPIO PH1<br />
|-<br />
|44||style="background:#2099FF" |TXD1||style="background:#2099FF" |uart1 tx||style="background:#FFFF80" |GPH2||style="background:#FFFF80" |GPIO PH2<br />
|-<br />
|45||style="background:#2099FF" |RXD1||style="background:#2099FF" |uart1 rx||style="background:#FFFF80" |GPH3||style="background:#FFFF80" |GPIO PH3<br />
|-<br />
|46||style="background:#2099FF" |TXD2||style="background:#2099FF" |uart2 tx||style="background:#FFFF80" |GPH4||style="background:#FFFF80" |GPIO PH4<br />
|-<br />
|47||style="background:#2099FF" |RXD2||style="background:#2099FF" |uart2 rx||style="background:#FFFF80" |GPH5||style="background:#FFFF80" |GPIO PH5<br />
|-<br />
|48||style="background:#99FF00" |I2CSCL||style="background:#99FF00" |IIC||style="background:#FFFF80" |GPE14||style="background:#FFFF80" |GPIO PE14<br />
|-<br />
|49||style="background:#99FF00" |I2CSDA||style="background:#99FF00" |IIC||style="background:#FFFF80" |GPE15||style="background:#FFFF80" |GPIO PE15<br />
|-<br />
|50||style="background:#FF80FF" |SPIMISO||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE11||style="background:#FFFF80" |GPIO PE11<br />
|-<br />
|51||style="background:#FF80FF" |SPICLK||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE13||style="background:#FFFF80" |GPIO PE13<br />
|-<br />
|52||style="background:#FF80FF" |SPIMOSI||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE12||style="background:#FFFF80" |GPIO PE12<br />
|-<br />
|53||style="background:#FF80FF" |SPI_nSS||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPL13||style="background:#FFFF80" |GPIO PL13<br />
|-<br />
|54||style="background:#FFFF40" |VCCRTC||style="background:#FFFF40" |RTC Vcc||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|55||style="background:#99FF00" |SDCLK||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL9||style="background:#FFFF80" |GPIO PL9<br />
|-<br />
|56||style="background:#99FF00" |SDCMD||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL8||style="background:#FFFF80" |GPIO PL8<br />
|-<br />
|57||style="background:#99FF00" |SDDAT0||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL0||style="background:#FFFF80" |GPIO PL0<br />
|-<br />
|58||style="background:#99FF00" |SDDAT1||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL1||style="background:#FFFF80" |GPIO PL1<br />
|-<br />
|59||style="background:#99FF00" |SDDAT2||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL2||style="background:#FFFF80" |GPIO PL2<br />
|-<br />
|60||style="background:#99FF00" |SDDTA3||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL3||style="background:#FFFF80" |GPIO PL3<br />
|-<br />
|61||style="background:#2099FF" |XP||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN9||style="background:#FFFF80" |ADC in9<br />
|-<br />
|62||style="background:#2099FF" |YP||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN7||style="background:#FFFF80" |ADC in7<br />
|-<br />
|63||style="background:#2099FF" |XM||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN8||style="background:#FFFF80" |ADC in8<br />
|-<br />
|64||style="background:#2099FF" |YM||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN6||style="background:#FFFF80" |ADC in6<br />
|-<br />
|65||style="background:#FFFF40" |LCD_PWR||style="background:#FFFF40" |LCD brightness||style="background:#FFFF80" |GPF2||style="background:#FFFF80" |GPIO PF2<br />
|-<br />
|66||style="background:#FFFF40" |BUS_INT||style="background:#FFFF40" |bus int.||style="background:#FFFF80" |GPF1||style="background:#FFFF80" |GPIO PF1<br />
|-<br />
|67||style="background:#FFFF40" |nSD_CD||style="background:#FFFF40" |SD detect||style="background:#FFFF80" |GPF5||style="background:#FFFF80" |GPIO PF5<br />
|-<br />
|68||style="background:#FFFF40" |SPI_INT||style="background:#FFFF40" |SPI int.||style="background:#FFFF80" |GPF0||style="background:#FFFF80" |GPIO PF0<br />
|-<br />
|69||style="background:#FFFF40" |GPIO_INT||style="background:#FFFF40" |GPIO int.||style="background:#FFFF80" |GPF6||style="background:#FFFF80" |GPIO PF6<br />
|-<br />
|70||style="background:#99FF00" |DN1||style="background:#99FF00" |USB device-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|71||style="background:#99FF00" |DP1||style="background:#99FF00" |USB device+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|72||style="background:#99FF00" |DN0||style="background:#99FF00" |USB Host-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|73||style="background:red" |VCC3V3||style="background:red" |DC 3.3V in||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|74||style="background:red" |GND||style="background:red" |GND||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|}<br />
<br />
||<br />
<br />
{|border="1"<br />
|+Pinout definition of SOM2416-II(120pin)<br />
!Pin number||Main Function||Note||Alt Function||Note<br />
|-style="background:#80FF80"<br />
| 1||ETX-||ETH TX-||-||-<br />
|-style="background:#80FF80"<br />
| 2||ETX+||ETH TX+||-||-<br />
|-style="background:#80FF80"<br />
| 3||GND||ETH GND||-||-<br />
|-style="background:#80FF80"<br />
| 4||ERX-||ETH RX-||-||-<br />
|-style="background:#80FF80"<br />
| 5||ERX+||ETH RX+||-||-<br />
|-style="background:#80FF80"<br />
| 6||ETH_SPD||ETH SPEED||-||-<br />
|-style="background:#80FF80"<br />
| 7||ETH_LINK||ETH LINK||-||-<br />
|-style="background:red"<br />
| 8||GND||GND||-||-<br />
|-style="background:#FFAA00"<br />
| 9||nRST||System Reset||-||-<br />
|-style="background:#FFFF40"<br />
|10||BUS_CLK||bus clock||-||-<br />
|-style="background:#FFFF40"<br />
|11||nWAIT||bus nWAIT||-||-<br />
|-style="background:#FFFF40"<br />
|12||nOE||bus nOE||-||-<br />
|-style="background:#FFFF40"<br />
|13||nWE||bus nWE||-||-<br />
|-style="background:#FFFF40"<br />
|14||nCS3||bus nCS3||-||-<br />
|-style="background:#FFFF40"<br />
|15||LADDR[0]||bus LADDR[0]||-||-<br />
|-style="background:#FFFF40"<br />
|16||LADDR[1]||bus LADDR[1]||-||-<br />
|-style="background:#FFFF40"<br />
|17||LADDR[2]||bus LADDR[2]||-||-<br />
|-style="background:#FFFF40"<br />
|18||LADDR[3]||bus LADDR[3]||-||-<br />
|-style="background:#FFFF40"<br />
|19||LADDR[4]||bus LADDR[4]||-||-<br />
|-style="background:#FFFF40"<br />
|20||LADDR[5]||bus LADDR[5]||-||-<br />
|-style="background:#FFFF40"<br />
|21||LADDR[6]||bus LADDR[6]||-||-<br />
|-style="background:#FFFF40"<br />
|22||LDATA[0]||bus LDATA[0]||-||-<br />
|-style="background:#FFFF40"<br />
|23||LDATA[1]||bus LDATA[1]||-||-<br />
|-style="background:#FFFF40"<br />
|24||LDATA[2]||bus LDATA[2]||-||-<br />
|-style="background:#FFFF40"<br />
|25||LDATA[3]||bus LDATA[3]||-||-<br />
|-style="background:#FFFF40"<br />
|26||LDATA[4]||bus LDATA[4]||-||-<br />
|-style="background:#FFFF40"<br />
|27||LDATA[5]||bus LDATA[5]||-||-<br />
|-style="background:#FFFF40"<br />
|28||LDATA[6]||bus LDATA[6]||-||-<br />
|-style="background:#FFFF40"<br />
|29||LDATA[7]||bus LDATA[7]||-||-<br />
|-style="background:red"<br />
|30||Vcc||Vcc input 3.3V||-||-<br />
|-style="background:red"<br />
|31||Vcc||Vcc input 3.3V||-||-<br />
|-style="background:#99FF00"<br />
|32||LCD_PWR||lcd Power||-||-<br />
|-style="background:#99FF00"<br />
|33||HSYNC||lcd HSYNC||-||-<br />
|-style="background:#99FF00"<br />
|34||PCLK||lcd PCLK||-||-<br />
|-style="background:#99FF00"<br />
|35||VSYNC||lcd VSYNC||-||-<br />
|-style="background:#99FF00"<br />
|36||VDEN||lcd VDEN||-||-<br />
|-style="background:red"<br />
|37||GND||GND||-||-<br />
|-style="background:#99FF00"<br />
|38||VD[2]||lcd VD[2]||-||-<br />
|-style="background:#99FF00"<br />
|39||VD[3]||lcd VD[3]||-||-<br />
|-style="background:#99FF00"<br />
|40||VD[4]||lcd VD[4]||-||-<br />
|-style="background:#99FF00"<br />
|41||VD[5]||lcd VD[5]||-||-<br />
|-style="background:#99FF00"<br />
|42||VD[6]||lcd VD[6]||-||-<br />
|-style="background:#99FF00"<br />
|43||VD[7]||lcd VD[7]||-||-<br />
|-style="background:#99FF00"<br />
|44||VD[10]||lcd VD[10]||-||-<br />
|-style="background:#99FF00"<br />
|45||VD[11]||lcd VD[11]||-||-<br />
|-style="background:#99FF00"<br />
|46||VD[12]||lcd VD[12]||-||-<br />
|-style="background:#99FF00"<br />
|47||VD[13]||lcd VD[13]||-||-<br />
|-style="background:#99FF00"<br />
|48||VD[14]||lcd VD[14]||-||-<br />
|-style="background:#99FF00"<br />
|49||VD[15]||lcd VD[15]||-||-<br />
|-style="background:#99FF00"<br />
|50||VD[18]||lcd VD[18]||-||-<br />
|-style="background:#99FF00"<br />
|51||VD[19]||lcd VD[19]||-||-<br />
|-style="background:#99FF00"<br />
|52||VD[20]||lcd VD[20]||-||-<br />
|-style="background:#99FF00"<br />
|53||VD[21]||lcd VD[21]||-||-<br />
|-style="background:#99FF00"<br />
|54||VD[22]||lcd VD[22]||-||-<br />
|-style="background:#99FF00"<br />
|55||VD[23]||lcd VD[23]||-||-<br />
|-style="background:#2099FF"<br />
|56||LPOUT||audio LPOUT||-||-<br />
|-style="background:#2099FF"<br />
|57||RPOUT||audio RPOUT||-||-<br />
|-style="background:#2099FF"<br />
|58||MIC||audio MIC||-||-<br />
|-style="background:#2099FF"<br />
|59||LIN||audio LIN||-||-<br />
|-style="background:#2099FF"<br />
|60||RIN||audio RIN||-||-<br />
|-style="background:red"<br />
|61||AGND||audio GND||-||-<br />
|-style="background:#80FF80"<br />
|62||TXD0||uart TXD0||-||-<br />
|-style="background:#80FF80"<br />
|63||RXD0||uart RXD0||-||-<br />
|-style="background:#80FF80"<br />
|64||nRTS0||uart nRTS0||-||-<br />
|-style="background:#80FF80"<br />
|65||nCTS0||uart nCTS0||-||-<br />
|-style="background:#80FF80"<br />
|66||TXD1||uart TXD1||-||-<br />
|-style="background:#80FF80"<br />
|67||RXD1||uart RXD1||-||-<br />
|-style="background:#80FF80"<br />
|68||nRTS1||uart nRTS1||-||-<br />
|-style="background:#80FF80"<br />
|69||nCTS1||uart nCTS1||-||-<br />
|-style="background:#80FF80"<br />
|70||TXD2||uart TXD2||-||-<br />
|-style="background:#80FF80"<br />
|71||RXD2||uart RXD2||-||-<br />
|-style="background:#80FF80"<br />
|72||TXD3||uart TXD3||-||-<br />
|-style="background:#80FF80"<br />
|73||RXD3||uart RXD3||-||-<br />
|-style="background:#FFAA00"<br />
|74||I2C_SCL||iic||-||-<br />
|-style="background:#FFAA00"<br />
|75||I2C_SDA||iic||-||-<br />
|-style="background:#FFFF40"<br />
|76||SPIMISO||spi||-||-<br />
|-style="background:#FFFF40"<br />
|77||SPICLK||spi||-||-<br />
|-style="background:#FFFF40"<br />
|78||SPIMOSI||spi||-||-<br />
|-style="background:#FFFF40"<br />
|79||nSS||spi||-||-<br />
|-style="background:#99FF00"<br />
|80||SD0CLK||sd0||-||-<br />
|-style="background:#99FF00"<br />
|81||SD0CMD||sd0||-||-<br />
|-style="background:#99FF00"<br />
|82||SD0DAT0||sd0||-||-<br />
|-style="background:#99FF00"<br />
|83||SD0DAT1||sd0||-||-<br />
|-style="background:#99FF00"<br />
|84||SD0DAT2||sd0||-||-<br />
|-style="background:#99FF00"<br />
|85||SD0DAT3||sd0||-||-<br />
|-style="background:red"<br />
|86||GND||GND||-||-<br />
|-style="background:red"<br />
|87||VCCRTC||VCCrtc||-||-<br />
|-style="background:#2099FF"<br />
|88||OM3||mode select||-||-<br />
|-style="background:#2099FF"<br />
|89||OM2||mode select||-||-<br />
|-style="background:#2099FF"<br />
|90||OM1||mode select||-||-<br />
|-style="background:#80FF80"<br />
|91||nSD1_CS||sd1 card detect||-||-<br />
|-style="background:#80FF80"<br />
|92||SD1CLK||sd1||-||-<br />
|-style="background:#80FF80"<br />
|93||SD1CMD||sd1||-||-<br />
|-style="background:#80FF80"<br />
|94||SD1DAT0||sd1||-||-<br />
|-style="background:#80FF80"<br />
|95||SD1DAT1||sd1||-||-<br />
|-style="background:#80FF80"<br />
|96||SD1DAT2||sd1||-||-<br />
|-style="background:#80FF80"<br />
|97||SD1DAT3||sd1||-||-<br />
|-style="background:red"<br />
|98||GND||GND||-||-<br />
|-style="background:#FFAA00"<br />
|99||XP||touch||-||-<br />
|-style="background:#FFAA00"<br />
|100||YP||touch||-||-<br />
|-style="background:#FFAA00"<br />
|101||XM||touch||-||-<br />
|-style="background:#FFAA00"<br />
|102||YM||touch||-||-<br />
|-style="background:#FFFF40"<br />
|103||AIN0||ADC||-||-<br />
|-style="background:#FFFF40"<br />
|104||AIN1||ADC||-||-<br />
|-style="background:#99FF00"<br />
|105||EINT0||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|106||EINT3||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|107||EINT5||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|108||EINT6||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|109||EINT7||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|110||EINT8||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|111||EINT9||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|112||EINT10||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|113||EINT11||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|114||EINT12||Ext Int||-||-<br />
|-style="background:red"<br />
|115||GND||GND||-||-<br />
|-style="background:#2099FF"<br />
|116||DN1||usb device||-||-<br />
|-style="background:#2099FF"<br />
|117||DP1||usb device||-||-<br />
|-style="background:#99FF00"<br />
|118||EINT2||Ext Int||-||-<br />
|-style="background:#80FF80"<br />
|119||DN0||usb host||-||-<br />
|-style="background:#80FF80"<br />
|120||DP0||usb host||-||-<br />
|-<br />
|}<br />
<br />
|-<br />
|}<br />
<br />
==Manual==<br />
* SOM2416-I Hardware Reference Manual released in Aug 22,2009: [http://www.techor.com/SOM/SOM2416_hw_ref_manual_v1.1.pdf SOM2416_hw_ref_manual_v1.1.pdf download here]<br />
* [http://www.techor.com/down/s3c2416x_rev10.rar S3C2416 datasheet Rev1.1 download here]<br />
<br />
==Layout==<br />
<br />
==Errata==<br />
==Clocking==<br />
==Power management==<br />
==Interfacing to Raw LCD Panels==<br />
<br />
=Availability=<br />
<br />
==SOM2416-I([http://www.techor.com/syssite/home/shop/1/pictures/productsimg/big/281.JPG 74pin]) Revision==<br />
===Rev PRELIMINARY===<br />
===Rev 1.0===<br />
==SOM2416-II(120pin) Revision==<br />
===Rev PRELIMINARY===<br />
<br />
==SOM2416-based products==<br />
{|<br />
|'''SOM2416-I''' based 7" DPF ODM design by ourself,<br />
DC 12V in/mini USB connected to PC/4-line AV out<br />
/USB host connected U Disk/Power switch<br />
/SDMMC socket /7" AT070TN84 LCD Panel<br />
/7 push buttons/2 speaker /IrDA remote control<br />
Rev 1.0 in Sept 24,2009<br />
||[[File:SOM2416-I-DPF7-2.JPG|frame|SOM2416-I based 7" DPF,front view,Rev 1.0 in Sept 24,2009]]||[[File:SOM2416-I-DPF7.JPG|frame|SOM2416-I based 7" DPF,back view,Rev 1.0 in Sept 24,2009]]<br />
|-<br />
|Customized '''SOM2416-II''' based 5.6" Industrial Touch Screen HMI,run uCOS/II with miniGUI windows management system,rev 1.0 in Sept 1,2009<br />
||[[File:SOM2416-II-HMI1.JPG|frame|SOM2416-II based Industrial Touch Screen HMI,front and back view]]||[[File:SOM2416-II-HMI.JPG|frame|SOM2416-II based Industrial Touch Screen HMI,run uCOS/II with miniGUI]]<br />
|}<br />
<br />
==SOM2416 ODM cases==<br />
{|border="0" align="center"<br />
|+'''SOM2416 baseded ODM/OEM Cases'''<br />
|'''Industrial HMI Machine''', SOM2416-I directly <br>soldered on top of 2-layer '''App board'''(below)||A Special '''Handheld Measurement Instrument''', <br>Customized 6-layer Main Board based on S3C2416<br />
|-<br />
|[[File:Solution2.jpg|448px|Industrial HMI Machine, SOM2416-I directly <br>soldered on top of 2-layer App board(below)]]||[[File:Solution1.jpg|746px|A Special Handheld Measurement Instrument, <br>Customized 6-layer Main Board based on S3C2416]]<br />
|}<br />
<br />
=App Demo Board=<br />
{|http://elinux.org/File:SOM2416%2B43TFTLCD.jpg<br />
|[[File:AppBoard800.jpg|frame|<b>AppDemoBoard Rev 2.1(KIT2416-II)</b> carries SOM2416-II]]<br />
|-<br />
[[File:SOM2416+43TFTLCD.jpg|600px|thumbnail|left|KIT2416-II := Latest Develop Kit(Ver2.1) + 5.6" LCD w/touch + T-Flash card<br />
Back view of KIT2416-II, running WINCE 6.0]]<br />
|}<br />
<br />
=Adapters=<br />
==Expansion boards==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOM2416&diff=29959SOM24162011-01-07T09:47:12Z<p>Som2416: /* SOM(System-on-Module) Order Part Number */</p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSom2416&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
<br />
This page collects information about [http://www.samsung.com/global/business/semiconductor SAMSUNG semiconductor's] [http://www.arm.com/ ARM926EJ] based 400MHz [[S3C2416]] [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C2416 Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_281.html '''SOM2416'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
<br />
<br />
=Events=<br />
<I><br />
'''2009.11.01''': KIT2416-II will be released in Nov 10, 2009, it's extendable, we will develop Wifi, Bluetooth,GPS, GPRS/3G, FM module, CAN, 4x4 keypad, CMMB, LCD to VGA, LCD to LVDS,and series of Industial Sensors like Toradex Oak : [http://www.toradex.com/En/Products/Oak_USB_Sensors Oak_USB_Sensors] to plug onto the KIT2416-II and KIT3530, KIT6410<br />
<br>[[File:KIT2416-II-640.JPG]]<br />
<br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM3530] '''Rev PRELIMINARY''' will be released in Oct 30,2009! [[SOM3530|elinux.org/SOM3530]] is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
<br>[[File:SOM3530msk.jpg|200px|SOM3530, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
<br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM6410] '''Rev PRELIMINARY''' will be released in Oct 30,2009! [[SOM6410|elinux.org/SOM6410]] is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
<br>[[File:SOM6410msk.jpg|200px|SOM6410, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
<br />
'''2009.09.30''': '''SOM2416-I Rev2''' and '''SOM2416-II Rev PRELIMINARY''' ([http://elinux.org/SOM2416#Pinout_definitions 120pin],4x4cm of 1.27mm pin pitch) Released and for Order/Samples<br><br />
'''2009.09.05''': Work together with [http://www.djyos.com/technology/2009-05-24/47.html DJYOS](The first of China Embedded Realtime Operation System) and port the DJYOS to '''SOM2416-I''' <br><br />
'''2009.08.30''': '''SOM2416-I Rev 1.0''' and '''SOM2416-II Rev PRELIMINARY''' annouce to be released on Mid-Sept,2009. '''SOM2416-II''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package <br><br />
'''2009.08.20''': [http://www.techor.com/product_281.html SOM2416-I] '''Rev PRELIMINARY''' released, '''SOM2416-I''' is 4x4cm size, 74pin 2.0mm pitch QFP-like package<br />
</I><br />
<br />
=How to Purchase=<br />
==SOM([[System-on-Module]]) Order Part Number(table items for refer only, Do not reflect the true inventory) ==<br />
True actual modules inventory please refer to: http://www.techor.com/prod-39.html<br />
{|border="0"<br />
!Part Number||Pin#||CPU Freq||DDR2 SDRAM||NAND Flash||Ethernet||Audio||Note<br />
|-<br />
|SOM2416-I-400-64-256M<br>default:'''SOM2416-I'''||74||400MHz||64MB||256MB||LAN9220||WM8731L||For Samples/In stock/no MOQ<ref>Minimum Order Quantity</ref> limited<br />
|-<br />
|SOM2416-I-400-64-256M-9221||74||400MHz||64MB||256MB||LAN9221||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-I-400-64-256M-NENA||74||400MHz||64MB||256MB||No||No||MOQ:10+pcs<br />
|-<br />
|SOM2416-II-400-64-256M<br>default:'''SOM2416-II'''||120||400MHz||64MB||256MB||LAN9220||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-II-400-64-256M-9221||120||400MHz||64MB||256MB||LAN9221||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-II-400-64-256M-NENA||120||400MHz||64MB||256MB||No||No||MOQ:10+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-I-400-32-64M||74||400MHz||32MB||64MB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-I-400-64-1G||74||400MHz||64MB||1GB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-I-400-64-2G-9221||74||400MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-II-400-32-64M||120||400MHz||32MB||64MB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-400-64-1G||120||400MHz||64MB||1GB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-400-64-2G-9221||120||400MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-I-266-64-256M||74||266MHz||64MB||256MB||LAN9220||WM8731L||MOQ:10+pcs<br />
|-<br />
|SOM2416-I-266-32-64M-NA||74||266MHz||32MB||64MB||LAN9220||No||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-266-64-256M-NE||120||266MHz||64MB||256MB||No||WM8731L||MOQ:10+pcs<br />
|-<br />
|SOM2416-II-266-64-2G-9221||120||266MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|}<br />
'''Note:''' <references/><br />
<br><br />
<br />
==Development/Evaluation KIT Order Part Number==<br />
<br />
{|border="1" align="center"<br />
<br />
!Part Number||Note<br />
|-<br />
|'''KIT2416-I'''<br>or<br>'''KIT2416-II'''||''KIT2416-I'' and ''KIT2416-II'' is a '''NECESSARY''' basic evaluation system kit for illustrating the functionality, connectivity of SOM2416-I/SOM2416-II modules on their each '''App Demo Board'''.<br />
; each KIT2416 includes :<br />
:# '''SOM2416-I'''(74pin,4x4cm) or '''SOM2416-II'''(120pin,4x4cm) Embedded Module<br />
:# 4.3" 16:9 '''TFT LCD''', LED backlight digital adjustable, 480 x RGB x 272 pixels, with 4-wire resistance touch screen<br />
:# Theirs corresponding [[SOM2416#App_Demo_Board|App Demo Board]] ''Rev 1.1'', which having USB host and device/Ethernet/3 or 4 UART/IIC/SPI/LCD/touch screen/Stereo Audio out/MIC/Line in/SDMMC/ADC/PWM/GPIO/local bus interfaces<br />
:# '''Cables''' : Ethernet cable, mini USB cable, RS232 Cable<br />
:# '''Power Supply''' AC 110V~220V in DC 5V 1A output<br />
:# '''SDK''': WINCE 5.0 SDK and documents,App Demo Board's SCH, PCB source code; Linux SDK in under developing and planing Nov 2009 release<br />
<br />
[[File:KIT2416-I-4.3-00.JPG]]<br><b>KIT2416-I(74pin)</b> connected U-Disk, Speaker, PC computer(Power Supply and data sync), Ethernet and console(RS232)<br />
<br />
|}<br />
<br><br />
'''3.How to Order? One of the 3 ways:'''<br />
{|<br />
|<br />
# Send Purchase Order mail to ''embed_sales at techor dot com'' and specifying ''Part#/Quantity/Where to Ship/Note'' , we will reply you the Quotation and payment instruction in 2 work days by e-mail<br />
# Add our services MSN: ''cxzeng at msn dot com'' , and chat/talk(in English and Chinese only) with our services to specify what your reqirements online<br />
# or you could refer to the official web page for detailed: [http://www.techor.com/product_281.html SOM2416]<br />
|}<br />
<br />
=Hardware=<br />
<br />
== General Info ==<br />
<br />
{|border="1"<br />
|+'''Two Models of SOM2416'''<br />
|Model||'''SOM2416-I'''<br>74pin 2.0mm pitch,4x4cm outer contour||'''SOM2416-II'''<br>120pin 1.27mm pitch,4x4cm outer contour<br />
|-<br />
|Picture||[[File:SOM2416-watermark.jpg]]||[[File:SOM2416-II-440.JPG]]<br />
|-<br />
|Components||<br />
<br />
{|border="0"<br />
!No.||Name||Comment<br />
|-<br />
|1||DDR2 SDRAM||64MB/32MB optional<br />
|-<br />
|2||LAN9220/LAN9221||High Performance 10/100M Ethernet controller<br />
|-<br />
|3||NAND Flash||2GB/1GB/512MB/256MB/128MB/64MB SLC/MLC optional<br />
|-<br />
|4||WM8731L||IIS Audio codec<br />
|-<br />
|5||S3C2416||400MHz/266MHz optional<br />
|}<br />
|-<br />
|Package||[[File:Som2416-package.gif]]||[[File:som2416-II-package.gif]]<br />
|-<br />
|Layout||[[File:72pin-top.jpg]]||[[File:120pin-top.jpg]]<br />
|}<br />
<br />
==Pinout definitions==<br />
<br />
{|<br />
|-<br />
|<br />
{|border="1"<br />
|+Pinout definition of SOM2416-I(74pin)<br />
!Pin number||Main Function||Note||Alt Function||Note<br />
|-<br />
| 1||style="background:#99FF00" |DP0 ||style="background:#99FF00" |USB Host+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 2||style="background:#80FF80" |ETX-||style="background:#80FF80" |ETH TX-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 3||style="background:#80FF80" |ETX+||style="background:#80FF80" |ETH TX+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 4||style="background:#80FF80" |ERX-||style="background:#80FF80" |ETH RX-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 5||style="background:#80FF80" |ERX+||style="background:#80FF80" |ETH RX+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 6||style="background:#FFAA00" |nOE||style="background:#FFAA00" |bus Read signal||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 7||style="background:#FFAA00" |nWE||style="background:#FFAA00" |bus Write signal||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 8||style="background:#FFAA00" |nCS3||style="background:#FFAA00" |bus Chip Select#3||style="background:#FFFF80" |GPA14||style="background:#FFFF80" |GPIO PA14<br />
|-<br />
| 9||style="background:#FFAA00" |ADDR0||style="background:#FFAA00" |bus addr||style="background:#FFFF80" |GPA0||style="background:#FFFF80"|GPIO PA0<br />
|-<br />
|10||style="background:#FFAA00" |ADDR1||style="background:#FFAA00" |bus addr||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|11||style="background:#FFAA00" |DATA0||style="background:#FFAA00" |bus data0||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|12||style="background:#FFAA00" |DATA1||style="background:#FFAA00" |bus data1||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|13||style="background:#FFAA00" |DATA2||style="background:#FFAA00" |bus data2||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|14||style="background:#FFAA00" |DATA3||style="background:#FFAA00" |bus data3||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|15||style="background:#FFAA00" |DATA4||style="background:#FFAA00" |bus data4||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|16||style="background:#FFAA00" |DATA5||style="background:#FFAA00" |bus data5||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|17||style="background:#FFAA00" |DATA6||style="background:#FFAA00" |bus data6||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|18||style="background:#FFAA00" |DATA7||style="background:#FFAA00" |bus data7||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|19||style="background:#80FF80" |HSYNC||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC2||style="background:#FFFF80" |GPIO PC2<br />
|-<br />
|20||style="background:#80FF80" |PCLK||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC1||style="background:#FFFF80" |GPIO PC1<br />
|-<br />
|21||style="background:#80FF80" |VSYNC||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC3||style="background:#FFFF80" |GPIO PC3<br />
|-<br />
|22||style="background:#80FF80" |VDEN||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC4||style="background:#FFFF80" |GPIO PC4<br />
|-<br />
|23||style="background:#80FF80" |LCD_B0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC11||style="background:#FFFF80" |GPIO PC11<br />
|-<br />
|24||style="background:#80FF80" |LCD_B1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC12||style="background:#FFFF80" |GPIO PC12<br />
|-<br />
|25||style="background:#80FF80" |LCD_B2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC13||style="background:#FFFF80" |GPIO PC13<br />
|-<br />
|26||style="background:#80FF80" |LCD_B3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC14||style="background:#FFFF80" |GPIO PC14<br />
|-<br />
|27||style="background:#80FF80" |LCD_B4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC15||style="background:#FFFF80" |GPIO PC15<br />
|-<br />
|28||style="background:#80FF80" |LCD_G0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD2||style="background:#FFFF80" |GPIO PD2<br />
|-<br />
|29||style="background:#80FF80" |LCD_G1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD3||style="background:#FFFF80" |GPIO PD3<br />
|-<br />
|30||style="background:#80FF80" |LCD_G2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD4||style="background:#FFFF80" |GPIO PD4<br />
|-<br />
|31||style="background:#80FF80" |LCD_G3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD5||style="background:#FFFF80" |GPIO PD5<br />
|-<br />
|32||style="background:#80FF80" |LCD_G4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD6||style="background:#FFFF80" |GPIO PD6<br />
|-<br />
|33||style="background:#80FF80" |LCD_G5||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD7||style="background:#FFFF80" |GPIO PD7<br />
|-<br />
|34||style="background:#80FF80" |LCD_R0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD11||style="background:#FFFF80" |GPIO PD11<br />
|-<br />
|35||style="background:#80FF80" |LCD_R1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD12||style="background:#FFFF80" |GPIO PD12<br />
|-<br />
|36||style="background:#80FF80" |LCD_R2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD13||style="background:#FFFF80" |GPIO PD13<br />
|-<br />
|37||style="background:#80FF80" |LCD_R3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD14||style="background:#FFFF80" |GPIO PD14<br />
|-<br />
|38||style="background:#80FF80" |LCD_R4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD15||style="background:#FFFF80" |GPIO PD15<br />
|-<br />
|39||style="background:#FFFF40" |ALOUT||style="background:#FFFF40" |audio left out ||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|40||style="background:#FFFF40" |AROUT||style="background:#FFFF40" |audio right out||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|41||style="background:#FFFF40" |MIC||style="background:#FFFF40" |audio MIC in||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|42||style="background:#2099FF" |TXD0||style="background:#2099FF" |uart0 tx||style="background:#FFFF80" |GPH0||style="background:#FFFF80" |GPIO PH0<br />
|-<br />
|43||style="background:#2099FF" |RXD0||style="background:#2099FF" |uart0 rx||style="background:#FFFF80" |GPH1||style="background:#FFFF80" |GPIO PH1<br />
|-<br />
|44||style="background:#2099FF" |TXD1||style="background:#2099FF" |uart1 tx||style="background:#FFFF80" |GPH2||style="background:#FFFF80" |GPIO PH2<br />
|-<br />
|45||style="background:#2099FF" |RXD1||style="background:#2099FF" |uart1 rx||style="background:#FFFF80" |GPH3||style="background:#FFFF80" |GPIO PH3<br />
|-<br />
|46||style="background:#2099FF" |TXD2||style="background:#2099FF" |uart2 tx||style="background:#FFFF80" |GPH4||style="background:#FFFF80" |GPIO PH4<br />
|-<br />
|47||style="background:#2099FF" |RXD2||style="background:#2099FF" |uart2 rx||style="background:#FFFF80" |GPH5||style="background:#FFFF80" |GPIO PH5<br />
|-<br />
|48||style="background:#99FF00" |I2CSCL||style="background:#99FF00" |IIC||style="background:#FFFF80" |GPE14||style="background:#FFFF80" |GPIO PE14<br />
|-<br />
|49||style="background:#99FF00" |I2CSDA||style="background:#99FF00" |IIC||style="background:#FFFF80" |GPE15||style="background:#FFFF80" |GPIO PE15<br />
|-<br />
|50||style="background:#FF80FF" |SPIMISO||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE11||style="background:#FFFF80" |GPIO PE11<br />
|-<br />
|51||style="background:#FF80FF" |SPICLK||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE13||style="background:#FFFF80" |GPIO PE13<br />
|-<br />
|52||style="background:#FF80FF" |SPIMOSI||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE12||style="background:#FFFF80" |GPIO PE12<br />
|-<br />
|53||style="background:#FF80FF" |SPI_nSS||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPL13||style="background:#FFFF80" |GPIO PL13<br />
|-<br />
|54||style="background:#FFFF40" |VCCRTC||style="background:#FFFF40" |RTC Vcc||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|55||style="background:#99FF00" |SDCLK||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL9||style="background:#FFFF80" |GPIO PL9<br />
|-<br />
|56||style="background:#99FF00" |SDCMD||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL8||style="background:#FFFF80" |GPIO PL8<br />
|-<br />
|57||style="background:#99FF00" |SDDAT0||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL0||style="background:#FFFF80" |GPIO PL0<br />
|-<br />
|58||style="background:#99FF00" |SDDAT1||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL1||style="background:#FFFF80" |GPIO PL1<br />
|-<br />
|59||style="background:#99FF00" |SDDAT2||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL2||style="background:#FFFF80" |GPIO PL2<br />
|-<br />
|60||style="background:#99FF00" |SDDTA3||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL3||style="background:#FFFF80" |GPIO PL3<br />
|-<br />
|61||style="background:#2099FF" |XP||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN9||style="background:#FFFF80" |ADC in9<br />
|-<br />
|62||style="background:#2099FF" |YP||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN7||style="background:#FFFF80" |ADC in7<br />
|-<br />
|63||style="background:#2099FF" |XM||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN8||style="background:#FFFF80" |ADC in8<br />
|-<br />
|64||style="background:#2099FF" |YM||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN6||style="background:#FFFF80" |ADC in6<br />
|-<br />
|65||style="background:#FFFF40" |LCD_PWR||style="background:#FFFF40" |LCD brightness||style="background:#FFFF80" |GPF2||style="background:#FFFF80" |GPIO PF2<br />
|-<br />
|66||style="background:#FFFF40" |BUS_INT||style="background:#FFFF40" |bus int.||style="background:#FFFF80" |GPF1||style="background:#FFFF80" |GPIO PF1<br />
|-<br />
|67||style="background:#FFFF40" |nSD_CD||style="background:#FFFF40" |SD detect||style="background:#FFFF80" |GPF5||style="background:#FFFF80" |GPIO PF5<br />
|-<br />
|68||style="background:#FFFF40" |SPI_INT||style="background:#FFFF40" |SPI int.||style="background:#FFFF80" |GPF0||style="background:#FFFF80" |GPIO PF0<br />
|-<br />
|69||style="background:#FFFF40" |GPIO_INT||style="background:#FFFF40" |GPIO int.||style="background:#FFFF80" |GPF6||style="background:#FFFF80" |GPIO PF6<br />
|-<br />
|70||style="background:#99FF00" |DN1||style="background:#99FF00" |USB device-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|71||style="background:#99FF00" |DP1||style="background:#99FF00" |USB device+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|72||style="background:#99FF00" |DN0||style="background:#99FF00" |USB Host-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|73||style="background:red" |VCC3V3||style="background:red" |DC 3.3V in||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|74||style="background:red" |GND||style="background:red" |GND||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|}<br />
<br />
||<br />
<br />
{|border="1"<br />
|+Pinout definition of SOM2416-II(120pin)<br />
!Pin number||Main Function||Note||Alt Function||Note<br />
|-style="background:#80FF80"<br />
| 1||ETX-||ETH TX-||-||-<br />
|-style="background:#80FF80"<br />
| 2||ETX+||ETH TX+||-||-<br />
|-style="background:#80FF80"<br />
| 3||GND||ETH GND||-||-<br />
|-style="background:#80FF80"<br />
| 4||ERX-||ETH RX-||-||-<br />
|-style="background:#80FF80"<br />
| 5||ERX+||ETH RX+||-||-<br />
|-style="background:#80FF80"<br />
| 6||ETH_SPD||ETH SPEED||-||-<br />
|-style="background:#80FF80"<br />
| 7||ETH_LINK||ETH LINK||-||-<br />
|-style="background:red"<br />
| 8||GND||GND||-||-<br />
|-style="background:#FFAA00"<br />
| 9||nRST||System Reset||-||-<br />
|-style="background:#FFFF40"<br />
|10||BUS_CLK||bus clock||-||-<br />
|-style="background:#FFFF40"<br />
|11||nWAIT||bus nWAIT||-||-<br />
|-style="background:#FFFF40"<br />
|12||nOE||bus nOE||-||-<br />
|-style="background:#FFFF40"<br />
|13||nWE||bus nWE||-||-<br />
|-style="background:#FFFF40"<br />
|14||nCS3||bus nCS3||-||-<br />
|-style="background:#FFFF40"<br />
|15||LADDR[0]||bus LADDR[0]||-||-<br />
|-style="background:#FFFF40"<br />
|16||LADDR[1]||bus LADDR[1]||-||-<br />
|-style="background:#FFFF40"<br />
|17||LADDR[2]||bus LADDR[2]||-||-<br />
|-style="background:#FFFF40"<br />
|18||LADDR[3]||bus LADDR[3]||-||-<br />
|-style="background:#FFFF40"<br />
|19||LADDR[4]||bus LADDR[4]||-||-<br />
|-style="background:#FFFF40"<br />
|20||LADDR[5]||bus LADDR[5]||-||-<br />
|-style="background:#FFFF40"<br />
|21||LADDR[6]||bus LADDR[6]||-||-<br />
|-style="background:#FFFF40"<br />
|22||LDATA[0]||bus LDATA[0]||-||-<br />
|-style="background:#FFFF40"<br />
|23||LDATA[1]||bus LDATA[1]||-||-<br />
|-style="background:#FFFF40"<br />
|24||LDATA[2]||bus LDATA[2]||-||-<br />
|-style="background:#FFFF40"<br />
|25||LDATA[3]||bus LDATA[3]||-||-<br />
|-style="background:#FFFF40"<br />
|26||LDATA[4]||bus LDATA[4]||-||-<br />
|-style="background:#FFFF40"<br />
|27||LDATA[5]||bus LDATA[5]||-||-<br />
|-style="background:#FFFF40"<br />
|28||LDATA[6]||bus LDATA[6]||-||-<br />
|-style="background:#FFFF40"<br />
|29||LDATA[7]||bus LDATA[7]||-||-<br />
|-style="background:red"<br />
|30||Vcc||Vcc input 3.3V||-||-<br />
|-style="background:red"<br />
|31||Vcc||Vcc input 3.3V||-||-<br />
|-style="background:#99FF00"<br />
|32||LCD_PWR||lcd Power||-||-<br />
|-style="background:#99FF00"<br />
|33||HSYNC||lcd HSYNC||-||-<br />
|-style="background:#99FF00"<br />
|34||PCLK||lcd PCLK||-||-<br />
|-style="background:#99FF00"<br />
|35||VSYNC||lcd VSYNC||-||-<br />
|-style="background:#99FF00"<br />
|36||VDEN||lcd VDEN||-||-<br />
|-style="background:red"<br />
|37||GND||GND||-||-<br />
|-style="background:#99FF00"<br />
|38||VD[2]||lcd VD[2]||-||-<br />
|-style="background:#99FF00"<br />
|39||VD[3]||lcd VD[3]||-||-<br />
|-style="background:#99FF00"<br />
|40||VD[4]||lcd VD[4]||-||-<br />
|-style="background:#99FF00"<br />
|41||VD[5]||lcd VD[5]||-||-<br />
|-style="background:#99FF00"<br />
|42||VD[6]||lcd VD[6]||-||-<br />
|-style="background:#99FF00"<br />
|43||VD[7]||lcd VD[7]||-||-<br />
|-style="background:#99FF00"<br />
|44||VD[10]||lcd VD[10]||-||-<br />
|-style="background:#99FF00"<br />
|45||VD[11]||lcd VD[11]||-||-<br />
|-style="background:#99FF00"<br />
|46||VD[12]||lcd VD[12]||-||-<br />
|-style="background:#99FF00"<br />
|47||VD[13]||lcd VD[13]||-||-<br />
|-style="background:#99FF00"<br />
|48||VD[14]||lcd VD[14]||-||-<br />
|-style="background:#99FF00"<br />
|49||VD[15]||lcd VD[15]||-||-<br />
|-style="background:#99FF00"<br />
|50||VD[18]||lcd VD[18]||-||-<br />
|-style="background:#99FF00"<br />
|51||VD[19]||lcd VD[19]||-||-<br />
|-style="background:#99FF00"<br />
|52||VD[20]||lcd VD[20]||-||-<br />
|-style="background:#99FF00"<br />
|53||VD[21]||lcd VD[21]||-||-<br />
|-style="background:#99FF00"<br />
|54||VD[22]||lcd VD[22]||-||-<br />
|-style="background:#99FF00"<br />
|55||VD[23]||lcd VD[23]||-||-<br />
|-style="background:#2099FF"<br />
|56||LPOUT||audio LPOUT||-||-<br />
|-style="background:#2099FF"<br />
|57||RPOUT||audio RPOUT||-||-<br />
|-style="background:#2099FF"<br />
|58||MIC||audio MIC||-||-<br />
|-style="background:#2099FF"<br />
|59||LIN||audio LIN||-||-<br />
|-style="background:#2099FF"<br />
|60||RIN||audio RIN||-||-<br />
|-style="background:red"<br />
|61||AGND||audio GND||-||-<br />
|-style="background:#80FF80"<br />
|62||TXD0||uart TXD0||-||-<br />
|-style="background:#80FF80"<br />
|63||RXD0||uart RXD0||-||-<br />
|-style="background:#80FF80"<br />
|64||nRTS0||uart nRTS0||-||-<br />
|-style="background:#80FF80"<br />
|65||nCTS0||uart nCTS0||-||-<br />
|-style="background:#80FF80"<br />
|66||TXD1||uart TXD1||-||-<br />
|-style="background:#80FF80"<br />
|67||RXD1||uart RXD1||-||-<br />
|-style="background:#80FF80"<br />
|68||nRTS1||uart nRTS1||-||-<br />
|-style="background:#80FF80"<br />
|69||nCTS1||uart nCTS1||-||-<br />
|-style="background:#80FF80"<br />
|70||TXD2||uart TXD2||-||-<br />
|-style="background:#80FF80"<br />
|71||RXD2||uart RXD2||-||-<br />
|-style="background:#80FF80"<br />
|72||TXD3||uart TXD3||-||-<br />
|-style="background:#80FF80"<br />
|73||RXD3||uart RXD3||-||-<br />
|-style="background:#FFAA00"<br />
|74||I2C_SCL||iic||-||-<br />
|-style="background:#FFAA00"<br />
|75||I2C_SDA||iic||-||-<br />
|-style="background:#FFFF40"<br />
|76||SPIMISO||spi||-||-<br />
|-style="background:#FFFF40"<br />
|77||SPICLK||spi||-||-<br />
|-style="background:#FFFF40"<br />
|78||SPIMOSI||spi||-||-<br />
|-style="background:#FFFF40"<br />
|79||nSS||spi||-||-<br />
|-style="background:#99FF00"<br />
|80||SD0CLK||sd0||-||-<br />
|-style="background:#99FF00"<br />
|81||SD0CMD||sd0||-||-<br />
|-style="background:#99FF00"<br />
|82||SD0DAT0||sd0||-||-<br />
|-style="background:#99FF00"<br />
|83||SD0DAT1||sd0||-||-<br />
|-style="background:#99FF00"<br />
|84||SD0DAT2||sd0||-||-<br />
|-style="background:#99FF00"<br />
|85||SD0DAT3||sd0||-||-<br />
|-style="background:red"<br />
|86||GND||GND||-||-<br />
|-style="background:red"<br />
|87||VCCRTC||VCCrtc||-||-<br />
|-style="background:#2099FF"<br />
|88||OM3||mode select||-||-<br />
|-style="background:#2099FF"<br />
|89||OM2||mode select||-||-<br />
|-style="background:#2099FF"<br />
|90||OM1||mode select||-||-<br />
|-style="background:#80FF80"<br />
|91||nSD1_CS||sd1 card detect||-||-<br />
|-style="background:#80FF80"<br />
|92||SD1CLK||sd1||-||-<br />
|-style="background:#80FF80"<br />
|93||SD1CMD||sd1||-||-<br />
|-style="background:#80FF80"<br />
|94||SD1DAT0||sd1||-||-<br />
|-style="background:#80FF80"<br />
|95||SD1DAT1||sd1||-||-<br />
|-style="background:#80FF80"<br />
|96||SD1DAT2||sd1||-||-<br />
|-style="background:#80FF80"<br />
|97||SD1DAT3||sd1||-||-<br />
|-style="background:red"<br />
|98||GND||GND||-||-<br />
|-style="background:#FFAA00"<br />
|99||XP||touch||-||-<br />
|-style="background:#FFAA00"<br />
|100||YP||touch||-||-<br />
|-style="background:#FFAA00"<br />
|101||XM||touch||-||-<br />
|-style="background:#FFAA00"<br />
|102||YM||touch||-||-<br />
|-style="background:#FFFF40"<br />
|103||AIN0||ADC||-||-<br />
|-style="background:#FFFF40"<br />
|104||AIN1||ADC||-||-<br />
|-style="background:#99FF00"<br />
|105||EINT0||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|106||EINT3||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|107||EINT5||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|108||EINT6||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|109||EINT7||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|110||EINT8||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|111||EINT9||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|112||EINT10||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|113||EINT11||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|114||EINT12||Ext Int||-||-<br />
|-style="background:red"<br />
|115||GND||GND||-||-<br />
|-style="background:#2099FF"<br />
|116||DN1||usb device||-||-<br />
|-style="background:#2099FF"<br />
|117||DP1||usb device||-||-<br />
|-style="background:#99FF00"<br />
|118||EINT2||Ext Int||-||-<br />
|-style="background:#80FF80"<br />
|119||DN0||usb host||-||-<br />
|-style="background:#80FF80"<br />
|120||DP0||usb host||-||-<br />
|-<br />
|}<br />
<br />
|-<br />
|}<br />
<br />
==Manual==<br />
* SOM2416-I Hardware Reference Manual released in Aug 22,2009: [http://www.techor.com/SOM/SOM2416_hw_ref_manual_v1.1.pdf SOM2416_hw_ref_manual_v1.1.pdf download here]<br />
* [http://www.techor.com/down/s3c2416x_rev10.rar S3C2416 datasheet Rev1.1 download here]<br />
<br />
==Layout==<br />
<br />
==Errata==<br />
==Clocking==<br />
==Power management==<br />
==Interfacing to Raw LCD Panels==<br />
<br />
=Availability=<br />
<br />
==SOM2416-I([http://www.techor.com/syssite/home/shop/1/pictures/productsimg/big/281.JPG 74pin]) Revision==<br />
===Rev PRELIMINARY===<br />
===Rev 1.0===<br />
==SOM2416-II(120pin) Revision==<br />
===Rev PRELIMINARY===<br />
<br />
==SOM2416-based products==<br />
{|<br />
|'''SOM2416-I''' based 7" DPF ODM design by ourself,<br />
DC 12V in/mini USB connected to PC/4-line AV out<br />
/USB host connected U Disk/Power switch<br />
/SDMMC socket /7" AT070TN84 LCD Panel<br />
/7 push buttons/2 speaker /IrDA remote control<br />
Rev 1.0 in Sept 24,2009<br />
||[[File:SOM2416-I-DPF7-2.JPG|frame|SOM2416-I based 7" DPF,front view,Rev 1.0 in Sept 24,2009]]||[[File:SOM2416-I-DPF7.JPG|frame|SOM2416-I based 7" DPF,back view,Rev 1.0 in Sept 24,2009]]<br />
|-<br />
|Customized '''SOM2416-II''' based 5.6" Industrial Touch Screen HMI,run uCOS/II with miniGUI windows management system,rev 1.0 in Sept 1,2009<br />
||[[File:SOM2416-II-HMI1.JPG|frame|SOM2416-II based Industrial Touch Screen HMI,front and back view]]||[[File:SOM2416-II-HMI.JPG|frame|SOM2416-II based Industrial Touch Screen HMI,run uCOS/II with miniGUI]]<br />
|}<br />
<br />
==SOM2416 ODM cases==<br />
{|border="0" align="center"<br />
|+'''SOM2416 baseded ODM/OEM Cases'''<br />
|'''Industrial HMI Machine''', SOM2416-I directly <br>soldered on top of 2-layer '''App board'''(below)||A Special '''Handheld Measurement Instrument''', <br>Customized 6-layer Main Board based on S3C2416<br />
|-<br />
|[[File:Solution2.jpg|448px|Industrial HMI Machine, SOM2416-I directly <br>soldered on top of 2-layer App board(below)]]||[[File:Solution1.jpg|746px|A Special Handheld Measurement Instrument, <br>Customized 6-layer Main Board based on S3C2416]]<br />
|}<br />
<br />
=App Demo Board=<br />
{|<br />
|[[File:AppBoard800.jpg|frame|<b>AppDemoBoard Rev 1.1(KIT2416-I)</b> carries SOM2416-I]]<br />
|-<br />
|[[File:SOM2416+43TFTLCD.jpg|frame|<b>KIT2416-I</b> := <i>SOM2416-I</i> + <i>AppDemoBoard Rev 1.1</i> + <i>4.3" LCD w/ touch</i> + <i>T-Flash card</i><br><b>Back view</b> of KIT2416-I, running WINCE 5.0 of Microsoft Media Player]]<br />
|}<br />
<br />
=Adapters=<br />
==Expansion boards==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=Computer-on-Module&diff=28177Computer-on-Module2010-12-06T03:32:29Z<p>Som2416: /* Computer-on-Module Provider */</p>
<hr />
<div>A computer-on-module (COM) is a type of [http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Single-Board-Computer-SBC-Quick-Reference-Guide/ single-board computer](SBC), a subtype of an embedded computer system. It is also called [http://www.emacinc.com/som/som_select_guide.htm System on Module]System-on-Module as an extension of the concept of System on Chip (SoC) and lying between a full-up computer and a microcontroller in nature.<br />
<br />
Today's COM/SOM modules are complete computers built on a single circuit board. The design is centered on a single microprocessor with RAM, input/output controllers and all other features needed to be a functional computer on the one board. However, unlike a single-board computer, the COM module will usually lack the standard connectors for any input/output peripherals to be attached directly to the board. Instead, the wiring for these peripherals are bussed out to connectors on the board.<br />
<br />
The module will usually need to be mounted on a carrier board (or "baseboard") which breaks the bus out to standard peripheral connectors. Some COMs also include peripheral connectors and/or can be used without a carrier.<br />
<br />
A COM/SOM solution offers a dense package computer system for use in small or specialized applications requiring low power consumption or small physical size as is needed in embedded systems.<br />
<br />
Some devices also incorporate Field Programmable Gate Arrays.<br />
<br />
The terms "Computer-on-Module" and "COM" were coined by Venture Development Corporation (Natick, MA, USA) to describe this class of embedded computer boards. The term became more notable upon industry standardization of the COM Express format.<br />
<br />
A number of manufacturers offer products which are defined as system-on-module or computer-on-module. Among those are Advanced Knowledge Associates (www.a-k-a.net) in Santa Clara, CA; BCM Advanced Research (www.bcmcom.com) in Irvine, CA; Embedded Systems (www.embedded-systems.net); MEN Micro (www.menmicro.com) in Ambler, PA; DAVE Embedded Systems (www.dave.eu) in Italy, [http://www.phytec.com PHYTEC America] in Seattle, WA.<br />
<br />
== Computer-on-Module Provider ==<br />
* [[SOM]] - by [http://www.techor.com/ TECHOR.COM of China], series of 40x40x4mm Size, Weight about 10g, the smallest and lightest [[System-on-Module]] in the World!<br />
* [[SOM2416]] - by [http://www.techor.com/prod-39.html TECHOR.COM of China], Samsung 400MHz ARM926EJ-S based cost effective Application Processor,120pin out, 40x40x3.5mm<br />
* [[SOM6410]] - by [http://www.techor.com/prod-49.html TECHOR.COM of China],Samsung 667Hz ARM1176JFZ-S based cost effective Application Processor,120pin out,40x40x3.5mm<br />
* [[SOM3530]] - by [http://www.techor.com/prod-48.html TECHOR.COM of China], TI 600MHz CORETEX-A8 + 430MHz TMS320C64x+ dual core SOC/AP,120pin out, 40x40x3.5mm<br />
* [http://www.elinux.org/SBC8100 Mini8100] - by [http://www.timll.com/chinese/OMAP/mini8100.asp Timll of China], TI 600MHz CORETEX-A8 + 430MHz TMS320DM64x+ dual core,67 mm * 37 mm<br />
<br />
* '''CSB7xx''' - by [http://www.cogcomp.com Cogent Computer Systems, Inc. of USA]<br />
* '''CM-XXX''' - by [http://www.compulab.co.il CompuLab of Italia]<br />
* '''Colibri Computer Modules''' - by [http://www.toradex.com Toradex of Switzerland]<br />
* '''[http://magniel.com/omapmod.htm OMAPMOD]''' by [http://magniel.com Magniel Inc.], TI OMAP3503 / OMAP3530 CORTEX A8, 67mm x 44mm, stand-alone system in a 144-pin SO-DIMM format.<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=ARM_RealView&diff=28171ARM RealView2010-12-06T03:17:33Z<p>Som2416: /* add Realview ICE */</p>
<hr />
<div>ARM Ltd. RealView is a blanket name for development packages from ARM including for example the "RealView Developer Suite" (RVDS) which includes a compiler. However to most developers the RealView is synonymous with an evaluation board which has it's machine set-up available in the kernel ''arch/arm/mach-realview''.<br />
<br />
The RealView siblings are:<br />
<br />
* ''mach-integrator'' [[ARM Integrator]] also named "RealView Integrator" boards are the oldest and support ARM7, ARM9 and ARM10 CPUs<br />
* ''mach-versatile'' [[ARM Versatile]] also named "RealView Versatile" is middle-age and supports a family of ARM9 CPUs<br />
* ''mach-realview'' '''ARM RealView''' - the machine configurations named simply RealView are the newest ones supporting ARM11 and Cortex A8/A9 (CPUv6,CPUv7) CPUs, the product name for these is actually also "RealView Versatile" but traditionally have their own entry in the kernel tree<br />
<br />
These all have own machine entries in the ARM arch kernel tree.<br />
<br />
All these boards come in a black square box with PCI card slots, and support using PCI peripherals and e.g. a PS2 keyboard and mouse so they can more or less be used as desktop computers if so desired.<br />
<br />
However RealView boards are quite expensive and few people can afford them, while they are still the preferred choice for companies wanting to work with the very latest ARM cores.<br />
<br />
== Links ==<br />
* [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.set.boards/index.html RealView development boards] over at ARM infocenter<br />
* [http://www.arm.com/products/tools/versatile.php RealView Versatile Family]<br />
* [http://www.realviewice.com RealView ICE(RVI) Emulator] target connection adopter tool, adopting Ethernet/USB host connection to 20pin JTAG/LVDS target conection<br />
<br />
[[Category: Linux]]<br />
[[Category:Development Boards]]<br />
[[Category:ARM Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOMV210&diff=22801SOMV2102010-08-16T06:36:25Z<p>Som2416: Redirected page to SOMs</p>
<hr />
<div>#REDIRECT [[SOMs]]<br />
<br />
there's a External Link: http://openembed.org/wiki/SOMV210</div>Som2416https://elinux.org/index.php?title=SOM3530&diff=22627SOM35302010-08-04T08:07:34Z<p>Som2416: /* Events */</p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOM3530&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页!Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.ti.com/ TI(Texas Instruments)'s] [http://www.arm.com/products/CPUs/ARM_Cortex-A8.html ARM Cortex-A8] + [https://focus.ti.com/general/docs/tags/fldrsfortagTemplate.tsp?&tagName=omap TMS320C64x+] based 720MHz [[OMAP3530]] [http://focus.ti.com/docs/prod/folders/print/omap3530.html Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product-283.html '''SOM3530''' System on Module]: [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
<br />
=Events=<br />
<I><br />
'''2010.1.1''': Mass supply of SOM3530[[System-on-Module]]: OMAP3530CUS(coretex-A8+64x), 128MB DDR, 128MB FLASH, eth, audio, usb, touch etc <br />
[[File:SOM3530-array.jpg ]]<br><br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/?product-283.html SOM3530] '''Rev PRELIMINARY''' will be released in Oct 30,2009! '''SOM3530''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br><br />
[[File:SOM3530msk.jpg|SOM3530 Engineering File, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]][[File:SOM3530-L.JPG|SOM3530 samples picture,Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
</I><br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
SOM3530: 720MHz OMAP3530 (Cortex-A8 + TMS320C64x) Mini Dual-Core Embedded Module (4x4cm)<br />
<br />
* OMAP3530/25/15/03:TI OMAP3XXX dual-core embedded module<br />
* size of SOM only 40x40x4mm<br />
* weight 11g<br />
* 1 USB master<br />
* 100M Ethernet<br />
* 3 UART<br />
* IIC<br />
* SPI<br />
* LCD & touchscreen interfaces<br />
* audio input and output<br />
* SDMMC<br />
* IO ports supporting ADC,PWM,GPIO<br />
* bus lines supporting data, address, interrupt, DMA, chip select and so on<br />
* SDKs avilable for wince5,wince6, LINUX 2.6 sdk<br />
<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOM3530 Revision ==<br />
==SOM3530-based products ==<br />
==SOM3530 ODM cases ==<br />
=App Demo Board =<br />
=Adapters =<br />
== Expansion boards ==<br />
<br />
<br><br />
<br><br />
----<br />
=SOM2530/KIT3530 FAQ=<br />
----<br />
<br />
主要描述基于KIT3530开发时所遇到的一些问题及解决方法。<br><br />
<br />
==硬件问题==<br />
=== 怎么让USB OTG口工作于主、从方式? ===<br />
A:在内核启动前,如果要让USB OTG工作于主方式,则板载USB OTG接套件提供的USB A型线;如果要让USB OTG工作于从方式,则板载USB OTG接套件提供的USB B型线。<br><br />
===问题->: 如何切换到MMC/SD启动开发板?===<br />
A:按住BOOT按键,上电启动,系统改为先从MMC/SD启动,再从NAND启动,详细请参考“3.18按键”介绍。<br><br />
<br />
=== KIT3530与仿真器相连接,调试DSP和ARM===<br />
目前正在找相关的仿真器,看有否可支持的仿真器系列。<br />
=== KIT3530中的RTC电池===<br />
KIT3530出货时不带RTC电池,需用户自行配备,电池型号用 CR1220即可<br />
=== KIT3530中的U20 (ISP1504) U13 (TXS0102)芯片问题 ===<br />
ISP1504 是USB HOST芯片,由于我们的USB HOST暂未调通,怀疑是硬件问题,故目前没有把此芯片焊上去。<br><br />
U13 (TXS0102) 是DVI的一个附带电路,但是此刻芯片未影响DVI的输出,故我们没有焊接此芯片,不影响DVI的使用。<br><br />
<br />
''the ISP1504 is for the USB HOST, but at now the USB HOST is not OK, so the board we sold don't have the chips.<br><br />
U13 (TXS0102) is not used for the dvi, and it don't effect your DVI output<br />
''<br />
<br />
==linux问题==<br />
=== 开发驱动时如何打开低层调试信息?===<br />
A:make menucofig -> kernel hacking -> lowlevel debug<br><br />
<br />
=== 如何让显示输出在lcd屏与DVI输出之间切换? ===<br />
A:只需修改内核启动参数即可.<br><br />
4.3” LCD屏:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode: 4.3inch_LCD<br><br />
5.6” LCD屏:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode: 5.6inch_LCD<br><br />
7” LCD屏:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:7inch_LCD<br><br />
DVI显示器:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:720p60<br><br />
VGA显示器:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:VGA<br><br />
<br />
===tftp更新方式===<br />
板上配置有10/100M自适应网卡dm9000,用户可通过tftp下载的方式更新nand启动映像<br><br />
1)x-loader启动映像的更新<br><br />
OMAP3 KIT3530 # tftp 80000000 x-load.bin.ift_for_NAND<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'x-load.bin.ift_for_NAND'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #<br><br />
done<br><br />
Bytes transferred = 9664 (25c0 hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 134217728!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc hw<br><br />
OMAP3 KIT3530 # nand erase 0 80000<br><br />
<br />
NAND erase: device 0 offset 0x0, size 0x80000<br><br />
Erasing at 0x60000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 0 80000<br><br />
<br />
NAND write: device 0 offset 0x0, size 0x80000<br><br />
<br />
Writing data at 0x7f800 -- 100% complete.<br><br />
524288 bytes written: OK<br><br />
<br />
2)u-boot启动映像的更新<br><br />
OMAP3 KIT3530 # tftp 80000000 flash-uboot.bin<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'flash-uboot.bin'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #################################################################<br><br />
done<br><br />
Bytes transferred = 1085536 (109060 hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 134217728!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc sw<br><br />
OMAP3 KIT3530 # nand erase 80000 160000<br><br />
<br />
NAND erase: device 0 offset 0x80000, size 0x160000<br><br />
Erasing at 0x1c0000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 80000 160000<br><br />
<br />
NAND write: device 0 offset 0x80000, size 0x160000<br><br />
<br />
Writing data at 0x1df800 -- 100% complete.<br><br />
1441792 bytes written: OK<br><br />
<br />
3)内核映像更新<br><br />
OMAP3 KIT3530 # tftp 80000000 uImage<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'uImage'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #################################################################<br><br />
done<br><br />
Bytes transferred = 1991900 (1e64dc hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 268435456!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc sw<br><br />
OMAP3 KIT3530 # nand erase 280000 200000<br><br />
<br />
NAND erase: device 0 offset 0x280000, size 0x200000<br><br />
Erasing at 0x460000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 280000 200000<br><br />
<br />
NAND write: device 0 offset 0x280000, size 0x200000<br><br />
<br />
Writing data at 0x47f800 -- 100% complete.<br><br />
2097152 bytes written: OK<br><br />
<br />
4)文件系统映像更新<br><br />
OMAP3 KIT3530 # tftp 80000000 ubi.img<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'ubi.img'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #################################################################<br><br />
done<br><br />
Bytes transferred = 12845056 (c40000 hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 268435456!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc sw<br><br />
OMAP3 KIT3530 # nand erase 680000 7980000<br><br />
<br />
NAND erase: device 0 offset 0x680000, size 0x7980000<br><br />
Erasing at 0x7fe0000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 680000 $(filesize)<br><br />
<br />
NAND write: device 0 offset 0x680000, size 0xc40000<br><br />
<br />
Writing data at 0x12bf800 -- 100% complete.<br><br />
12845056 bytes written: OK<br><br />
<br />
===linux交叉编译工具安装 ===<br />
1.网站下载交叉编译工具:<br />
http://www.codesourcery.com/sgpp/lite/arm/portal/package1787/public/arm-none-linux-gnueabi/arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 <br><br />
2.解压缩软件 <br><br />
sudo tar xvf arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 -C /home/ <br><br />
<br />
3. 工具安装<br><br />
mkdir /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/mkimage /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/signGP /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/mkfs.ubifs /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/ubinize /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/ ubinize.cfg /home/embest/tools<br><br />
<br />
4。设置环境变量<br><br />
export PATH=/home/arm-2007q3/bin/:/home/embest/tools:$PATH<br><br />
<br />
===linux摄像头显示模式转化 ===<br />
<br />
===OTG主口使用问题 ===<br />
USB使用方法:<br><br />
1. 连接USB hub电源到USB HUB<br><br />
2. 连接USB OTG转接线到KIT3530板上,<br><br />
3. 上电待开发板进入linux系统<br><br />
4. 插入usb hub线到USB OTG转接线上<br><br />
5.可以插入usb 鼠标键盘到hub了<br><br />
<br />
===7LCD触摸屏不准的解决方法===<br />
修改此文件arch/arm/mach-omap2/board-omap3KIT3530.c为如下数据即可<br><br />
struct ads7846_platform_data ads7846_conf = {<br><br />
.x_max = 0x0fff,<br><br />
.y_max = 0x0fff,<br><br />
//.x_plate_ohms = 180,<br><br />
//.pressure_max = 255,<br><br />
.debounce_max = 10,<br><br />
.debounce_tol = 5,<br><br />
.debounce_rep = 1,<br><br />
.get_pendown_state = ads7846_get_pendown_state,<br><br />
.keep_vref_on = 1,<br><br />
.settle_delay_usecs = 150,<br><br />
};<br><br />
<br />
===对于NFS,KIT3530 U-boot 下的配置参数===<br />
若您需要用NFS,首先需要在PC机上将NFS的服务打开,然后接上网线,打开KIT3530板子电源,在U-boot命令行里输入:<br>setenv bootargs console=ttyS2,115200n8 root=/dev/nfs nfsroot=192.192.192.117:/home/lijr/work/nfsroot/rootfs ip=192.192.192.200:192.192.192.101:192.192.192.101:255.255.255.0:KIT3530:eth0:off<br />
<br />
==wince问题==<br />
=== 烧写wince到NAND Flash系统映像更新===<br />
1.更新文件准备<br><br />
(1) 用软件HP Disk Storage Format Tool格式化SD卡为FAT或FAT32文件系统。<br><br />
(2) 拷贝光盘目录image[\wince_6]下子目录dvi1280X720或lcd480X272下文件MLO、EBOOTNAND.nb0、NK.bin、XLDRNAND.nb0和ADevKit9000.exe到SD卡并重命名EBOOTNAND.nb0为EBOOTSD.nb0<br><br />
2. 映像更新<br><br />
(1) 按住BOOT键,后插入SD卡重新启动系统。这时系统从SD卡启动。超级终端输出启动打印信息,按[SPACE]进入EBOOT菜单。<br><br />
(2) 按[5]进入Flash管理菜单。<br><br />
(3) 分别按[a]、[b]和[c],写XLDR、EBOOT和NK映像。<br><br />
(4) 然后按[0]键回到主菜单,并分别按下[2]、[4]、[7]和[y]更改启动设备。<br><br />
(5) 拔除SD卡,后重新启动系统。这时系统将从NAND Flash启动。<br><br />
英文显示<br><br />
the method to Update the image for NAND Flash<br><br />
(1)Run the software of HP Disk Storage Format Tool and format the SD card for FAT or FAT32 filesystem.<br><br />
(2) Copy the image file(MLO, EBOOTNAND.nb0, NK.bin, AKIT3530.exe) from CD:\wince_6\image\ lcd480X272 to SD card, then change the name from EBOOTNAND.nb0 to EBOOTSD.nb0 in the SD card.<br><br />
(3) Insert the SD card to the board, press the BOOT button and then power on the board again; HyperTerminal will start printing the output information, at the same time press [SPACE] to enter the EBOOT menu.<br><br />
(4) Press [5] to enter the Flash manage menu.<br><br />
(5) Press [a], [b], [c] separately to write the image(XLDR, EBOOT, NK) to flash.<br><br />
(6) Press [0] to return to the main menu, and press [2], [4], [7], [7] to change the boot device.<br><br />
(7) Power on the system again, and then the board will boot from the NAND flash. <br><br />
<br />
=== 屏蔽WinCE启动后的触摸屏打印信息===<br />
修改函数KIT3530\SRC\DRIVERS\TOUCH\touchscreen.cpp,<br />
把564行 RETAILMSG(1, ( TEXT( "Point: (%d,%d)\r\n" ), *pUncalX, *pUncalY ) );<br />
屏蔽掉然后重新编译就行了。如下所示:<br />
//RETAILMSG(1, ( TEXT( "Point: (%d,%d)\r\n" ), *pUncalX, *pUncalY ) );<br />
=== 关闭调试串口打印===<br />
setp: <br><br />
1,commnent out the RETAILMSG call in TouchDriverCalibrationPointGet function of touchscreen.cpp <br><br />
2,commnent out the RETAILMSG call in DdsiTouchPanelGetPoint function of touchscreen.cpp <br><br />
3,commnent out the RETAILMSG call in TLED_Backlight::SetPowerState function of tled_backlight.cpp <br><br />
4,commnent out the RETAILMSG call in SetDutyCycle function of tled.cpp <br><br />
5,commnent out the RETAILMSG call in LcdPdd_LCD_Initialize function of lcd_vga.c <br><br />
6,make sure that "set BSP_NOCOM=" is not set in KIT3530.bat <br><br />
7,make sure that "set BSP_NOCOM3=" is not set in KIT3530.bat <br><br />
8,delete the "IF BSP_COM3" of _FLATRELEASEDIR/platform.reg in line 1103 <br><br />
9,delete the "ENDIF BSP_COM3" of _FLATRELEASEDIR/platform.reg in line 1124 <br><br />
10,rebuilt the BSP <br><br />
=== 关闭触摸屏校准===<br />
setp: <br><br />
在BSP包的一级目录下,有KIT3530.bat文件,在其中任一行添加:<br><br />
set IMGNOCALIBRATION=1<br><br />
然后重新build编译即可<br />
<br />
===关于触摸屏不能用的问题解决方法===<br />
是编译时使用 build and sysgen导致的,在wince下不能用bulid and sysgen编译,用它就出问题,而且必须把pb6.0重装才可以<br />
<br />
=== WINCE无法存储===<br />
在SRC\DRIVERS\BLOCK\NAND\nand_MT29F2G16.h<br />
把下面这句<br />
#define NUMBER_OF_BLOCKS (2048) // 2048 blocks<br />
改成<br />
#define NUMBER_OF_BLOCKS (1024) // 1024 blocks<br />
<br />
=== WINCE无法设置时间===<br />
1,把新的rtc.c替换原来的src/oal/oalrtc/rtc.c(可询问技术人员提供)<br />
2,在src/inc/bsp_cfg.h后面加上#define BSP_OAL_RTC_USES_TWL4030 TRUE<br />
<br />
==其他问题==<br />
=== 格式化工具下载===<br />
网址:http://www.embedinfo.com/english/download/SP27213.exe<br />
<br />
=== SD卡不能启动===<br />
推荐使用HP USB Disk Storage Format Tool 2.0.6:下载下列网址工具<br><br />
http://www.embedinfo.com/english/download/SP27213.exe<br><br />
安装后执行如下操作。<br><br />
1、把MMC/SD卡插入PC下读卡器中<br><br />
2、打开HP USB Disk Storage Format Tool <br><br />
3、选择”FAT32“系统格式<br><br />
4、点击”Start”<br><br />
5、等待格式化完成,点击”OK”<br><br />
6、把映像文件拷贝到SD卡中。<br><br />
<English><br><br />
you should downlod the tools<br><br />
http://www.embedinfo.com/english/download/SP27213.exe<br><br />
then format your SD card for the fat32,then copy the file to it, then it can be booted.<br><br />
<br />
=== 提供demo配套u-boot.bin无法修改参数===<br />
提供demo配套u-boot.bin无法修改参数,用户想要修改并保存u-boot下参数,可采用KIT3530提供u-boot源码,修改传递给内核的MACH_ID,重新编译即可。<br><br />
具体操作方法:<br><br />
1、u-boot-1.3.3源码中<br><br />
修改board/omap3KIT3530/omap3KIT3530.c文件<br><br />
找到board_init函数<br><br />
修改:<br><br />
gd->bd->bi_arch_number = MACH_TYPE_KIT3530;为<br><br />
gd->bd->bi_arch_number = XXX;<br><br />
<br />
2、重新编译u-boot<br><br />
<br />
注:<br />
1、对于angstrom,XXX为MACH_TYPE_KIT3530<br />
2、对于android,XXX为MACH_TYPE_OMAP3_BEAGLE<br />
3、对于dvsdk,XXX为MACH_TYPE_OMAP3EVM<br />
<br />
=== KIT3530跑QT程序鼠标不工作===<br />
内核目录下输入make menuconfig,添加如下配置:<br />
<br />
Device Drivers ---><br />
Input device support ---><br />
<br />
<*>Mouse interface <br />
<br />
[*]Provide legacy /dev/psaux device <br />
<br />
(1024) Horizontal screen resolution <br />
<br />
(768) Vertical screen resolution<br />
<br />
[*] Mice ---><br />
<br />
=== 解决android demo系统下静态ip的分配问题===<br />
进入系统后,串口终端下输入:<br />
<br />
ifconfig eth0 192.192.192.90<br />
<br />
ifconfig eth0 up<br />
<br />
route add default gw 192.192.192.101 dev eth0<br />
<br />
setprop net.dns1 202.96.134.133<br />
<br />
注:<br />
客户可根据实际情况修改以上ip地址。<br />
<br />
<br />
----<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=BeagleBoard_Community&diff=19123BeagleBoard Community2010-04-08T04:48:58Z<p>Som2416: /* Other OMAP boards */</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
This page collects information about [http://www.ti.com/ TI's] [http://www.arm.com/ ARM] based [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&amp;DCMP=OMAP_Feb27_2008&amp;HQS=Other+PR+omap3503pr OMAP3] [http://beagleboard.org Beagle Board].<br />
<br />
<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#ffffcc; align:right; "><br />
'''NEWS:'''<br />
* [[BeagleBoard_Trainer|Trainer Boards]] are now available from [http://tincantools.com/product.php?productid=16149&cat=0&page=1&featured TinCanTools]<br />
* [[BeagleBoard_Zippy|Zippy Boards]] are now available from [http://www.sparkfun.com/commerce/product_info.php?products_id=9731 SparkFun]!<br />
* [[BeagleBoard_Zippy2|Zippy2]] 100baseT Expansion boards for the [[BeagleBoard]] are now available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?vendor=0&keywords=zippy2 Digikey]!<br><br />
</div><br />
<br><br />
=Events=<br />
* Meet BeagleBoard at TI booth in June, 9-12th @ Linux Tag, Berlin, Germany, http://www.linuxtag.org/2010/<br />
* See TI BeagleBoard demo @ Embedded World, Nuremberg, Germany, March 2-4, 2010, Hall 11. booth 308<br />
* Each last Saturday of the month, next August 29, 2009: [[BeagleBoard/bangalore user meet|BeagleBoard Bangalore user meeting]] (Beagle Clinic India)<br />
* all over the world 2009: [http://www.ti.com/corp/docs/landing/techday09/index.shtml# TI Technology Days 2009]. <br />
* ongoing 2009: [[BeagleBoard/contest|Beagle Sponsored Project Program]] - add a cool project and get a free BeagleBoard to realize it!<br />
<br />
=Hardware=<br />
<br />
The Beagle Board is ''a low-cost, fan-less single-board computer based on TI's OMAP3 device family, with all of the expandability of today's desktop machines, but without the bulk, expense, or noise'' (from [http://beagleboard.org/ beagleboard.org]). It uses a TI [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor (ARM Cortex-A8 superscalar core ~600MHz paired with a TMS320C64x+ DSP ~430MHz and an Imagination SGX 2D/3D graphics processor). See [http://focus.ti.com/docs/prod/folders/print/omap3530.html#features OMAP3530 features] for more processor features. [[BeagleBoard#Availability|Price is USD 149]]. The design goal was to make it as simple and cheap as possible, e.g. not having a LCD added, but letting you connect all add-ons available as cheap external components. See [http://beagleboard.org/brief What is Beagle?] and [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article] for more details.<br />
<br />
The videos [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings] and [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu] give you a good intro about what BeagleBoard is about and its capabilities.<br />
<br />
==Components==<br />
<br />
{|border=0<br />
!Top view of rev B:<br />
!Top view of rev C:<br />
|-<br />
|[[Image:Bb revb top numbered.jpg]]<br />
|[[Image:Bb revc top numbered.jpg]]<br />
|-<br />
|}<br />
{|border=1<br />
!No.<br />
!Name<br />
!Comment<br />
|-<br />
|'''1'''<br />
|[http://www.ti.com/omap35x OMAP3530] processor + 256MB NAND<br />
<br />
+ 128MB DDR (rev B)<br />
<br />
+ 256MB DDR (rev C)<br />
|PoP: Package-On-Package implementation for Memory Stacking<br />
[http://www.micron.com/products/partdetail?part=MT29C2G24MAKLAJG-6%20IT 256MB NAND/128MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1435-ND DigiKey]<br />
<br />
([http://www.micron.com/products/partdetail?part=MT29C4G48MAPLCJI-6%20IT 512MB NAND/256MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1436-ND DigiKey])<br />
<br />
[http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for Beagle Board]<br />
|-<br />
|'''2'''<br />
|[http://focus.ti.com/docs/prod/folders/print/tfp410.html DVI chip (TFP410)]<br />
|<br />
|-<br />
|'''3'''<br />
|[[BeagleBoard#DVI|DVI-D]]<br />
|Connection via HDMI connector<br />
|-<br />
|'''4'''<br />
|[[BeagleBoard#JTAG|14-pin JTAG]]<br />
|1.8V only!<br />
|-<br />
|'''5'''<br />
|Expansion connector: I2C, I2S, SPI, MMC/SD<br />
|User must solder desired header into place<br />
|-<br />
|'''6'''<br />
|[[BeagleBoard#User_button|User button]] <br />
|Allows setting boot order.<br />
|-<br />
|'''7'''<br />
| Reset button<br />
|<br />
|-<br />
| '''8'''<br />
|[[BeagleBoard#EHCI|USB 2.0 EHCI HS]]<br />
|Rev A and B: not working, unpopulated<br />
<br />
Rev C: populated and working<br />
|-<br />
|'''9'''<br />
|SD/MMC+<br />
| SDHC cards are supported<br />
|-<br />
|'''10'''<br />
|[[BeagleBoard#RS232|RS-232 serial]]<br />
|<br />
|-<br />
|'''11'''<br />
|Alternate power <br />
|normally powered by USB (unmounted on REV Ax boards, see [[BeagleBoard#Errata|errata]])<br />
|-<br />
|'''12'''<br />
|[[BeagleBoard#OTG|USB 2.0 HS OTG]] <br />
|Mini-AB connector. Board can be powered from port. <br />
|-<br />
|'''13'''<br />
|Stereo In<br />
|<br />
|-<br />
|'''14'''<br />
|Stereo Out<br />
|<br />
|-<br />
|'''15'''<br />
|S-Video<br />
|<br />
|-<br />
|'''16'''<br />
|TWL4030 (Rev A thru C2 inc.)<br />
[http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] (Rev C3 onwards)<br />
|Audio CODEC, USB port, power-on reset and power management. The TWL4030 is pin-compatible with the [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] chip and was used due to the very limited availability of the TPS65950 in early board revisions.<br />
|-<br />
|'''17'''<br />
|LCD<br />
|only rev C<br />
|-<br />
|'''18'''<br />
|USB power<br />
|<br />
|-<br />
|'''19'''<br />
|Host PHY<br />
|<br />
|-<br />
|'''20'''<br />
|32kHz<br />
|<br />
|-<br />
|'''21'''<br />
|12MHz<br />
|<br />
|-<br />
|'''22'''<br />
|RS232 XVCR<br />
|<br />
|-<br />
|'''23'''<br />
|PWR SW<br />
|<br />
|-<br />
|'''24'''<br />
|VBAT<br />
|<br />
|-<br />
|}<br />
<br />
* Board size: 3" x 3" (about 76.2 x 76.2 mm)<br />
* Weight: [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/beagleboard.png ~37g]<br />
* Currently 6 layer PCB; target: 4 layer<br />
<br />
'''Bottom of rev B:'''<br />
<br />
[[Image:Beagle_bottom.jpg]]<br />
<br />
See [http://www.flickr.com/photos/jadon/sets/72157606050144396/ jadonk's photostream] for some more detailed BeagleBoard pictures.<br />
<br />
==Manual==<br />
<br />
See [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)].<br />
<br />
==Schematic==<br />
<br />
Schematic of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous are also available from [http://beagleboard.org/hardware/design BeagleBoard.org design page] including in PDF format. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.<br />
<br />
==Layout== <br />
<br />
Layout of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous layouts are also available from the [http://beagleboard.org/hardware/design BeagleBoard.org design page]. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.<br />
<br />
==Errata==<br />
<br />
# ''Boards revision A only'': The DC power jack pinout is incorrect on the PCB layout. DC_5V and GND are switched on PCB layout. Normally, the power jack has DC_5V on the center pin and GND on the sleeve (see Figure 20 of [http://www.beagleboard.org/uploads/BBSRM_6.pdf Beagle HW manual]). But on revision Ax boards the PCB layout has GND on center and DC_5V on sleeve. For this reason it is currently removed. It will be back on the Rev B board. Workaround is to remove wire connecting the two power pins on revision Ax boards and use external [http://amethyst.openembedded.net/~koen/beagleboard/beagle-power-pads.jpg power supply with switched connector] (do not connect anything to the “?” terminal. USB power will be permanently disabled and the board can only be powered from the 5V.) See [http://www.flickr.com/photos/koenkooi/2512038988/ Koen's Beagleboard powermod picture] with short descriptions, too.<br />
# ''Boards revision < A5 only'': There is excess voltage drop across R6 which is used to measure the current consumption on the board. This needs to be a .1 ohm instead of a 1 ohm resistor (SMD 0805). All revision A5 boards have been updated to .1. You can also just solder in a jumper to J2 bypassing the current read point. This issue can cause issues with the USB host port as the voltage supplied to that port can be too low.<br />
# ''Boards revision A only'': User LEDs 0 and 1 are shorted on the layout preventing them from being controlled individually. You need to control both GPIO_149 and GPIO_150 to turn on or off both LEDs. This is fixed in the Rev B boards.<br />
# ''Boards revision < A5 only'': There is an issue where on some boards the 1.8V has excessive noise on it. This is the result of two incorrect parts L1 and L3 being installed on the board. The inductors that were initially installed in the switchers are 100uH and need to be 1uH. This change will require that the board be returned for update. To check for correct parts, have a look to bottom of BeagleBoard. L1 - L3 are the larger parts there. They all have to be labeled with "102" (== 1uH). If any of these three inductors are labeled with "104" (== 100uH) they are wrong and have to be exchanged.<br />
# ''Boards revision A and B'': USB HOST (EHCI) failures. See [http://code.google.com/p/beagleboard/issues/detail?id=15 issue 15] and [http://code.google.com/p/beagleboard/wiki/USBHostTestREPRODUCE USB host test reproduce]. This is a hardware defect. [http://www.beagleboard.org/irclogs/index.php?date=2008-05-29#T00:27:06 Most probably] Rev. B board does not have the EHCI USB connector mounted. Workaround: Use [[BeagleBoard#OTG|OTG port]] with something like [http://trisoft.de/pics/ZHost.JPG mini A to USB A adapter] instead.<br />
# ''Boards revision A and < B4'': Plugging in a USB OTG cable will prevent Beagle from booting (with git kernel), see [http://code.google.com/p/beagleboard/issues/detail?id=19 issue #19], too. This is due to missing filtering capacitor at USB OTG VBUS. When the kernel driver detects that a USB OTG cable is inserted it enables the charge pump to generate VBUS. With no filtering VBUS looks like any switching regulator output with no filtering -- a huge voltage spike when the switch is on, followed by a rapid decay to a low voltage until the next switch on period. The capacitor is there to store energy between the output switch ON and OFF time, the feedback loop in the regulator does sample the cap voltage. Fix is to piggy-back solder a 0603 2.2uF ceramic capacitor to D3, see [http://www.sakoman.net/omap3/beagle/vbus-mod-d3.jpg VBUS modification D3 picture]. Revision B4 boards and newer have this fix applied. Thanks to [http://groups.google.com/group/beagleboard/msg/eb789e15c99a673d Steve] for debugging this!<br />
# ''Boards revision A and < B5'': There is some issue with 32kHz clock depending on system configuration used to clock some OMAP3 peripherals. From this e.g. GPIOs, GPTIMERs, and USB on Beagle might be affected. See [http://code.google.com/p/beagleboard/issues/detail?id=22 Issue 22]. Symptom from this is that after booting Linux kernel serial console hangs after some time and no serial input/output is possible any more. There is one software workaround and one hardware fix for this: (A) Software workaround: Don't use 32kHz timer to clock Linux, instead use MPU timer. (B) Hardware workaround: Remove [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard capacitor C70], which improves the 32kHz clock quality and avoids hang-up. Note: Revision A boards have capacitor C70 [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard at the same location] as rev. B boards. Note: Board revision >= B5 removes capacitor C70.<br />
# ''Random boards, quite rare, revision < B6'': Some random boards and quite rare, show directly after purchasing broken serial communication from host PC to BeagleBoard. Symptom is that you get a new board, get serial output from BeagleBoard in terminal program, but can't type anything at U-Boot prompt (Note: Don't mix this with errata #7. With errata #7 you are able to use U-Boot normally, but Linux prompt input stops after some time). Most users don't have this issue, though. So, first double check your serial configuration ([[BeagleBoardFAQ#Serial_connection_.231|FAQ1]], [[BeagleBoardFAQ#Serial_connection_.232|FAQ2]] and [[BeagleBoardFAQ#Serial_connection_.233|FAQ3]]). Only if you are really, really sure that anything with your serial connection is fine, consider sending the board back doing a [http://beagleboard.org/support/rma RMA request]. This issue was resolved on revision B6 and later boards.<br />
<br />
For additional (software) issues and enhancement requests see [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker], too.<br />
<br />
Note: BeagleBoard revision B6 uses different package for U9/U11.<br />
<br />
==Clocking==<br />
<br />
Some [http://www.beagleboard.org/irclogs/index.php?date=2008-07-08#T21:12:23 notes] about (ARM processor) clock rates at BeagleBoard:<br />
<br />
* ARM Cortex-A8 processor is currently clocked at 500MHz<br />
* 500MHz is the default used because it is a balance of performance and longevity<br />
* For OMAP35x 600MHz is max recommended<br />
* An additional 720MHz overdrive is supported only on high-speed grade OMAP3530/25 devices as fitted to the Beagleboard C4<br />
* At 600MHz or higher OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy<br />
* Higher than 600/720MHz is out of spec and no guarantee it will work at all (or not damage itself)<br />
<br />
* Also keep in mind that if you go higher you probably want to increase the core voltage. Some of this is mentioned in tables 3-3, 4-15 and 4-16 of the [http://focus.ti.com/lit/ds/symlink/omap3530.pdf OMAP3530 data sheet]. Some numbers:<br />
<br />
{| border="1"<br />
||'''ARM'''||'''DSP'''||'''core voltage'''<br />
|-<br />
|720 MHz||520 MHz||1.35V<br />
|-<br />
|600 MHz||430 MHz||1.35V<br />
|-<br />
|550 MHz||400 MHz||1.27V<br />
|-<br />
|500 MHz||360 MHz||1.2V<br />
|}<br />
<br />
* For some OMAP3 clock, voltage and power management discussion see [http://focus.ti.com/lit/an/sprt495/sprt495.pdf OMAP3 power management white paper], too.<br />
* The OMAP3 chip on the Beagle lacks the efuses needed for using the SmartReflex technology, see [http://www.beagleboard.org/irclogs/index.php?date=2009-02-26#T10:44:24].<br />
* There is a thermal monitor in the core, you could use to scale frequency up and down<br />
<br />
To set CPU clock to 600 MHz, there are two options. Both '''do not''' adjust the voltage, so the system may become unstable:<br />
<br />
* The u-boot command "mw 48004940 0012580c" will temporarily set the CPU clock to 600 MHz (not permanent over reset).<br />
* To permanently set the CPU clock to 600 MHz, include the above command in the "bootcmd" variable or equivalent script.<br />
<br />
* To set the DSP clock to 430 Mhz use "mw 48004040 0x0009ae0c".<br />
<br />
==Power management==<br />
<br />
* Detailed OMAP3 Power Management Information can be found [[OMAP_Power_Management|HERE]]<br />
* Latest Linux kernel power management development for TI OMAP SoCs is maintained in [http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git;a=summary Kevin's linux-omap-pm git tree]<br />
* Russ' Beagle HW modifications resulted in [http://groups.google.com/group/beagleboard/browse_thread/thread/197a8ef6b46cc828 8mW sleep for Beagle Board]<br />
<br />
Without PM kernel, the Beagle [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm consumes ~1.5 watts idle, however it also uses the same amount under load] (see bottom of that page).<br />
<br />
==DLP Pico projector==<br />
<br />
Texas Instruments is developing a Pico Video Projector Kit (PVPK) as a peripheral for the Beagle Board. The stand alone pico projector will support VGA resolution (640 x 480), RGB 888 input through a DVI interface. The physical connector on the projector will be HDMI. See [http://groups.google.com/group/beagleboard/msg/10e218972380ee48 mailing list] and [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector] for more details.<br />
<br />
It is available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23836-ND DigiKey] for $349.<br />
<br />
See [http://blog.makezine.com/archive/2009/01/tis_beagleboard_and_dlp_pico_projector.html?CMP=OTC-0D6B48984890 article from Make], too.<br />
<br />
DigiKey videos [http://www.youtube.com/watch?v=KBbCdnOj5vg part 1], [http://www.youtube.com/watch?v=zymOmduNWyI part 2] and [http://www.youtube.com/watch?v=Uj19Bi5NYeU part 3].<br />
<br />
==Interfacing to Raw LCD Panels==<br />
<br />
Currently on Rev A / B boards there is no direct access to the LCD lines before they enter the DVI framer. The REV C2 provides access to these lines. Several projects to interface an LCD to the beagleboard exist:<br />
<br />
* [[BeagleBoardRawLCD|interfacing to Raw LCD Panels]] article <br />
* [http://digitalsurveyinstruments.com/beagleperiphials/hdmi2parallel/doc/index.htm hdmi to parallel] workaround method<br />
* [http://www.harbaum.org/till/dvi2par/index.shtml dvi2par cheap diy HDMI to parallel converter]<br />
<br />
=Availability=<br />
<br />
BeagleBoards, currently Rev. C3 boards, are available from<br />
<br />
* [http://www.mouser.com/beagleboard Mouser]<br />
* [http://dkc1.digikey.com/us/mkt/beagleboard.html Digi-Key] with part number [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23428-ND 296-23428-ND].<br />
<br />
Note: For non-US Digi-Key free shipping orders:<br />
<br />
* Click the US flag on the top right corner of [http://dkc1.digikey.com/us/mkt/beagleboard.html Digi-Key] BeagleBoard page to come to the international page<br />
* Select ''Order Online'' for your country<br />
* Add quantity ''1'' and part number ''296-23428-ND''<br />
* Click ''Add to order''<br />
<br />
When ordering over 65 EUR / GBP 50 product (BeagleBoard is above), for Europe the price depends on the actual dollar to EUR/GBP rate. On nov 9, 2008 the price was EUR 124 with free shipping.<br />
<br />
Note: Some users report that they got some questions from DigiKey to be answered before board shipping is done.<br />
<br />
Note: While you get free shipping, most probably you have to pay tax e.g. ordering from Europe. Users report that they had to pay EUR ~34 - 44 VAT + importing taxes (depending on european country), resulting in EUR 137 - 147 ordering from Europe.<br />
<br />
Note: For European users, [http://www.ebv.com/fileadmin/products/Press_Print/Campaigns/2009/Product_Campaigns/Texas_Beagle_Board_englisch.pdf EBV Elektronik] sells its own blue version of the board for 179 EUR, which includes all useful accessories (DVI cable, serial cable, USB 2.0 Ethernet, USB hub, 2 GB MMC, power supply, Linux BSP).<br />
<br />
Note: German (Europe) users can order through German shops, too. For higher price, though. <br />
* [http://shop.embedded-projects.net/product_info.php/info/p159_BeagleBoard--OMAP-3-.html Embedded Projects Shop] sells BeagleBoard for EUR 199.00 + shipping.<br />
* [http://www.handheld-linux.com/wiki.php?page=Beagle%20Board Handheld-Linux]<br />
<br />
See below for ''hardware'' differences of the revisions. There are no ''software'' differences. <br />
<br />
==Revision A==<br />
<br />
There are some limited early revision Ax prototypes out there used by some hackers hanging around at #beagle channel on irc.freenode.net. See [[BeagleBoard#Errata|errata]] for limitations.<br />
<br />
==Revision B==<br />
<br />
Revision B is same as revision A, except<br />
* fix for shorted LEDs 0/1<br />
* fix for wrong power jack pinout<br />
* revision B6 uses different package for U9/U11<br />
Still has USB HOST (EHCI) failures. USB HOST (EHCI) connector isn't mounted.<br />
<br />
There are 4 revisions of the B board in the field: B4, B5, B6 and B7.<br />
<br />
The most notable difference is the use of the ES3.0 silicon in B6 and B7, other changes are not relevant to software developers.<br />
<br />
==Revision C2==<br />
Revision C2 is same as revision B7 except:<br />
* USB HOST (EHCI) is operational on revision C2, with standard USB A female connector.<br />
* Add interface for raw LCDs ([http://groups.google.com/group/beagleboard/msg/2e82c3ed6061d9d2 mockup])<br />
* It uses updated OMAP3 revision. BeagleBoard revisions B4+B5 uses OMAP3 ES 2.1 (engineering sample), while BeagleBoard revision C2 uses ES 3.0. OMAP3 ES 3.0 fixes minor issues:<br />
** updated ARM Cortex A8 silicon (r1p3) fixing a very rare [http://elinux.org/BeagleBoardFAQ#NEON_performance NEON issue] that has not been seen in real code<br />
* Power measurement feature<br />
* Uses [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] OMAP power controller instead of TWL4030<br />
* Three additional PWM signals on the expansion connector added as pin mux options to existing pins ([http://groups.google.com/group/beagleboard/browse_thread/thread/d5872b7c6d74592c?hl=en# message])<br />
* Revision detection (to be able to identify C2 board from older boards by software, e.g. for different pin mux)<br />
* 256MB RAM ([http://groups.google.com/group/beagleboard/msg/3a38d0f21cefd6b1?hl=en message]) (and still 256MB NAND like rev B)<br />
<br />
Note: Revision C2 is the first production version, and all orders from from Digi-Key are shipped as Rev C2.<br />
<br />
==Revision C3==<br />
As revision C2 boards are [http://groups.google.com/group/beagleboard/msg/e41d3c97aa7d4951 sold out], revision C3 will ship now.<br />
<br />
Revision C3 is same as revision C2 [http://groups.google.com/group/beagleboard/msg/037318fbc44139d5 except]:<br />
* Optional RTC [http://parts.digikey.com/1/parts/1454-battery-lith-coin-3v-12-5mm-vert-vl-1220-vcn.html VL1220 series] backup battery<br />
* Mounting holes conected to ground<br />
* Slightly improved S-Video<br />
<br />
==Revision C4==<br />
Revision C4 boards are the same as Revision C3 except:<br />
* Processor is 720MHz capable OMAP3<br />
* Improved USB Host PHY power rails<br />
<br />
==Clones==<br />
===EBVBeagle===<br />
EBV build and sell their own BeagleBoard called [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], see e.g. [http://fl0rian.wordpress.com/2009/03/08/the-other-beagleboard/].<br />
It is actually a BeagleBoard revision C2 with green PCB boxed with some useful accessories. It comes as a quite complete starter kit with AC adapter, USB to Ethernet adapter, MMC card, USB hub and some cables.<br />
More information in [http://www.ebv.com/en/press-print/news-pr/details/news//press-releas-54.html official press release].<br />
<br />
===Mini Board===<br />
[[Mini_Board|ICETEK-OMAP3530-Mini]] is a chinese BeagleBoard clone.<br />
<br />
===DevKit 8000===<br />
[[DevKit8000]] is a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard).<br />
<br />
===IGEPv2===<br />
[http://www.igep-platform.com/ IGEPv2 Platform] is a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, wifi+bluetooth.<br />
* 720MHz OMAP3 Processor<br />
* 512MB RAM / 512MB Flash<br />
===SOM3530===<br />
[[SOM3530]] is a chinese BeagleBoard clone [[System-on-Module]],Dimension 40x40x4mm, Maybe the smallest [[OMAP3530]]-based modules in the world! Including 100M high perfomance ethernet I/F<br />
<br />
==BeagleBoard-based products==<br />
* [http://www.alwaysinnovating.com/touchbook/ Always Innovating Touch Book], see [http://gigglehd.com/zbxe/hdforum/files/attach/images/899852/493/987/001/always_innovating_touch_book_0011.jpg]<br />
<br />
==Beagle case==<br />
<br />
*[http://specialcomp.com/beagleboard/ Special Computing]<br />
*[http://groups.google.com/group/beagleboard/browse_thread/thread/1c82316019633e51 SketchUp 3D model]<br />
<br />
=Adapters=<br />
<br />
For quite detailed information about all BeagleBoard peripherals see [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)].<br />
<br />
See [[BeagleBoardPeripherals| BeagleBoard peripherals and adapters page]] for useful add ons for Beagle Board.<br />
<br />
==Expansion boards==<br />
* [[BeagleBoardPinMux|Expansion Board Support Information]]<br />
* [[BeagleBoard_Trainer|Trainer Boards]] are now available from [http://tincantools.com/product.php?productid=16149&cat=0&page=1&featured TinCanTools] for $59.00<br />
** I2C interface(+3.3v or +5v selectable)<br />
*** Can be used with the Nintendo Wii NunChuk interface<br />
*** Pin compatible with WiiChuk Adapter<br />
*** WiiChuk Adapter is available from SparkFun <br />
** SPI inteface (+3.3v)<br />
** GPIO's(+3.3v)<br />
** Large prototyping area (0.1" x 0.1" matrix with access to power bus)<br />
** Atmega328 processor (user programmable)<br />
*** Arduino compatible<br />
*** ATmega328 power is +3.3v or +5v selectable<br />
*** Communicate to the ATmega328 via the BeagleBoard's second RS-232 uart <br />
* [[BeagleBoard Zippy]] expansion board is now available from [http://www.tincantools.com/product.php?productid=16147&cat=0&page=1&featured TinCanTools] for $79.00. basic specs are:<br />
** Battery Backed RTC<br />
** Second MMC slot<br />
** 10BaseT Ethernet<br />
** Second RS-232<br />
** +5V level I2C<br />
** AT24 EEPROM<br />
* [https://sourceforge.net/apps/mediawiki/beagleserver/index.php?title=Main_Page BeagleServer expansion board] is an Open Hardware project. Currently a high level design note is available, which describes the components to be used. It aims at the following specifications :<br />
** Aims at transforming a Beagleboard or IGEPv2 into a full-blown home server that could cater to home automation needs<br />
** Compatible with both the Beagleboard and the IGEPv2<br />
** 12V battery powered, or mains-powered (accepts 9 ~ 18V)<br />
** Enough power for an internal 2.5" or 3.5" hard-disk, USB-attached<br />
** +3.3V and +5V I2C; +5V I2C is buffered with a line buffer accepting a larger capacitance which allows I2C devices at distances up to 50m<br />
** I2C to 1-wire hub (using DS2482-800 which is supported by OWFS); plugging in 1-wire devices lights a LED which makes it easy to confirm if a 1-wire device is detected.<br />
** Real time clock with super-capacitor backup<br />
** Internal monitoring of the HW health (power supplies + temperature)<br />
** Some relays<br />
** Ethernet-based console port<br />
** a few other options (RS232 interface with CTS and RTS, SPI port, S-video, additional SD-card)<br />
* [http://www.hy-research.com/beagle_expansion.html HY Research] has some expansion board basics and example.<br />
* [http://www.hervanta.com/stuff/Beaglebot#Expansion_Board Beaglebot] uses a custom extension board.<br />
* [http://beagleboard.org/leopard Leopard Board], a Beagle buddy web camera<br />
* There is also a VGA DB15 adapter board under development for the Rev C2 board. It should be available through a yet to be annnounced outlet.<br />
<br />
In Canada, check out [[http://robotcraft.ca RobotCraft]] in London, Ontario for expansion boards.<br />
<br />
==JTAG==<br />
<br />
Depending on your JTAG tool, you'd need a 14-pin to 20-pin adapter to use an ARM debugger. The 14-pin TI JTAG connector is used on BeagleBoard and is supported by a large number of JTAG emulation products.<br />
See [[BeagleBoardJTAG]] for more information.<br />
<br />
==RS232==<br />
<br />
The pinout on the beagle board is "AT/Everex" or "IDC10". You can buy [http://www.pccables.com/07120.htm IDC10 to DB9M adapters] in many places as they are commonly used for old PCs. Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available. You can also probably rip one of those cables out of any old desktop computer, where it's being used to support the serial port. Be careful, though -- some of those cables will have that tenth hole filled in so you'd have to snap off the extraneous pin on your BeagleBoard. Keep looking until you find a cable with all 10 holes open.<br />
<br />
Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available.<br />
<br />
==USB-to-Serial Converter==<br />
<br />
Since many systems no longer come with an actual serial port, you might need to pick up a USB-to-serial converter at your local computer store to connect to your BeagleBoard. Be warned that some of them simply do not work. Many of them are based on the Prolific chip, and require the pl2303 module to be loaded. But even when two converters appear to have exactly the same characteristics as listed in /var/log/messages, if you simply can't get one to work, be ready to try a different one.<br />
<br />
==USB==<br />
There are two USB ports on the BeagleBoard, one with an EHCI controller and another with an OTG controller. As of Rev B4, the usb EHCI has been removed because of a hardware defect. Rev C will include USB EHCI working properly.<br />
<br />
===EHCI===<br />
The HS ([http://en.wikipedia.org/wiki/USB#USB_signalling HighSpeed]) USB [http://en.wikipedia.org/wiki/EHCI ECHI] controller on OMAP3 on BeagleBoard supports high-speed only. This simplifies the logic on the device. FS/LS (FullSpeed/LowSpeed) devices, such as keyboards and mice, require going through a high-speed USB 2.0 hub.<br />
<br />
According to the BeagleBoard System Reference Manual Rev C2, the EHCI port can source 5V at 500mA which is enough to power a hub and several low-power devices. However, this is only true if the BeagleBoard is powered through its power jack from a well-regulated 5V external power supply. If the BeagleBoard is powered through the OTG port, the EHCI port sources an "extremely limited" ampount of power (probably 100mA or so) so you'll need a "self-powered" USB 2.0 hub with its own external power supply. [Reference: Sections 5.6 and 7.2 of the BBSRM Rev C2.2.]<br />
<br />
'''Hardware issue on rev C3''' - the EHCI port on some rev C3 boards is unstable and will disconnect hubs/devices. Symptoms are: devices are disconnected from the port and cannot be reconnected without a reboot. It appears the shared 1.8V rail between the OMAP3530 and the power chip was getting noisy. Suggested solution (works on many boards) is adding a 0.22 uF 0805 package SMT capacitor atop the existing cap on C97. If SMT parts are not available, some boards can be repaired by a 0.22 uF through-hole capacitor across GND and VIO_1V8 on the expansion connector. See [http://groups.google.com/group/beagleboard/browse_thread/thread/5b8385f0bb1f63da] for more information.<br />
<br />
===OTG===<br />
The HS USB OTG ([http://en.wikipedia.org/wiki/USB_On-The-Go OnTheGo]) controller on OMAP3 on the BeagleBoard does have support for all the USB 2.0 speeds (LS/FS/HS) and can act as either a host or a gadget/device. The HS USB OTG port is used as the default power input for the BeagleBoard. It is possible to boot the BeagleBoard using this USB port.<br />
<br />
When using the OTG port in host mode, you must power the BeagleBoard using the +5V power jack. If you connect a USB hub, you'll probably also need external power for the USB hub as well, because according to the Hardware Reference manual the BeagleBoard OTG port only sources 100 mA. This is enough to drive a single low-power device, but probably won't work with multiple devices.<br />
<br />
The Linux kernel needs to know you want to use the OTG port in host mode. I believe OTG ports are supposed to figure this out for themselves using the OTG Host Negotiation Protocol, but for now the Linux kernel may need some help. Specifically, Pin 4 (ID) of the OTG connector needs to be shorted to Pin 5 (GND) by using a [http://trisoft.de/pics/ZHost.JPG 5-pin USB Mini-A plug] which shorts these pins together in the plug. A [http://en.wikipedia.org/wiki/USB#USB_cables 5-pin USB Mini-B plug] leaves Pin 4 floating. Unfortunately, most USB Mini plugs are unmarked as to whether they are "A" or "B".<br />
<br />
You can find "mini A" adapters that have Pin 4 shorted and offer out a full-sized USB A Female jack [http://www.electronicproductonline.com/catalog/product_info.php?products_id=2043 here.]<br />
<table><br />
<tr><td><br />
Since the right cables might be hard to get, you simply can<br />
* short circuit the two pins encircled in red in the image to the right. You can do this by running a wire between the two pins. That at least allows easier undoing the change. Actually you could even have a small switch or so between 4 and 5.<br />
or<br />
* use a "mini B" cable (easier to get) and try the soldering of the two pins at the cable's connector. Depending on the cable it should be possible to open the plastic covering of mini-B port with a sharp-edged knife, then solder the two pins together, close the covering again and use some tape. This leaves the BeagleBoard unmodified.<br />
</td><td>[[Image:usb_otg.png]]</td></tr></table><br />
The Rev C BeagleBoard has a pair of pads labeled J6 on the back of the board under the OTG connector. Shorting these pads together with a wire or solder blob connects pins 4 and 5.<br />
See Figure 20 in the BeagleBoard System Reference Manual Rev C2.2.<br />
<br />
==DVI==<br />
<br />
DVI-D connection on BeagleBoard uses a [http://en.wikipedia.org/wiki/HDMI HDMI connector]:<br />
<br />
''HDMI is backward-compatible with the single-link Digital Visual Interface carrying digital video (DVI-D or DVI-I, but not DVI-A) used on modern computer monitors and graphics cards. This means that a DVI-D source can drive a HDMI monitor, or vice versa, by means of a suitable adapter or cable, but the audio and remote control features of HDMI will not be available.''<br />
<br />
BeagleBoard can be connected to a DVI monitor using HDMI female to DVI male cable.<br />
<br />
=BootRom=<br />
<br />
OMAP3 on BeagleBoard contains a BootRom. With this, BeagleBoard can boot without any code in permanent storage (NAND) or from peripherals. This is useful for first board bring up or if your BeagleBoard is bricked. For more information about BootRom booting see [http://www.ti.com/litv/pdf/sprufd6a SPRUFD6]. <br />
<br />
==User button==<br />
<br />
With user button on BeagleBoard you can configure boot order. Depending on this button, the order used to scan boot devices is changed. The boot order is (the first is the default boot source):<br />
<br />
* User button ''not'' pressed: NAND -> USB -> UART -> MMC<br />
* User button ''is'' pressed: USB -> UART -> MMC -> NAND<br />
<br />
Technically speaking, the user button configures pin SYS.BOOT[5]. See [http://focus-webapps.ti.com/general/docs/sitesearch/searchsite.tsp?selectedTopic=1653260327&numRecords=25&searchTerm=sprufd6&statusCode=null SPRUFD6] for more details.<br />
<br />
==Serial and USB boot==<br />
<br />
Historically, using OMAP3's boot ROM for serial and USB boot, there are several tools around. The newest are Nishanth' ''OMAP U-Boot Utils'', while there are still some older tools for serial boot and USB boot. It is also possible to access the [[u-boot environment variables in linux|u-boot env from linux]].<br />
<br />
===OMAP U-Boot Utils===<br />
<br />
Nishanth' [http://code.google.com/p/omap-u-boot-utils/ OMAP U-Boot Utils] provide<br />
<br />
* ''pserial'' - OMAP specific utility which downloads a file in response to ASIC ID over serial port.<br />
* ''pusb'' - OMAP specific utility which downloads a file in response to ASIC ID over USB connection.<br />
* ''ucmd'' - Send a command to U-Boot and wait till a specific match appears.<br />
* ''ukermit - Download a file from host without using kermit to U-Boot.<br />
<br />
See [http://nishanthmenon.blogspot.com/ Nishanth' blog] and [http://groups.google.com/group/beagleboard/browse_thread/thread/c5bfb1b8ed528b52# announce mail], too.<br />
<br />
===Serial boot===<br />
<br />
Besides Nishanth' ''OMAP U-Boot Utils'', to boot from USB or UART, you need a PC tool which talks with OMAP BootRom and speaks the correct protocol to download ARM target code to BeagleBoard. Currently there are two older (experimental) tools for UART boot:<br />
<br />
* [http://omapzoom.org/gf/project/omaptools/wiki PC Serial Boot perl script]<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/80ad3da0eb2aa555 Linux C utility] (not working yet with below target code)<br />
<br />
See [http://groups.google.com/group/beagleboard/browse_thread/thread/ae2c601ebe104a4 USB and serial download target code] for some example target code to be downloaded to OMAP3 on BeagleBoard.<br />
<br />
===USB boot===<br />
<br />
Besides Nishanth' ''OMAP U-Boot Utils'', for USB boot, there is currently one (experimental) tool to boot BeagleBoard over USB:<br />
<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/2b9e99886bb7a747 Linux C utility]<br />
<br />
See [http://groups.google.com/group/beagleboard/browse_thread/thread/ae2c601ebe104a4 USB and serial download target code] for some example target code to be downloaded to OMAP3 on BeagleBoard.<br />
<br />
See [[BeagleBoardRecovery#USB_recovery|USB recovery section]] how to use USB boot for board recovery.<br />
<br />
==NAND boot==<br />
<br />
See [[BeagleBoardNAND|NAND boot]] article.<br />
<br />
==MMC/SD boot==<br />
<br />
Currently, [http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard boot the BeagleBoard with MMC/SD] is the only working way for first board bring up.<br />
<br />
===MMC/SD formatting===<br />
<br />
As described in above MMC/SD boot description, you have to ''create a bootable partition on MMC/SD Card''. This can be done using e.g. Windows or Linux tools.<br />
<br />
'''Windows'''<br />
<br />
See ''HP USB Disk Storage Format Tool 2.0.6'' description on [http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard boot the BeagleBoard with MMC/SD] page.<br />
<br />
'''Linux'''<br />
<br />
Please see [http://wiki.omap.com/index.php?title=MMC_Boot_Format OMAP3 MMC Boot Format].<br />
<br />
===Dual partition card===<br />
<br />
You can [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat create a dual-partition card], booting from a FAT partition that can be read by the OMAP3 ROM bootloader and Windows, then utilizing an ext2 partition for the Linux root file system.<br />
<br />
To mount second ext2 partition as root file system (e.g. containing contents of [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode rd-ext2.bin]) use kernel boot arguments (e.g. in uboot using ''setenv bootargs''):<br />
<br />
console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait<br />
<br />
===U-Boot booting===<br />
<br />
If your MMC/SD card formatting is correct and you put [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode MLO, u-boot.bin and uImage] on the card you should get a u-boot prompt after booting beagle board. E.g. (output from terminal program with 115200 8N1):<br />
<br />
...40T.........XH.H.U�..Instruments X-Loader 1.41<br />
Starting on with MMC<br />
Reading boot sector<br />
<br />
717948 Bytes Read from MMC<br />
Starting OS Bootloader from MMC...<br />
<br />
U-Boot 1.1.4 (Apr 2 2008 - 13:42:13)<br />
<br />
OMAP3430-GP rev 2, CPU-OPP2 L3-133MHz<br />
TI 3430Beagle 2.0 Version + mDDR (Boot ONND)<br />
DRAM: 128 MB<br />
Flash: 0 kB<br />
NAND:256 MiB<br />
In: serial<br />
Out: serial<br />
Err: serial<br />
Audio Tone on Speakers ... complete<br />
OMAP3 beagleboard.org #<br />
<br />
Using this u-boot prompt, you now can start kernel uImage stored on MMC card manually:<br />
<br />
OMAP3 beagleboard.org # mmc init<br />
OMAP3 beagleboard.org # fatload mmc 0:1 0x80000000 uimage<br />
OMAP3 beagleboard.org # bootm<br />
<br />
If you like to make that happen every boot:<br />
<br />
OMAP3 beagleboard.org # set bootcmd 'mmc init ; fatload mmc 0:1 0x80000000 uimage ; bootm' ; saveenv<br />
<br />
=Code=<br />
<br />
Code and binaries for BeagleBoard are available at various places.<br />
<br />
==Binaries==<br />
<br />
BeagleBoard pre-built binaries and source code can be found at [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode Beagle source code] and [http://code.google.com/p/beagleboard/downloads/list downloads] page. These are the locations where "official" TI code is available. Please note that this code is mainly for reference and testing. More up to date binaries and code is available by community. Community took (parts) of TI reference code, improves and updates it. <br />
<br />
Actually, [http://www.angstrom-distribution.org/node/47 Koen's prebuilt Beagleboard demo images] are up to date binaries including e17 as window manager, the abiword word processor, the gnumeric spreadsheet application, a NEON accelerated mplayer and the popular NEON accelerated omapfbplay which gives you fullscreen 720p decoding. The [http://www.angstrom-distribution.org/demo/beagleboard www.angstrom-distribution.org/demo/beagleboard] directory should contain all the files you need:<br />
<br />
* [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.bin u-boot.bin]<br />
* [http://www.angstrom-distribution.org/demo/beagleboard/MLO MLO]<br />
* [http://www.angstrom-distribution.org/demo/beagleboard/uImage uImage]<br />
* [http://www.angstrom-distribution.org/demo/beagleboard/Angstrom-Beagleboard-demo-image-glibc-ipk-2009.X-test-20090104-beagleboard.rootfs.tar.bz2 rootfs]<br />
<br />
See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat beagle wiki] on how to setup your SD card to use all this goodness.<br />
<br />
==Source==<br />
<br />
Besides above binary and source images (TI's and communities one), for various parts of Beagle software stack there are community supported [http://git.or.cz/ git] repositories available. <br />
<br />
===X-Loader===<br />
<br />
Steve did some work to consolidate and update X-Loader from various sources and put it in a [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=x-load-omap3.git;a=summary X-Loader git repository]. Get it by<br />
<br />
git clone git://gitorious.org/x-load-omap3/mainline.git xloader<br />
cd xloader/<br />
<br />
Build:<br />
<br />
make distclean<br />
make omap3530beagle_config<br />
make<br />
<br />
Result will be a ~20k sized ''x-load.bin'' in main directory.<br />
<br />
===U-Boot===<br />
<br />
[http://www.denx.de/wiki/U-Boot/WebHome Mainline U-Boot] has good support for BeagleBoard. Get it by:<br />
<br />
git clone git://git.denx.de/u-boot.git u-boot-main<br />
cd u-boot-main<br />
git checkout --track -b omap3 origin/master<br />
<br />
Build (assuming [[ARMCompilers#Recommendations|Code Sourcery GCC]]):<br />
<br />
make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper<br />
make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_beagle_config<br />
make CROSS_COMPILE=arm-none-linux-gnueabi- <br />
<br />
Result will be a ~160k sized ''u-boot.bin'' in main directory.<br />
<br />
Note: Due to (patch and binary) size, BeagleBoard splash screen was removed from upstream version. If you want it back, use [http://groups.google.com/group/beagleboard/browse_thread/thread/3ad9b803a3418624 U-Boot v1 BeagleBoard splash screen patch].<br />
<br />
Note: For experimental U-Boot patches not ready for mainline yet, Steve's [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=summary Beagle U-Boot git repository] is used to test them. Get it by:<br />
<br />
git clone git://gitorious.org/u-boot-omap3/mainline.git u-boot-omap3<br />
cd u-boot-omap3<br />
git checkout --track -b omap3-dev origin/omap3-dev<br />
<br />
Note: For changing the screen resolution there is one option modifying the file in "include/configs/omap3_beagle.h" and adjusting the maximum resolution before compiling as describe in [http://gitorious.org/linux-omap-dss2/linux/blobs/master/Documentation/arm/OMAP/DSS ARM OMAP2/3 Display Subsystem]<br />
<br />
===Linux kernel===<br />
<br />
[http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary Git repository] of [http://muru.com/linux/omap/ OMAP Linux kernel] contains Beagle support. Get it by:<br />
<br />
git clone git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git linux-omap-2.6<br />
cd linux-omap-2.6<br />
<br />
Build:<br />
<br />
make distclean<br />
make omap3_beagle_defconfig<br />
make menuconfig # only needed if you want to change the default configuration<br />
make uImage<br />
<br />
The result will be a ''uImage'' in ''arch/arm/boot/'' directory.<br />
<br />
If you use the OE toolchain and want to build outside of the OE tree you should do<br />
ARCH=arm<br />
PATH=~/oe/tmp/cross/armv7a/bin:~/oe/tmp/staging/i686-linux/usr/bin:$PATH # add cross tools to your path<br />
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- distclean<br />
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- omap3_beagle_defconfig<br />
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- menuconfig # only needed if you want to change the default configuration<br />
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage<br />
Note: the staging dir in the path is for mkimage. If you've build a kernel before with oe, the program should be there<br />
<br />
Note: If you are interested in kernel development have a look to [[BeagleBoardLinuxKernel|manually compiling BeagleBoard kernel]], too.<br />
<br />
===Experimental kernel patches and hacks===<br />
<br />
Some beagle developers maintain their own kernel experimental patches and hacks not ready for upstream:<br />
<br />
* [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap Koen's collection of kernels patches for OE] and the [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap_git.bb list of relevant patches]<br />
* [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=shortlog;h=refs/heads/test Steve's kernel tree], a clone of main OMAP git with additional patches, mainly beagle audio (ASOC) related.<br />
* [http://git.mansr.com/?p=linux-omap;a=summary Mans' kernel tree], a clone of main OMAP git with additional patches, mainly display & framebuffer related.<br />
* [http://www.bat.org/~tomba/linux-omap.html Tomi's kernel tree], a clone of main OMAP git with display sub-system patches, replacing the entire display driver with one that is the likely direction moving forward.<br />
<br />
=Compiler=<br />
<br />
TI OMAP3530 processor on BeagleBoard contains an ARM Cortex-A8 general purpose processor and a TMS320C64x+ DSP.<br />
<br />
==ARM==<br />
<br />
There is broad compiler support including gcc - please see [http://www.elinux.org/ARMCompilers ARM Compilers]<br />
<br />
==C64x+ DSP==<br />
<br />
A free C64x DSP compiler is available as [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html Linux hosted C6x Code Generation Tools] (TMS320C6000 C/C++ CODE GENERATION TOOLS 6.1.3 July 2008).<br />
<br />
Note: my.TI account required. You may create an account [https://my.ti.com here]<br />
<br />
Note: Old c6000 Linux compiler available on [ftp://ftp.ti.com/pub/cs/linux_cgt500.tar.gz TI FTP site]. Does NOT support c64x+ core in OMAP3 devices. Not recommended.<br />
<br />
You can also utilize the [http://focus.ti.com/dsp/docs/dspsupportaut.tsp?familyId=44&sectionId=3&tabId=416&toolTypeId=30 full-CCS free evaluation tools for 120 days], but they currently require purchase to upgrade to service release 9 to support full JTAG debugging with supported JTAG hardware.<br />
<br />
See [[BeagleBoard/DSP_Howto| BeagleBoard DSP howto]] for information about how to use the DSP.<br />
<br />
=Cortex A8 ARM features =<br />
<br />
ARM Cortex-A8 in OMAP3 is a high performance dual-issue applications processor which reaches a performance of 2.0 DMIPS/MHz (compared to ARM11 at 1.2 DMIPS/MHz). It is ARM v7 architecture, which is fully backwards compatible with application code for previous ARM processors.<br />
<br />
It includes a floating point unit (ARM VFPv3 architecture) and the ARM NEON SIMD instruction set.<br />
<br />
See [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] article for an intro into VFP-lite and NEON.<br />
<br />
===ARM NEON===<br />
<br />
NEON is a 64/128-bit wide SIMD vector extension for ARM, which has been architected to be an efficient C compiler target as well as being used from assembly language. It has 32x 64-bit registers (with a dual view as 16x 128-bit registers) which can hold the following datatypes:<br />
* 64-bit signed/unsigned<br />
* 32-bit signed/unsigned<br />
* 32-bit single precision floating point<br />
* 16-bit signed/unsigned<br />
* 8-bit signed/unsigned<br />
<br />
The key advantage of NEON is very high performance vector math processing, whilst being easy to program. It is the same thread of control as the ARM (but different instructions), and is supported by the same tools, debuggers and operating systems.<br />
<br />
The NEON instruction set is documented in ARM's [http://infocenter.arm.com/help/topic/com.arm.doc.dui0204i/DUI0204I_rvct_assembler_guide.pdf RealView Compilation Tools Assembler Guide].<br />
<br />
For NEON optimized libraries see [http://www.us.design-reuse.com/news/18429/aac-mp3-mpeg-4-h-264-fft-openmax-cortex-a8-neon-arm11-processors.html ARM Releases AAC, MP3, MPEG-4, H.264 and FFT OpenMAX DL Libraries, Highly Optimized for Cortex-A8/NEON and ARM11 Processors]. Note: Read the [http://www.arm.com/products/esd/openmax_v7libraries.html EULA].<br />
<br />
NEON is currently used by<br />
* ffmpeg - libavcodec used by mplayer, omapfbplay, and many other linux applications<br />
* libpixman - used by X.org and Mozilla & Webkit browsers to render text and graphics<br />
* Bluez - official Linux Bluetooth stack<br />
<br />
=== ARM Cortex Floating Point ===<br />
<br />
There are two types of instructions in the ARM v7 ISA that handle floating point:<br />
<br />
1) '''VFPv3''' Floating point instruction set (used for single/double precision scalar operations).<br />
These is used by gcc for C floating point operations on 'float' and 'double'<br />
<br />
2) '''NEON''' [http://www.arm.com/products/multimedia/neon/ NEON] vectorized single precision operations (2 values in a D-register, or 4 values in a Q-register)<br />
These can be use by gcc when -ftree-vectorize is enabled and -mfpu=neon is specified, and the code can be vectorized. In other cases the VFPv3 scalar ops will be used.<br />
<br />
ARM Cortex-A processors have separate floating point pipelines that handle these different instructions.<br />
<br />
On Cortex-A8, the designers' focus was on the NEON unit performance which can sustain 1 cycle/instr throughput (processing 2 single-precision values at once). The scalar VFPv3 FPU cannot achieve this level of performance (cycle timings are in the Cortex-A8 TRM download), but it is still a lot better than doing floating point using integer instructions.<br />
<br />
If you need the highest performance floating point on Cortex-A8, you need to use single precision and ensure the code uses the NEON vectorized instructions:<br />
* use gcc with -ftree-vectorize (possibly modify source code to make it vector friendly)<br />
* use NEON instrinsics (#include <arm_neon.h>, float32x2_t datatype and vmul_f32() etc)<br />
* use NEON asm directly<br />
<br />
Keep in mind that mixing NEON and ARM load/stores can sometimes stall significantly. See [http://hardwarebug.org/2008/12/31/arm-neon-memory-hazards/ this link] for more info.<br />
<br />
On Cortex-A9, there is a much higher performance floating point unit which can sustain 1 cycle/instr throughput, with low result latencies.<br />
<br />
=Board recovery=<br />
<br />
If you played e.g. with the contents of the [http://www.sakoman.net/omap3/flash%20procedure.txt NAND], it might happen that the Board doesn't boot any more (without pressing user button) due to broken NAND content. See [[BeagleBoardRecovery|BeagleBoard recovery]] article how to fix this.<br />
<br />
=Development environments=<br />
<br />
Instead of just using compiler + editor, you can use complete image create "development tool chains" which integrate compiler, build system, packaging tools etc. in one tool chain.<br />
<br />
==OpenEmbedded==<br />
<br />
For [http://www.openembedded.org/ OpenEmbedded] (OE), there are some hints how to [http://www.beagleboard.org/irclogs/index.php?date=2008-04-29#T13:06:25 start with OE for BeagleBoard]. See [[BeagleBoardAndOpenEmbeddedGit|BeagleBoard and OpenEmbedded Git]] and [http://wiki.openembedded.org/index.php/Getting_Started OpenEmbedded getting started] as well.<br />
<br />
In the OE getting started document, for BeagleBoard replace ''MACHINE = "om-gta01"'' by ''MACHINE = "beagleboard"''. After confirming ''bitbake nano'' works, try ''bitbake console-image''. The first time you run bitbake OE will download all the needed source and build the tool chain. This will take several hours. After all went fine, the output is in ''${OE_ROOT}/tmp/deploy/glibc/images/beagleboard''.<br />
<br />
Note: Koen has some BeagleBoard [http://amethyst.openembedded.net/~koen/index.php?path=beagleboard/ source and binary images] built with OE. There, ''Angstrom-console*'' images don't include an X server, you can still use a e.g. DVI-D screen with console, but you won't have a GUI. ''Angstrom-x11*'' images contain an X server.<!-- DEAD LINK: resulting in something like [http://scap.linuxtogo.org/files/fc987d4acb2c745fb7e19cf4dca8de70.png this].--><br />
<br />
===One very important note:=== <br />
<br />
It's important to have an X-Loader on your Beagleboard that uses the uImage on the SD Card that goes with Angstrom. The B6 Beagleboards do not appear to come with such an X-Loader. So you likely will have to upgrade the X-Loader. Here's what to do:<br />
* Make an SD Card with the [http://www.angstrom-distribution.org/demo/beagleboard Angstrom Demo files]. See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat Beagleboard Wiki Page] for more info on making the SD Card.<br />
* Put the SD Card in the Beagle, and boot up to the U-Boot Prompt.<br />
* Do the first six instructions in the [http://code.google.com/p/beagleboard/wiki/BeagleNANDFlashing Flashing Commands with U-Boot] section. <br />
* Reboot the Beagle to see that the new X-Loader is properly loaded.<br />
<br />
This will update the X-Loader to a newer version that will automatically load uImage from the SD Card when present -- rather than always using the uImage in the Beagleboard NAND.<br />
<br />
==Eclipse==<br />
The Eclipse [http://www.eclipse.org/cdt/ C Development Tools Project] provides a "fully functional C and C++ Integrated Development Environment (IDE) for the Eclipse platform". The Eclipse [http://www.eclipse.org/dsdp/tm/ DSDP Target Managment Project] provides a "Remote System Explorer" (RSE) plugin that simplifies downloading files to the BeagleBoard and editing files on the BeagleBoard within the Eclipse IDE. A Linux Target Agent is available as part of the [http://wiki.eclipse.org/DSDP/TM/TCF_FAQ Target Communications Framework (TCF) component]. Info on how RSE is used for e.g. Gumstix development is described in [http://groups.google.com/group/beagleboard/browse_thread/thread/509831f7c24cb79f# this post].<br />
<br />
==Android==<br />
[http://source.android.com Android] platform is a software stack for mobile devices including an operating system, middleware and key applications. Developers can create applications for the platform using the [http://code.google.com/android/ Android SDK]. Applications are written using the Java programming language and run on Dalvik, a custom virtual machine designed for embedded use which runs on top of a Linux kernel.<br />
<br />
There are several resources for Android on OMAP (Beagle) available:<br />
<br />
'''OMAPZOOM'''<br />
<br />
You can find Android port for OMAP ZOOM architecture on [https://omapzoom.org/gf/project/omapandroid/wiki/ OMAPZoom.org's wiki page on Android]. <br />
<br />
'''EMBINUX'''<br />
<br />
[http://beagleboard.org/project/android Beagleboard.org's Android project page] [http://groups.google.com/group/beagleboard/browse_thread/thread/7b422f113ce489b5 announced], the successful porting of Android on Beagle board by [http://embinux.com EMBINUX&trade;] Team. The [http://labs.embinux.org/git/ source code] and [http://www.embinux.com/download_beagle.php binaries] are available for download and review. <br />
<br />
Detailed instructions, for porting Android on Beagle Board, are available [http://labs.embinux.org/index.php/Main_Page here]. Current release supports input devices (keyboard/mouse), network and sound.<br />
<br />
You can [http://in.youtube.com/watch?v=nADn_vNVEKw watch Android booting] on Beagle Board.<br />
<br />
'''Android on OMAP wiki'''<br />
<br />
Wiki page for Andorid on OMAP can be found [[Android on OMAP|here]]<br />
<br />
'''0xdroid'''<br />
<br />
[http://gitorious.org/0xdroid 0xdroid], the enhanced version of Android on Beagleboard by [http://0xlab.org 0xlab]. The [http://gitorious.org/0xdroid source code], [http://downloads.0xlab.org/ pre-built binaries], and [http://code.google.com/p/0xdroid/issues/list issue tracker] are available for review and reference.<br />
<br />
The latest development supports OMAP audio, OMAP video overlays, ARM Cortex A8 NEON/Thumb2 performance optimizations, mouse cursor, hot-pluggable USB keyboard & mouse, user-friendly installer for system image, and various Android tweaks. Detailed instructions for 0xdroid are available through [http://code.google.com/p/0xdroid/wiki/MainPage Google Code wiki].<br />
<br />
You can [http://www.youtube.com/watch?v=v6wdTOHrwQw watch 0xdroid demo video] on Beagle Board.<br />
* [http://www.youtube.com/watch?v=v6wdTOHrwQw 0xdroid demo video (1)]<br />
* [http://www.youtube.com/watch?v=ol9LWBKXXwQ 0xdroid demo video (2)]<br />
<br />
==Mamona==<br />
<br />
[http://dev.openbossa.org/trac/mamona/wiki Mamona] is an embedded Linux distribution for ARM EABI. The main goal of the Mamona Project is to offer a completely open source alternative/experimental platform for [http://maemo.org/ Maemo] using only free and open source components. Mamona [http://rsalveti.wordpress.com/2008/09/12/mamona-02-is-out 0.2] [http://franciscoalecrim.com/blog/2008/07/29/mamona-working-with-beagleboard/ supports] [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12013&contentId=28741 OMAP3430 Software Development Platform (SDP)], so you can also use it at Beagle (OMAP3530), too. Work is being done to officially support Beagle.<br />
<br />
==Ubuntu==<br />
<br />
See [[BeagleBoardUbuntu|Ubuntu (ARM)]] installation guide how to install Ubuntu (ARM) on BeagleBoard.<br />
<br />
==Debian ARM==<br />
<br />
See [[BeagleBoardDebian|Debian (ARM)]] installation guide how to install Debian (ARM) on BeagleBoard.<br />
<br />
==Handhelds Mojo ARM==<br />
<br />
See [[BeagleBoardHandheldsMojo|Handhelds Mojo (ARM)]] installation guide how to install Handhelds Mojo (ARM) port of Ubuntu on BeagleBoard. (The Mojo project is no longer active, see the Official Ubuntu ARM-port above instead)<br />
<br />
==Scratchbox==<br />
<br />
[http://www.scratchbox.org/ Scratchbox] is a cross-compilation toolkit designed to make embedded Linux application development easier. It also provides a full set of tools to integrate and cross-compile an entire Linux distribution. See [http://felipec.wordpress.com/2009/06/07/installing-scratchbox-1-and-2-for-arm-cross-compilation/ Felipe's Scratbox 1 and 2 intro], too.<br />
<br />
=Software hints=<br />
<br />
This section collects hints, tips & tricks for various software components running on beagle.<br />
<br />
==QEMU==<br />
<br />
[[Qemu|QEMU]] [http://vm-kernel.org/blog/2008/12/15/linux-is-running-on-qemu-omap3/ supports OMAP3] being able to boot a BeagleBoard Linux kernel.<br />
<br />
==Linux hints==<br />
<br />
See BeagleBoard [http://code.google.com/p/beagleboard/wiki/LinuxHints Google wiki Linux hints] page (for Linux WTBU (Wireless TI Business Unit) kernel [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode 2.6.22]). Currently featuring:<br />
<br />
* Switching video output between DVI-D and S-Video<br />
* Disabling framebuffer blanking<br />
* Listing USB devices<br />
<br />
==lmbench==<br />
<br />
Avik posted a detailed [http://groups.google.com/group/beagleboard/browse_thread/thread/c8b8f07ce61161a1 step-by-step procedure] to run [http://sourceforge.net/project/showfiles.php?group_id=14418 lmbench] on Beagle.<br />
<br />
==Mediaplayer (FFmpeg)==<br />
<br />
There is a thread how to get a [http://groups.google.com/group/beagleboard/browse_thread/thread/9b8025fc15120fd9# mediaplayer] with NEON optimization (FFmpeg) to run on Beagle. Includes compiler hints and patches.<br />
<br />
==Java==<br />
<br />
When using the [[BeagleBoard#OpenEmbedded|OpenEmbedded]]-based Angstrom image you have the following options of Java support:<br />
* JamVM + GNU Classpath (small vm, fast interpreter, J2SE-like)<br />
* Cacao + GNU Classpath (JIT compiler, J2SE-like)<br />
* PhoneME Advanced Foundation (JIT compiler, CDC)<br />
<br />
Java support in OpenEmbedded/Angstrom ([http://wiki.openembedded.net/index.php/Java details]) is provided voluntarily through [http://jalimo.org Jalimo].<br />
<br />
See a [http://groups.google.com/group/beagleboard/browse_thread/thread/102f627253919783# post at mailing list], too.<br />
<br />
OpenEmbedded users can add the [http://evolvis.org/scm/?group_id=11 Jalimo Subversion repository] as an overlay (instructions are in the repository). This will allow them to build OpenJDK packages. Inclusion of these recipes in mainline OpenEmbedded is planned but still ongoing.<br />
<br />
The recipes offer the following functionality:<br />
<br />
* OpenJDK + Hotspot (Zero port) (all J2SE functionality, including JVMTI, interpreted only)<br />
* OpenJDK + Cacaco (all J2SE library features, missing JVMTI, decent JIT compiler)<br />
* OpenJDK + Hotspot (Shark port) (not working yet)<br />
<br />
[http://camswl.com/ Edward Nevill] from ARM Ltd. is working on interpreter optimization in Zero for ARM.<br />
<br />
People interested in getting this stuff working better should contact people on:<br />
* [http://evolvis.org/mail/?group_id=11 Jalimo Mailinglist]<br />
* [http://mail.openjdk.java.net/mailman/listinfo/distro-pkg-dev Icedtea Mailinglist]<br />
<br />
You should also check out IcedTea's [http://iced-tea.org/wiki/FrequentlyAskedQuestions FAQ].<br />
<br />
=Graphics accelerator=<br />
<br />
OMAP3530 used on BeagleBoard contains a graphics accelerator (SGX) based on the SGX core from [http://www.imgtec.com/ Imagination Technologies]. [http://www.imgtec.com/powervr/powervr-graphics.asp PowerVR] SGX530 is a new generation of programmable PowerVR graphics and video IP cores. Only the kernel portions of Linux drivers will be open source. The PowerVR folks will provide binary user-space libraries. Using the EMail contact at [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12700&contentId=27458 TIs Mobile Gaming Developers page] there are Linux v2.6 OMAP3430 SDKs for OMAP3 Zoom and SDP supporting OpenGL ES v2.0, OpenGL ES v1.1 and OpenVG 1.0 available.<br />
<br />
Tutorial:<br />
* [http://code.google.com/p/beagleboard/wiki/HowtoUseSGXunderAngstrom How to use SGX with Angstrom in OE]<br />
<br />
Some videos:<br />
<br />
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle working with Linux 2.6.27]<br />
* [http://www.youtube.com/watch?v=24TXpqa9jG0&feature=related OpenGL ES 2.0 shader effects on OMAP3]<br />
* [http://www.youtube.com/watch?v=-UFUbqoNgs8&feature=related 3D User Interface on OMAP3 Platform]<br />
* [http://www.youtube.com/watch?v=8KcNgeUriqA 3D Mapping using OpenGL ES 2.0 on OMAP3 Platform]<br />
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]<br />
* [http://www.hitlabnz.org/wiki/EmbeddedAR An Augmented Reality application combining ARToolkit and OpenGL ES 2.0]<br />
<br />
=Beginners guide=<br />
<br />
You just got your new BeagleBoard, and now? See [[BeagleBoardBeginners|beginners guides]].<br />
<br />
=FAQ=<br />
<br />
For BeagleBoard frequently asked questions (FAQ) see [[BeagleBoardFAQ|community FAQ]] and "official" [http://beagleboard.org/support/faq BeagleBoard.org FAQ].<br />
<br />
=Links=<br />
==Home page==<br />
[http://beagleboard.org/ beagleboard.org] (beagle board home)<br />
* Using [http://www.google.de/ Google] you can search beagleboard.org (including [http://www.beagleboard.org/irclogs/ IRC logs]) using ''site:beagleboard.org <search term>''<br />
<br />
==Manuals and resources==<br />
* [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard HW Reference Manual (rev. C2)]<br />
* [http://beagle.s3.amazonaws.com/BBSRM_7_2_0.pdf BeagleBoard HW Reference Manual (rev. B7)]<br />
* [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)]<br />
* [http://www.beagleboard.org/uploads/BBSRM_B5.pdf BeagleBoard HW Reference Manual (rev. B5)]<br />
* [http://www.beagleboard.org/uploads/Beagle_HRM_B4.pdf BeagleBoard HW Reference Manual (rev. B4)]<br />
* [http://www.beagleboard.org/uploads/Beagle_HW_Reference_Manual_A_5.pdf BeagleBoard HW Reference Manual (rev. A5)]<br />
* [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor description and manuals<br />
* [http://code.google.com/p/beagleboard/ Beagle at code.google.com]<br />
* [http://focus.ti.com/dsp/docs/dspsupporttechdocs.tsp?sectionId=3&tabId=409&familyId=1526&documentCategoryId=4&techDoc=4 OMAP3530/25 CBB BSDL Model]<br />
* [http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for Beagle Board]<br />
* [http://beagleboard.org/resources Beagleboard resources page with hw docs]<br />
* Some [http://www.rasterman.com/ performance comparison] of BeagleBoard Rev. B with some other ARM/PC systems.<br />
* OMAP3 pinmux [http://www.hy-research.com/omap3_pinmux.html setup]<br />
* [http://elinux.org/BeagleBoardPinMux OMAP3 eLinux pinmux page]<br />
<br />
==Contact and communication==<br />
* [http://groups.google.com/group/beagleboard Beagle board discussion list]<br />
* [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker]<br />
* [http://beagleboard.blogspot.com/ Beagle board blog]<br />
* [http://feeds.feedburner.com/BeagleBoard Beagle board RSS feed]<br />
* Chat:<br />
** [http://beagleboard.org/chat Beagle Board chat]<br />
** IRC: #beagle channel on irc.freenode.net<br />
** [http://www.beagleboard.org/irclogs/index.php IRC archive]<br />
* [http://www.beaglesride.org/ Beagles Ride], a site about building a community around the BeagleBoard focused on in vehicle applications<br />
* [http://www.beagleboard.de/ German Beagle Board Forum and Wiki]<br />
<br />
==TI resources==<br />
* [http://opensource.ti.com/ TI open source page]<br />
* [https://community.ti.com/ TI E2E (Engineer-to-Engineer) Community]<br />
* [http://marc.info/?l=linux-omap&m=120761100810527&w=2 DSP Bridge driver for OMAP3 platform]<br />
* [http://lists.arm.linux.org.uk/lurker/message/20080701.142512.5eeff26b.en.html ARMv7 Oprofile support]<br />
* [http://focus.ti.com/pdfs/wtbu/swpu114g.pdf OMAP34xx Wireless Technical Reference Manual] (swpu114g.pdf, 47 MB)<br />
* [http://amethyst.openembedded.net/~koen/index.php?sort=date&order=desc&path=beagleboard/ Koen's (OpenEmbeded) BeagleBoard source and binaries]<br />
* [http://del.icio.us/tag/beagleboard+peripheral+verified Verified peripherals for BeagleBoard]<br />
* [http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt OMAP3430 Linux Power Management presentation]<br />
==Articles==<br />
* [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article about Beagle]<br />
* [http://www.linuxdevices.com/news/NS8479495970.html LinuxDevices article about Digi-Key launch]<br />
* [http://www.linuxdevices.com/news/NS5682470737.html LinuxDevices article about Beagle Rev C, Beagle MID from HY Research, Touch Book and Sponsored Projects Contest]<br />
* [http://www.linuxjournal.com/article/10607 Linuxjournal article on the BeagleBoard]<br />
<br />
==Books==<br />
* [[OMAP_and_DaVinci_Software_for_Dummies|OMAP and DaVinci Software for Dummies]]<br />
<br />
==Beagle based training materials==<br />
* http://free-electrons.com/blog/beagle-labs/<br />
<br />
==Past Beagle events==<br />
* TIDC, February 26-28, 2008: [http://www.beagleboard.org/uploads/tidc_opensource.pdf Slides from TI developer conference (TIDC) open source session], covering also beagle board<br />
* [http://www.lugradio.org/live/USA2008/ LUG RADIO Live USA 2008, April 12-13, 2008]: [http://www.beagleboard.org/uploads/lugradio_20080411.PPT TI/Beagle Presentation] and [http://forums.lugradio.org/viewtopic.php?f=4&t=4094&st=0&sk=t&sd=a&sid=d69cc807569ab41e33f93af698c536b8&start=15#p41549 video]<br />
* LinuxTag, May 28-31, 2008: [http://www.flickr.com/photos/jadon/2551439955/in/pool-beagleboard picture 1] and [http://www.flickr.com/photos/jadon/2535692865/in/pool-beagleboard picture 2]<br />
* [http://lugradio.org/live/UK2008/travel LugRadio Live UK 2008], July 19 - July 20, 2008: [http://www.flickr.com/photos/koenkooi/tags/lugradiolive/ Koen's pictures] showing e.g. [http://www.bigbuckbunny.org/index.php/download/ Big Buck BUNNY] playing at Beagle. [http://linuxoutlaws.com/podcast/48 Interview with Linux Outlaws (52:06)] and the [http://www.youtube.com/watch?v=m9xVbntl-DY video]<br />
* [http://osscamp.in/index.php/OSScamp_Bengaluru_Mobile_2008 OSScamp Bengaluru Mobile 2008], July 19, 2008<br />
* [http://www.linuxworldexpo.com LinuxWorld Conference & Expo], August 4 - August 7, 2008: [http://www.flickr.com/photos/jadon/sets/72157606586084668/ pictures with living beagle] and from [http://www.flickr.com/photos/linuxjournal/2738316951/in/set-72157606634486338/ Linux Journal's photostream]<br />
* BeagleBoard.org event at Jillian's during LinuxWorldExpo, August 5, 2008, 5:30-7:30 pm<br />
* [http://barcamp.pbwiki.com/BarCampHouston3 BarCamp Houston 3], August 9, 2008, 9:00 A.M.: [http://www.flickr.com/photos/jadon/sets/72157606656532041/ pictures]<br />
* NIT Suratkal, India [http://www.nitkieee.com/site/sp-connect2/schedule IEEE SP Connect 2], August 30, 20008<br />
* [http://barcampbangalore.org/wiki/BCB7_Demos BarCamp Bangalore], India, September 13, 2008<br />
* [http://www.ibc.org/ IBC 2008], September 11 - September 16, 2008: [http://www.flickr.com/photos/koenkooi/tags/ibc2008/ pictures]<br />
* Free Open "Embedded Linux" Training for Students in India, [http://code.google.com/p/beagleboard/wiki/Trainings?updated=Trainings&ts=1220250913 beagleboard.org Trainings in India], September 20, 2008: [http://www.youtube.com/watch?v=A6FLdmgQlb4&feature=PlayList&p=1BAB6EE9CC7285AD&index=0 video], [http://www.flickr.com/photos/25691331@N04/sets/72157607419766102/ photos] and [http://lakshmansrikanth.blogspot.com/2008/09/linux-embedded.html blog]<br />
* [http://www.embedded.co.uk/ Embedded Systems Show 2008], Birmingham, UK, October 1-2, 2008<br />
* [http://www.mvista.com/vision/ MontaVista Vision 2008 Embedded Linux Developers Conference], San Francisco, California, October 1-3, 2008 : [http://www.mvista.com/download/topic.php?t=18 Video and presentation overview], [http://www.mvista.com/download/fetchdoc.php?docid=323 William Mills' presentation], [http://www.mvista.com/download/fetchdoc.php?docid=333 Jason Kridner's presentation]<br />
* [http://www.rtcgroup.com/arm/2008/ ARM Developers' Conference], Santa Clara Convention Center, Santa Clara, Calif., USA, October 7-9, 2008<br />
* [http://www.cmp-egevents.com/web/escb Embedded Systems Conference Boston 2008], Hynes Convention Center, Boston, USA, October 26 - October 30, 2008: [http://beagleboard.org/demo/esc Resources]<br />
* [[BeagleBoard/contest|BeagleBoard contest]] #1: Create a cool BeagleBoard application and win a Rev C1! Closed, ran until January 9, 2009<br />
* [http://www.silica.com/events/seminars/seminar-overview/ti-omp-workshop.html OMAP35x training by Silica], January 21, 2009, Cambridge, UK, ARM Holdings Lecture Theatre. [[RichardB's notes from the seminar]]<br />
* [[BeagleBoard/contest|BeagleBoard contest #2]], unitl February 27, 2009: : Create a cool BeagleBoard application and win a Rev C2!<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/b15cf8a5797c73a2 Silica - Free TI - ARM OMAP Workshop], Brussels, Europe, March 31st 2009<br />
* SILICA's [http://www.silica.com/events/seminars/seminar-overview/ti-omap-piccolo-poing.html Texas Instruments 2-in-1 Seminar: OMAP & Piccolo], May 13th 2009: Poing (Munich) - Germany<br />
* 24th until 27th June 2009: [http://www.linuxtag.org/2009/en.html Linux Tag Germany] with [http://groups.google.com/group/beagleboard/msg/27fefef5f1d2ef73 TI booth] and [http://www.linuxtag.org/2009/en/program/freies-vortragsprogramm/all-events/details.html?talkid=183 Beagle presentation]<br />
* until 31st July 2009: [http://www.cranessoftware.com/services/training/beagledesigncontest.html BeagleBoard Design Contest INDIA Edition] ([http://beagleboard.blogspot.com/2009/04/beagleboard-design-contest-india.html blog entry])<br />
* TI Technology Day Dallas, Tex. on June 16 will held a [http://www.linuxdevices.com/news/NS5682470737.html BeagleBoard users group meeting] (see section ''Availability'').<br />
* Thursday, August 27th: [http://wiki.omap.com/index.php/ETechDays_Lightning_Talks ETechDays Lightning Talks]. 15 minute lightning talks via IRC, WebEx or Dial-In.<br />
* 22.- 23.08.2009, Sankt Augustin, Germany: [http://www.froscon.de/en/ FrOSCon 2009] ([http://groups.google.com/group/beagleboard/browse_thread/thread/6aee27a7d121f4f4# call for papers])<br />
<br />
==Beagle wiki pages==<br />
* [[BeagleBoardBeginners|BeagleBoard beginners guides]]<br />
* [[BeagleBoardAndOpenEmbeddedGit|BeagleBoard and OpenEmbedded Git]] installation guide and [[BeagleBoardOpenEmbeddedDevelopment|OpenEmbedded development]]<br />
* [[BeagleBoardDebian|Debian on BeagleBoard]] usage guide<br />
* [[BeagleBoardHandheldsMojo|Handhelds Mojo (ARM) on BeagleBoard]] usage guide (formerly known as Ubuntu (ARM))<br />
* [[BeagleBoardUbuntu|Ubuntu (ARM EABI) distribution at BeagleBoard]]<br />
* [[BeagleBoardRecovery|BeagleBoard recovery]] about fixing boards not booting any more because of broken NAND content<br />
* [[BeagleBoardJTAG|BeagleBoard JTAG]] and [[OMAP3530_ICEPICK|OMAP3530_ICEPICK]] about JTAG on BeagleBoard<br />
* [[BeagleBoardOpenOCD|BeagleBoard OpenOCD]] has infos about status and usage of open source JTAG software OpenOCD with Beagle<br />
* [[BeagleBoardNAND|BeagleBoard NAND boot]] about how to boot BeagleBoard from NAND flash<br />
* [[BeagleBoardPeripherals|BeagleBoard peripherals and adapters page]] about useful BeagleBoard add ons.<br />
* [[Mount_BeagleBoard_Root_Filesystem_over_NFS_via_USB|Mount BeagleBoard root file system over NFS via USB]]<br />
* [[BeagleBoardFAQ|BeagleBoard FAQ]]<br />
* [[BeagleBoardSugar|Sugar on BeagleBoard]]<br />
* [[BeagleBoard/DSP_Howto|BeagleBoard DSP howto]]<br />
* [[BeagleBoardRawLCD|Interfacing BeagleBoard to Raw LCD]]<br />
* [[BeagleBoard/gst-openmax|BeagleBoard OpenMAX usage]]<br />
* [[BeagleBoard/video|BeagleBoard video]]<br />
* [[BeagleBoardOpenCV|Using OpenCV computer vision library with BeagleBoard]]<br />
* [[BeagleBoard/James|James]]: Just A Miniature Entertainment System<br />
* [[U-boot_musb_gadget_support|U-boot musb gadget support]]<br />
* [[BeagleBoard-JP|Japanese translation of this Beagle page]]<br />
* [[BeagleEPD|BeagleBoard E-Ink Platform Driver]]<br />
* [[BeagleBoardFedora|Random hacking notes for getting Fedora 10 to kinda work with the BeagleBoard]]<br />
* BeagleBoard specific [[BeagleBoard/GSoC|Google Summer of Code 2009]] page, [[BeagleBoard/Ideas-2009|GSoC project ideas]] and [[BeagleBoard/GSoC/Application|GSoc application]]<br />
* [[BeagleBoard/Poky|Poky]] for BeagleBoard<br />
* [[Xenarc_USB_touchscreen_for_Beagleboard/OMAP3_EVM|Xenarc USB touchscreen for Beagleboard/OMAP3 EVM]]<br />
* [[BeagleBoard/BugAdapter|BeagleBoard Bug Adapter board]]<br />
* [[BeagleBoardDebianWifiInstallInfo|BeagleBoard Debian WiFi install info]]<br />
* [[BeagleBoard/DSP_Clarification|Info about the various Linux DSP systems for OMAP chips]]<br />
* [[BeagleBoardPinMux|BeagleBoard PinMux]]<br />
* [[BeagleBoardLinuxKernel|BeagleBoard Linux kernel manual compile]]<br />
* [http://www.hervanta.com/stuff/Beaglebot Beaglebot]: build an experimental robotics project with Beagle<br />
* [http://code.google.com/p/beagleboard/w/list code.google.com BeagleBoard wiki]<br />
* '''[[BeagleBoard/contest|BeagleBoard contest]]'''<br />
* [http://en.wikipedia.org/wiki/Beagle_Board Wikipedia BeagleBoard page]<br />
* [http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board Android port for BeagleBoard]: Instructions for porting Android on BeagleBoard<br />
* [[BeagleBoard/bangalore_user_meet |BeagleBoard Bangalore User Meet]]<br />
* [[BeagleBoardEclipse|Using Eclipse with Beagle]] (for JTAG debugging)<br />
* [[Zoom2Beginners|Zoom2 for Beginners]]<br />
* [http://wh1t3s.com/2009/05/11/beagleboard-as-usb-mass-storage-device-via-usb-otg/ BeagleBoard as USB Mass Storage Device via USB OTG]<br />
* [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm BeagleBoard as solar powered computer]<br />
* [http://blog.makezine.com/archive/2009/02/blinking_leds_with_the_beagle_board.html Blinking LEDs with the Beagle Board] from Make:Online<br />
* [http://www.crashcourse.ca/wiki/index.php/BeagleBoard Robert's private Beagle wiki] (please don't add anything there, do it here. It will help to avoid scattering. Thanks!)<br />
* [http://felipec.wordpress.com/2009/03/26/omap3-public-dsp-binaries-now-work/ Felipe's blog] about D1 MPEG-4 decoding using less than 15% of CPU with help of DSP<br />
* [http://www.syspire.de/node/3 Embedded Mediacenter] based on BeagleBoard (German)<br />
* [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] with VFP-lite and NEON intro<br />
* [http://particolarmente-urgentissimo.blogspot.com/2009/09/beagleboard-setting-date-via-gps.html Beagleboard setting date via GPS]<br />
* [http://free-electrons.com/blog/beagle-labs/ Complete embedded Linux training labs] on the BeageBoard<br />
<br />
==Beagle photos==<br />
* [http://www.flickr.com/groups/beagleboard/pool/ Beagle board pictures at flickr]<br />
* [http://www.flickr.com/photos/32615155@N00/2439256116/ Beagle board and USRP]<br />
* [http://www.flickr.com/photos/nishanthmenon/2438406603/ Modify SDP3430 QUART cable for beagle]<br />
* [http://www.flickr.com/photos/koenkooi/2695061759/ MythTV on Beagle]<br />
==Beagle videos==<br />
* [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings]<br />
* [http://www.youtube.com/watch?v=cXr-D1wROfQ Beagleboard in the Living Room]<br />
* [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu]<br />
* [http://uk.youtube.com/watch?v=TUYOjRGYeYU testsprite with beagleboard]<br />
* [http://uk.youtube.com/watch?v=9Z4ZTovtFKk Beagleboard LED demo]<br />
* [http://uk.youtube.com/watch?v=R33dzREZGEk LCD2USB attached to a beagleboard]<br />
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]<br />
* [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector]<br />
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle working with Linux 2.6.27]<br />
* Not on Beagle OMAP3530: [http://youtube.com/watch?v=5i9cWOK1spw Ubuntu 7.04 on on OMAP3430 SDP]<br />
* [http://in.youtube.com/watch?v=nADn_vNVEKw Beagle Board booting Android]<br />
* [http://www.youtube.com/watch?v=UHQdUS0i-nw Beagleboard, SGX, and libfreespace demo]<br />
<br />
==Beagle manufacturing==<br />
* [http://www.youtube.com/watch?v=C-CwkjT9z_0&feature=related Beagle Solder Paste Screening]<br />
* [http://www.youtube.com/watch?v=9LLjDovIG2M&feature=related Beagle Assembly Inspection]<br />
* [http://www.youtube.com/watch?v=sbOZfBnoVnM&feature=related Beagle Functional Test]<br />
* [http://www.youtube.com/watch?v=cvDtXmJJcEI&feature=related Beagle Reflow]<br />
* [http://www.youtube.com/watch?v=W2o4NTASxN0&feature=related Beagle Board Assembly at Circuitco]<br />
==Fun==<br />
* Enjoy [http://www.beaglegame.com/ BeagleGame]<br />
<br />
=Other OMAP boards=<br />
<br />
* OMAP1 OMAP5912 (ARM9 + C5x DSP) based [[OSK|OSK]] board.<br />
* OMAP3 OMAP3430 based [https://gforge.ti.com/gf/project/omapzoom/wiki/?pagename=HardwareInformation Zoom MDK], which has been superseded by the [http://www.logicpd.com/products/development-kits/texas-instruments-zoom%E2%84%A2-omap34x-ii-mdp Zoom II], and other [http://www.logicpd.com/products LogicPD kits].<br />
* OMAP3 OMAP3530 based [http://www.openpandora.org/ Pandora]<br />
* OMAP3 OMAP3503 based [http://www.gumstix.net/Overo/cat/Overo/115.html Gumstix Overo]<br />
* OMAP3 OMAP35x based EVM from [http://mistralsolutions.com/products/omap_3evm.php Mistral] and [http://focus.ti.com/docs/toolsw/folders/print/tmdxevm3503.html TI] (both are the same)<br />
* OMAP3 OMAP3430 based [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12013&contentId=28741 Software Development Platform (SDP)]<br />
* OMAP3 OMAP3530 based board from [http://www.magniel.com/omap3.html Magniel Inc.]<br />
* OMAP3 based [http://www.archos.com/products/imt/index.html?country=us&lang=en Archos 5, ARCHOS 5G and ARCHOS 7]<br />
* OMAP3 OMAP35x based [http://www.logicpd.com/products/som/ti/omap35x OMAP35x SOM-LV]<br />
* OMAP3 based [[Mini_Board|ICETEK-OMAP3530-Mini]], a Chinese BeagleBoard clone, with a [[MiniBoardFAQ|FAQ]]<br />
* OMAP3 based [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], a German BeagleBoard clone<br />
* OMAP3530 based [http://www.bsquare.com/products/hardware_solutions/3530.asp BSQUARE’s Dev Kit OMAP3530]<br />
* OMAP3530 based [http://beaversource.oregonstate.edu/projects/cspfl/wiki/CSPFL_Hardware OSWALD]<br />
* OMAP3 BeagleBoard-based [http://www.alwaysinnovating.com/touchbook/ Touch Book]<br />
* OMAP3530 based [http://www.analogue-micro.com/Cobra3530.html Cobra 3530 OMAP3530 module ]<br />
* OMAP3 based [http://www.kwikbyte.com/KBOC.html KwikByte 35XX System Module]<br />
* OMAP3530 based [[DevKit8000]], a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard)<br />
* OMAP3530 based [http://www.igep-platform.com/ IGEPv2 Platform], a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, wifi+bluetooth.<br />
* OMAP35x based [http://www.ultratronik.de/mmi-rechnerplattformen.html MMI4 from Ultratronik]<br />
* OMAP35x based [http://www.technexion.com/index.php/tao-3530 TAO-3530 from TechNexion]<br />
* OMAP35x based [http://www.variscite.com/varomap35xxsbc.html VAR-OM35xxSBC from Variscite]<br />
* OMAP35x based [[EGS3530]],a Chinese BeagleBoard clone from [http://www.ema-tech.com EMA]<br />
* OMAP3 OMAP35x based [http://www.buglabs.net/products BUG] from Bug Labs, Inc.<br />
* OMAP35x System-on-Module [[SOM3530]],The smallest(40x40x4mm) OMAP35XX-based System on Module in the world!<br />
<br />
=Subpages=<br />
<splist<br />
parent=<br />
showparent=no<br />
sort=desc<br />
sortby=title<br />
liststyle=ordered<br />
showpath=no<br />
kidsonly=no<br />
debug=0<br />
/></div>Som2416https://elinux.org/index.php?title=BeagleBoard_Community&diff=19029BeagleBoard Community2010-04-02T08:24:16Z<p>Som2416: /* SOM3530 */</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
This page collects information about [http://www.ti.com/ TI's] [http://www.arm.com/ ARM] based [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&amp;DCMP=OMAP_Feb27_2008&amp;HQS=Other+PR+omap3503pr OMAP3] [http://beagleboard.org Beagle Board].<br />
<br />
<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#ffffcc; align:right; "><br />
'''NEWS:'''<br />
* [[BeagleBoard_Zippy|Zippy Boards]] are now available from [http://www.sparkfun.com/commerce/product_info.php?products_id=9731 SparkFun]!<br />
* [[BeagleBoard_Zippy2|Zippy2]] 100baseT Expansion boards for the [[BeagleBoard]] are now available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?vendor=0&keywords=zippy2 Digikey]!<br><br />
</div><br />
<br><br />
=Events=<br />
* Meet BeagleBoard at TI booth in June, 9-12th @ Linux Tag, Berlin, Germany, http://www.linuxtag.org/2010/<br />
* See TI BeagleBoard demo @ Embedded World, Nuremberg, Germany, March 2-4, 2010, Hall 11. booth 308<br />
* Each last Saturday of the month, next August 29, 2009: [[BeagleBoard/bangalore user meet|BeagleBoard Bangalore user meeting]] (Beagle Clinic India)<br />
* all over the world 2009: [http://www.ti.com/corp/docs/landing/techday09/index.shtml# TI Technology Days 2009]. <br />
* ongoing 2009: [[BeagleBoard/contest|Beagle Sponsored Project Program]] - add a cool project and get a free BeagleBoard to realize it!<br />
<br />
=Hardware=<br />
<br />
The Beagle Board is ''a low-cost, fan-less single-board computer based on TI's OMAP3 device family, with all of the expandability of today's desktop machines, but without the bulk, expense, or noise'' (from [http://beagleboard.org/ beagleboard.org]). It uses a TI [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor (ARM Cortex-A8 superscalar core ~600MHz paired with a TMS320C64x+ DSP ~430MHz and an Imagination SGX 2D/3D graphics processor). See [http://focus.ti.com/docs/prod/folders/print/omap3530.html#features OMAP3530 features] for more processor features. [[BeagleBoard#Availability|Price is USD 149]]. The design goal was to make it as simple and cheap as possible, e.g. not having a LCD added, but letting you connect all add-ons available as cheap external components. See [http://beagleboard.org/brief What is Beagle?] and [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article] for more details.<br />
<br />
The videos [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings] and [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu] give you a good intro about what BeagleBoard is about and its capabilities.<br />
<br />
==Components==<br />
<br />
{|border=0<br />
!Top view of rev B:<br />
!Top view of rev C:<br />
|-<br />
|[[Image:Bb revb top numbered.jpg]]<br />
|[[Image:Bb revc top numbered.jpg]]<br />
|-<br />
|}<br />
{|border=1<br />
!No.<br />
!Name<br />
!Comment<br />
|-<br />
|'''1'''<br />
|[http://www.ti.com/omap35x OMAP3530] processor + 256MB NAND<br />
<br />
+ 128MB DDR (rev B)<br />
<br />
+ 256MB DDR (rev C)<br />
|PoP: Package-On-Package implementation for Memory Stacking<br />
[http://www.micron.com/products/partdetail?part=MT29C2G24MAKLAJG-6%20IT 256MB NAND/128MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1435-ND DigiKey]<br />
<br />
([http://www.micron.com/products/partdetail?part=MT29C4G48MAPLCJI-6%20IT 512MB NAND/256MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1436-ND DigiKey])<br />
<br />
[http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for Beagle Board]<br />
|-<br />
|'''2'''<br />
|[http://focus.ti.com/docs/prod/folders/print/tfp410.html DVI chip (TFP410)]<br />
|<br />
|-<br />
|'''3'''<br />
|[[BeagleBoard#DVI|DVI-D]]<br />
|Connection via HDMI connector<br />
|-<br />
|'''4'''<br />
|[[BeagleBoard#JTAG|14-pin JTAG]]<br />
|1.8V only!<br />
|-<br />
|'''5'''<br />
|Expansion connector: I2C, I2S, SPI, MMC/SD<br />
|User must solder desired header into place<br />
|-<br />
|'''6'''<br />
|[[BeagleBoard#User_button|User button]] <br />
|Allows setting boot order.<br />
|-<br />
|'''7'''<br />
| Reset button<br />
|<br />
|-<br />
| '''8'''<br />
|[[BeagleBoard#EHCI|USB 2.0 EHCI HS]]<br />
|Rev A and B: not working, unpopulated<br />
<br />
Rev C: populated and working<br />
|-<br />
|'''9'''<br />
|SD/MMC+<br />
| SDHC cards are supported<br />
|-<br />
|'''10'''<br />
|[[BeagleBoard#RS232|RS-232 serial]]<br />
|<br />
|-<br />
|'''11'''<br />
|Alternate power <br />
|normally powered by USB (unmounted on REV Ax boards, see [[BeagleBoard#Errata|errata]])<br />
|-<br />
|'''12'''<br />
|[[BeagleBoard#OTG|USB 2.0 HS OTG]] <br />
|Mini-AB connector. Board can be powered from port. <br />
|-<br />
|'''13'''<br />
|Stereo In<br />
|<br />
|-<br />
|'''14'''<br />
|Stereo Out<br />
|<br />
|-<br />
|'''15'''<br />
|S-Video<br />
|<br />
|-<br />
|'''16'''<br />
|TWL4030 (Rev A thru C2 inc.)<br />
[http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] (Rev C3 onwards)<br />
|Audio CODEC, USB port, power-on reset and power management. The TWL4030 is pin-compatible with the [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] chip and was used due to the very limited availability of the TPS65950 in early board revisions.<br />
|-<br />
|'''17'''<br />
|LCD<br />
|only rev C<br />
|-<br />
|'''18'''<br />
|USB power<br />
|<br />
|-<br />
|'''19'''<br />
|Host PHY<br />
|<br />
|-<br />
|'''20'''<br />
|32kHz<br />
|<br />
|-<br />
|'''21'''<br />
|12MHz<br />
|<br />
|-<br />
|'''22'''<br />
|RS232 XVCR<br />
|<br />
|-<br />
|'''23'''<br />
|PWR SW<br />
|<br />
|-<br />
|'''24'''<br />
|VBAT<br />
|<br />
|-<br />
|}<br />
<br />
* Board size: 3" x 3" (about 76.2 x 76.2 mm)<br />
* Weight: [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/beagleboard.png ~37g]<br />
* Currently 6 layer PCB; target: 4 layer<br />
<br />
'''Bottom of rev B:'''<br />
<br />
[[Image:Beagle_bottom.jpg]]<br />
<br />
See [http://www.flickr.com/photos/jadon/sets/72157606050144396/ jadonk's photostream] for some more detailed BeagleBoard pictures.<br />
<br />
==Manual==<br />
<br />
See [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)].<br />
<br />
==Schematic==<br />
<br />
Schematic of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous are also available from [http://beagleboard.org/hardware/design BeagleBoard.org design page] including in PDF format. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.<br />
<br />
==Layout== <br />
<br />
Layout of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous layouts are also available from the [http://beagleboard.org/hardware/design BeagleBoard.org design page]. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.<br />
<br />
==Errata==<br />
<br />
# ''Boards revision A only'': The DC power jack pinout is incorrect on the PCB layout. DC_5V and GND are switched on PCB layout. Normally, the power jack has DC_5V on the center pin and GND on the sleeve (see Figure 20 of [http://www.beagleboard.org/uploads/BBSRM_6.pdf Beagle HW manual]). But on revision Ax boards the PCB layout has GND on center and DC_5V on sleeve. For this reason it is currently removed. It will be back on the Rev B board. Workaround is to remove wire connecting the two power pins on revision Ax boards and use external [http://amethyst.openembedded.net/~koen/beagleboard/beagle-power-pads.jpg power supply with switched connector] (do not connect anything to the “?” terminal. USB power will be permanently disabled and the board can only be powered from the 5V.) See [http://www.flickr.com/photos/koenkooi/2512038988/ Koen's Beagleboard powermod picture] with short descriptions, too.<br />
# ''Boards revision < A5 only'': There is excess voltage drop across R6 which is used to measure the current consumption on the board. This needs to be a .1 ohm instead of a 1 ohm resistor (SMD 0805). All revision A5 boards have been updated to .1. You can also just solder in a jumper to J2 bypassing the current read point. This issue can cause issues with the USB host port as the voltage supplied to that port can be too low.<br />
# ''Boards revision A only'': User LEDs 0 and 1 are shorted on the layout preventing them from being controlled individually. You need to control both GPIO_149 and GPIO_150 to turn on or off both LEDs. This is fixed in the Rev B boards.<br />
# ''Boards revision < A5 only'': There is an issue where on some boards the 1.8V has excessive noise on it. This is the result of two incorrect parts L1 and L3 being installed on the board. The inductors that were initially installed in the switchers are 100uH and need to be 1uH. This change will require that the board be returned for update. To check for correct parts, have a look to bottom of BeagleBoard. L1 - L3 are the larger parts there. They all have to be labeled with "102" (== 1uH). If any of these three inductors are labeled with "104" (== 100uH) they are wrong and have to be exchanged.<br />
# ''Boards revision A and B'': USB HOST (EHCI) failures. See [http://code.google.com/p/beagleboard/issues/detail?id=15 issue 15] and [http://code.google.com/p/beagleboard/wiki/USBHostTestREPRODUCE USB host test reproduce]. This is a hardware defect. [http://www.beagleboard.org/irclogs/index.php?date=2008-05-29#T00:27:06 Most probably] Rev. B board does not have the EHCI USB connector mounted. Workaround: Use [[BeagleBoard#OTG|OTG port]] with something like [http://trisoft.de/pics/ZHost.JPG mini A to USB A adapter] instead.<br />
# ''Boards revision A and < B4'': Plugging in a USB OTG cable will prevent Beagle from booting (with git kernel), see [http://code.google.com/p/beagleboard/issues/detail?id=19 issue #19], too. This is due to missing filtering capacitor at USB OTG VBUS. When the kernel driver detects that a USB OTG cable is inserted it enables the charge pump to generate VBUS. With no filtering VBUS looks like any switching regulator output with no filtering -- a huge voltage spike when the switch is on, followed by a rapid decay to a low voltage until the next switch on period. The capacitor is there to store energy between the output switch ON and OFF time, the feedback loop in the regulator does sample the cap voltage. Fix is to piggy-back solder a 0603 2.2uF ceramic capacitor to D3, see [http://www.sakoman.net/omap3/beagle/vbus-mod-d3.jpg VBUS modification D3 picture]. Revision B4 boards and newer have this fix applied. Thanks to [http://groups.google.com/group/beagleboard/msg/eb789e15c99a673d Steve] for debugging this!<br />
# ''Boards revision A and < B5'': There is some issue with 32kHz clock depending on system configuration used to clock some OMAP3 peripherals. From this e.g. GPIOs, GPTIMERs, and USB on Beagle might be affected. See [http://code.google.com/p/beagleboard/issues/detail?id=22 Issue 22]. Symptom from this is that after booting Linux kernel serial console hangs after some time and no serial input/output is possible any more. There is one software workaround and one hardware fix for this: (A) Software workaround: Don't use 32kHz timer to clock Linux, instead use MPU timer. (B) Hardware workaround: Remove [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard capacitor C70], which improves the 32kHz clock quality and avoids hang-up. Note: Revision A boards have capacitor C70 [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard at the same location] as rev. B boards. Note: Board revision >= B5 removes capacitor C70.<br />
# ''Random boards, quite rare, revision < B6'': Some random boards and quite rare, show directly after purchasing broken serial communication from host PC to BeagleBoard. Symptom is that you get a new board, get serial output from BeagleBoard in terminal program, but can't type anything at U-Boot prompt (Note: Don't mix this with errata #7. With errata #7 you are able to use U-Boot normally, but Linux prompt input stops after some time). Most users don't have this issue, though. So, first double check your serial configuration ([[BeagleBoardFAQ#Serial_connection_.231|FAQ1]], [[BeagleBoardFAQ#Serial_connection_.232|FAQ2]] and [[BeagleBoardFAQ#Serial_connection_.233|FAQ3]]). Only if you are really, really sure that anything with your serial connection is fine, consider sending the board back doing a [http://beagleboard.org/support/rma RMA request]. This issue was resolved on revision B6 and later boards.<br />
<br />
For additional (software) issues and enhancement requests see [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker], too.<br />
<br />
Note: BeagleBoard revision B6 uses different package for U9/U11.<br />
<br />
==Clocking==<br />
<br />
Some [http://www.beagleboard.org/irclogs/index.php?date=2008-07-08#T21:12:23 notes] about (ARM processor) clock rates at BeagleBoard:<br />
<br />
* ARM Cortex-A8 processor is currently clocked at 500MHz<br />
* 500MHz is the default used because it is a balance of performance and longevity<br />
* For OMAP35x 600MHz is max recommended<br />
* An additional 720MHz overdrive is supported only on high-speed grade OMAP3530/25 devices as fitted to the Beagleboard C4<br />
* At 600MHz or higher OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy<br />
* Higher than 600/720MHz is out of spec and no guarantee it will work at all (or not damage itself)<br />
<br />
* Also keep in mind that if you go higher you probably want to increase the core voltage. Some of this is mentioned in tables 3-3, 4-15 and 4-16 of the [http://focus.ti.com/lit/ds/symlink/omap3530.pdf OMAP3530 data sheet]. Some numbers:<br />
<br />
{| border="1"<br />
||'''ARM'''||'''DSP'''||'''core voltage'''<br />
|-<br />
|720 MHz||520 MHz||1.35V<br />
|-<br />
|600 MHz||430 MHz||1.35V<br />
|-<br />
|550 MHz||400 MHz||1.27V<br />
|-<br />
|500 MHz||360 MHz||1.2V<br />
|}<br />
<br />
* For some OMAP3 clock, voltage and power management discussion see [http://focus.ti.com/lit/an/sprt495/sprt495.pdf OMAP3 power management white paper], too.<br />
* The OMAP3 chip on the Beagle lacks the efuses needed for using the SmartReflex technology, see [http://www.beagleboard.org/irclogs/index.php?date=2009-02-26#T10:44:24].<br />
* There is a thermal monitor in the core, you could use to scale frequency up and down<br />
<br />
To set CPU clock to 600 MHz, there are two options. Both '''do not''' adjust the voltage, so the system may become unstable:<br />
<br />
* The u-boot command "mw 48004940 0012580c" will temporarily set the CPU clock to 600 MHz (not permanent over reset).<br />
* To permanently set the CPU clock to 600 MHz, include the above command in the "bootcmd" variable or equivalent script.<br />
<br />
* To set the DSP clock to 430 Mhz use "mw 48004040 0x0009ae0c".<br />
<br />
==Power management==<br />
<br />
* Detailed OMAP3 Power Management Information can be found [[OMAP_Power_Management|HERE]]<br />
* Latest Linux kernel power management development for TI OMAP SoCs is maintained in [http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git;a=summary Kevin's linux-omap-pm git tree]<br />
* Russ' Beagle HW modifications resulted in [http://groups.google.com/group/beagleboard/browse_thread/thread/197a8ef6b46cc828 8mW sleep for Beagle Board]<br />
<br />
Without PM kernel, the Beagle [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm consumes ~1.5 watts idle, however it also uses the same amount under load] (see bottom of that page).<br />
<br />
==DLP Pico projector==<br />
<br />
Texas Instruments is developing a Pico Video Projector Kit (PVPK) as a peripheral for the Beagle Board. The stand alone pico projector will support VGA resolution (640 x 480), RGB 888 input through a DVI interface. The physical connector on the projector will be HDMI. See [http://groups.google.com/group/beagleboard/msg/10e218972380ee48 mailing list] and [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector] for more details.<br />
<br />
It is available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23836-ND DigiKey] for $349.<br />
<br />
See [http://blog.makezine.com/archive/2009/01/tis_beagleboard_and_dlp_pico_projector.html?CMP=OTC-0D6B48984890 article from Make], too.<br />
<br />
DigiKey videos [http://www.youtube.com/watch?v=KBbCdnOj5vg part 1], [http://www.youtube.com/watch?v=zymOmduNWyI part 2] and [http://www.youtube.com/watch?v=Uj19Bi5NYeU part 3].<br />
<br />
==Interfacing to Raw LCD Panels==<br />
<br />
Currently on Rev A / B boards there is no direct access to the LCD lines before they enter the DVI framer. The REV C2 provides access to these lines. Several projects to interface an LCD to the beagleboard exist:<br />
<br />
* [[BeagleBoardRawLCD|interfacing to Raw LCD Panels]] article <br />
* [http://digitalsurveyinstruments.com/beagleperiphials/hdmi2parallel/doc/index.htm hdmi to parallel] workaround method<br />
* [http://www.harbaum.org/till/dvi2par/index.shtml dvi2par cheap diy HDMI to parallel converter]<br />
<br />
=Availability=<br />
<br />
BeagleBoards, currently Rev. C3 boards, are available from<br />
<br />
* [http://www.mouser.com/beagleboard Mouser]<br />
* [http://dkc1.digikey.com/us/mkt/beagleboard.html Digi-Key] with part number [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23428-ND 296-23428-ND].<br />
<br />
Note: For non-US Digi-Key free shipping orders:<br />
<br />
* Click the US flag on the top right corner of [http://dkc1.digikey.com/us/mkt/beagleboard.html Digi-Key] BeagleBoard page to come to the international page<br />
* Select ''Order Online'' for your country<br />
* Add quantity ''1'' and part number ''296-23428-ND''<br />
* Click ''Add to order''<br />
<br />
When ordering over 65 EUR / GBP 50 product (BeagleBoard is above), for Europe the price depends on the actual dollar to EUR/GBP rate. On nov 9, 2008 the price was EUR 124 with free shipping.<br />
<br />
Note: Some users report that they got some questions from DigiKey to be answered before board shipping is done.<br />
<br />
Note: While you get free shipping, most probably you have to pay tax e.g. ordering from Europe. Users report that they had to pay EUR ~34 - 44 VAT + importing taxes (depending on european country), resulting in EUR 137 - 147 ordering from Europe.<br />
<br />
Note: For European users, [http://www.ebv.com/fileadmin/products/Press_Print/Campaigns/2009/Product_Campaigns/Texas_Beagle_Board_englisch.pdf EBV Elektronik] sells its own blue version of the board for 179 EUR, which includes all useful accessories (DVI cable, serial cable, USB 2.0 Ethernet, USB hub, 2 GB MMC, power supply, Linux BSP).<br />
<br />
Note: German (Europe) users can order through German shops, too. For higher price, though. <br />
* [http://shop.embedded-projects.net/product_info.php/info/p159_BeagleBoard--OMAP-3-.html Embedded Projects Shop] sells BeagleBoard for EUR 199.00 + shipping.<br />
* [http://www.handheld-linux.com/wiki.php?page=Beagle%20Board Handheld-Linux]<br />
<br />
See below for ''hardware'' differences of the revisions. There are no ''software'' differences. <br />
<br />
==Revision A==<br />
<br />
There are some limited early revision Ax prototypes out there used by some hackers hanging around at #beagle channel on irc.freenode.net. See [[BeagleBoard#Errata|errata]] for limitations.<br />
<br />
==Revision B==<br />
<br />
Revision B is same as revision A, except<br />
* fix for shorted LEDs 0/1<br />
* fix for wrong power jack pinout<br />
* revision B6 uses different package for U9/U11<br />
Still has USB HOST (EHCI) failures. USB HOST (EHCI) connector isn't mounted.<br />
<br />
There are 4 revisions of the B board in the field: B4, B5, B6 and B7.<br />
<br />
The most notable difference is the use of the ES3.0 silicon in B6 and B7, other changes are not relevant to software developers.<br />
<br />
==Revision C2==<br />
Revision C2 is same as revision B7 except:<br />
* USB HOST (EHCI) is operational on revision C2, with standard USB A female connector.<br />
* Add interface for raw LCDs ([http://groups.google.com/group/beagleboard/msg/2e82c3ed6061d9d2 mockup])<br />
* It uses updated OMAP3 revision. BeagleBoard revisions B4+B5 uses OMAP3 ES 2.1 (engineering sample), while BeagleBoard revision C2 uses ES 3.0. OMAP3 ES 3.0 fixes minor issues:<br />
** updated ARM Cortex A8 silicon (r1p3) fixing a very rare [http://elinux.org/BeagleBoardFAQ#NEON_performance NEON issue] that has not been seen in real code<br />
* Power measurement feature<br />
* Uses [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] OMAP power controller instead of TWL4030<br />
* Three additional PWM signals on the expansion connector added as pin mux options to existing pins ([http://groups.google.com/group/beagleboard/browse_thread/thread/d5872b7c6d74592c?hl=en# message])<br />
* Revision detection (to be able to identify C2 board from older boards by software, e.g. for different pin mux)<br />
* 256MB RAM ([http://groups.google.com/group/beagleboard/msg/3a38d0f21cefd6b1?hl=en message]) (and still 256MB NAND like rev B)<br />
<br />
Note: Revision C2 is the first production version, and all orders from from Digi-Key are shipped as Rev C2.<br />
<br />
==Revision C3==<br />
As revision C2 boards are [http://groups.google.com/group/beagleboard/msg/e41d3c97aa7d4951 sold out], revision C3 will ship now.<br />
<br />
Revision C3 is same as revision C2 [http://groups.google.com/group/beagleboard/msg/037318fbc44139d5 except]:<br />
* Optional RTC [http://parts.digikey.com/1/parts/1454-battery-lith-coin-3v-12-5mm-vert-vl-1220-vcn.html VL1220 series] backup battery<br />
* Mounting holes conected to ground<br />
* Slightly improved S-Video<br />
<br />
==Revision C4==<br />
Revision C4 boards are the same as Revision C3 except:<br />
* Processor is 720MHz capable OMAP3<br />
* Improved USB Host PHY power rails<br />
<br />
==Clones==<br />
===EBVBeagle===<br />
EBV build and sell their own BeagleBoard called [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], see e.g. [http://fl0rian.wordpress.com/2009/03/08/the-other-beagleboard/].<br />
It is actually a BeagleBoard revision C2 with green PCB boxed with some useful accessories. It comes as a quite complete starter kit with AC adapter, USB to Ethernet adapter, MMC card, USB hub and some cables.<br />
More information in [http://www.ebv.com/en/press-print/news-pr/details/news//press-releas-54.html official press release].<br />
<br />
===Mini Board===<br />
[[Mini_Board|ICETEK-OMAP3530-Mini]] is a chinese BeagleBoard clone.<br />
<br />
===DevKit 8000===<br />
[[DevKit8000]] is a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard).<br />
<br />
===IGEPv2===<br />
[http://www.igep-platform.com/ IGEPv2 Platform] is a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, wifi+bluetooth.<br />
* 720MHz OMAP3 Processor<br />
* 512MB RAM / 512MB Flash<br />
===SOM3530===<br />
[[SOM3530]] is a chinese BeagleBoard clone [[System-on-Module]],Dimension 40x40x4mm, Maybe the smallest [[OMAP3530]]-based modules in the world! Including 100M high perfomance ethernet I/F<br />
<br />
==BeagleBoard-based products==<br />
* [http://www.alwaysinnovating.com/touchbook/ Always Innovating Touch Book], see [http://gigglehd.com/zbxe/hdforum/files/attach/images/899852/493/987/001/always_innovating_touch_book_0011.jpg]<br />
<br />
==Beagle case==<br />
<br />
*[http://specialcomp.com/beagleboard/ Special Computing]<br />
*[http://groups.google.com/group/beagleboard/browse_thread/thread/1c82316019633e51 SketchUp 3D model]<br />
<br />
=Adapters=<br />
<br />
For quite detailed information about all BeagleBoard peripherals see [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)].<br />
<br />
See [[BeagleBoardPeripherals| BeagleBoard peripherals and adapters page]] for useful add ons for Beagle Board.<br />
<br />
==Expansion boards==<br />
* [[BeagleBoardPinMux|Expansion Board Support Information]]<br />
* [[BeagleBoard Zippy]] expansion board is now available from [http://www.tincantools.com/product.php?productid=16147&cat=0&page=1&featured TinCanTools] for $79.00. basic specs are:<br />
** Battery Backed RTC<br />
** Second MMC slot<br />
** 10BaseT Ethernet<br />
** Second RS-232<br />
** +5V level I2C<br />
** AT24 EEPROM<br />
* [https://sourceforge.net/apps/mediawiki/beagleserver/index.php?title=Main_Page BeagleServer expansion board] is an Open Hardware project. Currently a high level design note is available, which describes the components to be used. It aims at the following specifications :<br />
** Aims at transforming a Beagleboard or IGEPv2 into a full-blown home server that could cater to home automation needs<br />
** Compatible with both the Beagleboard and the IGEPv2<br />
** 12V battery powered, or mains-powered (accepts 9 ~ 18V)<br />
** Enough power for an internal 2.5" or 3.5" hard-disk, USB-attached<br />
** +3.3V and +5V I2C; +5V I2C is buffered with a line buffer accepting a larger capacitance which allows I2C devices at distances up to 50m<br />
** I2C to 1-wire hub (using DS2482-800 which is supported by OWFS); plugging in 1-wire devices lights a LED which makes it easy to confirm if a 1-wire device is detected.<br />
** Real time clock with super-capacitor backup<br />
** Internal monitoring of the HW health (power supplies + temperature)<br />
** Some relays<br />
** Ethernet-based console port<br />
** a few other options (RS232 interface with CTS and RTS, SPI port, S-video, additional SD-card)<br />
* [http://www.hy-research.com/beagle_expansion.html HY Research] has some expansion board basics and example.<br />
* [http://www.hervanta.com/stuff/Beaglebot#Expansion_Board Beaglebot] uses a custom extension board.<br />
* [http://beagleboard.org/leopard Leopard Board], a Beagle buddy web camera<br />
* There is also a VGA DB15 adapter board under development for the Rev C2 board. It should be available through a yet to be annnounced outlet.<br />
<br />
In Canada, check out [[http://robotcraft.ca RobotCraft]] in London, Ontario for expansion boards.<br />
<br />
==JTAG==<br />
<br />
Depending on your JTAG tool, you'd need a 14-pin to 20-pin adapter to use an ARM debugger. The 14-pin TI JTAG connector is used on BeagleBoard and is supported by a large number of JTAG emulation products.<br />
See [[BeagleBoardJTAG]] for more information.<br />
<br />
==RS232==<br />
<br />
The pinout on the beagle board is "AT/Everex" or "IDC10". You can buy [http://www.pccables.com/07120.htm IDC10 to DB9M adapters] in many places as they are commonly used for old PCs. Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available. You can also probably rip one of those cables out of any old desktop computer, where it's being used to support the serial port. Be careful, though -- some of those cables will have that tenth hole filled in so you'd have to snap off the extraneous pin on your BeagleBoard. Keep looking until you find a cable with all 10 holes open.<br />
<br />
Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available.<br />
<br />
==USB-to-Serial Converter==<br />
<br />
Since many systems no longer come with an actual serial port, you might need to pick up a USB-to-serial converter at your local computer store to connect to your BeagleBoard. Be warned that some of them simply do not work. Many of them are based on the Prolific chip, and require the pl2303 module to be loaded. But even when two converters appear to have exactly the same characteristics as listed in /var/log/messages, if you simply can't get one to work, be ready to try a different one.<br />
<br />
==USB==<br />
There are two USB ports on the BeagleBoard, one with an EHCI controller and another with an OTG controller. As of Rev B4, the usb EHCI has been removed because of a hardware defect. Rev C will include USB EHCI working properly.<br />
<br />
===EHCI===<br />
The HS ([http://en.wikipedia.org/wiki/USB#USB_signalling HighSpeed]) USB [http://en.wikipedia.org/wiki/EHCI ECHI] controller on OMAP3 on BeagleBoard supports high-speed only. This simplifies the logic on the device. FS/LS (FullSpeed/LowSpeed) devices, such as keyboards and mice, require going through a high-speed USB 2.0 hub.<br />
<br />
According to the BeagleBoard System Reference Manual Rev C2, the EHCI port can source 5V at 500mA which is enough to power a hub and several low-power devices. However, this is only true if the BeagleBoard is powered through its power jack from a well-regulated 5V external power supply. If the BeagleBoard is powered through the OTG port, the EHCI port sources an "extremely limited" ampount of power (probably 100mA or so) so you'll need a "self-powered" USB 2.0 hub with its own external power supply. [Reference: Sections 5.6 and 7.2 of the BBSRM Rev C2.2.]<br />
<br />
'''Hardware issue on rev C3''' - the EHCI port on some rev C3 boards is unstable and will disconnect hubs/devices. Symptoms are: devices are disconnected from the port and cannot be reconnected without a reboot. It appears the shared 1.8V rail between the OMAP3530 and the power chip was getting noisy. Suggested solution (works on many boards) is adding a 0.22 uF 0805 package SMT capacitor atop the existing cap on C97. If SMT parts are not available, some boards can be repaired by a 0.22 uF through-hole capacitor across GND and VIO_1V8 on the expansion connector. See [http://groups.google.com/group/beagleboard/browse_thread/thread/5b8385f0bb1f63da] for more information.<br />
<br />
===OTG===<br />
The HS USB OTG ([http://en.wikipedia.org/wiki/USB_On-The-Go OnTheGo]) controller on OMAP3 on the BeagleBoard does have support for all the USB 2.0 speeds (LS/FS/HS) and can act as either a host or a gadget/device. The HS USB OTG port is used as the default power input for the BeagleBoard. It is possible to boot the BeagleBoard using this USB port.<br />
<br />
When using the OTG port in host mode, you must power the BeagleBoard using the +5V power jack. If you connect a USB hub, you'll probably also need external power for the USB hub as well, because according to the Hardware Reference manual the BeagleBoard OTG port only sources 100 mA. This is enough to drive a single low-power device, but probably won't work with multiple devices.<br />
<br />
The Linux kernel needs to know you want to use the OTG port in host mode. I believe OTG ports are supposed to figure this out for themselves using the OTG Host Negotiation Protocol, but for now the Linux kernel may need some help. Specifically, Pin 4 (ID) of the OTG connector needs to be shorted to Pin 5 (GND) by using a [http://trisoft.de/pics/ZHost.JPG 5-pin USB Mini-A plug] which shorts these pins together in the plug. A [http://en.wikipedia.org/wiki/USB#USB_cables 5-pin USB Mini-B plug] leaves Pin 4 floating. Unfortunately, most USB Mini plugs are unmarked as to whether they are "A" or "B".<br />
<br />
You can find "mini A" adapters that have Pin 4 shorted and offer out a full-sized USB A Female jack [http://www.electronicproductonline.com/catalog/product_info.php?products_id=2043 here.]<br />
<table><br />
<tr><td><br />
Since the right cables might be hard to get, you simply can<br />
* short circuit the two pins encircled in red in the image to the right. You can do this by running a wire between the two pins. That at least allows easier undoing the change. Actually you could even have a small switch or so between 4 and 5.<br />
or<br />
* use a "mini B" cable (easier to get) and try the soldering of the two pins at the cable's connector. Depending on the cable it should be possible to open the plastic covering of mini-B port with a sharp-edged knife, then solder the two pins together, close the covering again and use some tape. This leaves the BeagleBoard unmodified.<br />
</td><td>[[Image:usb_otg.png]]</td></tr></table><br />
The Rev C BeagleBoard has a pair of pads labeled J6 on the back of the board under the OTG connector. Shorting these pads together with a wire or solder blob connects pins 4 and 5.<br />
See Figure 20 in the BeagleBoard System Reference Manual Rev C2.2.<br />
<br />
==DVI==<br />
<br />
DVI-D connection on BeagleBoard uses a [http://en.wikipedia.org/wiki/HDMI HDMI connector]:<br />
<br />
''HDMI is backward-compatible with the single-link Digital Visual Interface carrying digital video (DVI-D or DVI-I, but not DVI-A) used on modern computer monitors and graphics cards. This means that a DVI-D source can drive a HDMI monitor, or vice versa, by means of a suitable adapter or cable, but the audio and remote control features of HDMI will not be available.''<br />
<br />
BeagleBoard can be connected to a DVI monitor using HDMI female to DVI male cable.<br />
<br />
=BootRom=<br />
<br />
OMAP3 on BeagleBoard contains a BootRom. With this, BeagleBoard can boot without any code in permanent storage (NAND) or from peripherals. This is useful for first board bring up or if your BeagleBoard is bricked. For more information about BootRom booting see [http://www.ti.com/litv/pdf/sprufd6a SPRUFD6]. <br />
<br />
==User button==<br />
<br />
With user button on BeagleBoard you can configure boot order. Depending on this button, the order used to scan boot devices is changed. The boot order is (the first is the default boot source):<br />
<br />
* User button ''not'' pressed: NAND -> USB -> UART -> MMC<br />
* User button ''is'' pressed: USB -> UART -> MMC -> NAND<br />
<br />
Technically speaking, the user button configures pin SYS.BOOT[5]. See [http://focus-webapps.ti.com/general/docs/sitesearch/searchsite.tsp?selectedTopic=1653260327&numRecords=25&searchTerm=sprufd6&statusCode=null SPRUFD6] for more details.<br />
<br />
==Serial and USB boot==<br />
<br />
Historically, using OMAP3's boot ROM for serial and USB boot, there are several tools around. The newest are Nishanth' ''OMAP U-Boot Utils'', while there are still some older tools for serial boot and USB boot. It is also possible to access the [[u-boot environment variables in linux|u-boot env from linux]].<br />
<br />
===OMAP U-Boot Utils===<br />
<br />
Nishanth' [http://code.google.com/p/omap-u-boot-utils/ OMAP U-Boot Utils] provide<br />
<br />
* ''pserial'' - OMAP specific utility which downloads a file in response to ASIC ID over serial port.<br />
* ''pusb'' - OMAP specific utility which downloads a file in response to ASIC ID over USB connection.<br />
* ''ucmd'' - Send a command to U-Boot and wait till a specific match appears.<br />
* ''ukermit - Download a file from host without using kermit to U-Boot.<br />
<br />
See [http://nishanthmenon.blogspot.com/ Nishanth' blog] and [http://groups.google.com/group/beagleboard/browse_thread/thread/c5bfb1b8ed528b52# announce mail], too.<br />
<br />
===Serial boot===<br />
<br />
Besides Nishanth' ''OMAP U-Boot Utils'', to boot from USB or UART, you need a PC tool which talks with OMAP BootRom and speaks the correct protocol to download ARM target code to BeagleBoard. Currently there are two older (experimental) tools for UART boot:<br />
<br />
* [http://omapzoom.org/gf/project/omaptools/wiki PC Serial Boot perl script]<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/80ad3da0eb2aa555 Linux C utility] (not working yet with below target code)<br />
<br />
See [http://groups.google.com/group/beagleboard/browse_thread/thread/ae2c601ebe104a4 USB and serial download target code] for some example target code to be downloaded to OMAP3 on BeagleBoard.<br />
<br />
===USB boot===<br />
<br />
Besides Nishanth' ''OMAP U-Boot Utils'', for USB boot, there is currently one (experimental) tool to boot BeagleBoard over USB:<br />
<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/2b9e99886bb7a747 Linux C utility]<br />
<br />
See [http://groups.google.com/group/beagleboard/browse_thread/thread/ae2c601ebe104a4 USB and serial download target code] for some example target code to be downloaded to OMAP3 on BeagleBoard.<br />
<br />
See [[BeagleBoardRecovery#USB_recovery|USB recovery section]] how to use USB boot for board recovery.<br />
<br />
==NAND boot==<br />
<br />
See [[BeagleBoardNAND|NAND boot]] article.<br />
<br />
==MMC/SD boot==<br />
<br />
Currently, [http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard boot the BeagleBoard with MMC/SD] is the only working way for first board bring up.<br />
<br />
===MMC/SD formatting===<br />
<br />
As described in above MMC/SD boot description, you have to ''create a bootable partition on MMC/SD Card''. This can be done using e.g. Windows or Linux tools.<br />
<br />
'''Windows'''<br />
<br />
See ''HP USB Disk Storage Format Tool 2.0.6'' description on [http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard boot the BeagleBoard with MMC/SD] page.<br />
<br />
'''Linux'''<br />
<br />
Please see [http://wiki.omap.com/index.php?title=MMC_Boot_Format OMAP3 MMC Boot Format].<br />
<br />
===Dual partition card===<br />
<br />
You can [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat create a dual-partition card], booting from a FAT partition that can be read by the OMAP3 ROM bootloader and Windows, then utilizing an ext2 partition for the Linux root file system.<br />
<br />
To mount second ext2 partition as root file system (e.g. containing contents of [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode rd-ext2.bin]) use kernel boot arguments (e.g. in uboot using ''setenv bootargs''):<br />
<br />
console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait<br />
<br />
===U-Boot booting===<br />
<br />
If your MMC/SD card formatting is correct and you put [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode MLO, u-boot.bin and uImage] on the card you should get a u-boot prompt after booting beagle board. E.g. (output from terminal program with 115200 8N1):<br />
<br />
...40T.........XH.H.U�..Instruments X-Loader 1.41<br />
Starting on with MMC<br />
Reading boot sector<br />
<br />
717948 Bytes Read from MMC<br />
Starting OS Bootloader from MMC...<br />
<br />
U-Boot 1.1.4 (Apr 2 2008 - 13:42:13)<br />
<br />
OMAP3430-GP rev 2, CPU-OPP2 L3-133MHz<br />
TI 3430Beagle 2.0 Version + mDDR (Boot ONND)<br />
DRAM: 128 MB<br />
Flash: 0 kB<br />
NAND:256 MiB<br />
In: serial<br />
Out: serial<br />
Err: serial<br />
Audio Tone on Speakers ... complete<br />
OMAP3 beagleboard.org #<br />
<br />
Using this u-boot prompt, you now can start kernel uImage stored on MMC card manually:<br />
<br />
OMAP3 beagleboard.org # mmc init<br />
OMAP3 beagleboard.org # fatload mmc 0:1 0x80000000 uimage<br />
OMAP3 beagleboard.org # bootm<br />
<br />
If you like to make that happen every boot:<br />
<br />
OMAP3 beagleboard.org # set bootcmd 'mmc init ; fatload mmc 0:1 0x80000000 uimage ; bootm' ; saveenv<br />
<br />
=Code=<br />
<br />
Code and binaries for BeagleBoard are available at various places.<br />
<br />
==Binaries==<br />
<br />
BeagleBoard pre-built binaries and source code can be found at [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode Beagle source code] and [http://code.google.com/p/beagleboard/downloads/list downloads] page. These are the locations where "official" TI code is available. Please note that this code is mainly for reference and testing. More up to date binaries and code is available by community. Community took (parts) of TI reference code, improves and updates it. <br />
<br />
Actually, [http://www.angstrom-distribution.org/node/47 Koen's prebuilt Beagleboard demo images] are up to date binaries including e17 as window manager, the abiword word processor, the gnumeric spreadsheet application, a NEON accelerated mplayer and the popular NEON accelerated omapfbplay which gives you fullscreen 720p decoding. The [http://www.angstrom-distribution.org/demo/beagleboard www.angstrom-distribution.org/demo/beagleboard] directory should contain all the files you need:<br />
<br />
* [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.bin u-boot.bin]<br />
* [http://www.angstrom-distribution.org/demo/beagleboard/MLO MLO]<br />
* [http://www.angstrom-distribution.org/demo/beagleboard/uImage uImage]<br />
* [http://www.angstrom-distribution.org/demo/beagleboard/Angstrom-Beagleboard-demo-image-glibc-ipk-2009.X-test-20090104-beagleboard.rootfs.tar.bz2 rootfs]<br />
<br />
See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat beagle wiki] on how to setup your SD card to use all this goodness.<br />
<br />
==Source==<br />
<br />
Besides above binary and source images (TI's and communities one), for various parts of Beagle software stack there are community supported [http://git.or.cz/ git] repositories available. <br />
<br />
===X-Loader===<br />
<br />
Steve did some work to consolidate and update X-Loader from various sources and put it in a [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=x-load-omap3.git;a=summary X-Loader git repository]. Get it by<br />
<br />
git clone git://gitorious.org/x-load-omap3/mainline.git xloader<br />
cd xloader/<br />
<br />
Build:<br />
<br />
make distclean<br />
make omap3530beagle_config<br />
make<br />
<br />
Result will be a ~20k sized ''x-load.bin'' in main directory.<br />
<br />
===U-Boot===<br />
<br />
[http://www.denx.de/wiki/U-Boot/WebHome Mainline U-Boot] has good support for BeagleBoard. Get it by:<br />
<br />
git clone git://git.denx.de/u-boot.git u-boot-main<br />
cd u-boot-main<br />
git checkout --track -b omap3 origin/master<br />
<br />
Build (assuming [[ARMCompilers#Recommendations|Code Sourcery GCC]]):<br />
<br />
make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper<br />
make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_beagle_config<br />
make CROSS_COMPILE=arm-none-linux-gnueabi- <br />
<br />
Result will be a ~160k sized ''u-boot.bin'' in main directory.<br />
<br />
Note: Due to (patch and binary) size, BeagleBoard splash screen was removed from upstream version. If you want it back, use [http://groups.google.com/group/beagleboard/browse_thread/thread/3ad9b803a3418624 U-Boot v1 BeagleBoard splash screen patch].<br />
<br />
Note: For experimental U-Boot patches not ready for mainline yet, Steve's [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=summary Beagle U-Boot git repository] is used to test them. Get it by:<br />
<br />
git clone git://gitorious.org/u-boot-omap3/mainline.git u-boot-omap3<br />
cd u-boot-omap3<br />
git checkout --track -b omap3-dev origin/omap3-dev<br />
<br />
Note: For changing the screen resolution there is one option modifying the file in "include/configs/omap3_beagle.h" and adjusting the maximum resolution before compiling as describe in [http://gitorious.org/linux-omap-dss2/linux/blobs/master/Documentation/arm/OMAP/DSS ARM OMAP2/3 Display Subsystem]<br />
<br />
===Linux kernel===<br />
<br />
[http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary Git repository] of [http://muru.com/linux/omap/ OMAP Linux kernel] contains Beagle support. Get it by:<br />
<br />
git clone git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git linux-omap-2.6<br />
cd linux-omap-2.6<br />
<br />
Build:<br />
<br />
make distclean<br />
make omap3_beagle_defconfig<br />
make menuconfig # only needed if you want to change the default configuration<br />
make uImage<br />
<br />
The result will be a ''uImage'' in ''arch/arm/boot/'' directory.<br />
<br />
If you use the OE toolchain and want to build outside of the OE tree you should do<br />
ARCH=arm<br />
PATH=~/oe/tmp/cross/armv7a/bin:~/oe/tmp/staging/i686-linux/usr/bin:$PATH # add cross tools to your path<br />
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- distclean<br />
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- omap3_beagle_defconfig<br />
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- menuconfig # only needed if you want to change the default configuration<br />
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage<br />
Note: the staging dir in the path is for mkimage. If you've build a kernel before with oe, the program should be there<br />
<br />
Note: If you are interested in kernel development have a look to [[BeagleBoardLinuxKernel|manually compiling BeagleBoard kernel]], too.<br />
<br />
===Experimental kernel patches and hacks===<br />
<br />
Some beagle developers maintain their own kernel experimental patches and hacks not ready for upstream:<br />
<br />
* [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap Koen's collection of kernels patches for OE] and the [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap_git.bb list of relevant patches]<br />
* [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=shortlog;h=refs/heads/test Steve's kernel tree], a clone of main OMAP git with additional patches, mainly beagle audio (ASOC) related.<br />
* [http://git.mansr.com/?p=linux-omap;a=summary Mans' kernel tree], a clone of main OMAP git with additional patches, mainly display & framebuffer related.<br />
* [http://www.bat.org/~tomba/linux-omap.html Tomi's kernel tree], a clone of main OMAP git with display sub-system patches, replacing the entire display driver with one that is the likely direction moving forward.<br />
<br />
=Compiler=<br />
<br />
TI OMAP3530 processor on BeagleBoard contains an ARM Cortex-A8 general purpose processor and a TMS320C64x+ DSP.<br />
<br />
==ARM==<br />
<br />
There is broad compiler support including gcc - please see [http://www.elinux.org/ARMCompilers ARM Compilers]<br />
<br />
==C64x+ DSP==<br />
<br />
A free C64x DSP compiler is available as [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html Linux hosted C6x Code Generation Tools] (TMS320C6000 C/C++ CODE GENERATION TOOLS 6.1.3 July 2008).<br />
<br />
Note: my.TI account required. You may create an account [https://my.ti.com here]<br />
<br />
Note: Old c6000 Linux compiler available on [ftp://ftp.ti.com/pub/cs/linux_cgt500.tar.gz TI FTP site]. Does NOT support c64x+ core in OMAP3 devices. Not recommended.<br />
<br />
You can also utilize the [http://focus.ti.com/dsp/docs/dspsupportaut.tsp?familyId=44&sectionId=3&tabId=416&toolTypeId=30 full-CCS free evaluation tools for 120 days], but they currently require purchase to upgrade to service release 9 to support full JTAG debugging with supported JTAG hardware.<br />
<br />
See [[BeagleBoard/DSP_Howto| BeagleBoard DSP howto]] for information about how to use the DSP.<br />
<br />
=Cortex A8 ARM features =<br />
<br />
ARM Cortex-A8 in OMAP3 is a high performance dual-issue applications processor which reaches a performance of 2.0 DMIPS/MHz (compared to ARM11 at 1.2 DMIPS/MHz). It is ARM v7 architecture, which is fully backwards compatible with application code for previous ARM processors.<br />
<br />
It includes a floating point unit (ARM VFPv3 architecture) and the ARM NEON SIMD instruction set.<br />
<br />
See [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] article for an intro into VFP-lite and NEON.<br />
<br />
===ARM NEON===<br />
<br />
NEON is a 64/128-bit wide SIMD vector extension for ARM, which has been architected to be an efficient C compiler target as well as being used from assembly language. It has 32x 64-bit registers (with a dual view as 16x 128-bit registers) which can hold the following datatypes:<br />
* 64-bit signed/unsigned<br />
* 32-bit signed/unsigned<br />
* 32-bit single precision floating point<br />
* 16-bit signed/unsigned<br />
* 8-bit signed/unsigned<br />
<br />
The key advantage of NEON is very high performance vector math processing, whilst being easy to program. It is the same thread of control as the ARM (but different instructions), and is supported by the same tools, debuggers and operating systems.<br />
<br />
The NEON instruction set is documented in ARM's [http://infocenter.arm.com/help/topic/com.arm.doc.dui0204i/DUI0204I_rvct_assembler_guide.pdf RealView Compilation Tools Assembler Guide].<br />
<br />
For NEON optimized libraries see [http://www.us.design-reuse.com/news/18429/aac-mp3-mpeg-4-h-264-fft-openmax-cortex-a8-neon-arm11-processors.html ARM Releases AAC, MP3, MPEG-4, H.264 and FFT OpenMAX DL Libraries, Highly Optimized for Cortex-A8/NEON and ARM11 Processors]. Note: Read the [http://www.arm.com/products/esd/openmax_v7libraries.html EULA].<br />
<br />
NEON is currently used by<br />
* ffmpeg - libavcodec used by mplayer, omapfbplay, and many other linux applications<br />
* libpixman - used by X.org and Mozilla & Webkit browsers to render text and graphics<br />
* Bluez - official Linux Bluetooth stack<br />
<br />
=== ARM Cortex Floating Point ===<br />
<br />
There are two types of instructions in the ARM v7 ISA that handle floating point:<br />
<br />
1) '''VFPv3''' Floating point instruction set (used for single/double precision scalar operations).<br />
These is used by gcc for C floating point operations on 'float' and 'double'<br />
<br />
2) '''NEON''' [http://www.arm.com/products/multimedia/neon/ NEON] vectorized single precision operations (2 values in a D-register, or 4 values in a Q-register)<br />
These can be use by gcc when -ftree-vectorize is enabled and -mfpu=neon is specified, and the code can be vectorized. In other cases the VFPv3 scalar ops will be used.<br />
<br />
ARM Cortex-A processors have separate floating point pipelines that handle these different instructions.<br />
<br />
On Cortex-A8, the designers' focus was on the NEON unit performance which can sustain 1 cycle/instr throughput (processing 2 single-precision values at once). The scalar VFPv3 FPU cannot achieve this level of performance (cycle timings are in the Cortex-A8 TRM download), but it is still a lot better than doing floating point using integer instructions.<br />
<br />
If you need the highest performance floating point on Cortex-A8, you need to use single precision and ensure the code uses the NEON vectorized instructions:<br />
* use gcc with -ftree-vectorize (possibly modify source code to make it vector friendly)<br />
* use NEON instrinsics (#include <arm_neon.h>, float32x2_t datatype and vmul_f32() etc)<br />
* use NEON asm directly<br />
<br />
Keep in mind that mixing NEON and ARM load/stores can sometimes stall significantly. See [http://hardwarebug.org/2008/12/31/arm-neon-memory-hazards/ this link] for more info.<br />
<br />
On Cortex-A9, there is a much higher performance floating point unit which can sustain 1 cycle/instr throughput, with low result latencies.<br />
<br />
=Board recovery=<br />
<br />
If you played e.g. with the contents of the [http://www.sakoman.net/omap3/flash%20procedure.txt NAND], it might happen that the Board doesn't boot any more (without pressing user button) due to broken NAND content. See [[BeagleBoardRecovery|BeagleBoard recovery]] article how to fix this.<br />
<br />
=Development environments=<br />
<br />
Instead of just using compiler + editor, you can use complete image create "development tool chains" which integrate compiler, build system, packaging tools etc. in one tool chain.<br />
<br />
==OpenEmbedded==<br />
<br />
For [http://www.openembedded.org/ OpenEmbedded] (OE), there are some hints how to [http://www.beagleboard.org/irclogs/index.php?date=2008-04-29#T13:06:25 start with OE for BeagleBoard]. See [[BeagleBoardAndOpenEmbeddedGit|BeagleBoard and OpenEmbedded Git]] and [http://wiki.openembedded.org/index.php/Getting_Started OpenEmbedded getting started] as well.<br />
<br />
In the OE getting started document, for BeagleBoard replace ''MACHINE = "om-gta01"'' by ''MACHINE = "beagleboard"''. After confirming ''bitbake nano'' works, try ''bitbake console-image''. The first time you run bitbake OE will download all the needed source and build the tool chain. This will take several hours. After all went fine, the output is in ''${OE_ROOT}/tmp/deploy/glibc/images/beagleboard''.<br />
<br />
Note: Koen has some BeagleBoard [http://amethyst.openembedded.net/~koen/index.php?path=beagleboard/ source and binary images] built with OE. There, ''Angstrom-console*'' images don't include an X server, you can still use a e.g. DVI-D screen with console, but you won't have a GUI. ''Angstrom-x11*'' images contain an X server.<!-- DEAD LINK: resulting in something like [http://scap.linuxtogo.org/files/fc987d4acb2c745fb7e19cf4dca8de70.png this].--><br />
<br />
===One very important note:=== <br />
<br />
It's important to have an X-Loader on your Beagleboard that uses the uImage on the SD Card that goes with Angstrom. The B6 Beagleboards do not appear to come with such an X-Loader. So you likely will have to upgrade the X-Loader. Here's what to do:<br />
* Make an SD Card with the [http://www.angstrom-distribution.org/demo/beagleboard Angstrom Demo files]. See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat Beagleboard Wiki Page] for more info on making the SD Card.<br />
* Put the SD Card in the Beagle, and boot up to the U-Boot Prompt.<br />
* Do the first six instructions in the [http://code.google.com/p/beagleboard/wiki/BeagleNANDFlashing Flashing Commands with U-Boot] section. <br />
* Reboot the Beagle to see that the new X-Loader is properly loaded.<br />
<br />
This will update the X-Loader to a newer version that will automatically load uImage from the SD Card when present -- rather than always using the uImage in the Beagleboard NAND.<br />
<br />
==Eclipse==<br />
The Eclipse [http://www.eclipse.org/cdt/ C Development Tools Project] provides a "fully functional C and C++ Integrated Development Environment (IDE) for the Eclipse platform". The Eclipse [http://www.eclipse.org/dsdp/tm/ DSDP Target Managment Project] provides a "Remote System Explorer" (RSE) plugin that simplifies downloading files to the BeagleBoard and editing files on the BeagleBoard within the Eclipse IDE. A Linux Target Agent is available as part of the [http://wiki.eclipse.org/DSDP/TM/TCF_FAQ Target Communications Framework (TCF) component]. Info on how RSE is used for e.g. Gumstix development is described in [http://groups.google.com/group/beagleboard/browse_thread/thread/509831f7c24cb79f# this post].<br />
<br />
==Android==<br />
[http://source.android.com Android] platform is a software stack for mobile devices including an operating system, middleware and key applications. Developers can create applications for the platform using the [http://code.google.com/android/ Android SDK]. Applications are written using the Java programming language and run on Dalvik, a custom virtual machine designed for embedded use which runs on top of a Linux kernel.<br />
<br />
There are several resources for Android on OMAP (Beagle) available:<br />
<br />
'''OMAPZOOM'''<br />
<br />
You can find Android port for OMAP ZOOM architecture on [https://omapzoom.org/gf/project/omapandroid/wiki/ OMAPZoom.org's wiki page on Android]. <br />
<br />
'''EMBINUX'''<br />
<br />
[http://beagleboard.org/project/android Beagleboard.org's Android project page] [http://groups.google.com/group/beagleboard/browse_thread/thread/7b422f113ce489b5 announced], the successful porting of Android on Beagle board by [http://embinux.com EMBINUX&trade;] Team. The [http://labs.embinux.org/git/ source code] and [http://www.embinux.com/download_beagle.php binaries] are available for download and review. <br />
<br />
Detailed instructions, for porting Android on Beagle Board, are available [http://labs.embinux.org/index.php/Main_Page here]. Current release supports input devices (keyboard/mouse), network and sound.<br />
<br />
You can [http://in.youtube.com/watch?v=nADn_vNVEKw watch Android booting] on Beagle Board.<br />
<br />
'''Android on OMAP wiki'''<br />
<br />
Wiki page for Andorid on OMAP can be found [[Android on OMAP|here]]<br />
<br />
'''0xdroid'''<br />
<br />
[http://gitorious.org/0xdroid 0xdroid], the enhanced version of Android on Beagleboard by [http://0xlab.org 0xlab]. The [http://gitorious.org/0xdroid source code], [http://downloads.0xlab.org/ pre-built binaries], and [http://code.google.com/p/0xdroid/issues/list issue tracker] are available for review and reference.<br />
<br />
The latest development supports OMAP audio, OMAP video overlays, ARM Cortex A8 NEON/Thumb2 performance optimizations, mouse cursor, hot-pluggable USB keyboard & mouse, user-friendly installer for system image, and various Android tweaks. Detailed instructions for 0xdroid are available through [http://code.google.com/p/0xdroid/wiki/MainPage Google Code wiki].<br />
<br />
You can [http://www.youtube.com/watch?v=v6wdTOHrwQw watch 0xdroid demo video] on Beagle Board.<br />
* [http://www.youtube.com/watch?v=v6wdTOHrwQw 0xdroid demo video (1)]<br />
* [http://www.youtube.com/watch?v=ol9LWBKXXwQ 0xdroid demo video (2)]<br />
<br />
==Mamona==<br />
<br />
[http://dev.openbossa.org/trac/mamona/wiki Mamona] is an embedded Linux distribution for ARM EABI. The main goal of the Mamona Project is to offer a completely open source alternative/experimental platform for [http://maemo.org/ Maemo] using only free and open source components. Mamona [http://rsalveti.wordpress.com/2008/09/12/mamona-02-is-out 0.2] [http://franciscoalecrim.com/blog/2008/07/29/mamona-working-with-beagleboard/ supports] [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12013&contentId=28741 OMAP3430 Software Development Platform (SDP)], so you can also use it at Beagle (OMAP3530), too. Work is being done to officially support Beagle.<br />
<br />
==Ubuntu==<br />
<br />
See [[BeagleBoardUbuntu|Ubuntu (ARM)]] installation guide how to install Ubuntu (ARM) on BeagleBoard.<br />
<br />
==Debian ARM==<br />
<br />
See [[BeagleBoardDebian|Debian (ARM)]] installation guide how to install Debian (ARM) on BeagleBoard.<br />
<br />
==Handhelds Mojo ARM==<br />
<br />
See [[BeagleBoardHandheldsMojo|Handhelds Mojo (ARM)]] installation guide how to install Handhelds Mojo (ARM) port of Ubuntu on BeagleBoard. (The Mojo project is no longer active, see the Official Ubuntu ARM-port above instead)<br />
<br />
==Scratchbox==<br />
<br />
[http://www.scratchbox.org/ Scratchbox] is a cross-compilation toolkit designed to make embedded Linux application development easier. It also provides a full set of tools to integrate and cross-compile an entire Linux distribution. See [http://felipec.wordpress.com/2009/06/07/installing-scratchbox-1-and-2-for-arm-cross-compilation/ Felipe's Scratbox 1 and 2 intro], too.<br />
<br />
=Software hints=<br />
<br />
This section collects hints, tips & tricks for various software components running on beagle.<br />
<br />
==QEMU==<br />
<br />
[[Qemu|QEMU]] [http://vm-kernel.org/blog/2008/12/15/linux-is-running-on-qemu-omap3/ supports OMAP3] being able to boot a BeagleBoard Linux kernel.<br />
<br />
==Linux hints==<br />
<br />
See BeagleBoard [http://code.google.com/p/beagleboard/wiki/LinuxHints Google wiki Linux hints] page (for Linux WTBU (Wireless TI Business Unit) kernel [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode 2.6.22]). Currently featuring:<br />
<br />
* Switching video output between DVI-D and S-Video<br />
* Disabling framebuffer blanking<br />
* Listing USB devices<br />
<br />
==lmbench==<br />
<br />
Avik posted a detailed [http://groups.google.com/group/beagleboard/browse_thread/thread/c8b8f07ce61161a1 step-by-step procedure] to run [http://sourceforge.net/project/showfiles.php?group_id=14418 lmbench] on Beagle.<br />
<br />
==Mediaplayer (FFmpeg)==<br />
<br />
There is a thread how to get a [http://groups.google.com/group/beagleboard/browse_thread/thread/9b8025fc15120fd9# mediaplayer] with NEON optimization (FFmpeg) to run on Beagle. Includes compiler hints and patches.<br />
<br />
==Java==<br />
<br />
When using the [[BeagleBoard#OpenEmbedded|OpenEmbedded]]-based Angstrom image you have the following options of Java support:<br />
* JamVM + GNU Classpath (small vm, fast interpreter, J2SE-like)<br />
* Cacao + GNU Classpath (JIT compiler, J2SE-like)<br />
* PhoneME Advanced Foundation (JIT compiler, CDC)<br />
<br />
Java support in OpenEmbedded/Angstrom ([http://wiki.openembedded.net/index.php/Java details]) is provided voluntarily through [http://jalimo.org Jalimo].<br />
<br />
See a [http://groups.google.com/group/beagleboard/browse_thread/thread/102f627253919783# post at mailing list], too.<br />
<br />
OpenEmbedded users can add the [http://evolvis.org/scm/?group_id=11 Jalimo Subversion repository] as an overlay (instructions are in the repository). This will allow them to build OpenJDK packages. Inclusion of these recipes in mainline OpenEmbedded is planned but still ongoing.<br />
<br />
The recipes offer the following functionality:<br />
<br />
* OpenJDK + Hotspot (Zero port) (all J2SE functionality, including JVMTI, interpreted only)<br />
* OpenJDK + Cacaco (all J2SE library features, missing JVMTI, decent JIT compiler)<br />
* OpenJDK + Hotspot (Shark port) (not working yet)<br />
<br />
[http://camswl.com/ Edward Nevill] from ARM Ltd. is working on interpreter optimization in Zero for ARM.<br />
<br />
People interested in getting this stuff working better should contact people on:<br />
* [http://evolvis.org/mail/?group_id=11 Jalimo Mailinglist]<br />
* [http://mail.openjdk.java.net/mailman/listinfo/distro-pkg-dev Icedtea Mailinglist]<br />
<br />
You should also check out IcedTea's [http://iced-tea.org/wiki/FrequentlyAskedQuestions FAQ].<br />
<br />
=Graphics accelerator=<br />
<br />
OMAP3530 used on BeagleBoard contains a graphics accelerator (SGX) based on the SGX core from [http://www.imgtec.com/ Imagination Technologies]. [http://www.imgtec.com/powervr/powervr-graphics.asp PowerVR] SGX530 is a new generation of programmable PowerVR graphics and video IP cores. Only the kernel portions of Linux drivers will be open source. The PowerVR folks will provide binary user-space libraries. Using the EMail contact at [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12700&contentId=27458 TIs Mobile Gaming Developers page] there are Linux v2.6 OMAP3430 SDKs for OMAP3 Zoom and SDP supporting OpenGL ES v2.0, OpenGL ES v1.1 and OpenVG 1.0 available.<br />
<br />
Tutorial:<br />
* [http://code.google.com/p/beagleboard/wiki/HowtoUseSGXunderAngstrom How to use SGX with Angstrom in OE]<br />
<br />
Some videos:<br />
<br />
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle working with Linux 2.6.27]<br />
* [http://www.youtube.com/watch?v=24TXpqa9jG0&feature=related OpenGL ES 2.0 shader effects on OMAP3]<br />
* [http://www.youtube.com/watch?v=-UFUbqoNgs8&feature=related 3D User Interface on OMAP3 Platform]<br />
* [http://www.youtube.com/watch?v=8KcNgeUriqA 3D Mapping using OpenGL ES 2.0 on OMAP3 Platform]<br />
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]<br />
* [http://www.hitlabnz.org/wiki/EmbeddedAR An Augmented Reality application combining ARToolkit and OpenGL ES 2.0]<br />
<br />
=Beginners guide=<br />
<br />
You just got your new BeagleBoard, and now? See [[BeagleBoardBeginners|beginners guides]].<br />
<br />
=FAQ=<br />
<br />
For BeagleBoard frequently asked questions (FAQ) see [[BeagleBoardFAQ|community FAQ]] and "official" [http://beagleboard.org/support/faq BeagleBoard.org FAQ].<br />
<br />
=Links=<br />
==Home page==<br />
[http://beagleboard.org/ beagleboard.org] (beagle board home)<br />
* Using [http://www.google.de/ Google] you can search beagleboard.org (including [http://www.beagleboard.org/irclogs/ IRC logs]) using ''site:beagleboard.org <search term>''<br />
<br />
==Manuals and resources==<br />
* [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard HW Reference Manual (rev. C2)]<br />
* [http://beagle.s3.amazonaws.com/BBSRM_7_2_0.pdf BeagleBoard HW Reference Manual (rev. B7)]<br />
* [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)]<br />
* [http://www.beagleboard.org/uploads/BBSRM_B5.pdf BeagleBoard HW Reference Manual (rev. B5)]<br />
* [http://www.beagleboard.org/uploads/Beagle_HRM_B4.pdf BeagleBoard HW Reference Manual (rev. B4)]<br />
* [http://www.beagleboard.org/uploads/Beagle_HW_Reference_Manual_A_5.pdf BeagleBoard HW Reference Manual (rev. A5)]<br />
* [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor description and manuals<br />
* [http://code.google.com/p/beagleboard/ Beagle at code.google.com]<br />
* [http://focus.ti.com/dsp/docs/dspsupporttechdocs.tsp?sectionId=3&tabId=409&familyId=1526&documentCategoryId=4&techDoc=4 OMAP3530/25 CBB BSDL Model]<br />
* [http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for Beagle Board]<br />
* [http://beagleboard.org/resources Beagleboard resources page with hw docs]<br />
* Some [http://www.rasterman.com/ performance comparison] of BeagleBoard Rev. B with some other ARM/PC systems.<br />
* OMAP3 pinmux [http://www.hy-research.com/omap3_pinmux.html setup]<br />
* [http://elinux.org/BeagleBoardPinMux OMAP3 eLinux pinmux page]<br />
<br />
==Contact and communication==<br />
* [http://groups.google.com/group/beagleboard Beagle board discussion list]<br />
* [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker]<br />
* [http://beagleboard.blogspot.com/ Beagle board blog]<br />
* [http://feeds.feedburner.com/BeagleBoard Beagle board RSS feed]<br />
* Chat:<br />
** [http://beagleboard.org/chat Beagle Board chat]<br />
** IRC: #beagle channel on irc.freenode.net<br />
** [http://www.beagleboard.org/irclogs/index.php IRC archive]<br />
* [http://www.beaglesride.org/ Beagles Ride], a site about building a community around the BeagleBoard focused on in vehicle applications<br />
* [http://www.beagleboard.de/ German Beagle Board Forum and Wiki]<br />
<br />
==TI resources==<br />
* [http://opensource.ti.com/ TI open source page]<br />
* [https://community.ti.com/ TI E2E (Engineer-to-Engineer) Community]<br />
* [http://marc.info/?l=linux-omap&m=120761100810527&w=2 DSP Bridge driver for OMAP3 platform]<br />
* [http://lists.arm.linux.org.uk/lurker/message/20080701.142512.5eeff26b.en.html ARMv7 Oprofile support]<br />
* [http://focus.ti.com/pdfs/wtbu/swpu114g.pdf OMAP34xx Wireless Technical Reference Manual] (swpu114g.pdf, 47 MB)<br />
* [http://amethyst.openembedded.net/~koen/index.php?sort=date&order=desc&path=beagleboard/ Koen's (OpenEmbeded) BeagleBoard source and binaries]<br />
* [http://del.icio.us/tag/beagleboard+peripheral+verified Verified peripherals for BeagleBoard]<br />
* [http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt OMAP3430 Linux Power Management presentation]<br />
==Articles==<br />
* [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article about Beagle]<br />
* [http://www.linuxdevices.com/news/NS8479495970.html LinuxDevices article about Digi-Key launch]<br />
* [http://www.linuxdevices.com/news/NS5682470737.html LinuxDevices article about Beagle Rev C, Beagle MID from HY Research, Touch Book and Sponsored Projects Contest]<br />
* [http://www.linuxjournal.com/article/10607 Linuxjournal article on the BeagleBoard]<br />
<br />
==Books==<br />
* [[OMAP_and_DaVinci_Software_for_Dummies|OMAP and DaVinci Software for Dummies]]<br />
<br />
==Beagle based training materials==<br />
* http://free-electrons.com/blog/beagle-labs/<br />
<br />
==Past Beagle events==<br />
* TIDC, February 26-28, 2008: [http://www.beagleboard.org/uploads/tidc_opensource.pdf Slides from TI developer conference (TIDC) open source session], covering also beagle board<br />
* [http://www.lugradio.org/live/USA2008/ LUG RADIO Live USA 2008, April 12-13, 2008]: [http://www.beagleboard.org/uploads/lugradio_20080411.PPT TI/Beagle Presentation] and [http://forums.lugradio.org/viewtopic.php?f=4&t=4094&st=0&sk=t&sd=a&sid=d69cc807569ab41e33f93af698c536b8&start=15#p41549 video]<br />
* LinuxTag, May 28-31, 2008: [http://www.flickr.com/photos/jadon/2551439955/in/pool-beagleboard picture 1] and [http://www.flickr.com/photos/jadon/2535692865/in/pool-beagleboard picture 2]<br />
* [http://lugradio.org/live/UK2008/travel LugRadio Live UK 2008], July 19 - July 20, 2008: [http://www.flickr.com/photos/koenkooi/tags/lugradiolive/ Koen's pictures] showing e.g. [http://www.bigbuckbunny.org/index.php/download/ Big Buck BUNNY] playing at Beagle. [http://linuxoutlaws.com/podcast/48 Interview with Linux Outlaws (52:06)] and the [http://www.youtube.com/watch?v=m9xVbntl-DY video]<br />
* [http://osscamp.in/index.php/OSScamp_Bengaluru_Mobile_2008 OSScamp Bengaluru Mobile 2008], July 19, 2008<br />
* [http://www.linuxworldexpo.com LinuxWorld Conference & Expo], August 4 - August 7, 2008: [http://www.flickr.com/photos/jadon/sets/72157606586084668/ pictures with living beagle] and from [http://www.flickr.com/photos/linuxjournal/2738316951/in/set-72157606634486338/ Linux Journal's photostream]<br />
* BeagleBoard.org event at Jillian's during LinuxWorldExpo, August 5, 2008, 5:30-7:30 pm<br />
* [http://barcamp.pbwiki.com/BarCampHouston3 BarCamp Houston 3], August 9, 2008, 9:00 A.M.: [http://www.flickr.com/photos/jadon/sets/72157606656532041/ pictures]<br />
* NIT Suratkal, India [http://www.nitkieee.com/site/sp-connect2/schedule IEEE SP Connect 2], August 30, 20008<br />
* [http://barcampbangalore.org/wiki/BCB7_Demos BarCamp Bangalore], India, September 13, 2008<br />
* [http://www.ibc.org/ IBC 2008], September 11 - September 16, 2008: [http://www.flickr.com/photos/koenkooi/tags/ibc2008/ pictures]<br />
* Free Open "Embedded Linux" Training for Students in India, [http://code.google.com/p/beagleboard/wiki/Trainings?updated=Trainings&ts=1220250913 beagleboard.org Trainings in India], September 20, 2008: [http://www.youtube.com/watch?v=A6FLdmgQlb4&feature=PlayList&p=1BAB6EE9CC7285AD&index=0 video], [http://www.flickr.com/photos/25691331@N04/sets/72157607419766102/ photos] and [http://lakshmansrikanth.blogspot.com/2008/09/linux-embedded.html blog]<br />
* [http://www.embedded.co.uk/ Embedded Systems Show 2008], Birmingham, UK, October 1-2, 2008<br />
* [http://www.mvista.com/vision/ MontaVista Vision 2008 Embedded Linux Developers Conference], San Francisco, California, October 1-3, 2008 : [http://www.mvista.com/download/topic.php?t=18 Video and presentation overview], [http://www.mvista.com/download/fetchdoc.php?docid=323 William Mills' presentation], [http://www.mvista.com/download/fetchdoc.php?docid=333 Jason Kridner's presentation]<br />
* [http://www.rtcgroup.com/arm/2008/ ARM Developers' Conference], Santa Clara Convention Center, Santa Clara, Calif., USA, October 7-9, 2008<br />
* [http://www.cmp-egevents.com/web/escb Embedded Systems Conference Boston 2008], Hynes Convention Center, Boston, USA, October 26 - October 30, 2008: [http://beagleboard.org/demo/esc Resources]<br />
* [[BeagleBoard/contest|BeagleBoard contest]] #1: Create a cool BeagleBoard application and win a Rev C1! Closed, ran until January 9, 2009<br />
* [http://www.silica.com/events/seminars/seminar-overview/ti-omp-workshop.html OMAP35x training by Silica], January 21, 2009, Cambridge, UK, ARM Holdings Lecture Theatre. [[RichardB's notes from the seminar]]<br />
* [[BeagleBoard/contest|BeagleBoard contest #2]], unitl February 27, 2009: : Create a cool BeagleBoard application and win a Rev C2!<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/b15cf8a5797c73a2 Silica - Free TI - ARM OMAP Workshop], Brussels, Europe, March 31st 2009<br />
* SILICA's [http://www.silica.com/events/seminars/seminar-overview/ti-omap-piccolo-poing.html Texas Instruments 2-in-1 Seminar: OMAP & Piccolo], May 13th 2009: Poing (Munich) - Germany<br />
* 24th until 27th June 2009: [http://www.linuxtag.org/2009/en.html Linux Tag Germany] with [http://groups.google.com/group/beagleboard/msg/27fefef5f1d2ef73 TI booth] and [http://www.linuxtag.org/2009/en/program/freies-vortragsprogramm/all-events/details.html?talkid=183 Beagle presentation]<br />
* until 31st July 2009: [http://www.cranessoftware.com/services/training/beagledesigncontest.html BeagleBoard Design Contest INDIA Edition] ([http://beagleboard.blogspot.com/2009/04/beagleboard-design-contest-india.html blog entry])<br />
* TI Technology Day Dallas, Tex. on June 16 will held a [http://www.linuxdevices.com/news/NS5682470737.html BeagleBoard users group meeting] (see section ''Availability'').<br />
* Thursday, August 27th: [http://wiki.omap.com/index.php/ETechDays_Lightning_Talks ETechDays Lightning Talks]. 15 minute lightning talks via IRC, WebEx or Dial-In.<br />
* 22.- 23.08.2009, Sankt Augustin, Germany: [http://www.froscon.de/en/ FrOSCon 2009] ([http://groups.google.com/group/beagleboard/browse_thread/thread/6aee27a7d121f4f4# call for papers])<br />
<br />
==Beagle wiki pages==<br />
* [[BeagleBoardBeginners|BeagleBoard beginners guides]]<br />
* [[BeagleBoardAndOpenEmbeddedGit|BeagleBoard and OpenEmbedded Git]] installation guide and [[BeagleBoardOpenEmbeddedDevelopment|OpenEmbedded development]]<br />
* [[BeagleBoardDebian|Debian on BeagleBoard]] usage guide<br />
* [[BeagleBoardHandheldsMojo|Handhelds Mojo (ARM) on BeagleBoard]] usage guide (formerly known as Ubuntu (ARM))<br />
* [[BeagleBoardUbuntu|Ubuntu (ARM EABI) distribution at BeagleBoard]]<br />
* [[BeagleBoardRecovery|BeagleBoard recovery]] about fixing boards not booting any more because of broken NAND content<br />
* [[BeagleBoardJTAG|BeagleBoard JTAG]] and [[OMAP3530_ICEPICK|OMAP3530_ICEPICK]] about JTAG on BeagleBoard<br />
* [[BeagleBoardOpenOCD|BeagleBoard OpenOCD]] has infos about status and usage of open source JTAG software OpenOCD with Beagle<br />
* [[BeagleBoardNAND|BeagleBoard NAND boot]] about how to boot BeagleBoard from NAND flash<br />
* [[BeagleBoardPeripherals|BeagleBoard peripherals and adapters page]] about useful BeagleBoard add ons.<br />
* [[Mount_BeagleBoard_Root_Filesystem_over_NFS_via_USB|Mount BeagleBoard root file system over NFS via USB]]<br />
* [[BeagleBoardFAQ|BeagleBoard FAQ]]<br />
* [[BeagleBoardSugar|Sugar on BeagleBoard]]<br />
* [[BeagleBoard/DSP_Howto|BeagleBoard DSP howto]]<br />
* [[BeagleBoardRawLCD|Interfacing BeagleBoard to Raw LCD]]<br />
* [[BeagleBoard/gst-openmax|BeagleBoard OpenMAX usage]]<br />
* [[BeagleBoard/video|BeagleBoard video]]<br />
* [[BeagleBoardOpenCV|Using OpenCV computer vision library with BeagleBoard]]<br />
* [[BeagleBoard/James|James]]: Just A Miniature Entertainment System<br />
* [[U-boot_musb_gadget_support|U-boot musb gadget support]]<br />
* [[BeagleBoard-JP|Japanese translation of this Beagle page]]<br />
* [[BeagleEPD|BeagleBoard E-Ink Platform Driver]]<br />
* [[BeagleBoardFedora|Random hacking notes for getting Fedora 10 to kinda work with the BeagleBoard]]<br />
* BeagleBoard specific [[BeagleBoard/GSoC|Google Summer of Code 2009]] page, [[BeagleBoard/Ideas-2009|GSoC project ideas]] and [[BeagleBoard/GSoC/Application|GSoc application]]<br />
* [[BeagleBoard/Poky|Poky]] for BeagleBoard<br />
* [[Xenarc_USB_touchscreen_for_Beagleboard/OMAP3_EVM|Xenarc USB touchscreen for Beagleboard/OMAP3 EVM]]<br />
* [[BeagleBoard/BugAdapter|BeagleBoard Bug Adapter board]]<br />
* [[BeagleBoardDebianWifiInstallInfo|BeagleBoard Debian WiFi install info]]<br />
* [[BeagleBoard/DSP_Clarification|Info about the various Linux DSP systems for OMAP chips]]<br />
* [[BeagleBoardPinMux|BeagleBoard PinMux]]<br />
* [[BeagleBoardLinuxKernel|BeagleBoard Linux kernel manual compile]]<br />
* [http://www.hervanta.com/stuff/Beaglebot Beaglebot]: build an experimental robotics project with Beagle<br />
* [http://code.google.com/p/beagleboard/w/list code.google.com BeagleBoard wiki]<br />
* '''[[BeagleBoard/contest|BeagleBoard contest]]'''<br />
* [http://en.wikipedia.org/wiki/Beagle_Board Wikipedia BeagleBoard page]<br />
* [http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board Android port for BeagleBoard]: Instructions for porting Android on BeagleBoard<br />
* [[BeagleBoard/bangalore_user_meet |BeagleBoard Bangalore User Meet]]<br />
* [[BeagleBoardEclipse|Using Eclipse with Beagle]] (for JTAG debugging)<br />
* [[Zoom2Beginners|Zoom2 for Beginners]]<br />
* [http://wh1t3s.com/2009/05/11/beagleboard-as-usb-mass-storage-device-via-usb-otg/ BeagleBoard as USB Mass Storage Device via USB OTG]<br />
* [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm BeagleBoard as solar powered computer]<br />
* [http://blog.makezine.com/archive/2009/02/blinking_leds_with_the_beagle_board.html Blinking LEDs with the Beagle Board] from Make:Online<br />
* [http://www.crashcourse.ca/wiki/index.php/BeagleBoard Robert's private Beagle wiki] (please don't add anything there, do it here. It will help to avoid scattering. Thanks!)<br />
* [http://felipec.wordpress.com/2009/03/26/omap3-public-dsp-binaries-now-work/ Felipe's blog] about D1 MPEG-4 decoding using less than 15% of CPU with help of DSP<br />
* [http://www.syspire.de/node/3 Embedded Mediacenter] based on BeagleBoard (German)<br />
* [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] with VFP-lite and NEON intro<br />
* [http://particolarmente-urgentissimo.blogspot.com/2009/09/beagleboard-setting-date-via-gps.html Beagleboard setting date via GPS]<br />
* [http://free-electrons.com/blog/beagle-labs/ Complete embedded Linux training labs] on the BeageBoard<br />
<br />
==Beagle photos==<br />
* [http://www.flickr.com/groups/beagleboard/pool/ Beagle board pictures at flickr]<br />
* [http://www.flickr.com/photos/32615155@N00/2439256116/ Beagle board and USRP]<br />
* [http://www.flickr.com/photos/nishanthmenon/2438406603/ Modify SDP3430 QUART cable for beagle]<br />
* [http://www.flickr.com/photos/koenkooi/2695061759/ MythTV on Beagle]<br />
==Beagle videos==<br />
* [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings]<br />
* [http://www.youtube.com/watch?v=cXr-D1wROfQ Beagleboard in the Living Room]<br />
* [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu]<br />
* [http://uk.youtube.com/watch?v=TUYOjRGYeYU testsprite with beagleboard]<br />
* [http://uk.youtube.com/watch?v=9Z4ZTovtFKk Beagleboard LED demo]<br />
* [http://uk.youtube.com/watch?v=R33dzREZGEk LCD2USB attached to a beagleboard]<br />
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]<br />
* [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector]<br />
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle working with Linux 2.6.27]<br />
* Not on Beagle OMAP3530: [http://youtube.com/watch?v=5i9cWOK1spw Ubuntu 7.04 on on OMAP3430 SDP]<br />
* [http://in.youtube.com/watch?v=nADn_vNVEKw Beagle Board booting Android]<br />
* [http://www.youtube.com/watch?v=UHQdUS0i-nw Beagleboard, SGX, and libfreespace demo]<br />
<br />
==Beagle manufacturing==<br />
* [http://www.youtube.com/watch?v=C-CwkjT9z_0&feature=related Beagle Solder Paste Screening]<br />
* [http://www.youtube.com/watch?v=9LLjDovIG2M&feature=related Beagle Assembly Inspection]<br />
* [http://www.youtube.com/watch?v=sbOZfBnoVnM&feature=related Beagle Functional Test]<br />
* [http://www.youtube.com/watch?v=cvDtXmJJcEI&feature=related Beagle Reflow]<br />
* [http://www.youtube.com/watch?v=W2o4NTASxN0&feature=related Beagle Board Assembly at Circuitco]<br />
==Fun==<br />
* Enjoy [http://www.beaglegame.com/ BeagleGame]<br />
<br />
=Other OMAP boards=<br />
<br />
* OMAP1 OMAP5912 (ARM9 + C5x DSP) based [[OSK|OSK]] board.<br />
* OMAP3 OMAP3430 based [https://gforge.ti.com/gf/project/omapzoom/wiki/?pagename=HardwareInformation Zoom MDK], which has been superseded by the [http://www.logicpd.com/products/development-kits/texas-instruments-zoom%E2%84%A2-omap34x-ii-mdp Zoom II], and other [http://www.logicpd.com/products LogicPD kits].<br />
* OMAP3 OMAP3530 based [http://www.openpandora.org/ Pandora]<br />
* OMAP3 OMAP3503 based [http://www.gumstix.net/Overo/cat/Overo/115.html Gumstix Overo]<br />
* OMAP3 OMAP35x based EVM from [http://mistralsolutions.com/products/omap_3evm.php Mistral] and [http://focus.ti.com/docs/toolsw/folders/print/tmdxevm3503.html TI] (both are the same)<br />
* OMAP3 OMAP3430 based [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12013&contentId=28741 Software Development Platform (SDP)]<br />
* OMAP3 OMAP3530 based board from [http://www.magniel.com/omap3.html Magniel Inc.]<br />
* OMAP3 based [http://www.archos.com/products/imt/index.html?country=us&lang=en Archos 5, ARCHOS 5G and ARCHOS 7]<br />
* OMAP3 OMAP35x based [http://www.logicpd.com/products/som/ti/omap35x OMAP35x SOM-LV]<br />
* OMAP3 based [[Mini_Board|ICETEK-OMAP3530-Mini]], a Chinese BeagleBoard clone, with a [[MiniBoardFAQ|FAQ]]<br />
* OMAP3 based [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], a German BeagleBoard clone<br />
* OMAP3530 based [http://www.bsquare.com/products/hardware_solutions/3530.asp BSQUARE’s Dev Kit OMAP3530]<br />
* OMAP3530 based [http://beaversource.oregonstate.edu/projects/cspfl/wiki/CSPFL_Hardware OSWALD]<br />
* OMAP3 BeagleBoard-based [http://www.alwaysinnovating.com/touchbook/ Touch Book]<br />
* OMAP3530 based [http://www.analogue-micro.com/Cobra3530.html Cobra 3530 OMAP3530 module ]<br />
* OMAP3 based [http://www.kwikbyte.com/KBOC.html KwikByte 35XX System Module]<br />
* OMAP3530 based [[DevKit8000]], a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard)<br />
* OMAP3530 based [http://www.igep-platform.com/ IGEPv2 Platform], a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, wifi+bluetooth.<br />
* OMAP35x based [http://www.ultratronik.de/mmi-rechnerplattformen.html MMI4 from Ultratronik]<br />
* OMAP35x based [http://www.technexion.com/index.php/tao-3530 TAO-3530 from TechNexion]<br />
* OMAP35x based [http://www.variscite.com/varomap35xxsbc.html VAR-OM35xxSBC from Variscite]<br />
* OMAP35x based [[EGS3530]],a Chinese BeagleBoard clone from [http://www.ema-tech.com EMA]<br />
* OMAP3 OMAP35x based [http://www.buglabs.net/products BUG] from Bug Labs, Inc.<br />
<br />
=Subpages=<br />
<splist<br />
parent=<br />
showparent=no<br />
sort=desc<br />
sortby=title<br />
liststyle=ordered<br />
showpath=no<br />
kidsonly=no<br />
debug=0<br />
/></div>Som2416https://elinux.org/index.php?title=BeagleBoardJTAG&diff=18894BeagleBoardJTAG2010-03-30T12:51:56Z<p>Som2416: /* ARM RealView ICE */</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
The page is about [http://en.wikipedia.org/wiki/JTAG JTAG] on OMAP3530 used at [[BeagleBoard|BeagleBoard]].<br />
<br />
=Beagle JTAG connection=<br />
The [[BeagleBoard]] comes with a 14 pin [[JTAG-TI|TI JTAG]] connector. For JTAG pin out see section 8.16 of [http://www.beagleboard.org/uploads/Beagle_HW_Reference_Manual_B_5.pdf BeagleBoard HW Reference Manual (rev. B5)]. This is the same header interface as used in other TI products and is ''NOT'' the standard 14 pin ARM layout. Depending on your JTAG tool, you'd need a [[JTAG-TI|20-pin to 14-pin TI adapter]].<br />
<br />
'''Attention: JTAG on BeagleBoard uses 1.8V!'''<br />
<br />
The 14-pin TI JTAG connector that is used on BeagleBoard is supported by a large number of JTAG emulation products and has been tested using Lauterbach, Green Hills, Spectrum Digital XDS510USB+ and TI XDS560 emulation pods. Note that it will not work with the Spectrum Digital XDS510USB (non-plus) as it does not support a target with 1.8V JTAG.<br />
<br />
The following picture is from a [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf TI OMAP JTAG presentation]:<br />
<br />
[[Image:Ti arm jtag.jpg]]<br />
<br />
Beagle uses the 14-pin TI header.<br />
<br />
Note: TI uses some different pin names. Translation:<br />
* TVD => VREF at Beagle<br />
* TCLKR == RTCK<br />
* TCLKO == TCK<br />
* #### == Key (empty))<br />
* TDIS => GND at Beagle<br />
<br />
See [[OMAP3530_ICEPICK|ICEPICK configuration page]] for more details about how OMAP3 JTAG hardware needs to be configured.<br />
<br />
== Beagle adapter ==<br />
The [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]] we plan to use has a 14 pin ARM layout, so we need to create a converter. From [http://www.tincantools.com/assets/JTAG_pin_assignments.pdf JTAG pin assignments] document:<br />
<br />
''' ARM-14-JTAG TI-14-JTAG'''<br />
<br />
VREF 1 - - 2 GND JTAG_TMS 1 - - 2 JTAG_nTRST<br />
JTAG_nTRST 3 - - 4 GND JTAG_TDI 3 - - 4 GND<br />
JTAG_TDI 5 - - 6 GND VREF 5 - x 6 KEY (empty)<br />
JTAG_TMS 7 - - 8 GND JTAG_TDO 7 - - 8 GND<br />
JTAG_TCK 9 - - 10 GND JTAG_RTCK 9 - - 10 GND<br />
JTAG_TDO 11 - - 12 JTAG_SRST_N JTAG_TCK 11 - - 12 GND<br />
VREF 13 - - 14 GND JTAG_EMU0 13 - - 14 JTAG_EMU1<br />
FlySwatter TOP Beagle<br />
<br />
See [[media:flyswatter-ti-jtag.pdf|14 pin ARM to TI adapter]] for a verified JTAG adapter from [http://www.tincantools.com/ TinCanTools].<br />
<br />
* [http://tincantools.com/product.php?productid=16144 TinCanTools BeagleBoard Adapter Kit]<br />
* Nishanth Menon's [http://www.flickr.com/photos/nishanthmenon/2814595201/in/pool-beagleboard adapter] with explanation and [http://nishanthmenon.blogspot.com/2008/08/low-cost-jtag-for-beagle.html Nishanth's blog]<br />
* Lauterbach [http://www.lauterbach.com/frames.html?ord__7748.html JTAG converter to TI Target Adapter 14] (LA-7748) ([[media:Jtag-ti-front.jpg|front]] & [[media:Jtag-ti-back.jpg|back]])<br />
* [http://www.flickr.com/photos/51025379@N00/2822556950/in/photostream/ xdaiabx adapter]<br />
<br />
= Open source JTAG software= <br />
It would be very interesting to get the JTAG working with open source tools. The main open source JTAG software is [http://openocd.berlios.de/web/ OpenOCD]. See [[BeagleBoardOpenOCD|Beagle board OpenOCD page]] about status and usage of OpenOCD for Beagle.<br />
<br />
=JTAG hardware=<br />
<br />
For BeagleBoard JTAG debugging, there are some HW interfaces available. Several can be found on the [http://focus.ti.com/dsp/docs/dspfindtoolswresults.tsp?sectionId=3&tabId=1620&familyId=1526&toolTypeId=12&go=Go TI tools directory].<br />
<br />
==TinCanTools Flyswatter==<br />
<br />
[http://www.tincantools.com/ TinCanTools] is currently working at [http://www.tincantools.com/product.php?productid=16134&cat=0&page=1&featured Flyswatter] support for OpenOCD for OMAP3530. They also have a [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit].<br />
<br />
Costs:<br />
<br />
In case you like to order Flyswatter and Adapter Kit international, here an example for Europe (Germany):<br />
<br />
* Flyswatter: US-$ 49.95<br />
* BeagleBoard Adapter Kit: US-$ 18.00<br />
* International shipping: US-$ 27.00 (select USPS, it's the cheapest!)<br />
<br />
Sum: US-$ 94.95 => EUR 65.28 + EUR 8.76 VAT (Germany) = EUR 74.04<br />
<br />
Flyswatter can be used with [[BeagleBoardJTAG#Open_source_JTAG_software|OpenOCD]] (Beagle (OMAP3xx) support under development).<br />
<br />
'''Attention''': If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit], make sure you plug the JTAG adapter the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way (in contrast to the picture EMU0 & EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2)).<br />
<br />
==BDI 2000==<br />
<br />
===Example===<br />
<br />
[http://groups.google.com/group/beagleboard/msg/8463086de562ee00 Chuck Fleming] reports:<br />
<br />
The BDI2000 appears to work with the omap35xx.cfg and regOMAP3500.def files that come with the BDI hardware. I had to modify the 10-pin cable so that the BeagleBoard JTAG header matched the BDI target A connector:<br />
<br />
beagle>reset<br />
- TARGET: processing reset request<br />
- TARGET: BDI executes scan chain init string<br />
- TARGET: Bypass check 0x00000001 => 0x00000002<br />
- TARGET: JTAG exists check passed<br />
- Core#0: ID code is 0x0B6D602F<br />
- Core#0: DP-CSW is 0xF0000000<br />
- Core#0: DBG-AP at 0xD4011000<br />
- Core#0: DIDR is 0x15141012<br />
- TARGET: BDI removes RESET<br />
- TARGET: BDI waits for RESET inactive<br />
- TARGET: Reset sequence passed<br />
- TARGET: resetting target passed<br />
- TARGET: processing target startup ....<br />
- TARGET: processing target startup passed<br />
beagle>halt<br />
Core number : 0<br />
Core state : debug mode (ARM)<br />
Debug entry cause : Debug Request<br />
Current PC : 0x40200000<br />
Current CPSR : 0x000001d3 (Supervisor)<br />
beagle>rdall<br />
User FIQ Superv Abort IRQ Undef<br />
GPR00: 480029fc 480029fc 480029fc 480029fc 480029fc 480029fc<br />
GPR01: 00000000 00000000 00000000 00000000 00000000 00000000<br />
GPR02: 00000001 00000001 00000001 00000001 00000001 00000001<br />
GPR03: 00000060 00000060 00000060 00000060 00000060 00000060<br />
GPR04: 00000000 00000000 00000000 00000000 00000000 00000000<br />
GPR05: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4<br />
GPR06: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4<br />
GPR07: 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88<br />
GPR08: 80e3ffdc 34484608 80e3ffdc 80e3ffdc 80e3ffdc 80e3ffdc<br />
GPR09: 80e3fec8 26a1c132 80e3fec8 80e3fec8 80e3fec8 80e3fec8<br />
GPR10: 00000018 08040f16 00000018 00000018 00000018 00000018<br />
GPR11: 80e3fecc 3c278260 80e3fecc 80e3fecc 80e3fecc 80e3fecc<br />
GPR12: 0000006e 24200625 0000006e 0000006e 0000006e 0000006e<br />
GPR13: 00000000 00000000 80e3feb0 00000000 00000000 d1868045<br />
GPR14: 00000000 00000000 80e84f44 00000000 00000000 d55a4cc8<br />
PC : 40200000<br />
CPSR : 000001d3<br />
SPSR : 00000000 00000000 00000000 00000000 00000000<br />
beagle>md 0x40200000<br />
40200000 : e320f000 e320f000 e320f000 e320f000 .. ... ... ... .<br />
40200010 : e320f000 e320f000 e320f000 eafffffc .. ... ... .....<br />
40200020 : b6273502 e7aa052b 047694c8 91ca77d8 .5'.+.....v..w..<br />
40200030 : 12b9579e ef2eef1b 00543892 494f9bc1 .W.......8T...OI<br />
40200040 : 3f63013d 82eee656 b7adfe8d 993f1368 =.c?V.......h.?.<br />
40200050 : 51f1cf9b 0464a23e bea76e3c 3d275f5c ...Q>.d.<n..\_'=<br />
40200060 : 76554290 6776c892 a6cd088f 6dd4529a .BUv..vg.....R.m<br />
40200070 : 067261b8 e5f80e9e cb4ea075 25a9dd95 .ar.....u.N....%<br />
40200080 : 779db8c6 0496597b 7d5f8d5a 24f44cd6 ...w{Y..Z._}.L.$<br />
40200090 : 99ab46f9 9ddc06d9 fd34567a 2035bab8 .F......zV4...5<br />
402000a0 : a16b6760 fe863cf7 29046202 39fb0d49 `gk..<...b.)I..9<br />
402000b0 : dc9fd18c e50f536c 09ae66dd cad9ff91 ....lS...f......<br />
402000c0 : c46bdbdb be791808 89ff83fa 2d3bc71e ..k...y.......;-<br />
402000d0 : 43f5a3b6 0aed1747 ba3c4752 6af0573a ...CG...RG<.:W.j<br />
402000e0 : 3570da77 9a1dc961 324b876c 5d592060 w.p5a...l.K2` Y]<br />
402000f0 : b870f487 1277c035 4609dcf4 53b534c4 ..p.5.w....F.4.S<br />
beagle>ti<br />
Core number : 0<br />
Core state : debug mode (ARM)<br />
Debug entry cause : Single Step<br />
Current PC : 0x40200004<br />
Current CPSR : 0x000001d3 (Supervisor)<br />
beagle>ti<br />
Core number : 0<br />
Core state : debug mode (ARM)<br />
Debug entry cause : Single Step<br />
Current PC : 0x40200008<br />
Current CPSR : 0x000001d3 (Supervisor)<br />
beagle><br />
<br />
===BDI config===<br />
<br />
The [ftp://78.31.64.234/bdigdb/config/arm/cortex-a8/ BDI config files] might help getting OpenOCD to work with BeagleBoard.<br />
<br />
This configuration assumes the "default" EMU 0 and 1 configuration (both not connected/high state). In this EM setup at first only one TAP is exported. A set of commands must be run on the first tap (embedded ICE) <br />
to enable access to the core:<br />
<br />
SCANINIT t1:w1000:t0:w1000: ;toggle TRST,<br />
SCANINIT ch10:w1000: ;clock TCK with TMS high and wait<br />
SCANINIT i6=07:d8=89:i6=02: ;connect and select router<br />
SCANINIT d32=81000080: ;IP control: KeepPowered<br />
SCANINIT d32=a3002048: ;TAP3: DebugConnect, ForcePower, ForceActive<br />
SCANINIT d32=81000081: ;IP control: KeepPowered, SysReset<br />
SCANINIT d32=a3002148: ;enable TAP3<br />
SCANINIT cl10:i10=ffff ;clock 10 times in RTI, scan bypass<br />
<br />
==Lauterbach==<br />
<br />
Lauterbach Debugger supports [http://www.lauterbach.com/news_288.html OMAP3503/15/25/30].<br />
<br />
==XDS100, XDS510, USB560 and CCSV4==<br />
<br />
XDS510, BlackHawk USB560 and CCSV4 (code composer studio) can be used to debug OMAP3503/15/25/30. For CCS setup see [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf TI OMAP JTAG presentation], too (start page: 16).<br />
<br />
<H2> BeagleBoard Linux Kernel Aware Debugging using CCSV4 </H2><br />
Linux Aware debugging using CCSV4 is described in [http://tiexpressdsp.com/index.php?title=Linux_Aware_Debug CCSV4 Linux Aware Debugging]. CCSV4 is available for download from [http://tiexpressdsp.com/index.php/Category:Code_Composer_Studio_v4 CCSV4].<br />
<br />
<H3> CCSV4 Current Status </H3><br />
* CCSV4 is a Windows based application, which means that Linux Kernel Code compiled an a Linux machine must be shared using NFS for SAMBA.<br />
* Although CCSV4 is based on Eclipse, it will not work on Linux as there are currently no Linux Drivers for the JTAG Emulators. TI are developing Linux Drivers, but have not disclosed a release date<br />
* CCSV4 is based on Eclipse V3.1.0, which means that many of the features added through Eclipse based V3.4.2 are missing<br />
* TI are updating CCSV4 to use Eclipse V3.4.2, but have not disclosed a release date<br />
* When TI release CCSV4 using Eclipse V3.4.2, I expect TI to release a CCSV4 plugin for Code Sourcery<br />
* TI have produced a very good debugger, but there are still several bugs that TI are actively working to resolve and should be released in an update shortly. Most of these bugs are not show stoppers, but merely operational annoyances. <br />
* Blackhawk have released a $99 [http://www.blackhawk-dsp.com/products/usb100.aspx USB100], which is compatible with CCSV4. Please refer to [http://www.tiexpressdsp.com/index.php/XDS100 XDS100] about compatibility. Update: While CCSV4 does support XDB100, XDS100 does not yet support CortexA8 or C64X+. So, 4.02 (due in 11/09) will have XDS100 beagleboard support.<br />
<br />
==PEEDI==<br />
<br />
[http://www.ronetix.at/peedi.html PEEDI] JTAG/BDM Emulator and Flash Programmer of [http://www.ronetix.at Ronetix] supports OMAP3. A configuration file for the Beagleboard can be found here: [http://download.ronetix.info/peedi/cfg_examples/cortex-a8/omap3530.cfg omap3530.cfg]<br />
<br />
PEEDI has a built-in support for GNU gbd based debuggers and a built-in Flash Programmer.<br />
The Flash Programmer is capable to program:<br />
* NOR Flash devices (over 900)<br />
* NAND and OneNAND Flash devices (small page, larger page, 8/16 bit), various methods of ECC calculation, bad block management.<br />
* DataFlash devices<br />
* SPI DataFlash devices<br />
* images located on a TFTP/FTP/HTTP server or a MMC/SD card (which allows standalone mode).<br />
<br />
The PEEDI package includes also an PEEDI to TI14 adapter and an TI20 to TI14 adapter.<br />
<br />
<H2> Linux Kernel Aware Debugging using PEEDI Emulator </H2><br />
* For Linux Aware debugging, PEEDI is a great solution. Here is what you will need:<br />
* PEEDI JTAG emulator<br />
* Firmware version 9.8.216 or later<br />
* Arm Insight Debugger available on the Ronetix CDROM<br />
<br />
<I>Note: Enter all commands executed from the Linux Kernel build folder.</I><br />
<br />
<H4> Stopping the Debugger at start_kernel </H4><br />
* In OMAP3530.CFG, change the hardware breakpoint address in the [INIT_LINUX] section to the address of start_kernel<br />
* To obtain the address of start_kernel, use "nm vmlinux |grep -w start_kernel"<br />
* If your u-boot counts down from 10, you will need to extend the debugger timeout<br />
* Two lines down, change the line to "wait 25000 stop"<br />
* Power up the BeagleBoard and PEEDI<br />
* Let u-boot countdown and load the Linux Kernel<br />
* PEEDI will stop at "start_kernel"<br />
<H4> Launching the Insight Debugger </H4><br />
* Install the ARM Insight Debbugger from the Ronetix CDROM, which is normally installed in the /opt folder<br />
* From the Linux Kernel build folder type "/opt/arm-linux-4.3.3/bin/arm-linux-insight vmlinux &"<br />
* In the Console Window, type "target remote <xxx.xxx.xxx.xxx>:2000, where <xxx.xxx.xxx.xxx> is the BeagleBoard IP address<br />
* Next, type "ni". The Source Window will load /init/main.c and highlight a line in start_kernel<br />
* Step through the code, or enter breakpoints and run the program. <br />
<br />
<H4> Thread List </H4><br />
* If you are doing multi-threaded debugging, this feature is invaluable<br />
* The PEEDI config file (OMAP3530.CFG) must be setup to read this info from your kernel<br />
* The information needed by Insight GDB is in the [OS_ARM_LINUX_v26] section<br />
* This information is obtained from the Insight GDB Console Window<br />
* print &init_task ; BASE<br />
* print &((struct task_struct*)0)->tasks.next ; NEXT<br />
* print &((struct task_struct*)0)->pid ; PID<br />
* print &((struct task_struct*)0)->comm ; NAME<br />
* print &((struct task_struct*)0)->stack ; second CONTEXT arg<br />
* print &((struct thread_info*)0)->cpu_context ; third CONTEXT arg<br />
<br />
For Linux Kernel v2.6.29, this section looks something like this:<br />
* BASE = 4, 0xC066B110<br />
* NEXT = 4, -0x1B8<br />
* PID = 4, 0x1E4<br />
* NAME = 16, 0x2DB<br />
* CONTEXT = 10*4, 0x4, 0x1C<br />
<br />
Note: the BASE address will most definitely be different to the one provided here, but the other values should be similar.<br />
<br />
Ronetix technical support is excellent and they added features like the Thread List in just over a week. When I reported what seemed like a bug, they fixed most of them in just a few days. Overall, I am very impressed with the PEEDI emulator and it works great with the BeagleBoard. PEEDI is certainly the most responsive emulator I have worked with and what I like most is it is one of the few that works natively within Linux.<br />
<br />
==ARM RealView ICE==<br />
<br />
The new release of software (3.3) for the [http://www.bluewatersys.com/blog/?p=71 ARM RealView ICE] supports Texas Instruments’ range of OMAP3 processors. All you could buy RealviewICE at [http://www.realviewice.com]<br />
<br />
=Linux kernel debugging=<br />
<br />
If you like to debug Linux kernel (with one of the above JTAG tools?) using GDB have a look to [[DebuggingTheLinuxKernelUsingGdb|debugging Linux kernel using GDB]] article.</div>Som2416https://elinux.org/index.php?title=Computer-on-Module&diff=18893Computer-on-Module2010-03-30T12:45:47Z<p>Som2416: /* Computer-on-Module Provider */</p>
<hr />
<div>A computer-on-module (COM) is a type of [http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Single-Board-Computer-SBC-Quick-Reference-Guide/ single-board computer](SBC), a subtype of an embedded computer system. It is also called [http://www.emacinc.com/som/som_select_guide.htm System on Module]System-on-Module as an extension of the concept of System on Chip (SoC) and lying between a full-up computer and a microcontroller in nature.<br />
<br />
Today's COM/SOM modules are complete computers built on a single circuit board. The design is centered on a single microprocessor with RAM, input/output controllers and all other features needed to be a functional computer on the one board. However, unlike a single-board computer, the COM module will usually lack the standard connectors for any input/output peripherals to be attached directly to the board. Instead, the wiring for these peripherals are bussed out to connectors on the board.<br />
<br />
The module will usually need to be mounted on a carrier board (or "baseboard") which breaks the bus out to standard peripheral connectors. Some COMs also include peripheral connectors and/or can be used without a carrier.<br />
<br />
A COM/SOM solution offers a dense package computer system for use in small or specialized applications requiring low power consumption or small physical size as is needed in embedded systems.<br />
<br />
Some devices also incorporate Field Programmable Gate Arrays.<br />
<br />
The terms "Computer-on-Module" and "COM" were coined by Venture Development Corporation (Natick, MA, USA) to describe this class of embedded computer boards. The term became more notable upon industry standardization of the COM Express format.<br />
<br />
A number of manufacturers offer products which are defined as system-on-module or computer-on-module. Among those are Advanced Knowledge Associates (www.a-k-a.net) in Santa Clara, CA; BCM Advanced Research (www.bcmcom.com) in Irvine, CA; Embedded Systems (www.embedded-systems.net); MEN Micro (www.menmicro.com) in Ambler, PA; DAVE Embedded Systems (www.dave.eu) in Italy.<br />
<br />
== Computer-on-Module Provider ==<br />
* [[SOM]] - by [http://www.techor.com/ TECHOR.COM of China], series of 40x40x4mm Size, Weight about 10g, the smallest and lightest [[System-on-Module]] in the World!<br />
* [[SOM2416]] - by [http://www.techor.com/product-281.html TECHOR.COM of China], Samsung 400MHz ARM926EJ-S based cost effective Application Processor<br />
* [[SOM6410]] - by [http://www.techor.com/product-282.html TECHOR.COM of China],Samsung 667Hz ARM1176JFZ-S based cost effective Application Processor<br />
* [[SOM3530]] - by [http://www.techor.com/product-283.html TECHOR.COM of China], TI 720MHz CORETEX-A8 + 600MHz TMS320DM64x+ dual core SOC<br />
* '''CSB7xx''' - by [http://www.cogcomp.com Cogent Computer Systems, Inc. of USA]<br />
* '''CM-XXX''' - by [http://www.compulab.co.il CompuLab of Italia]<br />
* '''Colibri Computer Modules''' - by [http://www.toradex.com Toradex of Switzerland]<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=SOMX35&diff=18892SOMX352010-03-30T12:43:45Z<p>Som2416: </p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOMX35&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.freescale.com Freescale semiconductor's] [http://www.arm.com/products/CPUs/ ARM1136] based up-to 667MHz [http://www.freescale.com/webapp/sps/site/overview.jsp?code=IMX35_FAMILY MX35] Application Processors engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product-284.html '''SOMX35'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
=Events=<br />
<I><br />
'''2010.2.1''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product-284.html SOMX35] '''Rev PRELIMINARY''' released in Feb 1, 2010! '''SOMX35''' is SODIMM-244 pin System-on-Module, suitable for highend control, Automotive, Automobile etc.<br />
[[File:MX357-640X480-mark.JPG|SOMX35picture]]<br />
</I><br />
=Brief=<br />
Freescale i.MX357/356, 533MHz ARM11 核心<br />
<br />
128MB/256MB 32-bit DDR2,266MHz时钟<br />
<br />
第二路16-bit扩展总线(local bus for extension) <br />
<br />
512MB/1G/2G/4G SLC/MLC NAND <br />
<br />
2路高性能高速CAN BUS总线<br />
<br />
100Mbps Ethernet高性能以太网接口 <br />
<br />
2路高速UART (每路最高可达4Mbps) <br />
<br />
2路高速SPI (每路最高可达52Mbps) <br />
<br />
真正高速USB 2.0 HOST和OTG(可当HOST或Device来用) <br />
<br />
多协议高速外部存储卡接口,兼容:SD2.0/SDIO2.0/MMC4.2/SDHC<br />
<br />
支持16bit~24bit TFT LCD,典型分辨率1024x768,支持各种尺寸屏<br />
<br />
板载立体声功放,可直接输出2W驱动喇叭<br />
<br />
宽电压输入: 5V~60V DC<br />
<br />
240pin+24pin引出线,引出全部资源接口!<br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOMX35 Revision ==<br />
==SOMX35-based products ==<br />
==SOMX35 ODM cases ==<br />
=5 App Demo Board =<br />
=6 Adapters =<br />
== Expansion boards ==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=BeagleBoard_Community&diff=18546BeagleBoard Community2010-03-19T04:57:12Z<p>Som2416: /* Clones */</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
This page collects information about [http://www.ti.com/ TI's] [http://www.arm.com/ ARM] based [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&amp;DCMP=OMAP_Feb27_2008&amp;HQS=Other+PR+omap3503pr OMAP3] [http://beagleboard.org Beagle Board].<br />
<br />
<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#ffffcc; align:right; "><br />
'''NEWS:''' [[BeagleBoard_Zippy2|Zippy2]] 100baseT Expansion boards for the [[BeagleBoard]] are now available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?vendor=0&keywords=zippy2 Digikey]!</div><br />
<br />
<br />
=Events=<br />
* Meet BeagleBoard at TI booth in June, 9-12th @ Linux Tag, Berlin, Germany, http://www.linuxtag.org/2010/<br />
* See TI BeagleBoard demo @ Embedded World, Nuremberg, Germany, March 2-4, 2010, Hall 11. booth 308<br />
* Each last Saturday of the month, next August 29, 2009: [[BeagleBoard/bangalore user meet|BeagleBoard Bangalore user meeting]] (Beagle Clinic India)<br />
* all over the world 2009: [http://www.ti.com/corp/docs/landing/techday09/index.shtml# TI Technology Days 2009]. <br />
* ongoing 2009: [[BeagleBoard/contest|Beagle Sponsored Project Program]] - add a cool project and get a free BeagleBoard to realize it!<br />
<br />
=Hardware=<br />
<br />
The Beagle Board is ''a low-cost, fan-less single-board computer based on TI's OMAP3 device family, with all of the expandability of today's desktop machines, but without the bulk, expense, or noise'' (from [http://beagleboard.org/ beagleboard.org]). It uses a TI [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor (ARM Cortex-A8 superscalar core ~600MHz paired with a TMS320C64x+ DSP ~430MHz and an Imagination SGX 2D/3D graphics processor). See [http://focus.ti.com/docs/prod/folders/print/omap3530.html#features OMAP3530 features] for more processor features. [[BeagleBoard#Availability|Price is USD 149]]. The design goal was to make it as simple and cheap as possible, e.g. not having a LCD added, but letting you connect all add-ons available as cheap external components. See [http://beagleboard.org/brief What is Beagle?] and [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article] for more details.<br />
<br />
The videos [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings] and [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu] give you a good intro about what BeagleBoard is about and its capabilities.<br />
<br />
==Components==<br />
<br />
{|border=0<br />
!Top view of rev B:<br />
!Top view of rev C:<br />
|-<br />
|[[Image:Bb revb top numbered.jpg]]<br />
|[[Image:Bb revc top numbered.jpg]]<br />
|-<br />
|}<br />
{|border=1<br />
!No.<br />
!Name<br />
!Comment<br />
|-<br />
|'''1'''<br />
|[http://www.ti.com/omap35x OMAP3530] processor + 256MB NAND<br />
<br />
+ 128MB DDR (rev B)<br />
<br />
+ 256MB DDR (rev C)<br />
|PoP: Package-On-Package implementation for Memory Stacking<br />
[http://www.micron.com/products/partdetail?part=MT29C2G24MAKLAJG-6%20IT 256MB NAND/128MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1435-ND DigiKey]<br />
<br />
([http://www.micron.com/products/partdetail?part=MT29C4G48MAPLCJI-6%20IT 512MB NAND/256MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1436-ND DigiKey])<br />
<br />
[http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for Beagle Board]<br />
|-<br />
|'''2'''<br />
|[http://focus.ti.com/docs/prod/folders/print/tfp410.html DVI chip (TFP410)]<br />
|<br />
|-<br />
|'''3'''<br />
|[[BeagleBoard#DVI|DVI-D]]<br />
|Connection via HDMI connector<br />
|-<br />
|'''4'''<br />
|[[BeagleBoard#JTAG|14-pin JTAG]]<br />
|1.8V only!<br />
|-<br />
|'''5'''<br />
|Expansion connector: I2C, I2S, SPI, MMC/SD<br />
|User must solder desired header into place<br />
|-<br />
|'''6'''<br />
|[[BeagleBoard#User_button|User button]] <br />
|Allows setting boot order.<br />
|-<br />
|'''7'''<br />
| Reset button<br />
|<br />
|-<br />
| '''8'''<br />
|[[BeagleBoard#EHCI|USB 2.0 EHCI HS]]<br />
|Rev A and B: not working, unpopulated<br />
<br />
Rev C: populated and working<br />
|-<br />
|'''9'''<br />
|SD/MMC+<br />
| SDHC cards are supported<br />
|-<br />
|'''10'''<br />
|[[BeagleBoard#RS232|RS-232 serial]]<br />
|<br />
|-<br />
|'''11'''<br />
|Alternate power <br />
|normally powered by USB (unmounted on REV Ax boards, see [[BeagleBoard#Errata|errata]])<br />
|-<br />
|'''12'''<br />
|[[BeagleBoard#OTG|USB 2.0 HS OTG]] <br />
|Mini-AB connector. Board can be powered from port. <br />
|-<br />
|'''13'''<br />
|Stereo In<br />
|<br />
|-<br />
|'''14'''<br />
|Stereo Out<br />
|<br />
|-<br />
|'''15'''<br />
|S-Video<br />
|<br />
|-<br />
|'''16'''<br />
|TWL4030 (Rev A thru C2 inc.)<br />
[http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] (Rev C3 onwards)<br />
|Audio CODEC, USB port, power-on reset and power management. The TWL4030 is pin-compatible with the [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] chip and was used due to the very limited availability of the TPS65950 in early board revisions.<br />
|-<br />
|'''17'''<br />
|LCD<br />
|only rev C<br />
|-<br />
|'''18'''<br />
|USB power<br />
|<br />
|-<br />
|'''19'''<br />
|Host PHY<br />
|<br />
|-<br />
|'''20'''<br />
|32kHz<br />
|<br />
|-<br />
|'''21'''<br />
|12MHz<br />
|<br />
|-<br />
|'''22'''<br />
|RS232 XVCR<br />
|<br />
|-<br />
|'''23'''<br />
|PWR SW<br />
|<br />
|-<br />
|'''24'''<br />
|VBAT<br />
|<br />
|-<br />
|}<br />
<br />
* Board size: 3" x 3" (about 76.2 x 76.2 mm)<br />
* Weight: [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/beagleboard.png ~37g]<br />
* Currently 6 layer PCB; target: 4 layer<br />
<br />
'''Bottom of rev B:'''<br />
<br />
[[Image:Beagle_bottom.jpg]]<br />
<br />
See [http://www.flickr.com/photos/jadon/sets/72157606050144396/ jadonk's photostream] for some more detailed BeagleBoard pictures.<br />
<br />
==Manual==<br />
<br />
See [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)].<br />
<br />
==Schematic==<br />
<br />
Schematic of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous are also available from [http://beagleboard.org/hardware/design BeagleBoard.org design page] including in PDF format. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.<br />
<br />
==Layout== <br />
<br />
Layout of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous layouts are also available from the [http://beagleboard.org/hardware/design BeagleBoard.org design page]. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.<br />
<br />
==Errata==<br />
<br />
# ''Boards revision A only'': The DC power jack pinout is incorrect on the PCB layout. DC_5V and GND are switched on PCB layout. Normally, the power jack has DC_5V on the center pin and GND on the sleeve (see Figure 20 of [http://www.beagleboard.org/uploads/BBSRM_6.pdf Beagle HW manual]). But on revision Ax boards the PCB layout has GND on center and DC_5V on sleeve. For this reason it is currently removed. It will be back on the Rev B board. Workaround is to remove wire connecting the two power pins on revision Ax boards and use external [http://amethyst.openembedded.net/~koen/beagleboard/beagle-power-pads.jpg power supply with switched connector] (do not connect anything to the “?” terminal. USB power will be permanently disabled and the board can only be powered from the 5V.) See [http://www.flickr.com/photos/koenkooi/2512038988/ Koen's Beagleboard powermod picture] with short descriptions, too.<br />
# ''Boards revision < A5 only'': There is excess voltage drop across R6 which is used to measure the current consumption on the board. This needs to be a .1 ohm instead of a 1 ohm resistor (SMD 0805). All revision A5 boards have been updated to .1. You can also just solder in a jumper to J2 bypassing the current read point. This issue can cause issues with the USB host port as the voltage supplied to that port can be too low.<br />
# ''Boards revision A only'': User LEDs 0 and 1 are shorted on the layout preventing them from being controlled individually. You need to control both GPIO_149 and GPIO_150 to turn on or off both LEDs. This is fixed in the Rev B boards.<br />
# ''Boards revision < A5 only'': There is an issue where on some boards the 1.8V has excessive noise on it. This is the result of two incorrect parts L1 and L3 being installed on the board. The inductors that were initially installed in the switchers are 100uH and need to be 1uH. This change will require that the board be returned for update. To check for correct parts, have a look to bottom of BeagleBoard. L1 - L3 are the larger parts there. They all have to be labeled with "102" (== 1uH). If any of these three inductors are labeled with "104" (== 100uH) they are wrong and have to be exchanged.<br />
# ''Boards revision A and B'': USB HOST (EHCI) failures. See [http://code.google.com/p/beagleboard/issues/detail?id=15 issue 15] and [http://code.google.com/p/beagleboard/wiki/USBHostTestREPRODUCE USB host test reproduce]. This is a hardware defect. [http://www.beagleboard.org/irclogs/index.php?date=2008-05-29#T00:27:06 Most probably] Rev. B board does not have the EHCI USB connector mounted. Workaround: Use [[BeagleBoard#OTG|OTG port]] with something like [http://trisoft.de/pics/ZHost.JPG mini A to USB A adapter] instead.<br />
# ''Boards revision A and < B4'': Plugging in a USB OTG cable will prevent Beagle from booting (with git kernel), see [http://code.google.com/p/beagleboard/issues/detail?id=19 issue #19], too. This is due to missing filtering capacitor at USB OTG VBUS. When the kernel driver detects that a USB OTG cable is inserted it enables the charge pump to generate VBUS. With no filtering VBUS looks like any switching regulator output with no filtering -- a huge voltage spike when the switch is on, followed by a rapid decay to a low voltage until the next switch on period. The capacitor is there to store energy between the output switch ON and OFF time, the feedback loop in the regulator does sample the cap voltage. Fix is to piggy-back solder a 0603 2.2uF ceramic capacitor to D3, see [http://www.sakoman.net/omap3/beagle/vbus-mod-d3.jpg VBUS modification D3 picture]. Revision B4 boards and newer have this fix applied. Thanks to [http://groups.google.com/group/beagleboard/msg/eb789e15c99a673d Steve] for debugging this!<br />
# ''Boards revision A and < B5'': There is some issue with 32kHz clock depending on system configuration used to clock some OMAP3 peripherals. From this e.g. GPIOs, GPTIMERs, and USB on Beagle might be affected. See [http://code.google.com/p/beagleboard/issues/detail?id=22 Issue 22]. Symptom from this is that after booting Linux kernel serial console hangs after some time and no serial input/output is possible any more. There is one software workaround and one hardware fix for this: (A) Software workaround: Don't use 32kHz timer to clock Linux, instead use MPU timer. (B) Hardware workaround: Remove [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard capacitor C70], which improves the 32kHz clock quality and avoids hang-up. Note: Revision A boards have capacitor C70 [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard at the same location] as rev. B boards. Note: Board revision >= B5 removes capacitor C70.<br />
# ''Random boards, quite rare, revision < B6'': Some random boards and quite rare, show directly after purchasing broken serial communication from host PC to BeagleBoard. Symptom is that you get a new board, get serial output from BeagleBoard in terminal program, but can't type anything at U-Boot prompt (Note: Don't mix this with errata #7. With errata #7 you are able to use U-Boot normally, but Linux prompt input stops after some time). Most users don't have this issue, though. So, first double check your serial configuration ([[BeagleBoardFAQ#Serial_connection_.231|FAQ1]], [[BeagleBoardFAQ#Serial_connection_.232|FAQ2]] and [[BeagleBoardFAQ#Serial_connection_.233|FAQ3]]). Only if you are really, really sure that anything with your serial connection is fine, consider sending the board back doing a [http://beagleboard.org/support/rma RMA request]. This issue was resolved on revision B6 and later boards.<br />
<br />
For additional (software) issues and enhancement requests see [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker], too.<br />
<br />
Note: BeagleBoard revision B6 uses different package for U9/U11.<br />
<br />
==Clocking==<br />
<br />
Some [http://www.beagleboard.org/irclogs/index.php?date=2008-07-08#T21:12:23 notes] about (ARM processor) clock rates at BeagleBoard:<br />
<br />
* ARM Cortex-A8 processor is currently clocked at 500MHz<br />
* 500MHz is the default used because it is a balance of performance and longevity<br />
* For OMAP35x 600MHz is max recommended<br />
* An additional 720MHz overdrive is supported only on high-speed grade OMAP3530/25 devices as fitted to the Beagleboard C4<br />
* At 600MHz or higher OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy<br />
* Higher than 600/720MHz is out of spec and no guarantee it will work at all (or not damage itself)<br />
<br />
* Also keep in mind that if you go higher you probably want to increase the core voltage. Some of this is mentioned in tables 3-3, 4-15 and 4-16 of the [http://focus.ti.com/lit/ds/symlink/omap3530.pdf OMAP3530 data sheet]. Some numbers:<br />
<br />
{| border="1"<br />
||'''ARM'''||'''DSP'''||'''core voltage'''<br />
|-<br />
|720 MHz||520 MHz||1.35V<br />
|-<br />
|600 MHz||430 MHz||1.35V<br />
|-<br />
|550 MHz||400 MHz||1.27V<br />
|-<br />
|500 MHz||360 MHz||1.2V<br />
|}<br />
<br />
* For some OMAP3 clock, voltage and power management discussion see [http://focus.ti.com/lit/an/sprt495/sprt495.pdf OMAP3 power management white paper], too.<br />
* The OMAP3 chip on the Beagle lacks the efuses needed for using the SmartReflex technology, see [http://www.beagleboard.org/irclogs/index.php?date=2009-02-26#T10:44:24].<br />
* There is a thermal monitor in the core, you could use to scale frequency up and down<br />
<br />
To set CPU clock to 600 MHz, there are two options. Both '''do not''' adjust the voltage, so the system may become unstable:<br />
<br />
* The u-boot command "mw 48004940 0012580c" will temporarily set the CPU clock to 600 MHz (not permanent over reset).<br />
* To permanently set the CPU clock to 600 MHz, include the above command in the "bootcmd" variable or equivalent script.<br />
<br />
* To set the DSP clock to 430 Mhz use "mw 48004040 0x0009ae0c".<br />
<br />
==Power management==<br />
<br />
* Detailed OMAP3 Power Management Information can be found [[OMAP_Power_Management|HERE]]<br />
* Latest Linux kernel power management development for TI OMAP SoCs is maintained in [http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git;a=summary Kevin's linux-omap-pm git tree]<br />
* Russ' Beagle HW modifications resulted in [http://groups.google.com/group/beagleboard/browse_thread/thread/197a8ef6b46cc828 8mW sleep for Beagle Board]<br />
<br />
Without PM kernel, the Beagle [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm consumes ~1.5 watts idle, however it also uses the same amount under load] (see bottom of that page).<br />
<br />
==DLP Pico projector==<br />
<br />
Texas Instruments is developing a Pico Video Projector Kit (PVPK) as a peripheral for the Beagle Board. The stand alone pico projector will support VGA resolution (640 x 480), RGB 888 input through a DVI interface. The physical connector on the projector will be HDMI. See [http://groups.google.com/group/beagleboard/msg/10e218972380ee48 mailing list] and [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector] for more details.<br />
<br />
It is available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23836-ND DigiKey] for $349.<br />
<br />
See [http://blog.makezine.com/archive/2009/01/tis_beagleboard_and_dlp_pico_projector.html?CMP=OTC-0D6B48984890 article from Make], too.<br />
<br />
DigiKey videos [http://www.youtube.com/watch?v=KBbCdnOj5vg part 1], [http://www.youtube.com/watch?v=zymOmduNWyI part 2] and [http://www.youtube.com/watch?v=Uj19Bi5NYeU part 3].<br />
<br />
==Interfacing to Raw LCD Panels==<br />
<br />
Currently on Rev A / B boards there is no direct access to the LCD lines before they enter the DVI framer. The REV C2 provides access to these lines. Several projects to interface an LCD to the beagleboard exist:<br />
<br />
* [[BeagleBoardRawLCD|interfacing to Raw LCD Panels]] article <br />
* [http://digitalsurveyinstruments.com/beagleperiphials/hdmi2parallel/doc/index.htm hdmi to parallel] workaround method<br />
* [http://www.harbaum.org/till/dvi2par/index.shtml dvi2par cheap diy HDMI to parallel converter]<br />
<br />
=Availability=<br />
<br />
BeagleBoards, currently Rev. C3 boards, are available from<br />
<br />
* [http://www.mouser.com/beagleboard Mouser]<br />
* [http://dkc1.digikey.com/us/mkt/beagleboard.html Digi-Key] with part number [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23428-ND 296-23428-ND].<br />
<br />
Note: For non-US Digi-Key free shipping orders:<br />
<br />
* Click the US flag on the top right corner of [http://dkc1.digikey.com/us/mkt/beagleboard.html Digi-Key] BeagleBoard page to come to the international page<br />
* Select ''Order Online'' for your country<br />
* Add quantity ''1'' and part number ''296-23428-ND''<br />
* Click ''Add to order''<br />
<br />
When ordering over 65 EUR / GBP 50 product (BeagleBoard is above), for Europe the price depends on the actual dollar to EUR/GBP rate. On nov 9, 2008 the price was EUR 124 with free shipping.<br />
<br />
Note: Some users report that they got some questions from DigiKey to be answered before board shipping is done.<br />
<br />
Note: While you get free shipping, most probably you have to pay tax e.g. ordering from Europe. Users report that they had to pay EUR ~34 - 44 VAT + importing taxes (depending on european country), resulting in EUR 137 - 147 ordering from Europe.<br />
<br />
Note: For European users, [http://www.ebv.com/fileadmin/products/Press_Print/Campaigns/2009/Product_Campaigns/Texas_Beagle_Board_englisch.pdf EBV Elektronik] sells its own blue version of the board for 179 EUR, which includes all useful accessories (DVI cable, serial cable, USB 2.0 Ethernet, USB hub, 2 GB MMC, power supply, Linux BSP).<br />
<br />
Note: German (Europe) users can order through German shops, too. For higher price, though. <br />
* [http://shop.embedded-projects.net/product_info.php/info/p159_BeagleBoard--OMAP-3-.html Embedded Projects Shop] sells BeagleBoard for EUR 199.00 + shipping.<br />
* [http://www.handheld-linux.com/wiki.php?page=Beagle%20Board Handheld-Linux]<br />
<br />
See below for ''hardware'' differences of the revisions. There are no ''software'' differences. <br />
<br />
==Revision A==<br />
<br />
There are some limited early revision Ax prototypes out there used by some hackers hanging around at #beagle channel on irc.freenode.net. See [[BeagleBoard#Errata|errata]] for limitations.<br />
<br />
==Revision B==<br />
<br />
Revision B is same as revision A, except<br />
* fix for shorted LEDs 0/1<br />
* fix for wrong power jack pinout<br />
* revision B6 uses different package for U9/U11<br />
Still has USB HOST (EHCI) failures. USB HOST (EHCI) connector isn't mounted.<br />
<br />
There are 4 revisions of the B board in the field: B4, B5, B6 and B7.<br />
<br />
The most notable difference is the use of the ES3.0 silicon in B6 and B7, other changes are not relevant to software developers.<br />
<br />
==Revision C2==<br />
Revision C2 is same as revision B7 except:<br />
* USB HOST (EHCI) is operational on revision C2, with standard USB A female connector.<br />
* Add interface for raw LCDs ([http://groups.google.com/group/beagleboard/msg/2e82c3ed6061d9d2 mockup])<br />
* It uses updated OMAP3 revision. BeagleBoard revisions B4+B5 uses OMAP3 ES 2.1 (engineering sample), while BeagleBoard revision C2 uses ES 3.0. OMAP3 ES 3.0 fixes minor issues:<br />
** updated ARM Cortex A8 silicon (r1p3) fixing a very rare [http://elinux.org/BeagleBoardFAQ#NEON_performance NEON issue] that has not been seen in real code<br />
* Power measurement feature<br />
* Uses [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] OMAP power controller instead of TWL4030<br />
* Three additional PWM signals on the expansion connector added as pin mux options to existing pins ([http://groups.google.com/group/beagleboard/browse_thread/thread/d5872b7c6d74592c?hl=en# message])<br />
* Revision detection (to be able to identify C2 board from older boards by software, e.g. for different pin mux)<br />
* 256MB RAM ([http://groups.google.com/group/beagleboard/msg/3a38d0f21cefd6b1?hl=en message]) (and still 256MB NAND like rev B)<br />
<br />
Note: Revision C2 is the first production version, and all orders from from Digi-Key are shipped as Rev C2.<br />
<br />
==Revision C3==<br />
As revision C2 boards are [http://groups.google.com/group/beagleboard/msg/e41d3c97aa7d4951 sold out], revision C3 will ship now.<br />
<br />
Revision C3 is same as revision C2 [http://groups.google.com/group/beagleboard/msg/037318fbc44139d5 except]:<br />
* Optional RTC [http://parts.digikey.com/1/parts/1454-battery-lith-coin-3v-12-5mm-vert-vl-1220-vcn.html VL1220 series] backup battery<br />
* Mounting holes conected to ground<br />
* Slightly improved S-Video<br />
<br />
==Revision C4==<br />
Revision C4 boards are the same as Revision C3 except:<br />
* Processor is 720MHz capable OMAP3<br />
* Improved USB Host PHY power rails<br />
<br />
==Clones==<br />
===EBVBeagle===<br />
EBV build and sell their own BeagleBoard called [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], see e.g. [http://fl0rian.wordpress.com/2009/03/08/the-other-beagleboard/].<br />
It is actually a BeagleBoard revision C2 with green PCB boxed with some useful accessories. It comes as a quite complete starter kit with AC adapter, USB to Ethernet adapter, MMC card, USB hub and some cables.<br />
More information in [http://www.ebv.com/en/press-print/news-pr/details/news//press-releas-54.html official press release].<br />
<br />
===Mini Board===<br />
[[Mini_Board|ICETEK-OMAP3530-Mini]] is a chinese BeagleBoard clone.<br />
<br />
===DevKit 8000===<br />
[[DevKit8000]] is a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard).<br />
<br />
===IGEPv2===<br />
[http://www.igep-platform.com/ IGEPv2 Platform] is a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, wifi+bluetooth.<br />
* 720MHz OMAP3 Processor<br />
* 512MB RAM / 512MB Flash<br />
===SOM3530===<br />
[[SOM3530]] is a chinese BeagleBoard clone [[System-on-Module]],Dimension 40x40x4mm, Maybe the smallest [[OMAP350]]-based modules in the world! Including 100M high perfomance ethernet I/F<br />
<br />
==BeagleBoard-based products==<br />
* [http://www.alwaysinnovating.com/touchbook/ Always Innovating Touch Book], see [http://gigglehd.com/zbxe/hdforum/files/attach/images/899852/493/987/001/always_innovating_touch_book_0011.jpg]<br />
<br />
==Beagle case==<br />
<br />
*[http://specialcomp.com/beagleboard/ Special Computing]<br />
*[http://groups.google.com/group/beagleboard/browse_thread/thread/1c82316019633e51 SketchUp 3D model]<br />
<br />
=Adapters=<br />
<br />
For quite detailed information about all BeagleBoard peripherals see [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)].<br />
<br />
See [[BeagleBoardPeripherals| BeagleBoard peripherals and adapters page]] for useful add ons for Beagle Board.<br />
<br />
==Expansion boards==<br />
* [[BeagleBoardPinMux|Expansion Board Support Information]]<br />
* [[BeagleBoard Zippy]] expansion board is now available from [http://www.tincantools.com/product.php?productid=16147&cat=0&page=1&featured TinCanTools] for $79.00. basic specs are:<br />
** Battery Backed RTC<br />
** Second MMC slot<br />
** 10BaseT Ethernet<br />
** Second RS-232<br />
** +5V level I2C<br />
** AT24 EEPROM<br />
* [https://sourceforge.net/apps/mediawiki/beagleserver/index.php?title=Main_Page BeagleServer expansion board] is an Open Hardware project. Currently a high level design note is available, which describes the components to be used. It aims at the following specifications :<br />
** Aims at transforming a Beagleboard or IGEPv2 into a full-blown home server that could cater to home automation needs<br />
** Compatible with both the Beagleboard and the IGEPv2<br />
** 12V battery powered, or mains-powered (accepts 9 ~ 18V)<br />
** Enough power for an internal 2.5" or 3.5" hard-disk, USB-attached<br />
** +3.3V and +5V I2C; +5V I2C is buffered with a line buffer accepting a larger capacitance which allows I2C devices at distances up to 50m<br />
** I2C to 1-wire hub (using DS2482-800 which is supported by OWFS); plugging in 1-wire devices lights a LED which makes it easy to confirm if a 1-wire device is detected.<br />
** Real time clock with super-capacitor backup<br />
** Internal monitoring of the HW health (power supplies + temperature)<br />
** Some relays<br />
** Ethernet-based console port<br />
** a few other options (RS232 interface with CTS and RTS, SPI port, S-video, additional SD-card)<br />
* [http://www.hy-research.com/beagle_expansion.html HY Research] has some expansion board basics and example.<br />
* [http://www.hervanta.com/stuff/Beaglebot#Expansion_Board Beaglebot] uses a custom extension board.<br />
* [http://beagleboard.org/leopard Leopard Board], a Beagle buddy web camera<br />
* There is also a VGA DB15 adapter board under development for the Rev C2 board. It should be available through a yet to be annnounced outlet.<br />
<br />
In Canada, check out [[http://robotcraft.ca RobotCraft]] in London, Ontario for expansion boards.<br />
<br />
==JTAG==<br />
<br />
Depending on your JTAG tool, you'd need a 14-pin to 20-pin adapter to use an ARM debugger. The 14-pin TI JTAG connector is used on BeagleBoard and is supported by a large number of JTAG emulation products.<br />
See [[BeagleBoardJTAG]] for more information.<br />
<br />
==RS232==<br />
<br />
The pinout on the beagle board is "AT/Everex" or "IDC10". You can buy [http://www.pccables.com/07120.htm IDC10 to DB9M adapters] in many places as they are commonly used for old PCs. Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available. You can also probably rip one of those cables out of any old desktop computer, where it's being used to support the serial port. Be careful, though -- some of those cables will have that tenth hole filled in so you'd have to snap off the extraneous pin on your BeagleBoard. Keep looking until you find a cable with all 10 holes open.<br />
<br />
Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available.<br />
<br />
==USB-to-Serial Converter==<br />
<br />
Since many systems no longer come with an actual serial port, you might need to pick up a USB-to-serial converter at your local computer store to connect to your BeagleBoard. Be warned that some of them simply do not work. Many of them are based on the Prolific chip, and require the pl2303 module to be loaded. But even when two converters appear to have exactly the same characteristics as listed in /var/log/messages, if you simply can't get one to work, be ready to try a different one.<br />
<br />
==USB==<br />
There are two USB ports on the BeagleBoard, one with an EHCI controller and another with an OTG controller. As of Rev B4, the usb EHCI has been removed because of a hardware defect. Rev C will include USB EHCI working properly.<br />
<br />
===EHCI===<br />
The HS ([http://en.wikipedia.org/wiki/USB#USB_signalling HighSpeed]) USB [http://en.wikipedia.org/wiki/EHCI ECHI] controller on OMAP3 on BeagleBoard supports high-speed only. This simplifies the logic on the device. FS/LS (FullSpeed/LowSpeed) devices, such as keyboards and mice, require going through a high-speed USB 2.0 hub.<br />
<br />
According to the BeagleBoard System Reference Manual Rev C2, the EHCI port can source 5V at 500mA which is enough to power a hub and several low-power devices. However, this is only true if the BeagleBoard is powered through its power jack from a well-regulated 5V external power supply. If the BeagleBoard is powered through the OTG port, the EHCI port sources an "extremely limited" ampount of power (probably 100mA or so) so you'll need a "self-powered" USB 2.0 hub with its own external power supply. [Reference: Sections 5.6 and 7.2 of the BBSRM Rev C2.2.]<br />
<br />
'''Hardware issue on rev C3''' - the EHCI port on some rev C3 boards is unstable and will disconnect hubs/devices. Symptoms are: devices are disconnected from the port and cannot be reconnected without a reboot. It appears the shared 1.8V rail between the OMAP3530 and the power chip was getting noisy. Suggested solution (works on many boards) is adding a 0.22 uF 0805 package SMT capacitor atop the existing cap on C97. If SMT parts are not available, some boards can be repaired by a 0.22 uF through-hole capacitor across GND and VIO_1V8 on the expansion connector. See [http://groups.google.com/group/beagleboard/browse_thread/thread/5b8385f0bb1f63da] for more information.<br />
<br />
===OTG===<br />
The HS USB OTG ([http://en.wikipedia.org/wiki/USB_On-The-Go OnTheGo]) controller on OMAP3 on the BeagleBoard does have support for all the USB 2.0 speeds (LS/FS/HS) and can act as either a host or a gadget/device. The HS USB OTG port is used as the default power input for the BeagleBoard. It is possible to boot the BeagleBoard using this USB port.<br />
<br />
When using the OTG port in host mode, you must power the BeagleBoard using the +5V power jack. If you connect a USB hub, you'll probably also need external power for the USB hub as well, because according to the Hardware Reference manual the BeagleBoard OTG port only sources 100 mA. This is enough to drive a single low-power device, but probably won't work with multiple devices.<br />
<br />
The Linux kernel needs to know you want to use the OTG port in host mode. I believe OTG ports are supposed to figure this out for themselves using the OTG Host Negotiation Protocol, but for now the Linux kernel may need some help. Specifically, Pin 4 (ID) of the OTG connector needs to be shorted to Pin 5 (GND) by using a [http://trisoft.de/pics/ZHost.JPG 5-pin USB Mini-A plug] which shorts these pins together in the plug. A [http://en.wikipedia.org/wiki/USB#USB_cables 5-pin USB Mini-B plug] leaves Pin 4 floating. Unfortunately, most USB Mini plugs are unmarked as to whether they are "A" or "B".<br />
<br />
You can find "mini A" adapters that have Pin 4 shorted and offer out a full-sized USB A Female jack [http://www.electronicproductonline.com/catalog/product_info.php?products_id=2043 here.]<br />
<table><br />
<tr><td><br />
Since the right cables might be hard to get, you simply can<br />
* short circuit the two pins encircled in red in the image to the right. You can do this by running a wire between the two pins. That at least allows easier undoing the change. Actually you could even have a small switch or so between 4 and 5.<br />
or<br />
* use a "mini B" cable (easier to get) and try the soldering of the two pins at the cable's connector. Depending on the cable it should be possible to open the plastic covering of mini-B port with a sharp-edged knife, then solder the two pins together, close the covering again and use some tape. This leaves the BeagleBoard unmodified.<br />
</td><td>[[Image:usb_otg.png]]</td></tr></table><br />
The Rev C BeagleBoard has a pair of pads labeled J6 on the back of the board under the OTG connector. Shorting these pads together with a wire or solder blob connects pins 4 and 5.<br />
See Figure 20 in the BeagleBoard System Reference Manual Rev C2.2.<br />
<br />
==DVI==<br />
<br />
DVI-D connection on BeagleBoard uses a [http://en.wikipedia.org/wiki/HDMI HDMI connector]:<br />
<br />
''HDMI is backward-compatible with the single-link Digital Visual Interface carrying digital video (DVI-D or DVI-I, but not DVI-A) used on modern computer monitors and graphics cards. This means that a DVI-D source can drive a HDMI monitor, or vice versa, by means of a suitable adapter or cable, but the audio and remote control features of HDMI will not be available.''<br />
<br />
BeagleBoard can be connected to a DVI monitor using HDMI female to DVI male cable.<br />
<br />
=BootRom=<br />
<br />
OMAP3 on BeagleBoard contains a BootRom. With this, BeagleBoard can boot without any code in permanent storage (NAND) or from peripherals. This is useful for first board bring up or if your BeagleBoard is bricked. For more information about BootRom booting see [http://www.ti.com/litv/pdf/sprufd6a SPRUFD6]. <br />
<br />
==User button==<br />
<br />
With user button on BeagleBoard you can configure boot order. Depending on this button, the order used to scan boot devices is changed. The boot order is (the first is the default boot source):<br />
<br />
* User button ''not'' pressed: NAND -> USB -> UART -> MMC<br />
* User button ''is'' pressed: USB -> UART -> MMC -> NAND<br />
<br />
Technically speaking, the user button configures pin SYS.BOOT[5]. See [http://focus-webapps.ti.com/general/docs/sitesearch/searchsite.tsp?selectedTopic=1653260327&numRecords=25&searchTerm=sprufd6&statusCode=null SPRUFD6] for more details.<br />
<br />
==Serial and USB boot==<br />
<br />
Historically, using OMAP3's boot ROM for serial and USB boot, there are several tools around. The newest are Nishanth' ''OMAP U-Boot Utils'', while there are still some older tools for serial boot and USB boot. It is also possible to access the [[u-boot environment variables in linux|u-boot env from linux]].<br />
<br />
===OMAP U-Boot Utils===<br />
<br />
Nishanth' [http://code.google.com/p/omap-u-boot-utils/ OMAP U-Boot Utils] provide<br />
<br />
* ''pserial'' - OMAP specific utility which downloads a file in response to ASIC ID over serial port.<br />
* ''pusb'' - OMAP specific utility which downloads a file in response to ASIC ID over USB connection.<br />
* ''ucmd'' - Send a command to U-Boot and wait till a specific match appears.<br />
* ''ukermit - Download a file from host without using kermit to U-Boot.<br />
<br />
See [http://nishanthmenon.blogspot.com/ Nishanth' blog] and [http://groups.google.com/group/beagleboard/browse_thread/thread/c5bfb1b8ed528b52# announce mail], too.<br />
<br />
===Serial boot===<br />
<br />
Besides Nishanth' ''OMAP U-Boot Utils'', to boot from USB or UART, you need a PC tool which talks with OMAP BootRom and speaks the correct protocol to download ARM target code to BeagleBoard. Currently there are two older (experimental) tools for UART boot:<br />
<br />
* [http://omapzoom.org/gf/project/omaptools/wiki PC Serial Boot perl script]<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/80ad3da0eb2aa555 Linux C utility] (not working yet with below target code)<br />
<br />
See [http://groups.google.com/group/beagleboard/browse_thread/thread/ae2c601ebe104a4 USB and serial download target code] for some example target code to be downloaded to OMAP3 on BeagleBoard.<br />
<br />
===USB boot===<br />
<br />
Besides Nishanth' ''OMAP U-Boot Utils'', for USB boot, there is currently one (experimental) tool to boot BeagleBoard over USB:<br />
<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/2b9e99886bb7a747 Linux C utility]<br />
<br />
See [http://groups.google.com/group/beagleboard/browse_thread/thread/ae2c601ebe104a4 USB and serial download target code] for some example target code to be downloaded to OMAP3 on BeagleBoard.<br />
<br />
See [[BeagleBoardRecovery#USB_recovery|USB recovery section]] how to use USB boot for board recovery.<br />
<br />
==NAND boot==<br />
<br />
See [[BeagleBoardNAND|NAND boot]] article.<br />
<br />
==MMC/SD boot==<br />
<br />
Currently, [http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard boot the BeagleBoard with MMC/SD] is the only working way for first board bring up.<br />
<br />
===MMC/SD formatting===<br />
<br />
As described in above MMC/SD boot description, you have to ''create a bootable partition on MMC/SD Card''. This can be done using e.g. Windows or Linux tools.<br />
<br />
'''Windows'''<br />
<br />
See ''HP USB Disk Storage Format Tool 2.0.6'' description on [http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard boot the BeagleBoard with MMC/SD] page.<br />
<br />
'''Linux'''<br />
<br />
Please see [http://wiki.omap.com/index.php?title=MMC_Boot_Format OMAP3 MMC Boot Format].<br />
<br />
===Dual partition card===<br />
<br />
You can [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat create a dual-partition card], booting from a FAT partition that can be read by the OMAP3 ROM bootloader and Windows, then utilizing an ext2 partition for the Linux root file system.<br />
<br />
To mount second ext2 partition as root file system (e.g. containing contents of [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode rd-ext2.bin]) use kernel boot arguments (e.g. in uboot using ''setenv bootargs''):<br />
<br />
console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait<br />
<br />
===U-Boot booting===<br />
<br />
If your MMC/SD card formatting is correct and you put [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode MLO, u-boot.bin and uImage] on the card you should get a u-boot prompt after booting beagle board. E.g. (output from terminal program with 115200 8N1):<br />
<br />
...40T.........XH.H.U�..Instruments X-Loader 1.41<br />
Starting on with MMC<br />
Reading boot sector<br />
<br />
717948 Bytes Read from MMC<br />
Starting OS Bootloader from MMC...<br />
<br />
U-Boot 1.1.4 (Apr 2 2008 - 13:42:13)<br />
<br />
OMAP3430-GP rev 2, CPU-OPP2 L3-133MHz<br />
TI 3430Beagle 2.0 Version + mDDR (Boot ONND)<br />
DRAM: 128 MB<br />
Flash: 0 kB<br />
NAND:256 MiB<br />
In: serial<br />
Out: serial<br />
Err: serial<br />
Audio Tone on Speakers ... complete<br />
OMAP3 beagleboard.org #<br />
<br />
Using this u-boot prompt, you now can start kernel uImage stored on MMC card manually:<br />
<br />
OMAP3 beagleboard.org # mmc init<br />
OMAP3 beagleboard.org # fatload mmc 0:1 0x80000000 uimage<br />
OMAP3 beagleboard.org # bootm<br />
<br />
If you like to make that happen every boot:<br />
<br />
OMAP3 beagleboard.org # set bootcmd 'mmc init ; fatload mmc 0:1 0x80000000 uimage ; bootm' ; saveenv<br />
<br />
=Code=<br />
<br />
Code and binaries for BeagleBoard are available at various places.<br />
<br />
==Binaries==<br />
<br />
BeagleBoard pre-built binaries and source code can be found at [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode Beagle source code] and [http://code.google.com/p/beagleboard/downloads/list downloads] page. These are the locations where "official" TI code is available. Please note that this code is mainly for reference and testing. More up to date binaries and code is available by community. Community took (parts) of TI reference code, improves and updates it. <br />
<br />
Actually, [http://www.angstrom-distribution.org/node/47 Koen's prebuilt Beagleboard demo images] are up to date binaries including e17 as window manager, the abiword word processor, the gnumeric spreadsheet application, a NEON accelerated mplayer and the popular NEON accelerated omapfbplay which gives you fullscreen 720p decoding. The [http://www.angstrom-distribution.org/demo/beagleboard www.angstrom-distribution.org/demo/beagleboard] directory should contain all the files you need:<br />
<br />
* [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.bin u-boot.bin]<br />
* [http://www.angstrom-distribution.org/demo/beagleboard/MLO MLO]<br />
* [http://www.angstrom-distribution.org/demo/beagleboard/uImage uImage]<br />
* [http://www.angstrom-distribution.org/demo/beagleboard/Angstrom-Beagleboard-demo-image-glibc-ipk-2009.X-test-20090104-beagleboard.rootfs.tar.bz2 rootfs]<br />
<br />
See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat beagle wiki] on how to setup your SD card to use all this goodness.<br />
<br />
==Source==<br />
<br />
Besides above binary and source images (TI's and communities one), for various parts of Beagle software stack there are community supported [http://git.or.cz/ git] repositories available. <br />
<br />
===X-Loader===<br />
<br />
Steve did some work to consolidate and update X-Loader from various sources and put it in a [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=x-load-omap3.git;a=summary X-Loader git repository]. Get it by<br />
<br />
git clone git://gitorious.org/x-load-omap3/mainline.git xloader<br />
cd xloader/<br />
<br />
Build:<br />
<br />
make distclean<br />
make omap3530beagle_config<br />
make<br />
<br />
Result will be a ~20k sized ''x-load.bin'' in main directory.<br />
<br />
===U-Boot===<br />
<br />
[http://www.denx.de/wiki/U-Boot/WebHome Mainline U-Boot] has good support for BeagleBoard. Get it by:<br />
<br />
git clone git://git.denx.de/u-boot.git u-boot-main<br />
cd u-boot-main<br />
git checkout --track -b omap3 origin/master<br />
<br />
Build (assuming [[ARMCompilers#Recommendations|Code Sourcery GCC]]):<br />
<br />
make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper<br />
make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_beagle_config<br />
make CROSS_COMPILE=arm-none-linux-gnueabi- <br />
<br />
Result will be a ~160k sized ''u-boot.bin'' in main directory.<br />
<br />
Note: Due to (patch and binary) size, BeagleBoard splash screen was removed from upstream version. If you want it back, use [http://groups.google.com/group/beagleboard/browse_thread/thread/3ad9b803a3418624 U-Boot v1 BeagleBoard splash screen patch].<br />
<br />
Note: For experimental U-Boot patches not ready for mainline yet, Steve's [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=summary Beagle U-Boot git repository] is used to test them. Get it by:<br />
<br />
git clone git://gitorious.org/u-boot-omap3/mainline.git u-boot-omap3<br />
cd u-boot-omap3<br />
git checkout --track -b omap3-dev origin/omap3-dev<br />
<br />
Note: For changing the screen resolution there is one option modifying the file in "include/configs/omap3_beagle.h" and adjusting the maximum resolution before compiling as describe in [http://gitorious.org/linux-omap-dss2/linux/blobs/master/Documentation/arm/OMAP/DSS ARM OMAP2/3 Display Subsystem]<br />
<br />
===Linux kernel===<br />
<br />
[http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary Git repository] of [http://muru.com/linux/omap/ OMAP Linux kernel] contains Beagle support. Get it by:<br />
<br />
git clone git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git linux-omap-2.6<br />
cd linux-omap-2.6<br />
<br />
Build:<br />
<br />
make distclean<br />
make omap3_beagle_defconfig<br />
make menuconfig # only needed if you want to change the default configuration<br />
make uImage<br />
<br />
The result will be a ''uImage'' in ''arch/arm/boot/'' directory.<br />
<br />
If you use the OE toolchain and want to build outside of the OE tree you should do<br />
ARCH=arm<br />
PATH=~/oe/tmp/cross/armv7a/bin:~/oe/tmp/staging/i686-linux/usr/bin:$PATH # add cross tools to your path<br />
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- distclean<br />
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- omap3_beagle_defconfig<br />
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- menuconfig # only needed if you want to change the default configuration<br />
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage<br />
Note: the staging dir in the path is for mkimage. If you've build a kernel before with oe, the program should be there<br />
<br />
Note: If you are interested in kernel development have a look to [[BeagleBoardLinuxKernel|manually compiling BeagleBoard kernel]], too.<br />
<br />
===Experimental kernel patches and hacks===<br />
<br />
Some beagle developers maintain their own kernel experimental patches and hacks not ready for upstream:<br />
<br />
* [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap Koen's collection of kernels patches for OE] and the [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap_git.bb list of relevant patches]<br />
* [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=shortlog;h=refs/heads/test Steve's kernel tree], a clone of main OMAP git with additional patches, mainly beagle audio (ASOC) related.<br />
* [http://git.mansr.com/?p=linux-omap;a=summary Mans' kernel tree], a clone of main OMAP git with additional patches, mainly display & framebuffer related.<br />
* [http://www.bat.org/~tomba/linux-omap.html Tomi's kernel tree], a clone of main OMAP git with display sub-system patches, replacing the entire display driver with one that is the likely direction moving forward.<br />
<br />
=Compiler=<br />
<br />
TI OMAP3530 processor on BeagleBoard contains an ARM Cortex-A8 general purpose processor and a TMS320C64x+ DSP.<br />
<br />
==ARM==<br />
<br />
There is broad compiler support including gcc - please see [http://www.elinux.org/ARMCompilers ARM Compilers]<br />
<br />
==C64x+ DSP==<br />
<br />
A free C64x DSP compiler is available as [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html Linux hosted C6x Code Generation Tools] (TMS320C6000 C/C++ CODE GENERATION TOOLS 6.1.3 July 2008).<br />
<br />
Note: my.TI account required. You may create an account [https://my.ti.com here]<br />
<br />
Note: Old c6000 Linux compiler available on [ftp://ftp.ti.com/pub/cs/linux_cgt500.tar.gz TI FTP site]. Does NOT support c64x+ core in OMAP3 devices. Not recommended.<br />
<br />
You can also utilize the [http://focus.ti.com/dsp/docs/dspsupportaut.tsp?familyId=44&sectionId=3&tabId=416&toolTypeId=30 full-CCS free evaluation tools for 120 days], but they currently require purchase to upgrade to service release 9 to support full JTAG debugging with supported JTAG hardware.<br />
<br />
See [[BeagleBoard/DSP_Howto| BeagleBoard DSP howto]] for information about how to use the DSP.<br />
<br />
=Cortex A8 ARM features =<br />
<br />
ARM Cortex-A8 in OMAP3 is a high performance dual-issue applications processor which reaches a performance of 2.0 DMIPS/MHz (compared to ARM11 at 1.2 DMIPS/MHz). It is ARM v7 architecture, which is fully backwards compatible with application code for previous ARM processors.<br />
<br />
It includes a floating point unit (ARM VFPv3 architecture) and the ARM NEON SIMD instruction set.<br />
<br />
See [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] article for an intro into VFP-lite and NEON.<br />
<br />
===ARM NEON===<br />
<br />
NEON is a 64/128-bit wide SIMD vector extension for ARM, which has been architected to be an efficient C compiler target as well as being used from assembly language. It has 32x 64-bit registers (with a dual view as 16x 128-bit registers) which can hold the following datatypes:<br />
* 64-bit signed/unsigned<br />
* 32-bit signed/unsigned<br />
* 32-bit single precision floating point<br />
* 16-bit signed/unsigned<br />
* 8-bit signed/unsigned<br />
<br />
The key advantage of NEON is very high performance vector math processing, whilst being easy to program. It is the same thread of control as the ARM (but different instructions), and is supported by the same tools, debuggers and operating systems.<br />
<br />
The NEON instruction set is documented in ARM's [http://infocenter.arm.com/help/topic/com.arm.doc.dui0204i/DUI0204I_rvct_assembler_guide.pdf RealView Compilation Tools Assembler Guide].<br />
<br />
For NEON optimized libraries see [http://www.us.design-reuse.com/news/18429/aac-mp3-mpeg-4-h-264-fft-openmax-cortex-a8-neon-arm11-processors.html ARM Releases AAC, MP3, MPEG-4, H.264 and FFT OpenMAX DL Libraries, Highly Optimized for Cortex-A8/NEON and ARM11 Processors]. Note: Read the [http://www.arm.com/products/esd/openmax_v7libraries.html EULA].<br />
<br />
NEON is currently used by<br />
* ffmpeg - libavcodec used by mplayer, omapfbplay, and many other linux applications<br />
* libpixman - used by X.org and Mozilla & Webkit browsers to render text and graphics<br />
* Bluez - official Linux Bluetooth stack<br />
<br />
=== ARM Cortex Floating Point ===<br />
<br />
There are two types of instructions in the ARM v7 ISA that handle floating point:<br />
<br />
1) '''VFPv3''' Floating point instruction set (used for single/double precision scalar operations).<br />
These is used by gcc for C floating point operations on 'float' and 'double'<br />
<br />
2) '''NEON''' [http://www.arm.com/products/multimedia/neon/ NEON] vectorized single precision operations (2 values in a D-register, or 4 values in a Q-register)<br />
These can be use by gcc when -ftree-vectorize is enabled and -mfpu=neon is specified, and the code can be vectorized. In other cases the VFPv3 scalar ops will be used.<br />
<br />
ARM Cortex-A processors have separate floating point pipelines that handle these different instructions.<br />
<br />
On Cortex-A8, the designers' focus was on the NEON unit performance which can sustain 1 cycle/instr throughput (processing 2 single-precision values at once). The scalar VFPv3 FPU cannot achieve this level of performance (cycle timings are in the Cortex-A8 TRM download), but it is still a lot better than doing floating point using integer instructions.<br />
<br />
If you need the highest performance floating point on Cortex-A8, you need to use single precision and ensure the code uses the NEON vectorized instructions:<br />
* use gcc with -ftree-vectorize (possibly modify source code to make it vector friendly)<br />
* use NEON instrinsics (#include <arm_neon.h>, float32x2_t datatype and vmul_f32() etc)<br />
* use NEON asm directly<br />
<br />
Keep in mind that mixing NEON and ARM load/stores can sometimes stall significantly. See [http://hardwarebug.org/2008/12/31/arm-neon-memory-hazards/ this link] for more info.<br />
<br />
On Cortex-A9, there is a much higher performance floating point unit which can sustain 1 cycle/instr throughput, with low result latencies.<br />
<br />
=Board recovery=<br />
<br />
If you played e.g. with the contents of the [http://www.sakoman.net/omap3/flash%20procedure.txt NAND], it might happen that the Board doesn't boot any more (without pressing user button) due to broken NAND content. See [[BeagleBoardRecovery|BeagleBoard recovery]] article how to fix this.<br />
<br />
=Development environments=<br />
<br />
Instead of just using compiler + editor, you can use complete image create "development tool chains" which integrate compiler, build system, packaging tools etc. in one tool chain.<br />
<br />
==OpenEmbedded==<br />
<br />
For [http://www.openembedded.org/ OpenEmbedded] (OE), there are some hints how to [http://www.beagleboard.org/irclogs/index.php?date=2008-04-29#T13:06:25 start with OE for BeagleBoard]. See [[BeagleBoardAndOpenEmbeddedGit|BeagleBoard and OpenEmbedded Git]] and [http://wiki.openembedded.org/index.php/Getting_Started OpenEmbedded getting started] as well.<br />
<br />
In the OE getting started document, for BeagleBoard replace ''MACHINE = "om-gta01"'' by ''MACHINE = "beagleboard"''. After confirming ''bitbake nano'' works, try ''bitbake console-image''. The first time you run bitbake OE will download all the needed source and build the tool chain. This will take several hours. After all went fine, the output is in ''${OE_ROOT}/tmp/deploy/glibc/images/beagleboard''.<br />
<br />
Note: Koen has some BeagleBoard [http://amethyst.openembedded.net/~koen/index.php?path=beagleboard/ source and binary images] built with OE. There, ''Angstrom-console*'' images don't include an X server, you can still use a e.g. DVI-D screen with console, but you won't have a GUI. ''Angstrom-x11*'' images contain an X server.<!-- DEAD LINK: resulting in something like [http://scap.linuxtogo.org/files/fc987d4acb2c745fb7e19cf4dca8de70.png this].--><br />
<br />
===One very important note:=== <br />
<br />
It's important to have an X-Loader on your Beagleboard that uses the uImage on the SD Card that goes with Angstrom. The B6 Beagleboards do not appear to come with such an X-Loader. So you likely will have to upgrade the X-Loader. Here's what to do:<br />
* Make an SD Card with the [http://www.angstrom-distribution.org/demo/beagleboard Angstrom Demo files]. See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat Beagleboard Wiki Page] for more info on making the SD Card.<br />
* Put the SD Card in the Beagle, and boot up to the U-Boot Prompt.<br />
* Do the first six instructions in the [http://code.google.com/p/beagleboard/wiki/BeagleNANDFlashing Flashing Commands with U-Boot] section. <br />
* Reboot the Beagle to see that the new X-Loader is properly loaded.<br />
<br />
This will update the X-Loader to a newer version that will automatically load uImage from the SD Card when present -- rather than always using the uImage in the Beagleboard NAND.<br />
<br />
==Eclipse==<br />
The Eclipse [http://www.eclipse.org/cdt/ C Development Tools Project] provides a "fully functional C and C++ Integrated Development Environment (IDE) for the Eclipse platform". The Eclipse [http://www.eclipse.org/dsdp/tm/ DSDP Target Managment Project] provides a "Remote System Explorer" (RSE) plugin that simplifies downloading files to the BeagleBoard and editing files on the BeagleBoard within the Eclipse IDE. A Linux Target Agent is available as part of the [http://wiki.eclipse.org/DSDP/TM/TCF_FAQ Target Communications Framework (TCF) component]. Info on how RSE is used for e.g. Gumstix development is described in [http://groups.google.com/group/beagleboard/browse_thread/thread/509831f7c24cb79f# this post].<br />
<br />
==Android==<br />
[http://source.android.com Android] platform is a software stack for mobile devices including an operating system, middleware and key applications. Developers can create applications for the platform using the [http://code.google.com/android/ Android SDK]. Applications are written using the Java programming language and run on Dalvik, a custom virtual machine designed for embedded use which runs on top of a Linux kernel.<br />
<br />
There are several resources for Android on OMAP (Beagle) available:<br />
<br />
'''OMAPZOOM'''<br />
<br />
You can find Android port for OMAP ZOOM architecture on [https://omapzoom.org/gf/project/omapandroid/wiki/ OMAPZoom.org's wiki page on Android]. <br />
<br />
'''EMBINUX'''<br />
<br />
[http://beagleboard.org/project/android Beagleboard.org's Android project page] [http://groups.google.com/group/beagleboard/browse_thread/thread/7b422f113ce489b5 announced], the successful porting of Android on Beagle board by [http://embinux.com EMBINUX&trade;] Team. The [http://labs.embinux.org/git/ source code] and [http://www.embinux.com/download_beagle.php binaries] are available for download and review. <br />
<br />
Detailed instructions, for porting Android on Beagle Board, are available [http://labs.embinux.org/index.php/Main_Page here]. Current release supports input devices (keyboard/mouse), network and sound.<br />
<br />
You can [http://in.youtube.com/watch?v=nADn_vNVEKw watch Android booting] on Beagle Board.<br />
<br />
'''Android on OMAP wiki'''<br />
<br />
Wiki page for Andorid on OMAP can be found [[Android on OMAP|here]]<br />
<br />
'''0xdroid'''<br />
<br />
[http://gitorious.org/0xdroid 0xdroid], the enhanced version of Android on Beagleboard by [http://0xlab.org 0xlab]. The [http://gitorious.org/0xdroid source code], [http://downloads.0xlab.org/ pre-built binaries], and [http://code.google.com/p/0xdroid/issues/list issue tracker] are available for review and reference.<br />
<br />
The latest development supports OMAP audio, OMAP video overlays, ARM Cortex A8 NEON/Thumb2 performance optimizations, mouse cursor, hot-pluggable USB keyboard & mouse, user-friendly installer for system image, and various Android tweaks. Detailed instructions for 0xdroid are available through [http://code.google.com/p/0xdroid/wiki/MainPage Google Code wiki].<br />
<br />
You can [http://www.youtube.com/watch?v=v6wdTOHrwQw watch 0xdroid demo video] on Beagle Board.<br />
* [http://www.youtube.com/watch?v=v6wdTOHrwQw 0xdroid demo video (1)]<br />
* [http://www.youtube.com/watch?v=ol9LWBKXXwQ 0xdroid demo video (2)]<br />
<br />
==Mamona==<br />
<br />
[http://dev.openbossa.org/trac/mamona/wiki Mamona] is an embedded Linux distribution for ARM EABI. The main goal of the Mamona Project is to offer a completely open source alternative/experimental platform for [http://maemo.org/ Maemo] using only free and open source components. Mamona [http://rsalveti.wordpress.com/2008/09/12/mamona-02-is-out 0.2] [http://franciscoalecrim.com/blog/2008/07/29/mamona-working-with-beagleboard/ supports] [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12013&contentId=28741 OMAP3430 Software Development Platform (SDP)], so you can also use it at Beagle (OMAP3530), too. Work is being done to officially support Beagle.<br />
<br />
==Ubuntu==<br />
<br />
See [[BeagleBoardUbuntu|Ubuntu (ARM)]] installation guide how to install Ubuntu (ARM) on BeagleBoard.<br />
<br />
==Debian ARM==<br />
<br />
See [[BeagleBoardDebian|Debian (ARM)]] installation guide how to install Debian (ARM) on BeagleBoard.<br />
<br />
==Handhelds Mojo ARM==<br />
<br />
See [[BeagleBoardHandheldsMojo|Handhelds Mojo (ARM)]] installation guide how to install Handhelds Mojo (ARM) port of Ubuntu on BeagleBoard. (The Mojo project is no longer active, see the Official Ubuntu ARM-port above instead)<br />
<br />
==Scratchbox==<br />
<br />
[http://www.scratchbox.org/ Scratchbox] is a cross-compilation toolkit designed to make embedded Linux application development easier. It also provides a full set of tools to integrate and cross-compile an entire Linux distribution. See [http://felipec.wordpress.com/2009/06/07/installing-scratchbox-1-and-2-for-arm-cross-compilation/ Felipe's Scratbox 1 and 2 intro], too.<br />
<br />
=Software hints=<br />
<br />
This section collects hints, tips & tricks for various software components running on beagle.<br />
<br />
==QEMU==<br />
<br />
[[Qemu|QEMU]] [http://vm-kernel.org/blog/2008/12/15/linux-is-running-on-qemu-omap3/ supports OMAP3] being able to boot a BeagleBoard Linux kernel.<br />
<br />
==Linux hints==<br />
<br />
See BeagleBoard [http://code.google.com/p/beagleboard/wiki/LinuxHints Google wiki Linux hints] page (for Linux WTBU (Wireless TI Business Unit) kernel [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode 2.6.22]). Currently featuring:<br />
<br />
* Switching video output between DVI-D and S-Video<br />
* Disabling framebuffer blanking<br />
* Listing USB devices<br />
<br />
==lmbench==<br />
<br />
Avik posted a detailed [http://groups.google.com/group/beagleboard/browse_thread/thread/c8b8f07ce61161a1 step-by-step procedure] to run [http://sourceforge.net/project/showfiles.php?group_id=14418 lmbench] on Beagle.<br />
<br />
==Mediaplayer (FFmpeg)==<br />
<br />
There is a thread how to get a [http://groups.google.com/group/beagleboard/browse_thread/thread/9b8025fc15120fd9# mediaplayer] with NEON optimization (FFmpeg) to run on Beagle. Includes compiler hints and patches.<br />
<br />
==Java==<br />
<br />
When using the [[BeagleBoard#OpenEmbedded|OpenEmbedded]]-based Angstrom image you have the following options of Java support:<br />
* JamVM + GNU Classpath (small vm, fast interpreter, J2SE-like)<br />
* Cacao + GNU Classpath (JIT compiler, J2SE-like)<br />
* PhoneME Advanced Foundation (JIT compiler, CDC)<br />
<br />
Java support in OpenEmbedded/Angstrom ([http://wiki.openembedded.net/index.php/Java details]) is provided voluntarily through [http://jalimo.org Jalimo].<br />
<br />
See a [http://groups.google.com/group/beagleboard/browse_thread/thread/102f627253919783# post at mailing list], too.<br />
<br />
OpenEmbedded users can add the [http://evolvis.org/scm/?group_id=11 Jalimo Subversion repository] as an overlay (instructions are in the repository). This will allow them to build OpenJDK packages. Inclusion of these recipes in mainline OpenEmbedded is planned but still ongoing.<br />
<br />
The recipes offer the following functionality:<br />
<br />
* OpenJDK + Hotspot (Zero port) (all J2SE functionality, including JVMTI, interpreted only)<br />
* OpenJDK + Cacaco (all J2SE library features, missing JVMTI, decent JIT compiler)<br />
* OpenJDK + Hotspot (Shark port) (not working yet)<br />
<br />
Some guy from ARM Ltd. is working on interpreter optimization in Zero for ARM.<br />
<br />
People interested in getting this stuff working better should contact people on:<br />
* [http://evolvis.org/mail/?group_id=11 Jalimo Mailinglist]<br />
* [http://mail.openjdk.java.net/mailman/listinfo/distro-pkg-dev Icedtea Mailinglist]<br />
<br />
You should also check out IcedTea's [http://iced-tea.org/wiki/FrequentlyAskedQuestions FAQ].<br />
<br />
=Graphics accelerator=<br />
<br />
OMAP3530 used on BeagleBoard contains a graphics accelerator (SGX) based on the SGX core from [http://www.imgtec.com/ Imagination Technologies]. [http://www.imgtec.com/powervr/powervr-graphics.asp PowerVR] SGX530 is a new generation of programmable PowerVR graphics and video IP cores. Only the kernel portions of Linux drivers will be open source. The PowerVR folks will provide binary user-space libraries. Using the EMail contact at [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12700&contentId=27458 TIs Mobile Gaming Developers page] there are Linux v2.6 OMAP3430 SDKs for OMAP3 Zoom and SDP supporting OpenGL ES v2.0, OpenGL ES v1.1 and OpenVG 1.0 available.<br />
<br />
Tutorial:<br />
* [http://code.google.com/p/beagleboard/wiki/HowtoUseSGXunderAngstrom How to use SGX with Angstrom in OE]<br />
<br />
Some videos:<br />
<br />
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle working with Linux 2.6.27]<br />
* [http://www.youtube.com/watch?v=24TXpqa9jG0&feature=related OpenGL ES 2.0 shader effects on OMAP3]<br />
* [http://www.youtube.com/watch?v=-UFUbqoNgs8&feature=related 3D User Interface on OMAP3 Platform]<br />
* [http://www.youtube.com/watch?v=8KcNgeUriqA 3D Mapping using OpenGL ES 2.0 on OMAP3 Platform]<br />
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]<br />
* [http://www.hitlabnz.org/wiki/EmbeddedAR An Augmented Reality application combining ARToolkit and OpenGL ES 2.0]<br />
<br />
=Beginners guide=<br />
<br />
You just got your new BeagleBoard, and now? See [[BeagleBoardBeginners|beginners guides]].<br />
<br />
=FAQ=<br />
<br />
For BeagleBoard frequently asked questions (FAQ) see [[BeagleBoardFAQ|community FAQ]] and "official" [http://beagleboard.org/support/faq BeagleBoard.org FAQ].<br />
<br />
=Links=<br />
==Home page==<br />
[http://beagleboard.org/ beagleboard.org] (beagle board home)<br />
* Using [http://www.google.de/ Google] you can search beagleboard.org (including [http://www.beagleboard.org/irclogs/ IRC logs]) using ''site:beagleboard.org <search term>''<br />
<br />
==Manuals and resources==<br />
* [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard HW Reference Manual (rev. C2)]<br />
* [http://beagle.s3.amazonaws.com/BBSRM_7_2_0.pdf BeagleBoard HW Reference Manual (rev. B7)]<br />
* [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)]<br />
* [http://www.beagleboard.org/uploads/BBSRM_B5.pdf BeagleBoard HW Reference Manual (rev. B5)]<br />
* [http://www.beagleboard.org/uploads/Beagle_HRM_B4.pdf BeagleBoard HW Reference Manual (rev. B4)]<br />
* [http://www.beagleboard.org/uploads/Beagle_HW_Reference_Manual_A_5.pdf BeagleBoard HW Reference Manual (rev. A5)]<br />
* [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor description and manuals<br />
* [http://code.google.com/p/beagleboard/ Beagle at code.google.com]<br />
* [http://focus.ti.com/dsp/docs/dspsupporttechdocs.tsp?sectionId=3&tabId=409&familyId=1526&documentCategoryId=4&techDoc=4 OMAP3530/25 CBB BSDL Model]<br />
* [http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for Beagle Board]<br />
* [http://beagleboard.org/resources Beagleboard resources page with hw docs]<br />
* Some [http://www.rasterman.com/ performance comparison] of BeagleBoard Rev. B with some other ARM/PC systems.<br />
* OMAP3 pinmux [http://www.hy-research.com/omap3_pinmux.html setup]<br />
* [http://elinux.org/BeagleBoardPinMux OMAP3 eLinux pinmux page]<br />
<br />
==Contact and communication==<br />
* [http://groups.google.com/group/beagleboard Beagle board discussion list]<br />
* [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker]<br />
* [http://beagleboard.blogspot.com/ Beagle board blog]<br />
* [http://feeds.feedburner.com/BeagleBoard Beagle board RSS feed]<br />
* Chat:<br />
** [http://beagleboard.org/chat Beagle Board chat]<br />
** IRC: #beagle channel on irc.freenode.net<br />
** [http://www.beagleboard.org/irclogs/index.php IRC archive]<br />
* [http://www.beaglesride.org/ Beagles Ride], a site about building a community around the BeagleBoard focused on in vehicle applications<br />
* [http://www.beagleboard.de/ German Beagle Board Forum and Wiki]<br />
<br />
==TI resources==<br />
* [http://opensource.ti.com/ TI open source page]<br />
* [https://community.ti.com/ TI E2E (Engineer-to-Engineer) Community]<br />
* [http://marc.info/?l=linux-omap&m=120761100810527&w=2 DSP Bridge driver for OMAP3 platform]<br />
* [http://lists.arm.linux.org.uk/lurker/message/20080701.142512.5eeff26b.en.html ARMv7 Oprofile support]<br />
* [http://focus.ti.com/pdfs/wtbu/swpu114g.pdf OMAP34xx Wireless Technical Reference Manual] (swpu114g.pdf, 47 MB)<br />
* [http://amethyst.openembedded.net/~koen/index.php?sort=date&order=desc&path=beagleboard/ Koen's (OpenEmbeded) BeagleBoard source and binaries]<br />
* [http://del.icio.us/tag/beagleboard+peripheral+verified Verified peripherals for BeagleBoard]<br />
* [http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt OMAP3430 Linux Power Management presentation]<br />
==Articles==<br />
* [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article about Beagle]<br />
* [http://www.linuxdevices.com/news/NS8479495970.html LinuxDevices article about Digi-Key launch]<br />
* [http://www.linuxdevices.com/news/NS5682470737.html LinuxDevices article about Beagle Rev C, Beagle MID from HY Research, Touch Book and Sponsored Projects Contest]<br />
* [http://www.linuxjournal.com/article/10607 Linuxjournal article on the BeagleBoard]<br />
<br />
==Books==<br />
* [[OMAP_and_DaVinci_Software_for_Dummies|OMAP and DaVinci Software for Dummies]]<br />
<br />
==Beagle based training materials==<br />
* http://free-electrons.com/blog/beagle-labs/<br />
<br />
==Past Beagle events==<br />
* TIDC, February 26-28, 2008: [http://www.beagleboard.org/uploads/tidc_opensource.pdf Slides from TI developer conference (TIDC) open source session], covering also beagle board<br />
* [http://www.lugradio.org/live/USA2008/ LUG RADIO Live USA 2008, April 12-13, 2008]: [http://www.beagleboard.org/uploads/lugradio_20080411.PPT TI/Beagle Presentation] and [http://forums.lugradio.org/viewtopic.php?f=4&t=4094&st=0&sk=t&sd=a&sid=d69cc807569ab41e33f93af698c536b8&start=15#p41549 video]<br />
* LinuxTag, May 28-31, 2008: [http://www.flickr.com/photos/jadon/2551439955/in/pool-beagleboard picture 1] and [http://www.flickr.com/photos/jadon/2535692865/in/pool-beagleboard picture 2]<br />
* [http://lugradio.org/live/UK2008/travel LugRadio Live UK 2008], July 19 - July 20, 2008: [http://www.flickr.com/photos/koenkooi/tags/lugradiolive/ Koen's pictures] showing e.g. [http://www.bigbuckbunny.org/index.php/download/ Big Buck BUNNY] playing at Beagle. [http://linuxoutlaws.com/podcast/48 Interview with Linux Outlaws (52:06)] and the [http://www.youtube.com/watch?v=m9xVbntl-DY video]<br />
* [http://osscamp.in/index.php/OSScamp_Bengaluru_Mobile_2008 OSScamp Bengaluru Mobile 2008], July 19, 2008<br />
* [http://www.linuxworldexpo.com LinuxWorld Conference & Expo], August 4 - August 7, 2008: [http://www.flickr.com/photos/jadon/sets/72157606586084668/ pictures with living beagle] and from [http://www.flickr.com/photos/linuxjournal/2738316951/in/set-72157606634486338/ Linux Journal's photostream]<br />
* BeagleBoard.org event at Jillian's during LinuxWorldExpo, August 5, 2008, 5:30-7:30 pm<br />
* [http://barcamp.pbwiki.com/BarCampHouston3 BarCamp Houston 3], August 9, 2008, 9:00 A.M.: [http://www.flickr.com/photos/jadon/sets/72157606656532041/ pictures]<br />
* NIT Suratkal, India [http://www.nitkieee.com/site/sp-connect2/schedule IEEE SP Connect 2], August 30, 20008<br />
* [http://barcampbangalore.org/wiki/BCB7_Demos BarCamp Bangalore], India, September 13, 2008<br />
* [http://www.ibc.org/ IBC 2008], September 11 - September 16, 2008: [http://www.flickr.com/photos/koenkooi/tags/ibc2008/ pictures]<br />
* Free Open "Embedded Linux" Training for Students in India, [http://code.google.com/p/beagleboard/wiki/Trainings?updated=Trainings&ts=1220250913 beagleboard.org Trainings in India], September 20, 2008: [http://www.youtube.com/watch?v=A6FLdmgQlb4&feature=PlayList&p=1BAB6EE9CC7285AD&index=0 video], [http://www.flickr.com/photos/25691331@N04/sets/72157607419766102/ photos] and [http://lakshmansrikanth.blogspot.com/2008/09/linux-embedded.html blog]<br />
* [http://www.embedded.co.uk/ Embedded Systems Show 2008], Birmingham, UK, October 1-2, 2008<br />
* [http://www.mvista.com/vision/ MontaVista Vision 2008 Embedded Linux Developers Conference], San Francisco, California, October 1-3, 2008 : [http://www.mvista.com/download/topic.php?t=18 Video and presentation overview], [http://www.mvista.com/download/fetchdoc.php?docid=323 William Mills' presentation], [http://www.mvista.com/download/fetchdoc.php?docid=333 Jason Kridner's presentation]<br />
* [http://www.rtcgroup.com/arm/2008/ ARM Developers' Conference], Santa Clara Convention Center, Santa Clara, Calif., USA, October 7-9, 2008<br />
* [http://www.cmp-egevents.com/web/escb Embedded Systems Conference Boston 2008], Hynes Convention Center, Boston, USA, October 26 - October 30, 2008: [http://beagleboard.org/demo/esc Resources]<br />
* [[BeagleBoard/contest|BeagleBoard contest]] #1: Create a cool BeagleBoard application and win a Rev C1! Closed, ran until January 9, 2009<br />
* [http://www.silica.com/events/seminars/seminar-overview/ti-omp-workshop.html OMAP35x training by Silica], January 21, 2009, Cambridge, UK, ARM Holdings Lecture Theatre. [[RichardB's notes from the seminar]]<br />
* [[BeagleBoard/contest|BeagleBoard contest #2]], unitl February 27, 2009: : Create a cool BeagleBoard application and win a Rev C2!<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/b15cf8a5797c73a2 Silica - Free TI - ARM OMAP Workshop], Brussels, Europe, March 31st 2009<br />
* SILICA's [http://www.silica.com/events/seminars/seminar-overview/ti-omap-piccolo-poing.html Texas Instruments 2-in-1 Seminar: OMAP & Piccolo], May 13th 2009: Poing (Munich) - Germany<br />
* 24th until 27th June 2009: [http://www.linuxtag.org/2009/en.html Linux Tag Germany] with [http://groups.google.com/group/beagleboard/msg/27fefef5f1d2ef73 TI booth] and [http://www.linuxtag.org/2009/en/program/freies-vortragsprogramm/all-events/details.html?talkid=183 Beagle presentation]<br />
* until 31st July 2009: [http://www.cranessoftware.com/services/training/beagledesigncontest.html BeagleBoard Design Contest INDIA Edition] ([http://beagleboard.blogspot.com/2009/04/beagleboard-design-contest-india.html blog entry])<br />
* TI Technology Day Dallas, Tex. on June 16 will held a [http://www.linuxdevices.com/news/NS5682470737.html BeagleBoard users group meeting] (see section ''Availability'').<br />
* Thursday, August 27th: [http://wiki.omap.com/index.php/ETechDays_Lightning_Talks ETechDays Lightning Talks]. 15 minute lightning talks via IRC, WebEx or Dial-In.<br />
* 22.- 23.08.2009, Sankt Augustin, Germany: [http://www.froscon.de/en/ FrOSCon 2009] ([http://groups.google.com/group/beagleboard/browse_thread/thread/6aee27a7d121f4f4# call for papers])<br />
<br />
==Beagle wiki pages==<br />
* [[BeagleBoardBeginners|BeagleBoard beginners guides]]<br />
* [[BeagleBoardAndOpenEmbeddedGit|BeagleBoard and OpenEmbedded Git]] installation guide and [[BeagleBoardOpenEmbeddedDevelopment|OpenEmbedded development]]<br />
* [[BeagleBoardDebian|Debian on BeagleBoard]] usage guide<br />
* [[BeagleBoardHandheldsMojo|Handhelds Mojo (ARM) on BeagleBoard]] usage guide (formerly known as Ubuntu (ARM))<br />
* [[BeagleBoardUbuntu|Ubuntu (ARM EABI) distribution at BeagleBoard]]<br />
* [[BeagleBoardRecovery|BeagleBoard recovery]] about fixing boards not booting any more because of broken NAND content<br />
* [[BeagleBoardJTAG|BeagleBoard JTAG]] and [[OMAP3530_ICEPICK|OMAP3530_ICEPICK]] about JTAG on BeagleBoard<br />
* [[BeagleBoardOpenOCD|BeagleBoard OpenOCD]] has infos about status and usage of open source JTAG software OpenOCD with Beagle<br />
* [[BeagleBoardNAND|BeagleBoard NAND boot]] about how to boot BeagleBoard from NAND flash<br />
* [[BeagleBoardPeripherals|BeagleBoard peripherals and adapters page]] about useful BeagleBoard add ons.<br />
* [[Mount_BeagleBoard_Root_Filesystem_over_NFS_via_USB|Mount BeagleBoard root file system over NFS via USB]]<br />
* [[BeagleBoardFAQ|BeagleBoard FAQ]]<br />
* [[BeagleBoardSugar|Sugar on BeagleBoard]]<br />
* [[BeagleBoard/DSP_Howto|BeagleBoard DSP howto]]<br />
* [[BeagleBoardRawLCD|Interfacing BeagleBoard to Raw LCD]]<br />
* [[BeagleBoard/gst-openmax|BeagleBoard OpenMAX usage]]<br />
* [[BeagleBoard/video|BeagleBoard video]]<br />
* [[BeagleBoardOpenCV|Using OpenCV computer vision library with BeagleBoard]]<br />
* [[BeagleBoard/James|James]]: Just A Miniature Entertainment System<br />
* [[U-boot_musb_gadget_support|U-boot musb gadget support]]<br />
* [[BeagleBoard-JP|Japanese translation of this Beagle page]]<br />
* [[BeagleEPD|BeagleBoard E-Ink Platform Driver]]<br />
* [[BeagleBoardFedora|Random hacking notes for getting Fedora 10 to kinda work with the BeagleBoard]]<br />
* BeagleBoard specific [[BeagleBoard/GSoC|Google Summer of Code 2009]] page, [[BeagleBoard/Ideas-2009|GSoC project ideas]] and [[BeagleBoard/GSoC/Application|GSoc application]]<br />
* [[BeagleBoard/Poky|Poky]] for BeagleBoard<br />
* [[Xenarc_USB_touchscreen_for_Beagleboard/OMAP3_EVM|Xenarc USB touchscreen for Beagleboard/OMAP3 EVM]]<br />
* [[BeagleBoard/BugAdapter|BeagleBoard Bug Adapter board]]<br />
* [[BeagleBoardDebianWifiInstallInfo|BeagleBoard Debian WiFi install info]]<br />
* [[BeagleBoard/DSP_Clarification|Info about the various Linux DSP systems for OMAP chips]]<br />
* [[BeagleBoardPinMux|BeagleBoard PinMux]]<br />
* [[BeagleBoardLinuxKernel|BeagleBoard Linux kernel manual compile]]<br />
* [http://www.hervanta.com/stuff/Beaglebot Beaglebot]: build an experimental robotics project with Beagle<br />
* [http://code.google.com/p/beagleboard/w/list code.google.com BeagleBoard wiki]<br />
* '''[[BeagleBoard/contest|BeagleBoard contest]]'''<br />
* [http://en.wikipedia.org/wiki/Beagle_Board Wikipedia BeagleBoard page]<br />
* [http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board Android port for BeagleBoard]: Instructions for porting Android on BeagleBoard<br />
* [[BeagleBoard/bangalore_user_meet |BeagleBoard Bangalore User Meet]]<br />
* [[BeagleBoardEclipse|Using Eclipse with Beagle]] (for JTAG debugging)<br />
* [[Zoom2Beginners|Zoom2 for Beginners]]<br />
* [http://wh1t3s.com/2009/05/11/beagleboard-as-usb-mass-storage-device-via-usb-otg/ BeagleBoard as USB Mass Storage Device via USB OTG]<br />
* [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm BeagleBoard as solar powered computer]<br />
* [http://blog.makezine.com/archive/2009/02/blinking_leds_with_the_beagle_board.html Blinking LEDs with the Beagle Board] from Make:Online<br />
* [http://www.crashcourse.ca/wiki/index.php/BeagleBoard Robert's private Beagle wiki] (please don't add anything there, do it here. It will help to avoid scattering. Thanks!)<br />
* [http://felipec.wordpress.com/2009/03/26/omap3-public-dsp-binaries-now-work/ Felipe's blog] about D1 MPEG-4 decoding using less than 15% of CPU with help of DSP<br />
* [http://www.syspire.de/node/3 Embedded Mediacenter] based on BeagleBoard (German)<br />
* [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] with VFP-lite and NEON intro<br />
* [http://particolarmente-urgentissimo.blogspot.com/2009/09/beagleboard-setting-date-via-gps.html Beagleboard setting date via GPS]<br />
* [http://free-electrons.com/blog/beagle-labs/ Complete embedded Linux training labs] on the BeageBoard<br />
<br />
==Beagle photos==<br />
* [http://www.flickr.com/groups/beagleboard/pool/ Beagle board pictures at flickr]<br />
* [http://www.flickr.com/photos/32615155@N00/2439256116/ Beagle board and USRP]<br />
* [http://www.flickr.com/photos/nishanthmenon/2438406603/ Modify SDP3430 QUART cable for beagle]<br />
* [http://www.flickr.com/photos/koenkooi/2695061759/ MythTV on Beagle]<br />
==Beagle videos==<br />
* [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings]<br />
* [http://www.youtube.com/watch?v=cXr-D1wROfQ Beagleboard in the Living Room]<br />
* [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu]<br />
* [http://uk.youtube.com/watch?v=TUYOjRGYeYU testsprite with beagleboard]<br />
* [http://uk.youtube.com/watch?v=9Z4ZTovtFKk Beagleboard LED demo]<br />
* [http://uk.youtube.com/watch?v=R33dzREZGEk LCD2USB attached to a beagleboard]<br />
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]<br />
* [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector]<br />
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle working with Linux 2.6.27]<br />
* Not on Beagle OMAP3530: [http://youtube.com/watch?v=5i9cWOK1spw Ubuntu 7.04 on on OMAP3430 SDP]<br />
* [http://in.youtube.com/watch?v=nADn_vNVEKw Beagle Board booting Android]<br />
* [http://www.youtube.com/watch?v=UHQdUS0i-nw Beagleboard, SGX, and libfreespace demo]<br />
<br />
==Beagle manufacturing==<br />
* [http://www.youtube.com/watch?v=C-CwkjT9z_0&feature=related Beagle Solder Paste Screening]<br />
* [http://www.youtube.com/watch?v=9LLjDovIG2M&feature=related Beagle Assembly Inspection]<br />
* [http://www.youtube.com/watch?v=sbOZfBnoVnM&feature=related Beagle Functional Test]<br />
* [http://www.youtube.com/watch?v=cvDtXmJJcEI&feature=related Beagle Reflow]<br />
* [http://www.youtube.com/watch?v=W2o4NTASxN0&feature=related Beagle Board Assembly at Circuitco]<br />
==Fun==<br />
* Enjoy [http://www.beaglegame.com/ BeagleGame]<br />
<br />
=Other OMAP boards=<br />
<br />
* OMAP1 OMAP5912 (ARM9 + C5x DSP) based [[OSK|OSK]] board.<br />
* OMAP3 OMAP3430 based [https://gforge.ti.com/gf/project/omapzoom/wiki/?pagename=HardwareInformation Zoom MDK], which has been superseded by the [http://www.logicpd.com/products/development-kits/texas-instruments-zoom%E2%84%A2-omap34x-ii-mdp Zoom II], and other [http://www.logicpd.com/products LogicPD kits].<br />
* OMAP3 OMAP3530 based [http://www.openpandora.org/ Pandora]<br />
* OMAP3 OMAP3503 based [http://www.gumstix.net/Overo/cat/Overo/115.html Gumstix Overo]<br />
* OMAP3 OMAP35x based EVM from [http://mistralsolutions.com/products/omap_3evm.php Mistral] and [http://focus.ti.com/docs/toolsw/folders/print/tmdxevm3503.html TI] (both are the same)<br />
* OMAP3 OMAP3430 based [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12013&contentId=28741 Software Development Platform (SDP)]<br />
* OMAP3 OMAP3530 based board from [http://www.magniel.com/omap3.html Magniel Inc.]<br />
* OMAP3 based [http://www.archos.com/products/imt/index.html?country=us&lang=en Archos 5, ARCHOS 5G and ARCHOS 7]<br />
* OMAP3 OMAP35x based [http://www.logicpd.com/products/som/ti/omap35x OMAP35x SOM-LV]<br />
* OMAP3 based [[Mini_Board|ICETEK-OMAP3530-Mini]], a Chinese BeagleBoard clone, with a [[MiniBoardFAQ|FAQ]]<br />
* OMAP3 based [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], a German BeagleBoard clone<br />
* OMAP3530 based [http://www.bsquare.com/products/hardware_solutions/3530.asp BSQUARE’s Dev Kit OMAP3530]<br />
* OMAP3530 based [http://beaversource.oregonstate.edu/projects/cspfl/wiki/CSPFL_Hardware OSWALD]<br />
* OMAP3 BeagleBoard-based [http://www.alwaysinnovating.com/touchbook/ Touch Book]<br />
* OMAP3530 based [http://www.analogue-micro.com/Cobra3530.html Cobra 3530 OMAP3530 module ]<br />
* OMAP3 based [http://www.kwikbyte.com/KBOC.html KwikByte 35XX System Module]<br />
* OMAP3530 based [[DevKit8000]], a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard)<br />
* OMAP3530 based [http://www.igep-platform.com/ IGEPv2 Platform], a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, wifi+bluetooth.<br />
* OMAP35x based [http://www.ultratronik.de/mmi-rechnerplattformen.html MMI4 from Ultratronik]<br />
* OMAP35x based [http://www.technexion.com/index.php/tao-3530 TAO-3530 from TechNexion]<br />
* OMAP35x based [http://www.variscite.com/varomap35xxsbc.html VAR-OM35xxSBC from Variscite]<br />
* OMAP35x based [[EGS3530]],a Chinese BeagleBoard clone from [http://www.ema-tech.com EMA]<br />
<br />
=Subpages=<br />
<splist<br />
parent=<br />
showparent=no<br />
sort=desc<br />
sortby=title<br />
liststyle=ordered<br />
showpath=no<br />
kidsonly=no<br />
debug=0<br />
/></div>Som2416https://elinux.org/index.php?title=SOM&diff=17080SOM2010-02-04T14:57:17Z<p>Som2416: /* fix error link */</p>
<hr />
<div>SOM: System On Module, also call '[[Embedded_computer]],[[Embedded_System_Module(ESM)]],Computer_on-Module(COM)', <br />
<br />
<br />
''SOMxxx'' Series Embedded Module: <b>Designed and manufactured by [http://www.techor.com/ TECHOR of China]. Series of Size 40x40x4mm, Weight about 10g, the smallest and lightest [[System-on-Module]] in the World! including:</b><br />
* [[SOM2416]] - by [http://www.techor.com/product-281.html TECHOR.COM of China], Samsung 400MHz ARM926EJ-S based cost effective [[Application Processor]]<br />
* [[SOM6410]] - by [http://www.techor.com/product-282.html TECHOR.COM of China],Samsung 667Hz ARM1176JFZ-S based cost effective [[Application Processor]]<br />
* [[SOM3530]] - by [http://www.techor.com/product_283.html TECHOR.COM of China], TI 720MHz [[CORETEX-A8]] + 600MHz TMS320DM64x+ dual core SOC<br />
* [[SOM3517|SOM3517/SOM3505]] - by [http://www.techor.com/product-286.html TECHOR.COM of China], TI [[CORETEX-A8]] SOC<br />
* [[SOMX35]] - by [http://www.techor.com/product-285.html TECHOR.COM of China], ARM1136 SOC from [http://www.freescale.com/webapp/sps/site/overview.jsp?code=IMX35_FAMILY Freescale IMX35 Family]<br />
* [[SOMC100]] - by [http://www.techor.com/product-284.html TECHOR.COM of China], ARM CORETEX-A8 SOC from [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S5PC100 Samsung S5PC100 Application Processor] <br />
* [[SOM168|SOM168/SOM166]] - by [http://www.techor.com/product-287.html TECHOR.COM of China], Marvell PXA168 SOC<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=Computer-on-Module&diff=17079Computer-on-Module2010-02-04T14:52:11Z<p>Som2416: /* Computer-on-Module Provider */</p>
<hr />
<div>A computer-on-module (COM) is a type of [http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Single-Board-Computer-SBC-Quick-Reference-Guide/ single-board computer](SBC), a subtype of an embedded computer system. It is also called [http://www.emacinc.com/som/som_select_guide.htm System on Module]System-on-Module as an extension of the concept of System on Chip (SoC) and lying between a full-up computer and a microcontroller in nature.<br />
<br />
Today's COM/SOM modules are complete computers built on a single circuit board. The design is centered on a single microprocessor with RAM, input/output controllers and all other features needed to be a functional computer on the one board. However, unlike a single-board computer, the COM module will usually lack the standard connectors for any input/output peripherals to be attached directly to the board. Instead, the wiring for these peripherals are bussed out to connectors on the board.<br />
<br />
The module will usually need to be mounted on a carrier board (or "baseboard") which breaks the bus out to standard peripheral connectors. Some COMs also include peripheral connectors and/or can be used without a carrier.<br />
<br />
A COM/SOM solution offers a dense package computer system for use in small or specialized applications requiring low power consumption or small physical size as is needed in embedded systems.<br />
<br />
Some devices also incorporate Field Programmable Gate Arrays.<br />
<br />
The terms "Computer-on-Module" and "COM" were coined by Venture Development Corporation (Natick, MA, USA) to describe this class of embedded computer boards. The term became more notable upon industry standardization of the COM Express format.<br />
<br />
A number of manufacturers offer products which are defined as system-on-module or computer-on-module. Among those are Advanced Knowledge Associates (www.a-k-a.net) in Santa Clara, CA; BCM Advanced Research (www.bcmcom.com) in Irvine, CA; Embedded Systems (www.embedded-systems.net); MEN Micro (www.menmicro.com) in Ambler, PA; DAVE Embedded Systems (www.dave.eu) in Italy.<br />
<br />
== Computer-on-Module Provider ==<br />
* SOM - by [http://www.techor.com/ TECHOR.COM of China], series of 40x40x4mm Size, Weight about 10g, the smallest and lightest [[System-on-Module]] in the World!<br />
* [[SOM2416]] - by [http://www.techor.com/product-281.html TECHOR.COM of China], Samsung 400MHz ARM926EJ-S based cost effective Application Processor<br />
* [[SOM6410]] - by [http://www.techor.com/product-282.html TECHOR.COM of China],Samsung 667Hz ARM1176JFZ-S based cost effective Application Processor<br />
* [[SOM3530]] - by [http://www.techor.com/product-283.html TECHOR.COM of China], TI 720MHz CORETEX-A8 + 600MHz TMS320DM64x+ dual core SOC<br />
* '''CSB7xx''' - by [http://www.cogcomp.com Cogent Computer Systems, Inc. of USA]<br />
* '''CM-XXX''' - by [http://www.compulab.co.il CompuLab of Italia]<br />
* '''Colibri Computer Modules''' - by [http://www.toradex.com Toradex of Switzerland]<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=SOM3530&diff=17023SOM35302010-02-01T15:49:34Z<p>Som2416: </p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOM3530&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.ti.com/ TI(Texas Instruments)'s] [http://www.arm.com/products/CPUs/ARM_Cortex-A8.html ARM Cortex-A8] + [https://focus.ti.com/general/docs/tags/fldrsfortagTemplate.tsp?&tagName=omap TMS320C64x+] based 720MHz [[OMAP3530]] [http://focus.ti.com/docs/prod/folders/print/omap3530.html Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product-283.html '''SOM3530''' System on Module]: [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
<br />
=Events=<br />
<I><br />
'''2010.1.1''': Mass supply of SOM3530[[System-on-Module]]: OMAP3530CUS(coretex-A8+64x), 128MB DDR, 128MB FLASH, eth, audio, usb, touch etc <br />
[[File:SOM3530-array.jpg ]]<br><br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/?product-283.html SOM3530] '''Rev PRELIMINARY''' will be released in Oct 30,2009! '''SOM3530''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
[[File:SOM3530msk.jpg|SOM3530 Engineering File, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]][[File:SOM3530-L.JPG|SOM3530 samples picture,Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
</I><br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
SOM3530: 720MHz OMAP3530 (Cortex-A8 + TMS320C64x) Mini Dual-Core Embedded Module (4x4cm)<br />
<br />
* OMAP3530/25/15/03:TI OMAP3XXX dual-core embedded module<br />
* size of SOM only 40x40x4mm<br />
* weight 11g<br />
* 1 USB master<br />
* 100M Ethernet<br />
* 3 UART<br />
* IIC<br />
* SPI<br />
* LCD & touchscreen interfaces<br />
* audio input and output<br />
* SDMMC<br />
* IO ports supporting ADC,PWM,GPIO<br />
* bus lines supporting data, address, interrupt, DMA, chip select and so on<br />
* SDKs avilable for wince5,wince6, LINUX 2.6 sdk<br />
<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOM3530 Revision ==<br />
==SOM3530-based products ==<br />
==SOM3530 ODM cases ==<br />
=App Demo Board =<br />
=Adapters =<br />
== Expansion boards ==<br />
<br />
<br><br />
<br><br />
----<br />
=SOM2530/KIT3530 FAQ=<br />
----<br />
<br />
主要描述基于KIT3530开发时所遇到的一些问题及解决方法。<br><br />
<br />
==硬件问题==<br />
=== 怎么让USB OTG口工作于主、从方式? ===<br />
A:在内核启动前,如果要让USB OTG工作于主方式,则板载USB OTG接套件提供的USB A型线;如果要让USB OTG工作于从方式,则板载USB OTG接套件提供的USB B型线。<br><br />
===问题->: 如何切换到MMC/SD启动开发板?===<br />
A:按住BOOT按键,上电启动,系统改为先从MMC/SD启动,再从NAND启动,详细请参考“3.18按键”介绍。<br><br />
<br />
=== KIT3530与仿真器相连接,调试DSP和ARM===<br />
目前正在找相关的仿真器,看有否可支持的仿真器系列。<br />
=== KIT3530中的RTC电池===<br />
KIT3530出货时不带RTC电池,需用户自行配备,电池型号用 CR1220即可<br />
=== KIT3530中的U20 (ISP1504) U13 (TXS0102)芯片问题 ===<br />
ISP1504 是USB HOST芯片,由于我们的USB HOST暂未调通,怀疑是硬件问题,故目前没有把此芯片焊上去。<br><br />
U13 (TXS0102) 是DVI的一个附带电路,但是此刻芯片未影响DVI的输出,故我们没有焊接此芯片,不影响DVI的使用。<br><br />
<br />
''the ISP1504 is for the USB HOST, but at now the USB HOST is not OK, so the board we sold don't have the chips.<br><br />
U13 (TXS0102) is not used for the dvi, and it don't effect your DVI output<br />
''<br />
<br />
==linux问题==<br />
=== 开发驱动时如何打开低层调试信息?===<br />
A:make menucofig -> kernel hacking -> lowlevel debug<br><br />
<br />
=== 如何让显示输出在lcd屏与DVI输出之间切换? ===<br />
A:只需修改内核启动参数即可.<br><br />
4.3” LCD屏:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode: 4.3inch_LCD<br><br />
5.6” LCD屏:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode: 5.6inch_LCD<br><br />
7” LCD屏:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:7inch_LCD<br><br />
DVI显示器:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:720p60<br><br />
VGA显示器:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:VGA<br><br />
<br />
===tftp更新方式===<br />
板上配置有10/100M自适应网卡dm9000,用户可通过tftp下载的方式更新nand启动映像<br><br />
1)x-loader启动映像的更新<br><br />
OMAP3 KIT3530 # tftp 80000000 x-load.bin.ift_for_NAND<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'x-load.bin.ift_for_NAND'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #<br><br />
done<br><br />
Bytes transferred = 9664 (25c0 hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 134217728!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc hw<br><br />
OMAP3 KIT3530 # nand erase 0 80000<br><br />
<br />
NAND erase: device 0 offset 0x0, size 0x80000<br><br />
Erasing at 0x60000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 0 80000<br><br />
<br />
NAND write: device 0 offset 0x0, size 0x80000<br><br />
<br />
Writing data at 0x7f800 -- 100% complete.<br><br />
524288 bytes written: OK<br><br />
<br />
2)u-boot启动映像的更新<br><br />
OMAP3 KIT3530 # tftp 80000000 flash-uboot.bin<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'flash-uboot.bin'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #################################################################<br><br />
done<br><br />
Bytes transferred = 1085536 (109060 hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 134217728!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc sw<br><br />
OMAP3 KIT3530 # nand erase 80000 160000<br><br />
<br />
NAND erase: device 0 offset 0x80000, size 0x160000<br><br />
Erasing at 0x1c0000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 80000 160000<br><br />
<br />
NAND write: device 0 offset 0x80000, size 0x160000<br><br />
<br />
Writing data at 0x1df800 -- 100% complete.<br><br />
1441792 bytes written: OK<br><br />
<br />
3)内核映像更新<br><br />
OMAP3 KIT3530 # tftp 80000000 uImage<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'uImage'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #################################################################<br><br />
done<br><br />
Bytes transferred = 1991900 (1e64dc hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 268435456!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc sw<br><br />
OMAP3 KIT3530 # nand erase 280000 200000<br><br />
<br />
NAND erase: device 0 offset 0x280000, size 0x200000<br><br />
Erasing at 0x460000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 280000 200000<br><br />
<br />
NAND write: device 0 offset 0x280000, size 0x200000<br><br />
<br />
Writing data at 0x47f800 -- 100% complete.<br><br />
2097152 bytes written: OK<br><br />
<br />
4)文件系统映像更新<br><br />
OMAP3 KIT3530 # tftp 80000000 ubi.img<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'ubi.img'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #################################################################<br><br />
done<br><br />
Bytes transferred = 12845056 (c40000 hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 268435456!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc sw<br><br />
OMAP3 KIT3530 # nand erase 680000 7980000<br><br />
<br />
NAND erase: device 0 offset 0x680000, size 0x7980000<br><br />
Erasing at 0x7fe0000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 680000 $(filesize)<br><br />
<br />
NAND write: device 0 offset 0x680000, size 0xc40000<br><br />
<br />
Writing data at 0x12bf800 -- 100% complete.<br><br />
12845056 bytes written: OK<br><br />
<br />
===linux交叉编译工具安装 ===<br />
1.网站下载交叉编译工具:<br />
http://www.codesourcery.com/sgpp/lite/arm/portal/package1787/public/arm-none-linux-gnueabi/arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 <br><br />
2.解压缩软件 <br><br />
sudo tar xvf arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 -C /home/ <br><br />
<br />
3. 工具安装<br><br />
mkdir /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/mkimage /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/signGP /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/mkfs.ubifs /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/ubinize /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/ ubinize.cfg /home/embest/tools<br><br />
<br />
4。设置环境变量<br><br />
export PATH=/home/arm-2007q3/bin/:/home/embest/tools:$PATH<br><br />
<br />
===linux摄像头显示模式转化 ===<br />
<br />
===OTG主口使用问题 ===<br />
USB使用方法:<br><br />
1. 连接USB hub电源到USB HUB<br><br />
2. 连接USB OTG转接线到KIT3530板上,<br><br />
3. 上电待开发板进入linux系统<br><br />
4. 插入usb hub线到USB OTG转接线上<br><br />
5.可以插入usb 鼠标键盘到hub了<br><br />
<br />
===7LCD触摸屏不准的解决方法===<br />
修改此文件arch/arm/mach-omap2/board-omap3KIT3530.c为如下数据即可<br><br />
struct ads7846_platform_data ads7846_conf = {<br><br />
.x_max = 0x0fff,<br><br />
.y_max = 0x0fff,<br><br />
//.x_plate_ohms = 180,<br><br />
//.pressure_max = 255,<br><br />
.debounce_max = 10,<br><br />
.debounce_tol = 5,<br><br />
.debounce_rep = 1,<br><br />
.get_pendown_state = ads7846_get_pendown_state,<br><br />
.keep_vref_on = 1,<br><br />
.settle_delay_usecs = 150,<br><br />
};<br><br />
<br />
===对于NFS,KIT3530 U-boot 下的配置参数===<br />
若您需要用NFS,首先需要在PC机上将NFS的服务打开,然后接上网线,打开KIT3530板子电源,在U-boot命令行里输入:<br>setenv bootargs console=ttyS2,115200n8 root=/dev/nfs nfsroot=192.192.192.117:/home/lijr/work/nfsroot/rootfs ip=192.192.192.200:192.192.192.101:192.192.192.101:255.255.255.0:KIT3530:eth0:off<br />
<br />
==wince问题==<br />
=== 烧写wince到NAND Flash系统映像更新===<br />
1.更新文件准备<br><br />
(1) 用软件HP Disk Storage Format Tool格式化SD卡为FAT或FAT32文件系统。<br><br />
(2) 拷贝光盘目录image[\wince_6]下子目录dvi1280X720或lcd480X272下文件MLO、EBOOTNAND.nb0、NK.bin、XLDRNAND.nb0和ADevKit9000.exe到SD卡并重命名EBOOTNAND.nb0为EBOOTSD.nb0<br><br />
2. 映像更新<br><br />
(1) 按住BOOT键,后插入SD卡重新启动系统。这时系统从SD卡启动。超级终端输出启动打印信息,按[SPACE]进入EBOOT菜单。<br><br />
(2) 按[5]进入Flash管理菜单。<br><br />
(3) 分别按[a]、[b]和[c],写XLDR、EBOOT和NK映像。<br><br />
(4) 然后按[0]键回到主菜单,并分别按下[2]、[4]、[7]和[y]更改启动设备。<br><br />
(5) 拔除SD卡,后重新启动系统。这时系统将从NAND Flash启动。<br><br />
英文显示<br><br />
the method to Update the image for NAND Flash<br><br />
(1)Run the software of HP Disk Storage Format Tool and format the SD card for FAT or FAT32 filesystem.<br><br />
(2) Copy the image file(MLO, EBOOTNAND.nb0, NK.bin, AKIT3530.exe) from CD:\wince_6\image\ lcd480X272 to SD card, then change the name from EBOOTNAND.nb0 to EBOOTSD.nb0 in the SD card.<br><br />
(3) Insert the SD card to the board, press the BOOT button and then power on the board again; HyperTerminal will start printing the output information, at the same time press [SPACE] to enter the EBOOT menu.<br><br />
(4) Press [5] to enter the Flash manage menu.<br><br />
(5) Press [a], [b], [c] separately to write the image(XLDR, EBOOT, NK) to flash.<br><br />
(6) Press [0] to return to the main menu, and press [2], [4], [7], [7] to change the boot device.<br><br />
(7) Power on the system again, and then the board will boot from the NAND flash. <br><br />
<br />
=== 屏蔽WinCE启动后的触摸屏打印信息===<br />
修改函数KIT3530\SRC\DRIVERS\TOUCH\touchscreen.cpp,<br />
把564行 RETAILMSG(1, ( TEXT( "Point: (%d,%d)\r\n" ), *pUncalX, *pUncalY ) );<br />
屏蔽掉然后重新编译就行了。如下所示:<br />
//RETAILMSG(1, ( TEXT( "Point: (%d,%d)\r\n" ), *pUncalX, *pUncalY ) );<br />
=== 关闭调试串口打印===<br />
setp: <br><br />
1,commnent out the RETAILMSG call in TouchDriverCalibrationPointGet function of touchscreen.cpp <br><br />
2,commnent out the RETAILMSG call in DdsiTouchPanelGetPoint function of touchscreen.cpp <br><br />
3,commnent out the RETAILMSG call in TLED_Backlight::SetPowerState function of tled_backlight.cpp <br><br />
4,commnent out the RETAILMSG call in SetDutyCycle function of tled.cpp <br><br />
5,commnent out the RETAILMSG call in LcdPdd_LCD_Initialize function of lcd_vga.c <br><br />
6,make sure that "set BSP_NOCOM=" is not set in KIT3530.bat <br><br />
7,make sure that "set BSP_NOCOM3=" is not set in KIT3530.bat <br><br />
8,delete the "IF BSP_COM3" of _FLATRELEASEDIR/platform.reg in line 1103 <br><br />
9,delete the "ENDIF BSP_COM3" of _FLATRELEASEDIR/platform.reg in line 1124 <br><br />
10,rebuilt the BSP <br><br />
=== 关闭触摸屏校准===<br />
setp: <br><br />
在BSP包的一级目录下,有KIT3530.bat文件,在其中任一行添加:<br><br />
set IMGNOCALIBRATION=1<br><br />
然后重新build编译即可<br />
<br />
===关于触摸屏不能用的问题解决方法===<br />
是编译时使用 build and sysgen导致的,在wince下不能用bulid and sysgen编译,用它就出问题,而且必须把pb6.0重装才可以<br />
<br />
=== WINCE无法存储===<br />
在SRC\DRIVERS\BLOCK\NAND\nand_MT29F2G16.h<br />
把下面这句<br />
#define NUMBER_OF_BLOCKS (2048) // 2048 blocks<br />
改成<br />
#define NUMBER_OF_BLOCKS (1024) // 1024 blocks<br />
<br />
=== WINCE无法设置时间===<br />
1,把新的rtc.c替换原来的src/oal/oalrtc/rtc.c(可询问技术人员提供)<br />
2,在src/inc/bsp_cfg.h后面加上#define BSP_OAL_RTC_USES_TWL4030 TRUE<br />
<br />
==其他问题==<br />
=== 格式化工具下载===<br />
网址:http://www.embedinfo.com/english/download/SP27213.exe<br />
<br />
=== SD卡不能启动===<br />
推荐使用HP USB Disk Storage Format Tool 2.0.6:下载下列网址工具<br><br />
http://www.embedinfo.com/english/download/SP27213.exe<br><br />
安装后执行如下操作。<br><br />
1、把MMC/SD卡插入PC下读卡器中<br><br />
2、打开HP USB Disk Storage Format Tool <br><br />
3、选择”FAT32“系统格式<br><br />
4、点击”Start”<br><br />
5、等待格式化完成,点击”OK”<br><br />
6、把映像文件拷贝到SD卡中。<br><br />
<English><br><br />
you should downlod the tools<br><br />
http://www.embedinfo.com/english/download/SP27213.exe<br><br />
then format your SD card for the fat32,then copy the file to it, then it can be booted.<br><br />
<br />
=== 提供demo配套u-boot.bin无法修改参数===<br />
提供demo配套u-boot.bin无法修改参数,用户想要修改并保存u-boot下参数,可采用KIT3530提供u-boot源码,修改传递给内核的MACH_ID,重新编译即可。<br><br />
具体操作方法:<br><br />
1、u-boot-1.3.3源码中<br><br />
修改board/omap3KIT3530/omap3KIT3530.c文件<br><br />
找到board_init函数<br><br />
修改:<br><br />
gd->bd->bi_arch_number = MACH_TYPE_KIT3530;为<br><br />
gd->bd->bi_arch_number = XXX;<br><br />
<br />
2、重新编译u-boot<br><br />
<br />
注:<br />
1、对于angstrom,XXX为MACH_TYPE_KIT3530<br />
2、对于android,XXX为MACH_TYPE_OMAP3_BEAGLE<br />
3、对于dvsdk,XXX为MACH_TYPE_OMAP3EVM<br />
<br />
=== KIT3530跑QT程序鼠标不工作===<br />
内核目录下输入make menuconfig,添加如下配置:<br />
<br />
Device Drivers ---><br />
Input device support ---><br />
<br />
<*>Mouse interface <br />
<br />
[*]Provide legacy /dev/psaux device <br />
<br />
(1024) Horizontal screen resolution <br />
<br />
(768) Vertical screen resolution<br />
<br />
[*] Mice ---><br />
<br />
=== 解决android demo系统下静态ip的分配问题===<br />
进入系统后,串口终端下输入:<br />
<br />
ifconfig eth0 192.192.192.90<br />
<br />
ifconfig eth0 up<br />
<br />
route add default gw 192.192.192.101 dev eth0<br />
<br />
setprop net.dns1 202.96.134.133<br />
<br />
注:<br />
客户可根据实际情况修改以上ip地址。<br />
<br />
<br />
----<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOM6410&diff=17022SOM64102010-02-01T15:46:25Z<p>Som2416: </p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOM6410&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.samsung.com/global/business/semiconductor SAMSUNG semiconductor's] [http://www.arm.com/products/CPUs/ARM1176.html ARM1176JZF-S] based up-to 667MHz [[S3C6410]] [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C6410 Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product-282.html '''SOM6410'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
=Events=<br />
<I><br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product-282.html SOM6410] '''Rev PRELIMINARY''' will be released in Oct 30,2009! '''SOM6410''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
[[File:SOM6410msk.jpg|SOM6410 engineering picture, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]][[File:SOM6410-L.JPG|SOM6410 actual sample picture, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
</I><br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOM6410 Revision ==<br />
==SOM6410-based products ==<br />
==SOM6410 ODM cases ==<br />
=5 App Demo Board =<br />
=6 Adapters =<br />
== Expansion boards ==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOMX35&diff=17021SOMX352010-02-01T15:44:14Z<p>Som2416: </p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOMX35&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.freescale.com Freescale semiconductor's] [http://www.arm.com/products/CPUs/ ARM1136] based up-to 667MHz [http://www.freescale.com/webapp/sps/site/overview.jsp?code=IMX35_FAMILY MX35] Application Processors engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product-284.html '''SOMX35'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
=Events=<br />
<I><br />
'''2010.2.1''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product-284.html SOMX35] '''Rev PRELIMINARY''' released in Feb 1, 2010! '''SOMX35''' is SODIMM-244 pin System-on-Module, suitable for highend control, Automotive, Automobile etc.<br />
[[File:MX357-640X480-mark.JPG|SOMX35picture]]<br />
</I><br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOMX35 Revision ==<br />
==SOMX35-based products ==<br />
==SOMX35 ODM cases ==<br />
=5 App Demo Board =<br />
=6 Adapters =<br />
== Expansion boards ==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOM6410&diff=17020SOM64102010-02-01T15:40:31Z<p>Som2416: /* Events */</p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOM6410&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.samsung.com/global/business/semiconductor SAMSUNG semiconductor's] [http://www.arm.com/products/CPUs/ARM1176.html ARM1176JZF-S] based up-to 667MHz [[S3C6410]] [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C6410 Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_282.html '''SOM6410'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
=Events=<br />
<I><br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product-283.html SOM6410] '''Rev PRELIMINARY''' will be released in Oct 30,2009! '''SOM6410''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
[[File:SOM6410msk.jpg|SOM6410 engineering picture, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]][[File:SOM6410-L.JPG|SOM6410 actual sample picture, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
</I><br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOM6410 Revision ==<br />
==SOM6410-based products ==<br />
==SOM6410 ODM cases ==<br />
=5 App Demo Board =<br />
=6 Adapters =<br />
== Expansion boards ==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOMX35&diff=17019SOMX352010-02-01T15:38:45Z<p>Som2416: /* Events */</p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOMX35&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.freescale.com Freescale semiconductor's] [http://www.arm.com/products/CPUs/ ARM1136] based up-to 667MHz [http://www.freescale.com/webapp/sps/site/overview.jsp?code=IMX35_FAMILY MX35] Application Processors engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_285.html '''SOMX35'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
=Events=<br />
<I><br />
'''2010.2.1''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product-284.html SOMX35] '''Rev PRELIMINARY''' released in Feb 1, 2010! '''SOMX35''' is SODIMM-244 pin System-on-Module, suitable for highend control, Automotive, Automobile etc.<br />
[[File:MX357-640X480-mark.JPG|SOMX35picture]]<br />
</I><br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOMX35 Revision ==<br />
==SOMX35-based products ==<br />
==SOMX35 ODM cases ==<br />
=5 App Demo Board =<br />
=6 Adapters =<br />
== Expansion boards ==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOMX35&diff=17018SOMX352010-02-01T15:36:36Z<p>Som2416: /* Events */</p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOMX35&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.freescale.com Freescale semiconductor's] [http://www.arm.com/products/CPUs/ ARM1136] based up-to 667MHz [http://www.freescale.com/webapp/sps/site/overview.jsp?code=IMX35_FAMILY MX35] Application Processors engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_285.html '''SOMX35'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
=Events=<br />
<I><br />
'''2010.2.1''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_284.html SOMX35] '''Rev PRELIMINARY''' released in Feb 1, 2010! '''SOMX35''' is SODIMM-244 pin System-on-Module, suitable for highend control, Automotive, Automobile etc.<br />
[[File:MX357-640X480-mark.JPG|SOMX35picture]]<br />
</I><br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOMX35 Revision ==<br />
==SOMX35-based products ==<br />
==SOMX35 ODM cases ==<br />
=5 App Demo Board =<br />
=6 Adapters =<br />
== Expansion boards ==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=File:MX357-640X480-mark.JPG&diff=17017File:MX357-640X480-mark.JPG2010-02-01T15:34:59Z<p>Som2416: SOMX357: powered by techor.com</p>
<hr />
<div>SOMX357: powered by techor.com</div>Som2416https://elinux.org/index.php?title=SOM3530&diff=16155SOM35302010-01-21T09:11:06Z<p>Som2416: /* Events */</p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOM3530&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.ti.com/ TI(Texas Instruments)'s] [http://www.arm.com/products/CPUs/ARM_Cortex-A8.html ARM Cortex-A8] + [https://focus.ti.com/general/docs/tags/fldrsfortagTemplate.tsp?&tagName=omap TMS320C64x+] based 720MHz [[OMAP3530]] [http://focus.ti.com/docs/prod/folders/print/omap3530.html Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_283.html '''SOM3530''']: [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
<br />
=Events=<br />
<I><br />
'''2010.1.1''': Mass supply of SOM3530[[System-on-Module]]: OMAP3530CUS(coretex-A8+64x), 128MB DDR, 128MB FLASH, eth, audio, usb, touch etc <br />
[[File:SOM3530-array.jpg ]]<br><br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/?product-283.html SOM3530] '''Rev PRELIMINARY''' will be released in Oct 30,2009! '''SOM3530''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
[[File:SOM3530msk.jpg|SOM3530 Engineering File, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]][[File:SOM3530-L.JPG|SOM3530 samples picture,Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
</I><br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
SOM3530: 720MHz OMAP3530 (Cortex-A8 + TMS320C64x) Mini Dual-Core Embedded Module (4x4cm)<br />
<br />
* OMAP3530/25/15/03:TI OMAP3XXX dual-core embedded module<br />
* size of SOM only 40x40x4mm<br />
* weight 11g<br />
* 1 USB master<br />
* 100M Ethernet<br />
* 3 UART<br />
* IIC<br />
* SPI<br />
* LCD & touchscreen interfaces<br />
* audio input and output<br />
* SDMMC<br />
* IO ports supporting ADC,PWM,GPIO<br />
* bus lines supporting data, address, interrupt, DMA, chip select and so on<br />
* SDKs avilable for wince5,wince6, LINUX 2.6 sdk<br />
<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOM3530 Revision ==<br />
==SOM3530-based products ==<br />
==SOM3530 ODM cases ==<br />
=App Demo Board =<br />
=Adapters =<br />
== Expansion boards ==<br />
<br />
<br><br />
<br><br />
----<br />
=SOM2530/KIT3530 FAQ=<br />
----<br />
<br />
主要描述基于KIT3530开发时所遇到的一些问题及解决方法。<br><br />
<br />
==硬件问题==<br />
=== 怎么让USB OTG口工作于主、从方式? ===<br />
A:在内核启动前,如果要让USB OTG工作于主方式,则板载USB OTG接套件提供的USB A型线;如果要让USB OTG工作于从方式,则板载USB OTG接套件提供的USB B型线。<br><br />
===问题->: 如何切换到MMC/SD启动开发板?===<br />
A:按住BOOT按键,上电启动,系统改为先从MMC/SD启动,再从NAND启动,详细请参考“3.18按键”介绍。<br><br />
<br />
=== KIT3530与仿真器相连接,调试DSP和ARM===<br />
目前正在找相关的仿真器,看有否可支持的仿真器系列。<br />
=== KIT3530中的RTC电池===<br />
KIT3530出货时不带RTC电池,需用户自行配备,电池型号用 CR1220即可<br />
=== KIT3530中的U20 (ISP1504) U13 (TXS0102)芯片问题 ===<br />
ISP1504 是USB HOST芯片,由于我们的USB HOST暂未调通,怀疑是硬件问题,故目前没有把此芯片焊上去。<br><br />
U13 (TXS0102) 是DVI的一个附带电路,但是此刻芯片未影响DVI的输出,故我们没有焊接此芯片,不影响DVI的使用。<br><br />
<br />
''the ISP1504 is for the USB HOST, but at now the USB HOST is not OK, so the board we sold don't have the chips.<br><br />
U13 (TXS0102) is not used for the dvi, and it don't effect your DVI output<br />
''<br />
<br />
==linux问题==<br />
=== 开发驱动时如何打开低层调试信息?===<br />
A:make menucofig -> kernel hacking -> lowlevel debug<br><br />
<br />
=== 如何让显示输出在lcd屏与DVI输出之间切换? ===<br />
A:只需修改内核启动参数即可.<br><br />
4.3” LCD屏:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode: 4.3inch_LCD<br><br />
5.6” LCD屏:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode: 5.6inch_LCD<br><br />
7” LCD屏:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:7inch_LCD<br><br />
DVI显示器:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:720p60<br><br />
VGA显示器:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:VGA<br><br />
<br />
===tftp更新方式===<br />
板上配置有10/100M自适应网卡dm9000,用户可通过tftp下载的方式更新nand启动映像<br><br />
1)x-loader启动映像的更新<br><br />
OMAP3 KIT3530 # tftp 80000000 x-load.bin.ift_for_NAND<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'x-load.bin.ift_for_NAND'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #<br><br />
done<br><br />
Bytes transferred = 9664 (25c0 hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 134217728!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc hw<br><br />
OMAP3 KIT3530 # nand erase 0 80000<br><br />
<br />
NAND erase: device 0 offset 0x0, size 0x80000<br><br />
Erasing at 0x60000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 0 80000<br><br />
<br />
NAND write: device 0 offset 0x0, size 0x80000<br><br />
<br />
Writing data at 0x7f800 -- 100% complete.<br><br />
524288 bytes written: OK<br><br />
<br />
2)u-boot启动映像的更新<br><br />
OMAP3 KIT3530 # tftp 80000000 flash-uboot.bin<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'flash-uboot.bin'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #################################################################<br><br />
done<br><br />
Bytes transferred = 1085536 (109060 hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 134217728!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc sw<br><br />
OMAP3 KIT3530 # nand erase 80000 160000<br><br />
<br />
NAND erase: device 0 offset 0x80000, size 0x160000<br><br />
Erasing at 0x1c0000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 80000 160000<br><br />
<br />
NAND write: device 0 offset 0x80000, size 0x160000<br><br />
<br />
Writing data at 0x1df800 -- 100% complete.<br><br />
1441792 bytes written: OK<br><br />
<br />
3)内核映像更新<br><br />
OMAP3 KIT3530 # tftp 80000000 uImage<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'uImage'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #################################################################<br><br />
done<br><br />
Bytes transferred = 1991900 (1e64dc hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 268435456!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc sw<br><br />
OMAP3 KIT3530 # nand erase 280000 200000<br><br />
<br />
NAND erase: device 0 offset 0x280000, size 0x200000<br><br />
Erasing at 0x460000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 280000 200000<br><br />
<br />
NAND write: device 0 offset 0x280000, size 0x200000<br><br />
<br />
Writing data at 0x47f800 -- 100% complete.<br><br />
2097152 bytes written: OK<br><br />
<br />
4)文件系统映像更新<br><br />
OMAP3 KIT3530 # tftp 80000000 ubi.img<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'ubi.img'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #################################################################<br><br />
done<br><br />
Bytes transferred = 12845056 (c40000 hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 268435456!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc sw<br><br />
OMAP3 KIT3530 # nand erase 680000 7980000<br><br />
<br />
NAND erase: device 0 offset 0x680000, size 0x7980000<br><br />
Erasing at 0x7fe0000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 680000 $(filesize)<br><br />
<br />
NAND write: device 0 offset 0x680000, size 0xc40000<br><br />
<br />
Writing data at 0x12bf800 -- 100% complete.<br><br />
12845056 bytes written: OK<br><br />
<br />
===linux交叉编译工具安装 ===<br />
1.网站下载交叉编译工具:<br />
http://www.codesourcery.com/sgpp/lite/arm/portal/package1787/public/arm-none-linux-gnueabi/arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 <br><br />
2.解压缩软件 <br><br />
sudo tar xvf arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 -C /home/ <br><br />
<br />
3. 工具安装<br><br />
mkdir /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/mkimage /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/signGP /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/mkfs.ubifs /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/ubinize /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/ ubinize.cfg /home/embest/tools<br><br />
<br />
4。设置环境变量<br><br />
export PATH=/home/arm-2007q3/bin/:/home/embest/tools:$PATH<br><br />
<br />
===linux摄像头显示模式转化 ===<br />
<br />
===OTG主口使用问题 ===<br />
USB使用方法:<br><br />
1. 连接USB hub电源到USB HUB<br><br />
2. 连接USB OTG转接线到KIT3530板上,<br><br />
3. 上电待开发板进入linux系统<br><br />
4. 插入usb hub线到USB OTG转接线上<br><br />
5.可以插入usb 鼠标键盘到hub了<br><br />
<br />
===7LCD触摸屏不准的解决方法===<br />
修改此文件arch/arm/mach-omap2/board-omap3KIT3530.c为如下数据即可<br><br />
struct ads7846_platform_data ads7846_conf = {<br><br />
.x_max = 0x0fff,<br><br />
.y_max = 0x0fff,<br><br />
//.x_plate_ohms = 180,<br><br />
//.pressure_max = 255,<br><br />
.debounce_max = 10,<br><br />
.debounce_tol = 5,<br><br />
.debounce_rep = 1,<br><br />
.get_pendown_state = ads7846_get_pendown_state,<br><br />
.keep_vref_on = 1,<br><br />
.settle_delay_usecs = 150,<br><br />
};<br><br />
<br />
===对于NFS,KIT3530 U-boot 下的配置参数===<br />
若您需要用NFS,首先需要在PC机上将NFS的服务打开,然后接上网线,打开KIT3530板子电源,在U-boot命令行里输入:<br>setenv bootargs console=ttyS2,115200n8 root=/dev/nfs nfsroot=192.192.192.117:/home/lijr/work/nfsroot/rootfs ip=192.192.192.200:192.192.192.101:192.192.192.101:255.255.255.0:KIT3530:eth0:off<br />
<br />
==wince问题==<br />
=== 烧写wince到NAND Flash系统映像更新===<br />
1.更新文件准备<br><br />
(1) 用软件HP Disk Storage Format Tool格式化SD卡为FAT或FAT32文件系统。<br><br />
(2) 拷贝光盘目录image[\wince_6]下子目录dvi1280X720或lcd480X272下文件MLO、EBOOTNAND.nb0、NK.bin、XLDRNAND.nb0和ADevKit9000.exe到SD卡并重命名EBOOTNAND.nb0为EBOOTSD.nb0<br><br />
2. 映像更新<br><br />
(1) 按住BOOT键,后插入SD卡重新启动系统。这时系统从SD卡启动。超级终端输出启动打印信息,按[SPACE]进入EBOOT菜单。<br><br />
(2) 按[5]进入Flash管理菜单。<br><br />
(3) 分别按[a]、[b]和[c],写XLDR、EBOOT和NK映像。<br><br />
(4) 然后按[0]键回到主菜单,并分别按下[2]、[4]、[7]和[y]更改启动设备。<br><br />
(5) 拔除SD卡,后重新启动系统。这时系统将从NAND Flash启动。<br><br />
英文显示<br><br />
the method to Update the image for NAND Flash<br><br />
(1)Run the software of HP Disk Storage Format Tool and format the SD card for FAT or FAT32 filesystem.<br><br />
(2) Copy the image file(MLO, EBOOTNAND.nb0, NK.bin, AKIT3530.exe) from CD:\wince_6\image\ lcd480X272 to SD card, then change the name from EBOOTNAND.nb0 to EBOOTSD.nb0 in the SD card.<br><br />
(3) Insert the SD card to the board, press the BOOT button and then power on the board again; HyperTerminal will start printing the output information, at the same time press [SPACE] to enter the EBOOT menu.<br><br />
(4) Press [5] to enter the Flash manage menu.<br><br />
(5) Press [a], [b], [c] separately to write the image(XLDR, EBOOT, NK) to flash.<br><br />
(6) Press [0] to return to the main menu, and press [2], [4], [7], [7] to change the boot device.<br><br />
(7) Power on the system again, and then the board will boot from the NAND flash. <br><br />
<br />
=== 屏蔽WinCE启动后的触摸屏打印信息===<br />
修改函数KIT3530\SRC\DRIVERS\TOUCH\touchscreen.cpp,<br />
把564行 RETAILMSG(1, ( TEXT( "Point: (%d,%d)\r\n" ), *pUncalX, *pUncalY ) );<br />
屏蔽掉然后重新编译就行了。如下所示:<br />
//RETAILMSG(1, ( TEXT( "Point: (%d,%d)\r\n" ), *pUncalX, *pUncalY ) );<br />
=== 关闭调试串口打印===<br />
setp: <br><br />
1,commnent out the RETAILMSG call in TouchDriverCalibrationPointGet function of touchscreen.cpp <br><br />
2,commnent out the RETAILMSG call in DdsiTouchPanelGetPoint function of touchscreen.cpp <br><br />
3,commnent out the RETAILMSG call in TLED_Backlight::SetPowerState function of tled_backlight.cpp <br><br />
4,commnent out the RETAILMSG call in SetDutyCycle function of tled.cpp <br><br />
5,commnent out the RETAILMSG call in LcdPdd_LCD_Initialize function of lcd_vga.c <br><br />
6,make sure that "set BSP_NOCOM=" is not set in KIT3530.bat <br><br />
7,make sure that "set BSP_NOCOM3=" is not set in KIT3530.bat <br><br />
8,delete the "IF BSP_COM3" of _FLATRELEASEDIR/platform.reg in line 1103 <br><br />
9,delete the "ENDIF BSP_COM3" of _FLATRELEASEDIR/platform.reg in line 1124 <br><br />
10,rebuilt the BSP <br><br />
=== 关闭触摸屏校准===<br />
setp: <br><br />
在BSP包的一级目录下,有KIT3530.bat文件,在其中任一行添加:<br><br />
set IMGNOCALIBRATION=1<br><br />
然后重新build编译即可<br />
<br />
===关于触摸屏不能用的问题解决方法===<br />
是编译时使用 build and sysgen导致的,在wince下不能用bulid and sysgen编译,用它就出问题,而且必须把pb6.0重装才可以<br />
<br />
=== WINCE无法存储===<br />
在SRC\DRIVERS\BLOCK\NAND\nand_MT29F2G16.h<br />
把下面这句<br />
#define NUMBER_OF_BLOCKS (2048) // 2048 blocks<br />
改成<br />
#define NUMBER_OF_BLOCKS (1024) // 1024 blocks<br />
<br />
=== WINCE无法设置时间===<br />
1,把新的rtc.c替换原来的src/oal/oalrtc/rtc.c(可询问技术人员提供)<br />
2,在src/inc/bsp_cfg.h后面加上#define BSP_OAL_RTC_USES_TWL4030 TRUE<br />
<br />
==其他问题==<br />
=== 格式化工具下载===<br />
网址:http://www.embedinfo.com/english/download/SP27213.exe<br />
<br />
=== SD卡不能启动===<br />
推荐使用HP USB Disk Storage Format Tool 2.0.6:下载下列网址工具<br><br />
http://www.embedinfo.com/english/download/SP27213.exe<br><br />
安装后执行如下操作。<br><br />
1、把MMC/SD卡插入PC下读卡器中<br><br />
2、打开HP USB Disk Storage Format Tool <br><br />
3、选择”FAT32“系统格式<br><br />
4、点击”Start”<br><br />
5、等待格式化完成,点击”OK”<br><br />
6、把映像文件拷贝到SD卡中。<br><br />
<English><br><br />
you should downlod the tools<br><br />
http://www.embedinfo.com/english/download/SP27213.exe<br><br />
then format your SD card for the fat32,then copy the file to it, then it can be booted.<br><br />
<br />
=== 提供demo配套u-boot.bin无法修改参数===<br />
提供demo配套u-boot.bin无法修改参数,用户想要修改并保存u-boot下参数,可采用KIT3530提供u-boot源码,修改传递给内核的MACH_ID,重新编译即可。<br><br />
具体操作方法:<br><br />
1、u-boot-1.3.3源码中<br><br />
修改board/omap3KIT3530/omap3KIT3530.c文件<br><br />
找到board_init函数<br><br />
修改:<br><br />
gd->bd->bi_arch_number = MACH_TYPE_KIT3530;为<br><br />
gd->bd->bi_arch_number = XXX;<br><br />
<br />
2、重新编译u-boot<br><br />
<br />
注:<br />
1、对于angstrom,XXX为MACH_TYPE_KIT3530<br />
2、对于android,XXX为MACH_TYPE_OMAP3_BEAGLE<br />
3、对于dvsdk,XXX为MACH_TYPE_OMAP3EVM<br />
<br />
=== KIT3530跑QT程序鼠标不工作===<br />
内核目录下输入make menuconfig,添加如下配置:<br />
<br />
Device Drivers ---><br />
Input device support ---><br />
<br />
<*>Mouse interface <br />
<br />
[*]Provide legacy /dev/psaux device <br />
<br />
(1024) Horizontal screen resolution <br />
<br />
(768) Vertical screen resolution<br />
<br />
[*] Mice ---><br />
<br />
=== 解决android demo系统下静态ip的分配问题===<br />
进入系统后,串口终端下输入:<br />
<br />
ifconfig eth0 192.192.192.90<br />
<br />
ifconfig eth0 up<br />
<br />
route add default gw 192.192.192.101 dev eth0<br />
<br />
setprop net.dns1 202.96.134.133<br />
<br />
注:<br />
客户可根据实际情况修改以上ip地址。<br />
<br />
<br />
----<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=File:SOM3530-array.jpg&diff=16154File:SOM3530-array.jpg2010-01-21T09:07:02Z<p>Som2416: Mass supply of SOM3530: OMAP3530CUS(coretex-A8+64x), 128MB DDR, 128MB FLASH, eth, audio, usb, touch etc</p>
<hr />
<div>Mass supply of SOM3530: OMAP3530CUS(coretex-A8+64x), 128MB DDR, 128MB FLASH, eth, audio, usb, touch etc</div>Som2416https://elinux.org/index.php?title=SOMs&diff=14970SOMs2009-11-28T17:40:42Z<p>Som2416: /* Initial by techor.com */</p>
<hr />
<div>#REDIRECT [[SOM]]</div>Som2416https://elinux.org/index.php?title=SOM3517&diff=14969SOM35172009-11-28T17:37:44Z<p>Som2416: /* Initial by techor.com */</p>
<hr />
<div>SOM3517/SOM3505 - by TECHOR.COM of China, TI Industrial SOC based on Single ARM CORTEC-A8/A9 SOC<br />
Retrieved from "http://elinux.org/SOM"<br />
<br />
<br />
To be created by TECHOR.COM...<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOM168&diff=14968SOM1682009-11-28T17:35:35Z<p>Som2416: /* Initial by techor.com */</p>
<hr />
<div>SOM168/SOM166 - by TECHOR.COM of China, Marvell PXA168 SOC <br />
Retrieved from "http://elinux.org/SOM"<br />
<br />
<br />
To be created by TECHOR.COM...<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOM&diff=14967SOM2009-11-28T17:32:47Z<p>Som2416: </p>
<hr />
<div>SOM: System On Module, also call '[[Embedded_computer]],[[Embedded_System_Module(ESM)]],Computer_on-Module(COM)', <br />
<br />
<br />
''SOMxxx'' Series Embedded Module: <b>Designed and manufactured by [http://www.techor.com/ TECHOR of China]. Series of Size 40x40x4mm, Weight about 10g, the smallest and lightest [[System-on-Module]] in the World! including:</b><br />
* [[SOM2416]] - by [http://www.techor.com/product_281.html TECHOR.COM of China], Samsung 400MHz ARM926EJ-S based cost effective [[Application Processor]]<br />
* [[SOM6410]] - by [http://www.techor.com/product_282.html TECHOR.COM of China],Samsung 667Hz ARM1176JFZ-S based cost effective [[Application Processor]]<br />
* [[SOM3530]] - by [http://www.techor.com/product_283.html TECHOR.COM of China], TI 720MHz [[CORETEX-A8]] + 600MHz TMS320DM64x+ dual core SOC<br />
* [[SOM3517|SOM3517/SOM3505]] - by [http://www.techor.com/product_286.html TECHOR.COM of China], TI [[CORETEX-A8]] SOC<br />
* [[SOMX35]] - by [http://www.techor.com/product_285.html TECHOR.COM of China], ARM1136 SOC from [http://www.freescale.com/webapp/sps/site/overview.jsp?code=IMX35_FAMILY Freescale IMX35 Family]<br />
* [[SOMC100]] - by [http://www.techor.com/product_284.html TECHOR.COM of China], ARM CORETEX-A8 SOC from [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S5PC100 Samsung S5PC100 Application Processor] <br />
* [[SOM168|SOM168/SOM166]] - by [http://www.techor.com/product_287.html TECHOR.COM of China], Marvell PXA168 SOC<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=SOM&diff=14966SOM2009-11-28T17:32:12Z<p>Som2416: </p>
<hr />
<div>SOM: System On Module, also call '[[Embedded_computer]],[[Embedded_System_Module(ESM)]],Computer_on-Module(COM)', <br />
<br />
<br />
''SOMxxx'' Series Embedded Module: <b>Designed and manufactured by [http://www.techor.com/ TECHOR of China]. Series of Size 40x40x4mm, Weight about 10g, the smallest and lightest [[System-on-Module]] in the World! including:</b><br />
* [[SOM2416]] - by [http://www.techor.com/product_281.html TECHOR.COM of China], Samsung 400MHz ARM926EJ-S based cost effective [[Application Processor]]<br />
* [[SOM6410]] - by [http://www.techor.com/product_282.html TECHOR.COM of China],Samsung 667Hz ARM1176JFZ-S based cost effective [[Application Processor]]<br />
* [[SOM3530]] - by [http://www.techor.com/product_283.html TECHOR.COM of China], TI 720MHz [[CORETEX-A8]] + 600MHz TMS320DM64x+ dual core SOC<br />
* [[SOM3517|SOM3517/SOM3505]] - by [http://www.techor.com/product_286.html TECHOR.COM of China], TI [[CORETEX-A8]] SOC<br />
* [[SOMX35]] - by [http://www.techor.com/product_285.html TECHOR.COM of China], ARM1136 SOC from [http://www.freescale.com/webapp/sps/site/overview.jsp?code=IMX35_FAMILY Freescale IMX35 Family]<br />
* [[SOMC100]] - by [http://www.techor.com/product_284.html TECHOR.COM of China], ARM CORETEX-A8 SOC from [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S5PC100 Samsung S5PC100 Application Processor] <br />
* [[SOM168]] - by [http://www.techor.com/product_287.html TECHOR.COM of China], Marvell PXA168 SOC<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=SOM&diff=14965SOM2009-11-28T17:30:30Z<p>Som2416: /* add PXA168, AM3517/3505 */</p>
<hr />
<div>SOM: System On Module, also call '[[Embedded_computer]],[[Embedded_System_Module(ESM)]],Computer_on-Module(COM)', <br />
<br />
<br />
''SOMxxx'' Series Embedded Module: <b>Designed and manufactured by [http://www.techor.com/ TECHOR of China]. Series of Size 40x40x4mm, Weight about 10g, the smallest and lightest [[System-on-Module]] in the World! including:</b><br />
* [[SOM2416]] - by [http://www.techor.com/product_281.html TECHOR.COM of China], Samsung 400MHz ARM926EJ-S based cost effective [[Application Processor]]<br />
* [[SOM6410]] - by [http://www.techor.com/product_282.html TECHOR.COM of China],Samsung 667Hz ARM1176JFZ-S based cost effective [[Application Processor]]<br />
* [[SOM3530]] - by [http://www.techor.com/product_283.html TECHOR.COM of China], TI 720MHz [[CORETEX-A8]] + 600MHz TMS320DM64x+ dual core SOC<br />
* [[SOM3517|SOM3505]] - by [http://www.techor.com/product_286.html TECHOR.COM of China], TI [[CORETEX-A8]] SOC<br />
* [[SOMX35]] - by [http://www.techor.com/product_285.html TECHOR.COM of China], ARM1136 SOC from [http://www.freescale.com/webapp/sps/site/overview.jsp?code=IMX35_FAMILY Freescale IMX35 Family]<br />
* [[SOMC100]] - by [http://www.techor.com/product_284.html TECHOR.COM of China], ARM CORETEX-A8 SOC from [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S5PC100 Samsung S5PC100 Application Processor] <br />
* [[SOM168]] - by [http://www.techor.com/product_287.html TECHOR.COM of China], Marvell PXA168 SOC<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=SOM2416&diff=14735SOM24162009-11-17T17:28:06Z<p>Som2416: /* App Demo Board */</p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSom2416&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
<br />
This page collects information about [http://www.samsung.com/global/business/semiconductor SAMSUNG semiconductor's] [http://www.arm.com/ ARM926EJ] based 400MHz [[S3C2416]] [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C2416 Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_281.html '''SOM2416'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
<br />
<br />
=Events=<br />
<I><br />
'''2009.11.01''': KIT2416-II will be released in Nov 10, 2009, it's extendable, we will develop Wifi, Bluetooth,GPS, GPRS/3G, FM module, CAN, 4x4 keypad, CMMB, LCD to VGA, LCD to LVDS,and series of Industial Sensors like Toradex Oak : [http://www.toradex.com/En/Products/Oak_USB_Sensors Oak_USB_Sensors] to plug onto the KIT2416-II and KIT3530, KIT6410<br />
<br>[[File:KIT2416-II-640.JPG]]<br />
<br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM3530] '''Rev PRELIMINARY''' will be released in Oct 30,2009! [[SOM3530|elinux.org/SOM3530]] is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
<br>[[File:SOM3530msk.jpg|200px|SOM3530, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
<br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM6410] '''Rev PRELIMINARY''' will be released in Oct 30,2009! [[SOM6410|elinux.org/SOM6410]] is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
<br>[[File:SOM6410msk.jpg|200px|SOM6410, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
<br />
'''2009.09.30''': '''SOM2416-I Rev2''' and '''SOM2416-II Rev PRELIMINARY''' ([http://elinux.org/SOM2416#Pinout_definitions 120pin],4x4cm of 1.27mm pin pitch) Released and for Order/Samples<br><br />
'''2009.09.05''': Work together with [http://www.djyos.com/technology/2009-05-24/47.html DJYOS](The first of China Embedded Realtime Operation System) and port the DJYOS to '''SOM2416-I''' <br><br />
'''2009.08.30''': '''SOM2416-I Rev 1.0''' and '''SOM2416-II Rev PRELIMINARY''' annouce to be released on Mid-Sept,2009. '''SOM2416-II''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package <br><br />
'''2009.08.20''': [http://www.techor.com/product_281.html SOM2416-I] '''Rev PRELIMINARY''' released, '''SOM2416-I''' is 4x4cm size, 74pin 2.0mm pitch QFP-like package<br />
</I><br />
<br />
=How to Purchase=<br />
==SOM([[System-on-Module]]) Order Part Number==<br />
{|border="0"<br />
!Part Number||Pin#||CPU Freq||DDR2 SDRAM||NAND Flash||Ethernet||Audio||Note<br />
|-<br />
|SOM2416-I-400-64-256M<br>default:'''SOM2416-I'''||74||400MHz||64MB||256MB||LAN9220||WM8731L||For Samples/In stock/no MOQ<ref>Minimum Order Quantity</ref> limited<br />
|-<br />
|SOM2416-I-400-64-256M-9221||74||400MHz||64MB||256MB||LAN9221||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-I-400-64-256M-NENA||74||400MHz||64MB||256MB||No||No||MOQ:10+pcs<br />
|-<br />
|SOM2416-II-400-64-256M<br>default:'''SOM2416-II'''||120||400MHz||64MB||256MB||LAN9220||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-II-400-64-256M-9221||120||400MHz||64MB||256MB||LAN9221||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-II-400-64-256M-NENA||120||400MHz||64MB||256MB||No||No||MOQ:10+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-I-400-32-64M||74||400MHz||32MB||64MB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-I-400-64-1G||74||400MHz||64MB||1GB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-I-400-64-2G-9221||74||400MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-II-400-32-64M||120||400MHz||32MB||64MB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-400-64-1G||120||400MHz||64MB||1GB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-400-64-2G-9221||120||400MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-I-266-64-256M||74||266MHz||64MB||256MB||LAN9220||WM8731L||MOQ:10+pcs<br />
|-<br />
|SOM2416-I-266-32-64M-NA||74||266MHz||32MB||64MB||LAN9220||No||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-266-64-256M-NE||120||266MHz||64MB||256MB||No||WM8731L||MOQ:10+pcs<br />
|-<br />
|SOM2416-II-266-64-2G-9221||120||266MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|}<br />
'''Note:''' <references/><br />
<br><br />
==Development/Evaluation KIT Order Part Number==<br />
<br />
{|border="1" align="center"<br />
<br />
!Part Number||Note<br />
|-<br />
|'''KIT2416-I'''<br>or<br>'''KIT2416-II'''||''KIT2416-I'' and ''KIT2416-II'' is a '''NECESSARY''' basic evaluation system kit for illustrating the functionality, connectivity of SOM2416-I/SOM2416-II modules on their each '''App Demo Board'''.<br />
; each KIT2416 includes :<br />
:# '''SOM2416-I'''(74pin,4x4cm) or '''SOM2416-II'''(120pin,4x4cm) Embedded Module<br />
:# 4.3" 16:9 '''TFT LCD''', LED backlight digital adjustable, 480 x RGB x 272 pixels, with 4-wire resistance touch screen<br />
:# Theirs corresponding [[SOM2416#App_Demo_Board|App Demo Board]] ''Rev 1.1'', which having USB host and device/Ethernet/3 or 4 UART/IIC/SPI/LCD/touch screen/Stereo Audio out/MIC/Line in/SDMMC/ADC/PWM/GPIO/local bus interfaces<br />
:# '''Cables''' : Ethernet cable, mini USB cable, RS232 Cable<br />
:# '''Power Supply''' AC 110V~220V in DC 5V 1A output<br />
:# '''SDK''': WINCE 5.0 SDK and documents,App Demo Board's SCH, PCB source code; Linux SDK in under developing and planing Nov 2009 release<br />
<br />
[[File:KIT2416-I-4.3-00.JPG]]<br><b>KIT2416-I(74pin)</b> connected U-Disk, Speaker, PC computer(Power Supply and data sync), Ethernet and console(RS232)<br />
<br />
|}<br />
<br><br />
'''3.How to Order? One of the 3 ways:'''<br />
{|<br />
|<br />
# Send Purchase Order mail to ''embed_sales at techor dot com'' and specifying ''Part#/Quantity/Where to Ship/Note'' , we will reply you the Quotation and payment instruction in 2 work days by e-mail<br />
# Add our services MSN: ''cxzeng at msn dot com'' , and chat/talk(in English and Chinese only) with our services to specify what your reqirements online<br />
# or you could refer to the official web page for detailed: [http://www.techor.com/product_281.html SOM2416]<br />
|}<br />
<br />
=Hardware=<br />
<br />
== General Info ==<br />
<br />
{|border="1"<br />
|+'''Two Models of SOM2416'''<br />
|Model||'''SOM2416-I'''<br>74pin 2.0mm pitch,4x4cm outer contour||'''SOM2416-II'''<br>120pin 1.27mm pitch,4x4cm outer contour<br />
|-<br />
|Picture||[[File:SOM2416-watermark.jpg]]||[[File:SOM2416-II-440.JPG]]<br />
|-<br />
|Components||<br />
<br />
{|border="0"<br />
!No.||Name||Comment<br />
|-<br />
|1||DDR2 SDRAM||64MB/32MB optional<br />
|-<br />
|2||LAN9220/LAN9221||High Performance 10/100M Ethernet controller<br />
|-<br />
|3||NAND Flash||2GB/1GB/512MB/256MB/128MB/64MB SLC/MLC optional<br />
|-<br />
|4||WM8731L||IIS Audio codec<br />
|-<br />
|5||S3C2416||400MHz/266MHz optional<br />
|}<br />
|-<br />
|Package||[[File:Som2416-package.gif]]||[[File:som2416-II-package.gif]]<br />
|-<br />
|Layout||[[File:72pin-top.jpg]]||[[File:120pin-top.jpg]]<br />
|}<br />
<br />
==Pinout definitions==<br />
<br />
{|<br />
|-<br />
|<br />
{|border="1"<br />
|+Pinout definition of SOM2416-I(74pin)<br />
!Pin number||Main Function||Note||Alt Function||Note<br />
|-<br />
| 1||style="background:#99FF00" |DP0 ||style="background:#99FF00" |USB Host+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 2||style="background:#80FF80" |ETX-||style="background:#80FF80" |ETH TX-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 3||style="background:#80FF80" |ETX+||style="background:#80FF80" |ETH TX+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 4||style="background:#80FF80" |ERX-||style="background:#80FF80" |ETH RX-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 5||style="background:#80FF80" |ERX+||style="background:#80FF80" |ETH RX+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 6||style="background:#FFAA00" |nOE||style="background:#FFAA00" |bus Read signal||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 7||style="background:#FFAA00" |nWE||style="background:#FFAA00" |bus Write signal||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 8||style="background:#FFAA00" |nCS3||style="background:#FFAA00" |bus Chip Select#3||style="background:#FFFF80" |GPA14||style="background:#FFFF80" |GPIO PA14<br />
|-<br />
| 9||style="background:#FFAA00" |ADDR0||style="background:#FFAA00" |bus addr||style="background:#FFFF80" |GPA0||style="background:#FFFF80"|GPIO PA0<br />
|-<br />
|10||style="background:#FFAA00" |ADDR1||style="background:#FFAA00" |bus addr||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|11||style="background:#FFAA00" |DATA0||style="background:#FFAA00" |bus data0||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|12||style="background:#FFAA00" |DATA1||style="background:#FFAA00" |bus data1||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|13||style="background:#FFAA00" |DATA2||style="background:#FFAA00" |bus data2||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|14||style="background:#FFAA00" |DATA3||style="background:#FFAA00" |bus data3||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|15||style="background:#FFAA00" |DATA4||style="background:#FFAA00" |bus data4||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|16||style="background:#FFAA00" |DATA5||style="background:#FFAA00" |bus data5||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|17||style="background:#FFAA00" |DATA6||style="background:#FFAA00" |bus data6||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|18||style="background:#FFAA00" |DATA7||style="background:#FFAA00" |bus data7||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|19||style="background:#80FF80" |HSYNC||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC2||style="background:#FFFF80" |GPIO PC2<br />
|-<br />
|20||style="background:#80FF80" |PCLK||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC1||style="background:#FFFF80" |GPIO PC1<br />
|-<br />
|21||style="background:#80FF80" |VSYNC||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC3||style="background:#FFFF80" |GPIO PC3<br />
|-<br />
|22||style="background:#80FF80" |VDEN||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC4||style="background:#FFFF80" |GPIO PC4<br />
|-<br />
|23||style="background:#80FF80" |LCD_B0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC11||style="background:#FFFF80" |GPIO PC11<br />
|-<br />
|24||style="background:#80FF80" |LCD_B1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC12||style="background:#FFFF80" |GPIO PC12<br />
|-<br />
|25||style="background:#80FF80" |LCD_B2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC13||style="background:#FFFF80" |GPIO PC13<br />
|-<br />
|26||style="background:#80FF80" |LCD_B3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC14||style="background:#FFFF80" |GPIO PC14<br />
|-<br />
|27||style="background:#80FF80" |LCD_B4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC15||style="background:#FFFF80" |GPIO PC15<br />
|-<br />
|28||style="background:#80FF80" |LCD_G0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD2||style="background:#FFFF80" |GPIO PD2<br />
|-<br />
|29||style="background:#80FF80" |LCD_G1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD3||style="background:#FFFF80" |GPIO PD3<br />
|-<br />
|30||style="background:#80FF80" |LCD_G2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD4||style="background:#FFFF80" |GPIO PD4<br />
|-<br />
|31||style="background:#80FF80" |LCD_G3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD5||style="background:#FFFF80" |GPIO PD5<br />
|-<br />
|32||style="background:#80FF80" |LCD_G4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD6||style="background:#FFFF80" |GPIO PD6<br />
|-<br />
|33||style="background:#80FF80" |LCD_G5||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD7||style="background:#FFFF80" |GPIO PD7<br />
|-<br />
|34||style="background:#80FF80" |LCD_R0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD11||style="background:#FFFF80" |GPIO PD11<br />
|-<br />
|35||style="background:#80FF80" |LCD_R1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD12||style="background:#FFFF80" |GPIO PD12<br />
|-<br />
|36||style="background:#80FF80" |LCD_R2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD13||style="background:#FFFF80" |GPIO PD13<br />
|-<br />
|37||style="background:#80FF80" |LCD_R3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD14||style="background:#FFFF80" |GPIO PD14<br />
|-<br />
|38||style="background:#80FF80" |LCD_R4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD15||style="background:#FFFF80" |GPIO PD15<br />
|-<br />
|39||style="background:#FFFF40" |ALOUT||style="background:#FFFF40" |audio left out ||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|40||style="background:#FFFF40" |AROUT||style="background:#FFFF40" |audio right out||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|41||style="background:#FFFF40" |MIC||style="background:#FFFF40" |audio MIC in||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|42||style="background:#2099FF" |TXD0||style="background:#2099FF" |uart0 tx||style="background:#FFFF80" |GPH0||style="background:#FFFF80" |GPIO PH0<br />
|-<br />
|43||style="background:#2099FF" |RXD0||style="background:#2099FF" |uart0 rx||style="background:#FFFF80" |GPH1||style="background:#FFFF80" |GPIO PH1<br />
|-<br />
|44||style="background:#2099FF" |TXD1||style="background:#2099FF" |uart1 tx||style="background:#FFFF80" |GPH2||style="background:#FFFF80" |GPIO PH2<br />
|-<br />
|45||style="background:#2099FF" |RXD1||style="background:#2099FF" |uart1 rx||style="background:#FFFF80" |GPH3||style="background:#FFFF80" |GPIO PH3<br />
|-<br />
|46||style="background:#2099FF" |TXD2||style="background:#2099FF" |uart2 tx||style="background:#FFFF80" |GPH4||style="background:#FFFF80" |GPIO PH4<br />
|-<br />
|47||style="background:#2099FF" |RXD2||style="background:#2099FF" |uart2 rx||style="background:#FFFF80" |GPH5||style="background:#FFFF80" |GPIO PH5<br />
|-<br />
|48||style="background:#99FF00" |I2CSCL||style="background:#99FF00" |IIC||style="background:#FFFF80" |GPE14||style="background:#FFFF80" |GPIO PE14<br />
|-<br />
|49||style="background:#99FF00" |I2CSDA||style="background:#99FF00" |IIC||style="background:#FFFF80" |GPE15||style="background:#FFFF80" |GPIO PE15<br />
|-<br />
|50||style="background:#FF80FF" |SPIMISO||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE11||style="background:#FFFF80" |GPIO PE11<br />
|-<br />
|51||style="background:#FF80FF" |SPICLK||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE13||style="background:#FFFF80" |GPIO PE13<br />
|-<br />
|52||style="background:#FF80FF" |SPIMOSI||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE12||style="background:#FFFF80" |GPIO PE12<br />
|-<br />
|53||style="background:#FF80FF" |SPI_nSS||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPL13||style="background:#FFFF80" |GPIO PL13<br />
|-<br />
|54||style="background:#FFFF40" |VCCRTC||style="background:#FFFF40" |RTC Vcc||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|55||style="background:#99FF00" |SDCLK||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL9||style="background:#FFFF80" |GPIO PL9<br />
|-<br />
|56||style="background:#99FF00" |SDCMD||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL8||style="background:#FFFF80" |GPIO PL8<br />
|-<br />
|57||style="background:#99FF00" |SDDAT0||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL0||style="background:#FFFF80" |GPIO PL0<br />
|-<br />
|58||style="background:#99FF00" |SDDAT1||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL1||style="background:#FFFF80" |GPIO PL1<br />
|-<br />
|59||style="background:#99FF00" |SDDAT2||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL2||style="background:#FFFF80" |GPIO PL2<br />
|-<br />
|60||style="background:#99FF00" |SDDTA3||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL3||style="background:#FFFF80" |GPIO PL3<br />
|-<br />
|61||style="background:#2099FF" |XP||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN9||style="background:#FFFF80" |ADC in9<br />
|-<br />
|62||style="background:#2099FF" |YP||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN7||style="background:#FFFF80" |ADC in7<br />
|-<br />
|63||style="background:#2099FF" |XM||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN8||style="background:#FFFF80" |ADC in8<br />
|-<br />
|64||style="background:#2099FF" |YM||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN6||style="background:#FFFF80" |ADC in6<br />
|-<br />
|65||style="background:#FFFF40" |LCD_PWR||style="background:#FFFF40" |LCD brightness||style="background:#FFFF80" |GPF2||style="background:#FFFF80" |GPIO PF2<br />
|-<br />
|66||style="background:#FFFF40" |BUS_INT||style="background:#FFFF40" |bus int.||style="background:#FFFF80" |GPF1||style="background:#FFFF80" |GPIO PF1<br />
|-<br />
|67||style="background:#FFFF40" |nSD_CD||style="background:#FFFF40" |SD detect||style="background:#FFFF80" |GPF5||style="background:#FFFF80" |GPIO PF5<br />
|-<br />
|68||style="background:#FFFF40" |SPI_INT||style="background:#FFFF40" |SPI int.||style="background:#FFFF80" |GPF0||style="background:#FFFF80" |GPIO PF0<br />
|-<br />
|69||style="background:#FFFF40" |GPIO_INT||style="background:#FFFF40" |GPIO int.||style="background:#FFFF80" |GPF6||style="background:#FFFF80" |GPIO PF6<br />
|-<br />
|70||style="background:#99FF00" |DN1||style="background:#99FF00" |USB device-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|71||style="background:#99FF00" |DP1||style="background:#99FF00" |USB device+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|72||style="background:#99FF00" |DN0||style="background:#99FF00" |USB Host-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|73||style="background:red" |VCC3V3||style="background:red" |DC 3.3V in||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|74||style="background:red" |GND||style="background:red" |GND||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|}<br />
<br />
||<br />
<br />
{|border="1"<br />
|+Pinout definition of SOM2416-II(120pin)<br />
!Pin number||Main Function||Note||Alt Function||Note<br />
|-style="background:#80FF80"<br />
| 1||ETX-||ETH TX-||-||-<br />
|-style="background:#80FF80"<br />
| 2||ETX+||ETH TX+||-||-<br />
|-style="background:#80FF80"<br />
| 3||GND||ETH GND||-||-<br />
|-style="background:#80FF80"<br />
| 4||ERX-||ETH RX-||-||-<br />
|-style="background:#80FF80"<br />
| 5||ERX+||ETH RX+||-||-<br />
|-style="background:#80FF80"<br />
| 6||ETH_SPD||ETH SPEED||-||-<br />
|-style="background:#80FF80"<br />
| 7||ETH_LINK||ETH LINK||-||-<br />
|-style="background:red"<br />
| 8||GND||GND||-||-<br />
|-style="background:#FFAA00"<br />
| 9||nRST||System Reset||-||-<br />
|-style="background:#FFFF40"<br />
|10||BUS_CLK||bus clock||-||-<br />
|-style="background:#FFFF40"<br />
|11||nWAIT||bus nWAIT||-||-<br />
|-style="background:#FFFF40"<br />
|12||nOE||bus nOE||-||-<br />
|-style="background:#FFFF40"<br />
|13||nWE||bus nWE||-||-<br />
|-style="background:#FFFF40"<br />
|14||nCS3||bus nCS3||-||-<br />
|-style="background:#FFFF40"<br />
|15||LADDR[0]||bus LADDR[0]||-||-<br />
|-style="background:#FFFF40"<br />
|16||LADDR[1]||bus LADDR[1]||-||-<br />
|-style="background:#FFFF40"<br />
|17||LADDR[2]||bus LADDR[2]||-||-<br />
|-style="background:#FFFF40"<br />
|18||LADDR[3]||bus LADDR[3]||-||-<br />
|-style="background:#FFFF40"<br />
|19||LADDR[4]||bus LADDR[4]||-||-<br />
|-style="background:#FFFF40"<br />
|20||LADDR[5]||bus LADDR[5]||-||-<br />
|-style="background:#FFFF40"<br />
|21||LADDR[6]||bus LADDR[6]||-||-<br />
|-style="background:#FFFF40"<br />
|22||LDATA[0]||bus LDATA[0]||-||-<br />
|-style="background:#FFFF40"<br />
|23||LDATA[1]||bus LDATA[1]||-||-<br />
|-style="background:#FFFF40"<br />
|24||LDATA[2]||bus LDATA[2]||-||-<br />
|-style="background:#FFFF40"<br />
|25||LDATA[3]||bus LDATA[3]||-||-<br />
|-style="background:#FFFF40"<br />
|26||LDATA[4]||bus LDATA[4]||-||-<br />
|-style="background:#FFFF40"<br />
|27||LDATA[5]||bus LDATA[5]||-||-<br />
|-style="background:#FFFF40"<br />
|28||LDATA[6]||bus LDATA[6]||-||-<br />
|-style="background:#FFFF40"<br />
|29||LDATA[7]||bus LDATA[7]||-||-<br />
|-style="background:red"<br />
|30||Vcc||Vcc input 3.3V||-||-<br />
|-style="background:red"<br />
|31||Vcc||Vcc input 3.3V||-||-<br />
|-style="background:#99FF00"<br />
|32||LCD_PWR||lcd Power||-||-<br />
|-style="background:#99FF00"<br />
|33||HSYNC||lcd HSYNC||-||-<br />
|-style="background:#99FF00"<br />
|34||PCLK||lcd PCLK||-||-<br />
|-style="background:#99FF00"<br />
|35||VSYNC||lcd VSYNC||-||-<br />
|-style="background:#99FF00"<br />
|36||VDEN||lcd VDEN||-||-<br />
|-style="background:red"<br />
|37||GND||GND||-||-<br />
|-style="background:#99FF00"<br />
|38||VD[2]||lcd VD[2]||-||-<br />
|-style="background:#99FF00"<br />
|39||VD[3]||lcd VD[3]||-||-<br />
|-style="background:#99FF00"<br />
|40||VD[4]||lcd VD[4]||-||-<br />
|-style="background:#99FF00"<br />
|41||VD[5]||lcd VD[5]||-||-<br />
|-style="background:#99FF00"<br />
|42||VD[6]||lcd VD[6]||-||-<br />
|-style="background:#99FF00"<br />
|43||VD[7]||lcd VD[7]||-||-<br />
|-style="background:#99FF00"<br />
|44||VD[10]||lcd VD[10]||-||-<br />
|-style="background:#99FF00"<br />
|45||VD[11]||lcd VD[11]||-||-<br />
|-style="background:#99FF00"<br />
|46||VD[12]||lcd VD[12]||-||-<br />
|-style="background:#99FF00"<br />
|47||VD[13]||lcd VD[13]||-||-<br />
|-style="background:#99FF00"<br />
|48||VD[14]||lcd VD[14]||-||-<br />
|-style="background:#99FF00"<br />
|49||VD[15]||lcd VD[15]||-||-<br />
|-style="background:#99FF00"<br />
|50||VD[18]||lcd VD[18]||-||-<br />
|-style="background:#99FF00"<br />
|51||VD[19]||lcd VD[19]||-||-<br />
|-style="background:#99FF00"<br />
|52||VD[20]||lcd VD[20]||-||-<br />
|-style="background:#99FF00"<br />
|53||VD[21]||lcd VD[21]||-||-<br />
|-style="background:#99FF00"<br />
|54||VD[22]||lcd VD[22]||-||-<br />
|-style="background:#99FF00"<br />
|55||VD[23]||lcd VD[23]||-||-<br />
|-style="background:#2099FF"<br />
|56||LPOUT||audio LPOUT||-||-<br />
|-style="background:#2099FF"<br />
|57||RPOUT||audio RPOUT||-||-<br />
|-style="background:#2099FF"<br />
|58||MIC||audio MIC||-||-<br />
|-style="background:#2099FF"<br />
|59||LIN||audio LIN||-||-<br />
|-style="background:#2099FF"<br />
|60||RIN||audio RIN||-||-<br />
|-style="background:red"<br />
|61||AGND||audio GND||-||-<br />
|-style="background:#80FF80"<br />
|62||TXD0||uart TXD0||-||-<br />
|-style="background:#80FF80"<br />
|63||RXD0||uart RXD0||-||-<br />
|-style="background:#80FF80"<br />
|64||nRTS0||uart nRTS0||-||-<br />
|-style="background:#80FF80"<br />
|65||nCTS0||uart nCTS0||-||-<br />
|-style="background:#80FF80"<br />
|66||TXD1||uart TXD1||-||-<br />
|-style="background:#80FF80"<br />
|67||RXD1||uart RXD1||-||-<br />
|-style="background:#80FF80"<br />
|68||nRTS1||uart nRTS1||-||-<br />
|-style="background:#80FF80"<br />
|69||nCTS1||uart nCTS1||-||-<br />
|-style="background:#80FF80"<br />
|70||TXD2||uart TXD2||-||-<br />
|-style="background:#80FF80"<br />
|71||RXD2||uart RXD2||-||-<br />
|-style="background:#80FF80"<br />
|72||TXD3||uart TXD3||-||-<br />
|-style="background:#80FF80"<br />
|73||RXD3||uart RXD3||-||-<br />
|-style="background:#FFAA00"<br />
|74||I2C_SCL||iic||-||-<br />
|-style="background:#FFAA00"<br />
|75||I2C_SDA||iic||-||-<br />
|-style="background:#FFFF40"<br />
|76||SPIMISO||spi||-||-<br />
|-style="background:#FFFF40"<br />
|77||SPICLK||spi||-||-<br />
|-style="background:#FFFF40"<br />
|78||SPIMOSI||spi||-||-<br />
|-style="background:#FFFF40"<br />
|79||nSS||spi||-||-<br />
|-style="background:#99FF00"<br />
|80||SD0CLK||sd0||-||-<br />
|-style="background:#99FF00"<br />
|81||SD0CMD||sd0||-||-<br />
|-style="background:#99FF00"<br />
|82||SD0DAT0||sd0||-||-<br />
|-style="background:#99FF00"<br />
|83||SD0DAT1||sd0||-||-<br />
|-style="background:#99FF00"<br />
|84||SD0DAT2||sd0||-||-<br />
|-style="background:#99FF00"<br />
|85||SD0DAT3||sd0||-||-<br />
|-style="background:red"<br />
|86||GND||GND||-||-<br />
|-style="background:red"<br />
|87||VCCRTC||VCCrtc||-||-<br />
|-style="background:#2099FF"<br />
|88||OM3||mode select||-||-<br />
|-style="background:#2099FF"<br />
|89||OM2||mode select||-||-<br />
|-style="background:#2099FF"<br />
|90||OM1||mode select||-||-<br />
|-style="background:#80FF80"<br />
|91||nSD1_CS||sd1 card detect||-||-<br />
|-style="background:#80FF80"<br />
|92||SD1CLK||sd1||-||-<br />
|-style="background:#80FF80"<br />
|93||SD1CMD||sd1||-||-<br />
|-style="background:#80FF80"<br />
|94||SD1DAT0||sd1||-||-<br />
|-style="background:#80FF80"<br />
|95||SD1DAT1||sd1||-||-<br />
|-style="background:#80FF80"<br />
|96||SD1DAT2||sd1||-||-<br />
|-style="background:#80FF80"<br />
|97||SD1DAT3||sd1||-||-<br />
|-style="background:red"<br />
|98||GND||GND||-||-<br />
|-style="background:#FFAA00"<br />
|99||XP||touch||-||-<br />
|-style="background:#FFAA00"<br />
|100||YP||touch||-||-<br />
|-style="background:#FFAA00"<br />
|101||XM||touch||-||-<br />
|-style="background:#FFAA00"<br />
|102||YM||touch||-||-<br />
|-style="background:#FFFF40"<br />
|103||AIN0||ADC||-||-<br />
|-style="background:#FFFF40"<br />
|104||AIN1||ADC||-||-<br />
|-style="background:#99FF00"<br />
|105||EINT0||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|106||EINT3||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|107||EINT5||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|108||EINT6||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|109||EINT7||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|110||EINT8||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|111||EINT9||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|112||EINT10||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|113||EINT11||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|114||EINT12||Ext Int||-||-<br />
|-style="background:red"<br />
|115||GND||GND||-||-<br />
|-style="background:#2099FF"<br />
|116||DN1||usb device||-||-<br />
|-style="background:#2099FF"<br />
|117||DP1||usb device||-||-<br />
|-style="background:#99FF00"<br />
|118||EINT2||Ext Int||-||-<br />
|-style="background:#80FF80"<br />
|119||DN0||usb host||-||-<br />
|-style="background:#80FF80"<br />
|120||DP0||usb host||-||-<br />
|-<br />
|}<br />
<br />
|-<br />
|}<br />
<br />
==Manual==<br />
* SOM2416-I Hardware Reference Manual released in Aug 22,2009: [http://www.techor.com/SOM/SOM2416_hw_ref_manual_v1.1.pdf SOM2416_hw_ref_manual_v1.1.pdf download here]<br />
* [http://www.techor.com/down/s3c2416x_rev10.rar S3C2416 datasheet Rev1.1 download here]<br />
<br />
==Layout==<br />
<br />
==Errata==<br />
==Clocking==<br />
==Power management==<br />
==Interfacing to Raw LCD Panels==<br />
<br />
=Availability=<br />
<br />
==SOM2416-I([http://www.techor.com/syssite/home/shop/1/pictures/productsimg/big/281.JPG 74pin]) Revision==<br />
===Rev PRELIMINARY===<br />
===Rev 1.0===<br />
==SOM2416-II(120pin) Revision==<br />
===Rev PRELIMINARY===<br />
<br />
==SOM2416-based products==<br />
{|<br />
|'''SOM2416-I''' based 7" DPF ODM design by ourself,<br />
DC 12V in/mini USB connected to PC/4-line AV out<br />
/USB host connected U Disk/Power switch<br />
/SDMMC socket /7" AT070TN84 LCD Panel<br />
/7 push buttons/2 speaker /IrDA remote control<br />
Rev 1.0 in Sept 24,2009<br />
||[[File:SOM2416-I-DPF7-2.JPG|frame|SOM2416-I based 7" DPF,front view,Rev 1.0 in Sept 24,2009]]||[[File:SOM2416-I-DPF7.JPG|frame|SOM2416-I based 7" DPF,back view,Rev 1.0 in Sept 24,2009]]<br />
|-<br />
|Customized '''SOM2416-II''' based 5.6" Industrial Touch Screen HMI,run uCOS/II with miniGUI windows management system,rev 1.0 in Sept 1,2009<br />
||[[File:SOM2416-II-HMI1.JPG|frame|SOM2416-II based Industrial Touch Screen HMI,front and back view]]||[[File:SOM2416-II-HMI.JPG|frame|SOM2416-II based Industrial Touch Screen HMI,run uCOS/II with miniGUI]]<br />
|}<br />
<br />
==SOM2416 ODM cases==<br />
{|border="0" align="center"<br />
|+'''SOM2416 baseded ODM/OEM Cases'''<br />
|'''Industrial HMI Machine''', SOM2416-I directly <br>soldered on top of 2-layer '''App board'''(below)||A Special '''Handheld Measurement Instrument''', <br>Customized 6-layer Main Board based on S3C2416<br />
|-<br />
|[[File:Solution2.jpg|448px|Industrial HMI Machine, SOM2416-I directly <br>soldered on top of 2-layer App board(below)]]||[[File:Solution1.jpg|746px|A Special Handheld Measurement Instrument, <br>Customized 6-layer Main Board based on S3C2416]]<br />
|}<br />
<br />
=App Demo Board=<br />
{|<br />
|[[File:AppBoard800.jpg|frame|<b>AppDemoBoard Rev 1.1(KIT2416-I)</b> carries SOM2416-I]]<br />
|-<br />
|[[File:SOM2416+43TFTLCD.jpg|frame|<b>KIT2416-I</b> := <i>SOM2416-I</i> + <i>AppDemoBoard Rev 1.1</i> + <i>4.3" LCD w/ touch</i> + <i>T-Flash card</i><br><b>Back view</b> of KIT2416-I, running WINCE 5.0 of Microsoft Media Player]]<br />
|}<br />
<br />
=Adapters=<br />
==Expansion boards==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=Category:System-On-Module&diff=14697Category:System-On-Module2009-11-12T18:22:19Z<p>Som2416: </p>
<hr />
<div>Listing Of Various ARM based high-end embedded modules of 4x4cm size, cost-effective and suitable for evaluation and mass use in the products<br />
<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=SOM&diff=14696SOM2009-11-12T18:19:33Z<p>Som2416: </p>
<hr />
<div>SOM: System On Module, also call '[[Embedded_computer]],[[Embedded_System_Module(ESM)]],Computer_on-Module(COM)', <br />
<br />
<br />
''SOMxxx'' Series Embedded Module: <b>Designed and manufactured by [http://www.techor.com/ TECHOR of China]. Series of Size 40x40x4mm, Weight about 10g, the smallest and lightest [[System-on-Module]] in the World! including:</b><br />
* [[SOM2416]] - by [http://www.techor.com/product_281.html TECHOR.COM of China], Samsung 400MHz ARM926EJ-S based cost effective [[Application Processor]]<br />
* [[SOM6410]] - by [http://www.techor.com/product_282.html TECHOR.COM of China],Samsung 667Hz ARM1176JFZ-S based cost effective [[Application Processor]]<br />
* [[SOM3530]] - by [http://www.techor.com/product_283.html TECHOR.COM of China], TI 720MHz [[CORETEX-A8]] + 600MHz TMS320DM64x+ dual core SOC<br />
* [[SOMX35]] - by [http://www.techor.com/product_285.html TECHOR.COM of China], ARM1136 SOC from [http://www.freescale.com/webapp/sps/site/overview.jsp?code=IMX35_FAMILY Freescale IMX35 Family]<br />
* [[SOMC100]] - by [http://www.techor.com/product_284.html TECHOR.COM of China], ARM CORETEX-A8 SOC from [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S5PC100 Samsung S5PC100 Application Processor] <br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=SOMX35&diff=14695SOMX352009-11-12T18:14:36Z<p>Som2416: </p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOMX35&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.freescale.com Freescale semiconductor's] [http://www.arm.com/products/CPUs/ ARM1136] based up-to 667MHz [http://www.freescale.com/webapp/sps/site/overview.jsp?code=IMX35_FAMILY MX35] Application Processors engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_285.html '''SOMX35'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
=Events=<br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOMX35 Revision ==<br />
==SOMX35-based products ==<br />
==SOMX35 ODM cases ==<br />
=5 App Demo Board =<br />
=6 Adapters =<br />
== Expansion boards ==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOMX35&diff=14694SOMX352009-11-12T18:12:30Z<p>Som2416: Created page with '[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOMX35&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Transla…'</p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOMX35&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.freescale.com Freescale semiconductor's] [http://www.arm.com/products/CPUs/ ARM1136] based up-to 667MHz [[MX35]] Application Processor engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_285.html '''SOMX35'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
=Events=<br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOMX35 Revision ==<br />
==SOMX35-based products ==<br />
==SOMX35 ODM cases ==<br />
=5 App Demo Board =<br />
=6 Adapters =<br />
== Expansion boards ==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOMC100&diff=14693SOMC1002009-11-12T18:07:07Z<p>Som2416: Created page with '[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOMC100&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Transl…'</p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOMC100&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.samsung.com/global/business/semiconductor SAMSUNG semiconductor's] [http://www.arm.com/products/CPUs/ARM_Cortex-A8.html CORETEX-A8] based up-to 833MHz [[S5PC100]] [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S5PC100 Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_284.html '''SOMC100'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
=Events=<br />
<I><br />
'''2009.11.13''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_284.html SOMC100] '''Rev PRELIMINARY''' will be released in Dec 20,2009! '''SOMC100''' is 4x4cm size, Weight about 12g, 120pin 1.27mm pitch QFP-like package<br />
[[File:SOMC100msk.jpg|SOMC100 engineering picture, Diameter:4x4cm Height:4mm Weight:(nominal) 12g]][[File:SOMC100-L.JPG|SOMC100 actual sample picture, Diameter:4x4cm Height:4mm Weight:(nominal) 12g]]<br />
</I><br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOMC100 Revision ==<br />
==SOMC100-based products ==<br />
==SOMC100 ODM cases ==<br />
=5 App Demo Board =<br />
=6 Adapters =<br />
== Expansion boards ==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=Computer-on-Module&diff=14692Computer-on-Module2009-11-12T17:58:33Z<p>Som2416: </p>
<hr />
<div>A computer-on-module (COM) is a type of [http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Single-Board-Computer-SBC-Quick-Reference-Guide/ single-board computer](SBC), a subtype of an embedded computer system. It is also called [http://www.emacinc.com/som/som_select_guide.htm System on Module]([[System-on-Module|SOM]]) as an extension of the concept of System on Chip (SoC) and lying between a full-up computer and a microcontroller in nature.<br />
<br />
Today's COM/SOM modules are complete computers built on a single circuit board. The design is centered on a single microprocessor with RAM, input/output controllers and all other features needed to be a functional computer on the one board. However, unlike a single-board computer, the COM module will usually lack the standard connectors for any input/output peripherals to be attached directly to the board. Instead, the wiring for these peripherals are bussed out to connectors on the board.<br />
<br />
The module will usually need to be mounted on a carrier board (or "baseboard") which breaks the bus out to standard peripheral connectors. Some COMs also include peripheral connectors and/or can be used without a carrier.<br />
<br />
A COM/SOM solution offers a dense package computer system for use in small or specialized applications requiring low power consumption or small physical size as is needed in embedded systems.<br />
<br />
Some devices also incorporate Field Programmable Gate Arrays.<br />
<br />
The terms "Computer-on-Module" and "COM" were coined by Venture Development Corporation (Natick, MA, USA) to describe this class of embedded computer boards. The term became more notable upon industry standardization of the COM Express format.<br />
<br />
A number of manufacturers offer products which are defined as system-on-module or computer-on-module. Among those are Advanced Knowledge Associates (www.a-k-a.net) in Santa Clara, CA; BCM Advanced Research (www.bcmcom.com) in Irvine, CA; Embedded Systems (www.embedded-systems.net); MEN Micro (www.menmicro.com) in Ambler, PA; DAVE Embedded Systems (www.dave.eu) in Italy.<br />
<br />
== Computer-on-Module Provider ==<br />
* [[SOM]] - by [http://www.techor.com/ TECHOR.COM of China], series of 40x40x4mm Size, Weight about 10g, the smallest and lightest [[System-on-Module]] in the World!<br />
* [[SOM2416]] - by [http://www.techor.com/product_281.html TECHOR.COM of China], Samsung 400MHz ARM926EJ-S based cost effective [[Application Processor]]<br />
* [[SOM6410]] - by [http://www.techor.com/product_282.html TECHOR.COM of China],Samsung 667Hz ARM1176JFZ-S based cost effective [[Application Processor]]<br />
* [[SOM3530]] - by [http://www.techor.com/product_283.html TECHOR.COM of China], TI 720MHz [[CORETEX-A8]] + 600MHz TMS320DM64x+ dual core SOC<br />
* '''CSB7xx''' - by [http://www.cogcomp.com Cogent Computer Systems, Inc. of USA]<br />
* '''CM-XXX''' - by [http://www.compulab.co.il CompuLab of Italia]<br />
* '''Colibri Computer Modules''' - by [http://www.toradex.com Toradex of Switzerland]<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=Category:System-on-Module&diff=14691Category:System-on-Module2009-11-12T17:57:32Z<p>Som2416: Redirected page to Category:System-On-Module</p>
<hr />
<div>#REDIRECT [[Category:System-On-Module]]</div>Som2416https://elinux.org/index.php?title=Category:System-On-Module&diff=14690Category:System-On-Module2009-11-12T17:54:47Z<p>Som2416: Created page with 'Listing Of Various ARM based high-end embedded modules of 4x4cm size, cost-effective and suitable for evaluation and mass use in the products'</p>
<hr />
<div>Listing Of Various ARM based high-end embedded modules of 4x4cm size, cost-effective and suitable for evaluation and mass use in the products</div>Som2416https://elinux.org/index.php?title=Category:Development_Boards&diff=14689Category:Development Boards2009-11-12T17:50:06Z<p>Som2416: </p>
<hr />
<div>Contains hardware reference/studying boards for R&D, prototype and research<br />
[[Category:Development Tools]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=Category:ARM_Development_Boards&diff=14688Category:ARM Development Boards2009-11-12T17:48:27Z<p>Som2416: </p>
<hr />
<div>Listing Of Various ARM based development boards and ARM [[System-on-Module]] Modules<br />
<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=Category:System-on-Module&diff=14687Category:System-on-Module2009-11-12T17:46:41Z<p>Som2416: Created page with '#REDIRECT Category:System-On-Module'</p>
<hr />
<div>#REDIRECT Category:System-On-Module</div>Som2416https://elinux.org/index.php?title=System-On-Board&diff=14686System-On-Board2009-11-12T17:44:42Z<p>Som2416: Redirected page to Computer-on-Module</p>
<hr />
<div>#REDIRECT [[Computer-on-Module]]</div>Som2416https://elinux.org/index.php?title=SOM6410&diff=14685SOM64102009-11-12T17:39:41Z<p>Som2416: /* remove record in Categories */</p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOM6410&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.samsung.com/global/business/semiconductor SAMSUNG semiconductor's] [http://www.arm.com/products/CPUs/ARM1176.html ARM1176JZF-S] based up-to 667MHz [[S3C6410]] [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C6410 Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_282.html '''SOM6410'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
=Events=<br />
<I><br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM6410] '''Rev PRELIMINARY''' will be released in Oct 30,2009! '''SOM6410''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
[[File:SOM6410msk.jpg|SOM6410 engineering picture, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]][[File:SOM6410-L.JPG|SOM6410 actual sample picture, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
</I><br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOM6410 Revision ==<br />
==SOM6410-based products ==<br />
==SOM6410 ODM cases ==<br />
=5 App Demo Board =<br />
=6 Adapters =<br />
== Expansion boards ==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOM3530&diff=14684SOM35302009-11-12T17:39:16Z<p>Som2416: /* remove record in Categories */</p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOM3530&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.ti.com/ TI(Texas Instruments)'s] [http://www.arm.com/products/CPUs/ARM_Cortex-A8.html ARM Cortex-A8] + [https://focus.ti.com/general/docs/tags/fldrsfortagTemplate.tsp?&tagName=omap TMS320C64x+] based 720MHz [[OMAP3530]] [http://focus.ti.com/docs/prod/folders/print/omap3530.html Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_283.html '''SOM3530''']: [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
<br />
=Events=<br />
<I><br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM3530] '''Rev PRELIMINARY''' will be released in Oct 30,2009! '''SOM3530''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
[[File:SOM3530msk.jpg|SOM3530 Engineering File, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]][[File:SOM3530-L.JPG|SOM3530 samples picture,Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
</I><br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOM3530 Revision ==<br />
==SOM3530-based products ==<br />
==SOM3530 ODM cases ==<br />
=App Demo Board =<br />
=Adapters =<br />
== Expansion boards ==<br />
<br />
<br><br />
<br><br />
----<br />
=SOM2530/KIT3530 FAQ=<br />
----<br />
<br />
主要描述基于KIT3530开发时所遇到的一些问题及解决方法。<br><br />
<br />
==硬件问题==<br />
=== 怎么让USB OTG口工作于主、从方式? ===<br />
A:在内核启动前,如果要让USB OTG工作于主方式,则板载USB OTG接套件提供的USB A型线;如果要让USB OTG工作于从方式,则板载USB OTG接套件提供的USB B型线。<br><br />
===问题->: 如何切换到MMC/SD启动开发板?===<br />
A:按住BOOT按键,上电启动,系统改为先从MMC/SD启动,再从NAND启动,详细请参考“3.18按键”介绍。<br><br />
<br />
=== KIT3530与仿真器相连接,调试DSP和ARM===<br />
目前正在找相关的仿真器,看有否可支持的仿真器系列。<br />
=== KIT3530中的RTC电池===<br />
KIT3530出货时不带RTC电池,需用户自行配备,电池型号用 CR1220即可<br />
=== KIT3530中的U20 (ISP1504) U13 (TXS0102)芯片问题 ===<br />
ISP1504 是USB HOST芯片,由于我们的USB HOST暂未调通,怀疑是硬件问题,故目前没有把此芯片焊上去。<br><br />
U13 (TXS0102) 是DVI的一个附带电路,但是此刻芯片未影响DVI的输出,故我们没有焊接此芯片,不影响DVI的使用。<br><br />
<br />
''the ISP1504 is for the USB HOST, but at now the USB HOST is not OK, so the board we sold don't have the chips.<br><br />
U13 (TXS0102) is not used for the dvi, and it don't effect your DVI output<br />
''<br />
<br />
==linux问题==<br />
=== 开发驱动时如何打开低层调试信息?===<br />
A:make menucofig -> kernel hacking -> lowlevel debug<br><br />
<br />
=== 如何让显示输出在lcd屏与DVI输出之间切换? ===<br />
A:只需修改内核启动参数即可.<br><br />
4.3” LCD屏:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode: 4.3inch_LCD<br><br />
5.6” LCD屏:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode: 5.6inch_LCD<br><br />
7” LCD屏:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:7inch_LCD<br><br />
DVI显示器:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:720p60<br><br />
VGA显示器:<br><br />
OMAP3 KIT3530 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:VGA<br><br />
<br />
===tftp更新方式===<br />
板上配置有10/100M自适应网卡dm9000,用户可通过tftp下载的方式更新nand启动映像<br><br />
1)x-loader启动映像的更新<br><br />
OMAP3 KIT3530 # tftp 80000000 x-load.bin.ift_for_NAND<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'x-load.bin.ift_for_NAND'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #<br><br />
done<br><br />
Bytes transferred = 9664 (25c0 hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 134217728!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc hw<br><br />
OMAP3 KIT3530 # nand erase 0 80000<br><br />
<br />
NAND erase: device 0 offset 0x0, size 0x80000<br><br />
Erasing at 0x60000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 0 80000<br><br />
<br />
NAND write: device 0 offset 0x0, size 0x80000<br><br />
<br />
Writing data at 0x7f800 -- 100% complete.<br><br />
524288 bytes written: OK<br><br />
<br />
2)u-boot启动映像的更新<br><br />
OMAP3 KIT3530 # tftp 80000000 flash-uboot.bin<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'flash-uboot.bin'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #################################################################<br><br />
done<br><br />
Bytes transferred = 1085536 (109060 hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 134217728!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc sw<br><br />
OMAP3 KIT3530 # nand erase 80000 160000<br><br />
<br />
NAND erase: device 0 offset 0x80000, size 0x160000<br><br />
Erasing at 0x1c0000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 80000 160000<br><br />
<br />
NAND write: device 0 offset 0x80000, size 0x160000<br><br />
<br />
Writing data at 0x1df800 -- 100% complete.<br><br />
1441792 bytes written: OK<br><br />
<br />
3)内核映像更新<br><br />
OMAP3 KIT3530 # tftp 80000000 uImage<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'uImage'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #################################################################<br><br />
done<br><br />
Bytes transferred = 1991900 (1e64dc hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 268435456!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc sw<br><br />
OMAP3 KIT3530 # nand erase 280000 200000<br><br />
<br />
NAND erase: device 0 offset 0x280000, size 0x200000<br><br />
Erasing at 0x460000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 280000 200000<br><br />
<br />
NAND write: device 0 offset 0x280000, size 0x200000<br><br />
<br />
Writing data at 0x47f800 -- 100% complete.<br><br />
2097152 bytes written: OK<br><br />
<br />
4)文件系统映像更新<br><br />
OMAP3 KIT3530 # tftp 80000000 ubi.img<br><br />
dm9000 i/o: 0x2c000000, id: 0x90000a46 <br><br />
MAC: aa:bb:cc:dd:ee:ff<br><br />
operating at 100M full duplex mode<br><br />
TFTP from server 192.192.192.90; our IP address is 192.192.192.200<br><br />
Filename 'ubi.img'.<br><br />
Load address: 0x80000000<br><br />
Loading: T #################################################################<br><br />
done<br><br />
Bytes transferred = 12845056 (c40000 hex)<br><br />
OMAP3 KIT3530 # nand unlock<br><br />
device 0 whole chip<br><br />
nand_unlock: start: 00000000, length: 268435456!<br><br />
NAND flash successfully unlocked<br><br />
OMAP3 KIT3530 # nand ecc sw<br><br />
OMAP3 KIT3530 # nand erase 680000 7980000<br><br />
<br />
NAND erase: device 0 offset 0x680000, size 0x7980000<br><br />
Erasing at 0x7fe0000 -- 100% complete.<br><br />
OK<br><br />
OMAP3 KIT3530 # nand write.i 80000000 680000 $(filesize)<br><br />
<br />
NAND write: device 0 offset 0x680000, size 0xc40000<br><br />
<br />
Writing data at 0x12bf800 -- 100% complete.<br><br />
12845056 bytes written: OK<br><br />
<br />
===linux交叉编译工具安装 ===<br />
1.网站下载交叉编译工具:<br />
http://www.codesourcery.com/sgpp/lite/arm/portal/package1787/public/arm-none-linux-gnueabi/arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 <br><br />
2.解压缩软件 <br><br />
sudo tar xvf arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 -C /home/ <br><br />
<br />
3. 工具安装<br><br />
mkdir /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/mkimage /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/signGP /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/mkfs.ubifs /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/ubinize /home/embest/tools<br><br />
cp /media/cdrom/linux/tools/ ubinize.cfg /home/embest/tools<br><br />
<br />
4。设置环境变量<br><br />
export PATH=/home/arm-2007q3/bin/:/home/embest/tools:$PATH<br><br />
<br />
===linux摄像头显示模式转化 ===<br />
<br />
===OTG主口使用问题 ===<br />
USB使用方法:<br><br />
1. 连接USB hub电源到USB HUB<br><br />
2. 连接USB OTG转接线到KIT3530板上,<br><br />
3. 上电待开发板进入linux系统<br><br />
4. 插入usb hub线到USB OTG转接线上<br><br />
5.可以插入usb 鼠标键盘到hub了<br><br />
<br />
===7LCD触摸屏不准的解决方法===<br />
修改此文件arch/arm/mach-omap2/board-omap3KIT3530.c为如下数据即可<br><br />
struct ads7846_platform_data ads7846_conf = {<br><br />
.x_max = 0x0fff,<br><br />
.y_max = 0x0fff,<br><br />
//.x_plate_ohms = 180,<br><br />
//.pressure_max = 255,<br><br />
.debounce_max = 10,<br><br />
.debounce_tol = 5,<br><br />
.debounce_rep = 1,<br><br />
.get_pendown_state = ads7846_get_pendown_state,<br><br />
.keep_vref_on = 1,<br><br />
.settle_delay_usecs = 150,<br><br />
};<br><br />
<br />
===对于NFS,KIT3530 U-boot 下的配置参数===<br />
若您需要用NFS,首先需要在PC机上将NFS的服务打开,然后接上网线,打开KIT3530板子电源,在U-boot命令行里输入:<br>setenv bootargs console=ttyS2,115200n8 root=/dev/nfs nfsroot=192.192.192.117:/home/lijr/work/nfsroot/rootfs ip=192.192.192.200:192.192.192.101:192.192.192.101:255.255.255.0:KIT3530:eth0:off<br />
<br />
==wince问题==<br />
=== 烧写wince到NAND Flash系统映像更新===<br />
1.更新文件准备<br><br />
(1) 用软件HP Disk Storage Format Tool格式化SD卡为FAT或FAT32文件系统。<br><br />
(2) 拷贝光盘目录image[\wince_6]下子目录dvi1280X720或lcd480X272下文件MLO、EBOOTNAND.nb0、NK.bin、XLDRNAND.nb0和ADevKit9000.exe到SD卡并重命名EBOOTNAND.nb0为EBOOTSD.nb0<br><br />
2. 映像更新<br><br />
(1) 按住BOOT键,后插入SD卡重新启动系统。这时系统从SD卡启动。超级终端输出启动打印信息,按[SPACE]进入EBOOT菜单。<br><br />
(2) 按[5]进入Flash管理菜单。<br><br />
(3) 分别按[a]、[b]和[c],写XLDR、EBOOT和NK映像。<br><br />
(4) 然后按[0]键回到主菜单,并分别按下[2]、[4]、[7]和[y]更改启动设备。<br><br />
(5) 拔除SD卡,后重新启动系统。这时系统将从NAND Flash启动。<br><br />
英文显示<br><br />
the method to Update the image for NAND Flash<br><br />
(1)Run the software of HP Disk Storage Format Tool and format the SD card for FAT or FAT32 filesystem.<br><br />
(2) Copy the image file(MLO, EBOOTNAND.nb0, NK.bin, AKIT3530.exe) from CD:\wince_6\image\ lcd480X272 to SD card, then change the name from EBOOTNAND.nb0 to EBOOTSD.nb0 in the SD card.<br><br />
(3) Insert the SD card to the board, press the BOOT button and then power on the board again; HyperTerminal will start printing the output information, at the same time press [SPACE] to enter the EBOOT menu.<br><br />
(4) Press [5] to enter the Flash manage menu.<br><br />
(5) Press [a], [b], [c] separately to write the image(XLDR, EBOOT, NK) to flash.<br><br />
(6) Press [0] to return to the main menu, and press [2], [4], [7], [7] to change the boot device.<br><br />
(7) Power on the system again, and then the board will boot from the NAND flash. <br><br />
<br />
=== 屏蔽WinCE启动后的触摸屏打印信息===<br />
修改函数KIT3530\SRC\DRIVERS\TOUCH\touchscreen.cpp,<br />
把564行 RETAILMSG(1, ( TEXT( "Point: (%d,%d)\r\n" ), *pUncalX, *pUncalY ) );<br />
屏蔽掉然后重新编译就行了。如下所示:<br />
//RETAILMSG(1, ( TEXT( "Point: (%d,%d)\r\n" ), *pUncalX, *pUncalY ) );<br />
=== 关闭调试串口打印===<br />
setp: <br><br />
1,commnent out the RETAILMSG call in TouchDriverCalibrationPointGet function of touchscreen.cpp <br><br />
2,commnent out the RETAILMSG call in DdsiTouchPanelGetPoint function of touchscreen.cpp <br><br />
3,commnent out the RETAILMSG call in TLED_Backlight::SetPowerState function of tled_backlight.cpp <br><br />
4,commnent out the RETAILMSG call in SetDutyCycle function of tled.cpp <br><br />
5,commnent out the RETAILMSG call in LcdPdd_LCD_Initialize function of lcd_vga.c <br><br />
6,make sure that "set BSP_NOCOM=" is not set in KIT3530.bat <br><br />
7,make sure that "set BSP_NOCOM3=" is not set in KIT3530.bat <br><br />
8,delete the "IF BSP_COM3" of _FLATRELEASEDIR/platform.reg in line 1103 <br><br />
9,delete the "ENDIF BSP_COM3" of _FLATRELEASEDIR/platform.reg in line 1124 <br><br />
10,rebuilt the BSP <br><br />
=== 关闭触摸屏校准===<br />
setp: <br><br />
在BSP包的一级目录下,有KIT3530.bat文件,在其中任一行添加:<br><br />
set IMGNOCALIBRATION=1<br><br />
然后重新build编译即可<br />
<br />
===关于触摸屏不能用的问题解决方法===<br />
是编译时使用 build and sysgen导致的,在wince下不能用bulid and sysgen编译,用它就出问题,而且必须把pb6.0重装才可以<br />
<br />
=== WINCE无法存储===<br />
在SRC\DRIVERS\BLOCK\NAND\nand_MT29F2G16.h<br />
把下面这句<br />
#define NUMBER_OF_BLOCKS (2048) // 2048 blocks<br />
改成<br />
#define NUMBER_OF_BLOCKS (1024) // 1024 blocks<br />
<br />
=== WINCE无法设置时间===<br />
1,把新的rtc.c替换原来的src/oal/oalrtc/rtc.c(可询问技术人员提供)<br />
2,在src/inc/bsp_cfg.h后面加上#define BSP_OAL_RTC_USES_TWL4030 TRUE<br />
<br />
==其他问题==<br />
=== 格式化工具下载===<br />
网址:http://www.embedinfo.com/english/download/SP27213.exe<br />
<br />
=== SD卡不能启动===<br />
推荐使用HP USB Disk Storage Format Tool 2.0.6:下载下列网址工具<br><br />
http://www.embedinfo.com/english/download/SP27213.exe<br><br />
安装后执行如下操作。<br><br />
1、把MMC/SD卡插入PC下读卡器中<br><br />
2、打开HP USB Disk Storage Format Tool <br><br />
3、选择”FAT32“系统格式<br><br />
4、点击”Start”<br><br />
5、等待格式化完成,点击”OK”<br><br />
6、把映像文件拷贝到SD卡中。<br><br />
<English><br><br />
you should downlod the tools<br><br />
http://www.embedinfo.com/english/download/SP27213.exe<br><br />
then format your SD card for the fat32,then copy the file to it, then it can be booted.<br><br />
<br />
=== 提供demo配套u-boot.bin无法修改参数===<br />
提供demo配套u-boot.bin无法修改参数,用户想要修改并保存u-boot下参数,可采用KIT3530提供u-boot源码,修改传递给内核的MACH_ID,重新编译即可。<br><br />
具体操作方法:<br><br />
1、u-boot-1.3.3源码中<br><br />
修改board/omap3KIT3530/omap3KIT3530.c文件<br><br />
找到board_init函数<br><br />
修改:<br><br />
gd->bd->bi_arch_number = MACH_TYPE_KIT3530;为<br><br />
gd->bd->bi_arch_number = XXX;<br><br />
<br />
2、重新编译u-boot<br><br />
<br />
注:<br />
1、对于angstrom,XXX为MACH_TYPE_KIT3530<br />
2、对于android,XXX为MACH_TYPE_OMAP3_BEAGLE<br />
3、对于dvsdk,XXX为MACH_TYPE_OMAP3EVM<br />
<br />
=== KIT3530跑QT程序鼠标不工作===<br />
内核目录下输入make menuconfig,添加如下配置:<br />
<br />
Device Drivers ---><br />
Input device support ---><br />
<br />
<*>Mouse interface <br />
<br />
[*]Provide legacy /dev/psaux device <br />
<br />
(1024) Horizontal screen resolution <br />
<br />
(768) Vertical screen resolution<br />
<br />
[*] Mice ---><br />
<br />
=== 解决android demo系统下静态ip的分配问题===<br />
进入系统后,串口终端下输入:<br />
<br />
ifconfig eth0 192.192.192.90<br />
<br />
ifconfig eth0 up<br />
<br />
route add default gw 192.192.192.101 dev eth0<br />
<br />
setprop net.dns1 202.96.134.133<br />
<br />
注:<br />
客户可根据实际情况修改以上ip地址。<br />
<br />
<br />
----<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOM2416&diff=14683SOM24162009-11-12T17:38:32Z<p>Som2416: /* remove record in Categories */</p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSom2416&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
<br />
This page collects information about [http://www.samsung.com/global/business/semiconductor SAMSUNG semiconductor's] [http://www.arm.com/ ARM926EJ] based 400MHz [[S3C2416]] [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C2416 Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_281.html '''SOM2416'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
<br />
<br />
=Events=<br />
<I><br />
'''2009.11.01''': KIT2416-II will be released in Nov 10, 2009, it's extendable, we will develop Wifi, Bluetooth,GPS, GPRS/3G, FM module, CAN, 4x4 keypad, CMMB, LCD to VGA, LCD to LVDS,and series of Industial Sensors like Toradex Oak : [http://www.toradex.com/En/Products/Oak_USB_Sensors Oak_USB_Sensors] to plug onto the KIT2416-II and KIT3530, KIT6410<br />
<br>[[File:KIT2416-II-640.JPG]]<br />
<br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM3530] '''Rev PRELIMINARY''' will be released in Oct 30,2009! [[SOM3530|elinux.org/SOM3530]] is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
<br>[[File:SOM3530msk.jpg|200px|SOM3530, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
<br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM6410] '''Rev PRELIMINARY''' will be released in Oct 30,2009! [[SOM6410|elinux.org/SOM6410]] is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
<br>[[File:SOM6410msk.jpg|200px|SOM6410, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
<br />
'''2009.09.30''': '''SOM2416-I Rev2''' and '''SOM2416-II Rev PRELIMINARY''' ([http://elinux.org/SOM2416#Pinout_definitions 120pin],4x4cm of 1.27mm pin pitch) Released and for Order/Samples<br><br />
'''2009.09.05''': Work together with [http://www.djyos.com/technology/2009-05-24/47.html DJYOS](The first of China Embedded Realtime Operation System) and port the DJYOS to '''SOM2416-I''' <br><br />
'''2009.08.30''': '''SOM2416-I Rev 1.0''' and '''SOM2416-II Rev PRELIMINARY''' annouce to be released on Mid-Sept,2009. '''SOM2416-II''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package <br><br />
'''2009.08.20''': [http://www.techor.com/product_281.html SOM2416-I] '''Rev PRELIMINARY''' released, '''SOM2416-I''' is 4x4cm size, 74pin 2.0mm pitch QFP-like package<br />
</I><br />
<br />
=How to Purchase=<br />
==SOM([[System-on-Module]]) Order Part Number==<br />
{|border="0"<br />
!Part Number||Pin#||CPU Freq||DDR2 SDRAM||NAND Flash||Ethernet||Audio||Note<br />
|-<br />
|SOM2416-I-400-64-256M<br>default:'''SOM2416-I'''||74||400MHz||64MB||256MB||LAN9220||WM8731L||For Samples/In stock/no MOQ<ref>Minimum Order Quantity</ref> limited<br />
|-<br />
|SOM2416-I-400-64-256M-9221||74||400MHz||64MB||256MB||LAN9221||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-I-400-64-256M-NENA||74||400MHz||64MB||256MB||No||No||MOQ:10+pcs<br />
|-<br />
|SOM2416-II-400-64-256M<br>default:'''SOM2416-II'''||120||400MHz||64MB||256MB||LAN9220||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-II-400-64-256M-9221||120||400MHz||64MB||256MB||LAN9221||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-II-400-64-256M-NENA||120||400MHz||64MB||256MB||No||No||MOQ:10+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-I-400-32-64M||74||400MHz||32MB||64MB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-I-400-64-1G||74||400MHz||64MB||1GB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-I-400-64-2G-9221||74||400MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-II-400-32-64M||120||400MHz||32MB||64MB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-400-64-1G||120||400MHz||64MB||1GB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-400-64-2G-9221||120||400MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-I-266-64-256M||74||266MHz||64MB||256MB||LAN9220||WM8731L||MOQ:10+pcs<br />
|-<br />
|SOM2416-I-266-32-64M-NA||74||266MHz||32MB||64MB||LAN9220||No||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-266-64-256M-NE||120||266MHz||64MB||256MB||No||WM8731L||MOQ:10+pcs<br />
|-<br />
|SOM2416-II-266-64-2G-9221||120||266MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|}<br />
'''Note:''' <references/><br />
<br><br />
==Development/Evaluation KIT Order Part Number==<br />
<br />
{|border="1" align="center"<br />
<br />
!Part Number||Note<br />
|-<br />
|'''KIT2416-I'''<br>or<br>'''KIT2416-II'''||''KIT2416-I'' and ''KIT2416-II'' is a '''NECESSARY''' basic evaluation system kit for illustrating the functionality, connectivity of SOM2416-I/SOM2416-II modules on their each '''App Demo Board'''.<br />
; each KIT2416 includes :<br />
:# '''SOM2416-I'''(74pin,4x4cm) or '''SOM2416-II'''(120pin,4x4cm) Embedded Module<br />
:# 4.3" 16:9 '''TFT LCD''', LED backlight digital adjustable, 480 x RGB x 272 pixels, with 4-wire resistance touch screen<br />
:# Theirs corresponding [[SOM2416#App_Demo_Board|App Demo Board]] ''Rev 1.1'', which having USB host and device/Ethernet/3 or 4 UART/IIC/SPI/LCD/touch screen/Stereo Audio out/MIC/Line in/SDMMC/ADC/PWM/GPIO/local bus interfaces<br />
:# '''Cables''' : Ethernet cable, mini USB cable, RS232 Cable<br />
:# '''Power Supply''' AC 110V~220V in DC 5V 1A output<br />
:# '''SDK''': WINCE 5.0 SDK and documents,App Demo Board's SCH, PCB source code; Linux SDK in under developing and planing Nov 2009 release<br />
<br />
[[File:KIT2416-I-4.3-00.JPG]]<br><b>KIT2416-I(74pin)</b> connected U-Disk, Speaker, PC computer(Power Supply and data sync), Ethernet and console(RS232)<br />
<br />
|}<br />
<br><br />
'''3.How to Order? One of the 3 ways:'''<br />
{|<br />
|<br />
# Send Purchase Order mail to ''embed_sales at techor dot com'' and specifying ''Part#/Quantity/Where to Ship/Note'' , we will reply you the Quotation and payment instruction in 2 work days by e-mail<br />
# Add our services MSN: ''cxzeng at msn dot com'' , and chat/talk(in English and Chinese only) with our services to specify what your reqirements online<br />
# or you could refer to the official web page for detailed: [http://www.techor.com/product_281.html SOM2416]<br />
|}<br />
<br />
=Hardware=<br />
<br />
== General Info ==<br />
<br />
{|border="1"<br />
|+'''Two Models of SOM2416'''<br />
|Model||'''SOM2416-I'''<br>74pin 2.0mm pitch,4x4cm outer contour||'''SOM2416-II'''<br>120pin 1.27mm pitch,4x4cm outer contour<br />
|-<br />
|Picture||[[File:SOM2416-watermark.jpg]]||[[File:SOM2416-II-440.JPG]]<br />
|-<br />
|Components||<br />
<br />
{|border="0"<br />
!No.||Name||Comment<br />
|-<br />
|1||DDR2 SDRAM||64MB/32MB optional<br />
|-<br />
|2||LAN9220/LAN9221||High Performance 10/100M Ethernet controller<br />
|-<br />
|3||NAND Flash||2GB/1GB/512MB/256MB/128MB/64MB SLC/MLC optional<br />
|-<br />
|4||WM8731L||IIS Audio codec<br />
|-<br />
|5||S3C2416||400MHz/266MHz optional<br />
|}<br />
|-<br />
|Package||[[File:Som2416-package.gif]]||[[File:som2416-II-package.gif]]<br />
|-<br />
|Layout||[[File:72pin-top.jpg]]||[[File:120pin-top.jpg]]<br />
|}<br />
<br />
==Pinout definitions==<br />
<br />
{|<br />
|-<br />
|<br />
{|border="1"<br />
|+Pinout definition of SOM2416-I(74pin)<br />
!Pin number||Main Function||Note||Alt Function||Note<br />
|-<br />
| 1||style="background:#99FF00" |DP0 ||style="background:#99FF00" |USB Host+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 2||style="background:#80FF80" |ETX-||style="background:#80FF80" |ETH TX-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 3||style="background:#80FF80" |ETX+||style="background:#80FF80" |ETH TX+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 4||style="background:#80FF80" |ERX-||style="background:#80FF80" |ETH RX-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 5||style="background:#80FF80" |ERX+||style="background:#80FF80" |ETH RX+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 6||style="background:#FFAA00" |nOE||style="background:#FFAA00" |bus Read signal||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 7||style="background:#FFAA00" |nWE||style="background:#FFAA00" |bus Write signal||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 8||style="background:#FFAA00" |nCS3||style="background:#FFAA00" |bus Chip Select#3||style="background:#FFFF80" |GPA14||style="background:#FFFF80" |GPIO PA14<br />
|-<br />
| 9||style="background:#FFAA00" |ADDR0||style="background:#FFAA00" |bus addr||style="background:#FFFF80" |GPA0||style="background:#FFFF80"|GPIO PA0<br />
|-<br />
|10||style="background:#FFAA00" |ADDR1||style="background:#FFAA00" |bus addr||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|11||style="background:#FFAA00" |DATA0||style="background:#FFAA00" |bus data0||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|12||style="background:#FFAA00" |DATA1||style="background:#FFAA00" |bus data1||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|13||style="background:#FFAA00" |DATA2||style="background:#FFAA00" |bus data2||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|14||style="background:#FFAA00" |DATA3||style="background:#FFAA00" |bus data3||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|15||style="background:#FFAA00" |DATA4||style="background:#FFAA00" |bus data4||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|16||style="background:#FFAA00" |DATA5||style="background:#FFAA00" |bus data5||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|17||style="background:#FFAA00" |DATA6||style="background:#FFAA00" |bus data6||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|18||style="background:#FFAA00" |DATA7||style="background:#FFAA00" |bus data7||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|19||style="background:#80FF80" |HSYNC||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC2||style="background:#FFFF80" |GPIO PC2<br />
|-<br />
|20||style="background:#80FF80" |PCLK||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC1||style="background:#FFFF80" |GPIO PC1<br />
|-<br />
|21||style="background:#80FF80" |VSYNC||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC3||style="background:#FFFF80" |GPIO PC3<br />
|-<br />
|22||style="background:#80FF80" |VDEN||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC4||style="background:#FFFF80" |GPIO PC4<br />
|-<br />
|23||style="background:#80FF80" |LCD_B0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC11||style="background:#FFFF80" |GPIO PC11<br />
|-<br />
|24||style="background:#80FF80" |LCD_B1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC12||style="background:#FFFF80" |GPIO PC12<br />
|-<br />
|25||style="background:#80FF80" |LCD_B2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC13||style="background:#FFFF80" |GPIO PC13<br />
|-<br />
|26||style="background:#80FF80" |LCD_B3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC14||style="background:#FFFF80" |GPIO PC14<br />
|-<br />
|27||style="background:#80FF80" |LCD_B4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC15||style="background:#FFFF80" |GPIO PC15<br />
|-<br />
|28||style="background:#80FF80" |LCD_G0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD2||style="background:#FFFF80" |GPIO PD2<br />
|-<br />
|29||style="background:#80FF80" |LCD_G1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD3||style="background:#FFFF80" |GPIO PD3<br />
|-<br />
|30||style="background:#80FF80" |LCD_G2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD4||style="background:#FFFF80" |GPIO PD4<br />
|-<br />
|31||style="background:#80FF80" |LCD_G3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD5||style="background:#FFFF80" |GPIO PD5<br />
|-<br />
|32||style="background:#80FF80" |LCD_G4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD6||style="background:#FFFF80" |GPIO PD6<br />
|-<br />
|33||style="background:#80FF80" |LCD_G5||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD7||style="background:#FFFF80" |GPIO PD7<br />
|-<br />
|34||style="background:#80FF80" |LCD_R0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD11||style="background:#FFFF80" |GPIO PD11<br />
|-<br />
|35||style="background:#80FF80" |LCD_R1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD12||style="background:#FFFF80" |GPIO PD12<br />
|-<br />
|36||style="background:#80FF80" |LCD_R2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD13||style="background:#FFFF80" |GPIO PD13<br />
|-<br />
|37||style="background:#80FF80" |LCD_R3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD14||style="background:#FFFF80" |GPIO PD14<br />
|-<br />
|38||style="background:#80FF80" |LCD_R4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD15||style="background:#FFFF80" |GPIO PD15<br />
|-<br />
|39||style="background:#FFFF40" |ALOUT||style="background:#FFFF40" |audio left out ||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|40||style="background:#FFFF40" |AROUT||style="background:#FFFF40" |audio right out||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|41||style="background:#FFFF40" |MIC||style="background:#FFFF40" |audio MIC in||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|42||style="background:#2099FF" |TXD0||style="background:#2099FF" |uart0 tx||style="background:#FFFF80" |GPH0||style="background:#FFFF80" |GPIO PH0<br />
|-<br />
|43||style="background:#2099FF" |RXD0||style="background:#2099FF" |uart0 rx||style="background:#FFFF80" |GPH1||style="background:#FFFF80" |GPIO PH1<br />
|-<br />
|44||style="background:#2099FF" |TXD1||style="background:#2099FF" |uart1 tx||style="background:#FFFF80" |GPH2||style="background:#FFFF80" |GPIO PH2<br />
|-<br />
|45||style="background:#2099FF" |RXD1||style="background:#2099FF" |uart1 rx||style="background:#FFFF80" |GPH3||style="background:#FFFF80" |GPIO PH3<br />
|-<br />
|46||style="background:#2099FF" |TXD2||style="background:#2099FF" |uart2 tx||style="background:#FFFF80" |GPH4||style="background:#FFFF80" |GPIO PH4<br />
|-<br />
|47||style="background:#2099FF" |RXD2||style="background:#2099FF" |uart2 rx||style="background:#FFFF80" |GPH5||style="background:#FFFF80" |GPIO PH5<br />
|-<br />
|48||style="background:#99FF00" |I2CSCL||style="background:#99FF00" |IIC||style="background:#FFFF80" |GPE14||style="background:#FFFF80" |GPIO PE14<br />
|-<br />
|49||style="background:#99FF00" |I2CSDA||style="background:#99FF00" |IIC||style="background:#FFFF80" |GPE15||style="background:#FFFF80" |GPIO PE15<br />
|-<br />
|50||style="background:#FF80FF" |SPIMISO||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE11||style="background:#FFFF80" |GPIO PE11<br />
|-<br />
|51||style="background:#FF80FF" |SPICLK||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE13||style="background:#FFFF80" |GPIO PE13<br />
|-<br />
|52||style="background:#FF80FF" |SPIMOSI||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE12||style="background:#FFFF80" |GPIO PE12<br />
|-<br />
|53||style="background:#FF80FF" |SPI_nSS||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPL13||style="background:#FFFF80" |GPIO PL13<br />
|-<br />
|54||style="background:#FFFF40" |VCCRTC||style="background:#FFFF40" |RTC Vcc||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|55||style="background:#99FF00" |SDCLK||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL9||style="background:#FFFF80" |GPIO PL9<br />
|-<br />
|56||style="background:#99FF00" |SDCMD||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL8||style="background:#FFFF80" |GPIO PL8<br />
|-<br />
|57||style="background:#99FF00" |SDDAT0||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL0||style="background:#FFFF80" |GPIO PL0<br />
|-<br />
|58||style="background:#99FF00" |SDDAT1||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL1||style="background:#FFFF80" |GPIO PL1<br />
|-<br />
|59||style="background:#99FF00" |SDDAT2||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL2||style="background:#FFFF80" |GPIO PL2<br />
|-<br />
|60||style="background:#99FF00" |SDDTA3||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL3||style="background:#FFFF80" |GPIO PL3<br />
|-<br />
|61||style="background:#2099FF" |XP||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN9||style="background:#FFFF80" |ADC in9<br />
|-<br />
|62||style="background:#2099FF" |YP||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN7||style="background:#FFFF80" |ADC in7<br />
|-<br />
|63||style="background:#2099FF" |XM||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN8||style="background:#FFFF80" |ADC in8<br />
|-<br />
|64||style="background:#2099FF" |YM||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN6||style="background:#FFFF80" |ADC in6<br />
|-<br />
|65||style="background:#FFFF40" |LCD_PWR||style="background:#FFFF40" |LCD brightness||style="background:#FFFF80" |GPF2||style="background:#FFFF80" |GPIO PF2<br />
|-<br />
|66||style="background:#FFFF40" |BUS_INT||style="background:#FFFF40" |bus int.||style="background:#FFFF80" |GPF1||style="background:#FFFF80" |GPIO PF1<br />
|-<br />
|67||style="background:#FFFF40" |nSD_CD||style="background:#FFFF40" |SD detect||style="background:#FFFF80" |GPF5||style="background:#FFFF80" |GPIO PF5<br />
|-<br />
|68||style="background:#FFFF40" |SPI_INT||style="background:#FFFF40" |SPI int.||style="background:#FFFF80" |GPF0||style="background:#FFFF80" |GPIO PF0<br />
|-<br />
|69||style="background:#FFFF40" |GPIO_INT||style="background:#FFFF40" |GPIO int.||style="background:#FFFF80" |GPF6||style="background:#FFFF80" |GPIO PF6<br />
|-<br />
|70||style="background:#99FF00" |DN1||style="background:#99FF00" |USB device-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|71||style="background:#99FF00" |DP1||style="background:#99FF00" |USB device+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|72||style="background:#99FF00" |DN0||style="background:#99FF00" |USB Host-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|73||style="background:red" |VCC3V3||style="background:red" |DC 3.3V in||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|74||style="background:red" |GND||style="background:red" |GND||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|}<br />
<br />
||<br />
<br />
{|border="1"<br />
|+Pinout definition of SOM2416-II(120pin)<br />
!Pin number||Main Function||Note||Alt Function||Note<br />
|-style="background:#80FF80"<br />
| 1||ETX-||ETH TX-||-||-<br />
|-style="background:#80FF80"<br />
| 2||ETX+||ETH TX+||-||-<br />
|-style="background:#80FF80"<br />
| 3||GND||ETH GND||-||-<br />
|-style="background:#80FF80"<br />
| 4||ERX-||ETH RX-||-||-<br />
|-style="background:#80FF80"<br />
| 5||ERX+||ETH RX+||-||-<br />
|-style="background:#80FF80"<br />
| 6||ETH_SPD||ETH SPEED||-||-<br />
|-style="background:#80FF80"<br />
| 7||ETH_LINK||ETH LINK||-||-<br />
|-style="background:red"<br />
| 8||GND||GND||-||-<br />
|-style="background:#FFAA00"<br />
| 9||nRST||System Reset||-||-<br />
|-style="background:#FFFF40"<br />
|10||BUS_CLK||bus clock||-||-<br />
|-style="background:#FFFF40"<br />
|11||nWAIT||bus nWAIT||-||-<br />
|-style="background:#FFFF40"<br />
|12||nOE||bus nOE||-||-<br />
|-style="background:#FFFF40"<br />
|13||nWE||bus nWE||-||-<br />
|-style="background:#FFFF40"<br />
|14||nCS3||bus nCS3||-||-<br />
|-style="background:#FFFF40"<br />
|15||LADDR[0]||bus LADDR[0]||-||-<br />
|-style="background:#FFFF40"<br />
|16||LADDR[1]||bus LADDR[1]||-||-<br />
|-style="background:#FFFF40"<br />
|17||LADDR[2]||bus LADDR[2]||-||-<br />
|-style="background:#FFFF40"<br />
|18||LADDR[3]||bus LADDR[3]||-||-<br />
|-style="background:#FFFF40"<br />
|19||LADDR[4]||bus LADDR[4]||-||-<br />
|-style="background:#FFFF40"<br />
|20||LADDR[5]||bus LADDR[5]||-||-<br />
|-style="background:#FFFF40"<br />
|21||LADDR[6]||bus LADDR[6]||-||-<br />
|-style="background:#FFFF40"<br />
|22||LDATA[0]||bus LDATA[0]||-||-<br />
|-style="background:#FFFF40"<br />
|23||LDATA[1]||bus LDATA[1]||-||-<br />
|-style="background:#FFFF40"<br />
|24||LDATA[2]||bus LDATA[2]||-||-<br />
|-style="background:#FFFF40"<br />
|25||LDATA[3]||bus LDATA[3]||-||-<br />
|-style="background:#FFFF40"<br />
|26||LDATA[4]||bus LDATA[4]||-||-<br />
|-style="background:#FFFF40"<br />
|27||LDATA[5]||bus LDATA[5]||-||-<br />
|-style="background:#FFFF40"<br />
|28||LDATA[6]||bus LDATA[6]||-||-<br />
|-style="background:#FFFF40"<br />
|29||LDATA[7]||bus LDATA[7]||-||-<br />
|-style="background:red"<br />
|30||Vcc||Vcc input 3.3V||-||-<br />
|-style="background:red"<br />
|31||Vcc||Vcc input 3.3V||-||-<br />
|-style="background:#99FF00"<br />
|32||LCD_PWR||lcd Power||-||-<br />
|-style="background:#99FF00"<br />
|33||HSYNC||lcd HSYNC||-||-<br />
|-style="background:#99FF00"<br />
|34||PCLK||lcd PCLK||-||-<br />
|-style="background:#99FF00"<br />
|35||VSYNC||lcd VSYNC||-||-<br />
|-style="background:#99FF00"<br />
|36||VDEN||lcd VDEN||-||-<br />
|-style="background:red"<br />
|37||GND||GND||-||-<br />
|-style="background:#99FF00"<br />
|38||VD[2]||lcd VD[2]||-||-<br />
|-style="background:#99FF00"<br />
|39||VD[3]||lcd VD[3]||-||-<br />
|-style="background:#99FF00"<br />
|40||VD[4]||lcd VD[4]||-||-<br />
|-style="background:#99FF00"<br />
|41||VD[5]||lcd VD[5]||-||-<br />
|-style="background:#99FF00"<br />
|42||VD[6]||lcd VD[6]||-||-<br />
|-style="background:#99FF00"<br />
|43||VD[7]||lcd VD[7]||-||-<br />
|-style="background:#99FF00"<br />
|44||VD[10]||lcd VD[10]||-||-<br />
|-style="background:#99FF00"<br />
|45||VD[11]||lcd VD[11]||-||-<br />
|-style="background:#99FF00"<br />
|46||VD[12]||lcd VD[12]||-||-<br />
|-style="background:#99FF00"<br />
|47||VD[13]||lcd VD[13]||-||-<br />
|-style="background:#99FF00"<br />
|48||VD[14]||lcd VD[14]||-||-<br />
|-style="background:#99FF00"<br />
|49||VD[15]||lcd VD[15]||-||-<br />
|-style="background:#99FF00"<br />
|50||VD[18]||lcd VD[18]||-||-<br />
|-style="background:#99FF00"<br />
|51||VD[19]||lcd VD[19]||-||-<br />
|-style="background:#99FF00"<br />
|52||VD[20]||lcd VD[20]||-||-<br />
|-style="background:#99FF00"<br />
|53||VD[21]||lcd VD[21]||-||-<br />
|-style="background:#99FF00"<br />
|54||VD[22]||lcd VD[22]||-||-<br />
|-style="background:#99FF00"<br />
|55||VD[23]||lcd VD[23]||-||-<br />
|-style="background:#2099FF"<br />
|56||LPOUT||audio LPOUT||-||-<br />
|-style="background:#2099FF"<br />
|57||RPOUT||audio RPOUT||-||-<br />
|-style="background:#2099FF"<br />
|58||MIC||audio MIC||-||-<br />
|-style="background:#2099FF"<br />
|59||LIN||audio LIN||-||-<br />
|-style="background:#2099FF"<br />
|60||RIN||audio RIN||-||-<br />
|-style="background:red"<br />
|61||AGND||audio GND||-||-<br />
|-style="background:#80FF80"<br />
|62||TXD0||uart TXD0||-||-<br />
|-style="background:#80FF80"<br />
|63||RXD0||uart RXD0||-||-<br />
|-style="background:#80FF80"<br />
|64||nRTS0||uart nRTS0||-||-<br />
|-style="background:#80FF80"<br />
|65||nCTS0||uart nCTS0||-||-<br />
|-style="background:#80FF80"<br />
|66||TXD1||uart TXD1||-||-<br />
|-style="background:#80FF80"<br />
|67||RXD1||uart RXD1||-||-<br />
|-style="background:#80FF80"<br />
|68||nRTS1||uart nRTS1||-||-<br />
|-style="background:#80FF80"<br />
|69||nCTS1||uart nCTS1||-||-<br />
|-style="background:#80FF80"<br />
|70||TXD2||uart TXD2||-||-<br />
|-style="background:#80FF80"<br />
|71||RXD2||uart RXD2||-||-<br />
|-style="background:#80FF80"<br />
|72||TXD3||uart TXD3||-||-<br />
|-style="background:#80FF80"<br />
|73||RXD3||uart RXD3||-||-<br />
|-style="background:#FFAA00"<br />
|74||I2C_SCL||iic||-||-<br />
|-style="background:#FFAA00"<br />
|75||I2C_SDA||iic||-||-<br />
|-style="background:#FFFF40"<br />
|76||SPIMISO||spi||-||-<br />
|-style="background:#FFFF40"<br />
|77||SPICLK||spi||-||-<br />
|-style="background:#FFFF40"<br />
|78||SPIMOSI||spi||-||-<br />
|-style="background:#FFFF40"<br />
|79||nSS||spi||-||-<br />
|-style="background:#99FF00"<br />
|80||SD0CLK||sd0||-||-<br />
|-style="background:#99FF00"<br />
|81||SD0CMD||sd0||-||-<br />
|-style="background:#99FF00"<br />
|82||SD0DAT0||sd0||-||-<br />
|-style="background:#99FF00"<br />
|83||SD0DAT1||sd0||-||-<br />
|-style="background:#99FF00"<br />
|84||SD0DAT2||sd0||-||-<br />
|-style="background:#99FF00"<br />
|85||SD0DAT3||sd0||-||-<br />
|-style="background:red"<br />
|86||GND||GND||-||-<br />
|-style="background:red"<br />
|87||VCCRTC||VCCrtc||-||-<br />
|-style="background:#2099FF"<br />
|88||OM3||mode select||-||-<br />
|-style="background:#2099FF"<br />
|89||OM2||mode select||-||-<br />
|-style="background:#2099FF"<br />
|90||OM1||mode select||-||-<br />
|-style="background:#80FF80"<br />
|91||nSD1_CS||sd1 card detect||-||-<br />
|-style="background:#80FF80"<br />
|92||SD1CLK||sd1||-||-<br />
|-style="background:#80FF80"<br />
|93||SD1CMD||sd1||-||-<br />
|-style="background:#80FF80"<br />
|94||SD1DAT0||sd1||-||-<br />
|-style="background:#80FF80"<br />
|95||SD1DAT1||sd1||-||-<br />
|-style="background:#80FF80"<br />
|96||SD1DAT2||sd1||-||-<br />
|-style="background:#80FF80"<br />
|97||SD1DAT3||sd1||-||-<br />
|-style="background:red"<br />
|98||GND||GND||-||-<br />
|-style="background:#FFAA00"<br />
|99||XP||touch||-||-<br />
|-style="background:#FFAA00"<br />
|100||YP||touch||-||-<br />
|-style="background:#FFAA00"<br />
|101||XM||touch||-||-<br />
|-style="background:#FFAA00"<br />
|102||YM||touch||-||-<br />
|-style="background:#FFFF40"<br />
|103||AIN0||ADC||-||-<br />
|-style="background:#FFFF40"<br />
|104||AIN1||ADC||-||-<br />
|-style="background:#99FF00"<br />
|105||EINT0||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|106||EINT3||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|107||EINT5||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|108||EINT6||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|109||EINT7||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|110||EINT8||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|111||EINT9||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|112||EINT10||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|113||EINT11||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|114||EINT12||Ext Int||-||-<br />
|-style="background:red"<br />
|115||GND||GND||-||-<br />
|-style="background:#2099FF"<br />
|116||DN1||usb device||-||-<br />
|-style="background:#2099FF"<br />
|117||DP1||usb device||-||-<br />
|-style="background:#99FF00"<br />
|118||EINT2||Ext Int||-||-<br />
|-style="background:#80FF80"<br />
|119||DN0||usb host||-||-<br />
|-style="background:#80FF80"<br />
|120||DP0||usb host||-||-<br />
|-<br />
|}<br />
<br />
|-<br />
|}<br />
<br />
==Manual==<br />
* SOM2416-I Hardware Reference Manual released in Aug 22,2009: [http://www.techor.com/SOM/SOM2416_hw_ref_manual_v1.1.pdf SOM2416_hw_ref_manual_v1.1.pdf download here]<br />
* [http://www.techor.com/down/s3c2416x_rev10.rar S3C2416 datasheet Rev1.1 download here]<br />
<br />
==Layout==<br />
<br />
==Errata==<br />
==Clocking==<br />
==Power management==<br />
==Interfacing to Raw LCD Panels==<br />
<br />
=Availability=<br />
<br />
==SOM2416-I([http://www.techor.com/syssite/home/shop/1/pictures/productsimg/big/281.JPG 74pin]) Revision==<br />
===Rev PRELIMINARY===<br />
===Rev 1.0===<br />
==SOM2416-II(120pin) Revision==<br />
===Rev PRELIMINARY===<br />
<br />
==SOM2416-based products==<br />
{|<br />
|'''SOM2416-I''' based 7" DPF ODM design by ourself,<br />
DC 12V in/mini USB connected to PC/4-line AV out<br />
/USB host connected U Disk/Power switch<br />
/SDMMC socket /7" AT070TN84 LCD Panel<br />
/7 push buttons/2 speaker /IrDA remote control<br />
Rev 1.0 in Sept 24,2009<br />
||[[File:SOM2416-I-DPF7-2.JPG|frame|SOM2416-I based 7" DPF,front view,Rev 1.0 in Sept 24,2009]]||[[File:SOM2416-I-DPF7.JPG|frame|SOM2416-I based 7" DPF,back view,Rev 1.0 in Sept 24,2009]]<br />
|-<br />
|Customized '''SOM2416-II''' based 5.6" Industrial Touch Screen HMI,run uCOS/II with miniGUI windows management system,rev 1.0 in Sept 1,2009<br />
||[[File:SOM2416-II-HMI1.JPG|frame|SOM2416-II based Industrial Touch Screen HMI,front and back view]]||[[File:SOM2416-II-HMI.JPG|frame|SOM2416-II based Industrial Touch Screen HMI,run uCOS/II with miniGUI]]<br />
|}<br />
<br />
==SOM2416 ODM cases==<br />
{|border="0" align="center"<br />
|+'''SOM2416 baseded ODM/OEM Cases'''<br />
|'''Industrial HMI Machine''', SOM2416-I directly <br>soldered on top of 2-layer '''App board'''(below)||A Special '''Handheld Measurement Instrument''', <br>Customized 6-layer Main Board based on S3C2416<br />
|-<br />
|[[File:Solution2.jpg|448px|Industrial HMI Machine, SOM2416-I directly <br>soldered on top of 2-layer App board(below)]]||[[File:Solution1.jpg|746px|A Special Handheld Measurement Instrument, <br>Customized 6-layer Main Board based on S3C2416]]<br />
|}<br />
<br />
=App Demo Board=<br />
{|<br />
|[[File:AppBoard800.jpg|frame|<b>AppDemoBoard Rev 1.1</b> carries SOM2416-I]]<br />
|-<br />
|[[File:SOM2416+43TFTLCD.jpg|frame|<b>KIT2416-I</b> := <i>SOM2416-I</i> + <i>AppDemoBoard Rev 1.1</i> + <i>4.3" LCD w/ touch</i> + <i>T-Flash card</i><br><b>Back view</b> of KIT2416-I, running WINCE 5.0 of Microsoft Media Player]]<br />
|}<br />
<br />
=Adapters=<br />
==Expansion boards==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]</div>Som2416https://elinux.org/index.php?title=SOM&diff=14682SOM2009-11-12T17:36:56Z<p>Som2416: </p>
<hr />
<div>SOM: System On Module, also call '[[Embedded_computer]],[[Embedded_System_Module(ESM)]],Computer_on-Module(COM)', <br />
<br />
<br />
''SOMxxx'' Series Embedded Module: <b>Designed and manufactured by [http://www.techor.com/ TECHOR of China]. Series of Size 40x40x4mm, Weight about 10g, the smallest and lightest [[System-on-Module]] in the World! including:</b><br />
* [[SOM2416]] - by [http://www.techor.com/product_281.html TECHOR.COM of China], Samsung 400MHz ARM926EJ-S based cost effective [[Application Processor]]<br />
* [[SOM6410]] - by [http://www.techor.com/product_282.html TECHOR.COM of China],Samsung 667Hz ARM1176JFZ-S based cost effective [[Application Processor]]<br />
* [[SOM3530]] - by [http://www.techor.com/product_283.html TECHOR.COM of China], TI 720MHz [[CORETEX-A8]] + 600MHz TMS320DM64x+ dual core SOC<br />
<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=SOM2416&diff=14681SOM24162009-11-12T17:31:10Z<p>Som2416: </p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSom2416&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
<br />
This page collects information about [http://www.samsung.com/global/business/semiconductor SAMSUNG semiconductor's] [http://www.arm.com/ ARM926EJ] based 400MHz [[S3C2416]] [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C2416 Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_281.html '''SOM2416'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
<br />
<br />
=Events=<br />
<I><br />
'''2009.11.01''': KIT2416-II will be released in Nov 10, 2009, it's extendable, we will develop Wifi, Bluetooth,GPS, GPRS/3G, FM module, CAN, 4x4 keypad, CMMB, LCD to VGA, LCD to LVDS,and series of Industial Sensors like Toradex Oak : [http://www.toradex.com/En/Products/Oak_USB_Sensors Oak_USB_Sensors] to plug onto the KIT2416-II and KIT3530, KIT6410<br />
<br>[[File:KIT2416-II-640.JPG]]<br />
<br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM3530] '''Rev PRELIMINARY''' will be released in Oct 30,2009! [[SOM3530|elinux.org/SOM3530]] is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
<br>[[File:SOM3530msk.jpg|200px|SOM3530, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
<br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM6410] '''Rev PRELIMINARY''' will be released in Oct 30,2009! [[SOM6410|elinux.org/SOM6410]] is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
<br>[[File:SOM6410msk.jpg|200px|SOM6410, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
<br />
'''2009.09.30''': '''SOM2416-I Rev2''' and '''SOM2416-II Rev PRELIMINARY''' ([http://elinux.org/SOM2416#Pinout_definitions 120pin],4x4cm of 1.27mm pin pitch) Released and for Order/Samples<br><br />
'''2009.09.05''': Work together with [http://www.djyos.com/technology/2009-05-24/47.html DJYOS](The first of China Embedded Realtime Operation System) and port the DJYOS to '''SOM2416-I''' <br><br />
'''2009.08.30''': '''SOM2416-I Rev 1.0''' and '''SOM2416-II Rev PRELIMINARY''' annouce to be released on Mid-Sept,2009. '''SOM2416-II''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package <br><br />
'''2009.08.20''': [http://www.techor.com/product_281.html SOM2416-I] '''Rev PRELIMINARY''' released, '''SOM2416-I''' is 4x4cm size, 74pin 2.0mm pitch QFP-like package<br />
</I><br />
<br />
=How to Purchase=<br />
==SOM([[System-on-Module]]) Order Part Number==<br />
{|border="0"<br />
!Part Number||Pin#||CPU Freq||DDR2 SDRAM||NAND Flash||Ethernet||Audio||Note<br />
|-<br />
|SOM2416-I-400-64-256M<br>default:'''SOM2416-I'''||74||400MHz||64MB||256MB||LAN9220||WM8731L||For Samples/In stock/no MOQ<ref>Minimum Order Quantity</ref> limited<br />
|-<br />
|SOM2416-I-400-64-256M-9221||74||400MHz||64MB||256MB||LAN9221||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-I-400-64-256M-NENA||74||400MHz||64MB||256MB||No||No||MOQ:10+pcs<br />
|-<br />
|SOM2416-II-400-64-256M<br>default:'''SOM2416-II'''||120||400MHz||64MB||256MB||LAN9220||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-II-400-64-256M-9221||120||400MHz||64MB||256MB||LAN9221||WM8731L||For Samples/In stock/no MOQ limited<br />
|-<br />
|SOM2416-II-400-64-256M-NENA||120||400MHz||64MB||256MB||No||No||MOQ:10+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-I-400-32-64M||74||400MHz||32MB||64MB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-I-400-64-1G||74||400MHz||64MB||1GB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-I-400-64-2G-9221||74||400MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-II-400-32-64M||120||400MHz||32MB||64MB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-400-64-1G||120||400MHz||64MB||1GB||LAN9220||WM8731L||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-400-64-2G-9221||120||400MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|...<br />
|-<br />
|SOM2416-I-266-64-256M||74||266MHz||64MB||256MB||LAN9220||WM8731L||MOQ:10+pcs<br />
|-<br />
|SOM2416-I-266-32-64M-NA||74||266MHz||32MB||64MB||LAN9220||No||MOQ:50+pcs<br />
|-<br />
|SOM2416-II-266-64-256M-NE||120||266MHz||64MB||256MB||No||WM8731L||MOQ:10+pcs<br />
|-<br />
|SOM2416-II-266-64-2G-9221||120||266MHz||64MB||2GB||LAN9221||WM8731L||MOQ:50+pcs<br />
|-<br />
|}<br />
'''Note:''' <references/><br />
<br><br />
==Development/Evaluation KIT Order Part Number==<br />
<br />
{|border="1" align="center"<br />
<br />
!Part Number||Note<br />
|-<br />
|'''KIT2416-I'''<br>or<br>'''KIT2416-II'''||''KIT2416-I'' and ''KIT2416-II'' is a '''NECESSARY''' basic evaluation system kit for illustrating the functionality, connectivity of SOM2416-I/SOM2416-II modules on their each '''App Demo Board'''.<br />
; each KIT2416 includes :<br />
:# '''SOM2416-I'''(74pin,4x4cm) or '''SOM2416-II'''(120pin,4x4cm) Embedded Module<br />
:# 4.3" 16:9 '''TFT LCD''', LED backlight digital adjustable, 480 x RGB x 272 pixels, with 4-wire resistance touch screen<br />
:# Theirs corresponding [[SOM2416#App_Demo_Board|App Demo Board]] ''Rev 1.1'', which having USB host and device/Ethernet/3 or 4 UART/IIC/SPI/LCD/touch screen/Stereo Audio out/MIC/Line in/SDMMC/ADC/PWM/GPIO/local bus interfaces<br />
:# '''Cables''' : Ethernet cable, mini USB cable, RS232 Cable<br />
:# '''Power Supply''' AC 110V~220V in DC 5V 1A output<br />
:# '''SDK''': WINCE 5.0 SDK and documents,App Demo Board's SCH, PCB source code; Linux SDK in under developing and planing Nov 2009 release<br />
<br />
[[File:KIT2416-I-4.3-00.JPG]]<br><b>KIT2416-I(74pin)</b> connected U-Disk, Speaker, PC computer(Power Supply and data sync), Ethernet and console(RS232)<br />
<br />
|}<br />
<br><br />
'''3.How to Order? One of the 3 ways:'''<br />
{|<br />
|<br />
# Send Purchase Order mail to ''embed_sales at techor dot com'' and specifying ''Part#/Quantity/Where to Ship/Note'' , we will reply you the Quotation and payment instruction in 2 work days by e-mail<br />
# Add our services MSN: ''cxzeng at msn dot com'' , and chat/talk(in English and Chinese only) with our services to specify what your reqirements online<br />
# or you could refer to the official web page for detailed: [http://www.techor.com/product_281.html SOM2416]<br />
|}<br />
<br />
=Hardware=<br />
<br />
== General Info ==<br />
<br />
{|border="1"<br />
|+'''Two Models of SOM2416'''<br />
|Model||'''SOM2416-I'''<br>74pin 2.0mm pitch,4x4cm outer contour||'''SOM2416-II'''<br>120pin 1.27mm pitch,4x4cm outer contour<br />
|-<br />
|Picture||[[File:SOM2416-watermark.jpg]]||[[File:SOM2416-II-440.JPG]]<br />
|-<br />
|Components||<br />
<br />
{|border="0"<br />
!No.||Name||Comment<br />
|-<br />
|1||DDR2 SDRAM||64MB/32MB optional<br />
|-<br />
|2||LAN9220/LAN9221||High Performance 10/100M Ethernet controller<br />
|-<br />
|3||NAND Flash||2GB/1GB/512MB/256MB/128MB/64MB SLC/MLC optional<br />
|-<br />
|4||WM8731L||IIS Audio codec<br />
|-<br />
|5||S3C2416||400MHz/266MHz optional<br />
|}<br />
|-<br />
|Package||[[File:Som2416-package.gif]]||[[File:som2416-II-package.gif]]<br />
|-<br />
|Layout||[[File:72pin-top.jpg]]||[[File:120pin-top.jpg]]<br />
|}<br />
<br />
==Pinout definitions==<br />
<br />
{|<br />
|-<br />
|<br />
{|border="1"<br />
|+Pinout definition of SOM2416-I(74pin)<br />
!Pin number||Main Function||Note||Alt Function||Note<br />
|-<br />
| 1||style="background:#99FF00" |DP0 ||style="background:#99FF00" |USB Host+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 2||style="background:#80FF80" |ETX-||style="background:#80FF80" |ETH TX-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 3||style="background:#80FF80" |ETX+||style="background:#80FF80" |ETH TX+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 4||style="background:#80FF80" |ERX-||style="background:#80FF80" |ETH RX-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 5||style="background:#80FF80" |ERX+||style="background:#80FF80" |ETH RX+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 6||style="background:#FFAA00" |nOE||style="background:#FFAA00" |bus Read signal||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 7||style="background:#FFAA00" |nWE||style="background:#FFAA00" |bus Write signal||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
| 8||style="background:#FFAA00" |nCS3||style="background:#FFAA00" |bus Chip Select#3||style="background:#FFFF80" |GPA14||style="background:#FFFF80" |GPIO PA14<br />
|-<br />
| 9||style="background:#FFAA00" |ADDR0||style="background:#FFAA00" |bus addr||style="background:#FFFF80" |GPA0||style="background:#FFFF80"|GPIO PA0<br />
|-<br />
|10||style="background:#FFAA00" |ADDR1||style="background:#FFAA00" |bus addr||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|11||style="background:#FFAA00" |DATA0||style="background:#FFAA00" |bus data0||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|12||style="background:#FFAA00" |DATA1||style="background:#FFAA00" |bus data1||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|13||style="background:#FFAA00" |DATA2||style="background:#FFAA00" |bus data2||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|14||style="background:#FFAA00" |DATA3||style="background:#FFAA00" |bus data3||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|15||style="background:#FFAA00" |DATA4||style="background:#FFAA00" |bus data4||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|16||style="background:#FFAA00" |DATA5||style="background:#FFAA00" |bus data5||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|17||style="background:#FFAA00" |DATA6||style="background:#FFAA00" |bus data6||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|18||style="background:#FFAA00" |DATA7||style="background:#FFAA00" |bus data7||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|19||style="background:#80FF80" |HSYNC||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC2||style="background:#FFFF80" |GPIO PC2<br />
|-<br />
|20||style="background:#80FF80" |PCLK||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC1||style="background:#FFFF80" |GPIO PC1<br />
|-<br />
|21||style="background:#80FF80" |VSYNC||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC3||style="background:#FFFF80" |GPIO PC3<br />
|-<br />
|22||style="background:#80FF80" |VDEN||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC4||style="background:#FFFF80" |GPIO PC4<br />
|-<br />
|23||style="background:#80FF80" |LCD_B0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC11||style="background:#FFFF80" |GPIO PC11<br />
|-<br />
|24||style="background:#80FF80" |LCD_B1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC12||style="background:#FFFF80" |GPIO PC12<br />
|-<br />
|25||style="background:#80FF80" |LCD_B2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC13||style="background:#FFFF80" |GPIO PC13<br />
|-<br />
|26||style="background:#80FF80" |LCD_B3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC14||style="background:#FFFF80" |GPIO PC14<br />
|-<br />
|27||style="background:#80FF80" |LCD_B4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPC15||style="background:#FFFF80" |GPIO PC15<br />
|-<br />
|28||style="background:#80FF80" |LCD_G0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD2||style="background:#FFFF80" |GPIO PD2<br />
|-<br />
|29||style="background:#80FF80" |LCD_G1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD3||style="background:#FFFF80" |GPIO PD3<br />
|-<br />
|30||style="background:#80FF80" |LCD_G2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD4||style="background:#FFFF80" |GPIO PD4<br />
|-<br />
|31||style="background:#80FF80" |LCD_G3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD5||style="background:#FFFF80" |GPIO PD5<br />
|-<br />
|32||style="background:#80FF80" |LCD_G4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD6||style="background:#FFFF80" |GPIO PD6<br />
|-<br />
|33||style="background:#80FF80" |LCD_G5||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD7||style="background:#FFFF80" |GPIO PD7<br />
|-<br />
|34||style="background:#80FF80" |LCD_R0||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD11||style="background:#FFFF80" |GPIO PD11<br />
|-<br />
|35||style="background:#80FF80" |LCD_R1||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD12||style="background:#FFFF80" |GPIO PD12<br />
|-<br />
|36||style="background:#80FF80" |LCD_R2||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD13||style="background:#FFFF80" |GPIO PD13<br />
|-<br />
|37||style="background:#80FF80" |LCD_R3||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD14||style="background:#FFFF80" |GPIO PD14<br />
|-<br />
|38||style="background:#80FF80" |LCD_R4||style="background:#80FF80" |lcd||style="background:#FFFF80" |GPD15||style="background:#FFFF80" |GPIO PD15<br />
|-<br />
|39||style="background:#FFFF40" |ALOUT||style="background:#FFFF40" |audio left out ||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|40||style="background:#FFFF40" |AROUT||style="background:#FFFF40" |audio right out||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|41||style="background:#FFFF40" |MIC||style="background:#FFFF40" |audio MIC in||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|42||style="background:#2099FF" |TXD0||style="background:#2099FF" |uart0 tx||style="background:#FFFF80" |GPH0||style="background:#FFFF80" |GPIO PH0<br />
|-<br />
|43||style="background:#2099FF" |RXD0||style="background:#2099FF" |uart0 rx||style="background:#FFFF80" |GPH1||style="background:#FFFF80" |GPIO PH1<br />
|-<br />
|44||style="background:#2099FF" |TXD1||style="background:#2099FF" |uart1 tx||style="background:#FFFF80" |GPH2||style="background:#FFFF80" |GPIO PH2<br />
|-<br />
|45||style="background:#2099FF" |RXD1||style="background:#2099FF" |uart1 rx||style="background:#FFFF80" |GPH3||style="background:#FFFF80" |GPIO PH3<br />
|-<br />
|46||style="background:#2099FF" |TXD2||style="background:#2099FF" |uart2 tx||style="background:#FFFF80" |GPH4||style="background:#FFFF80" |GPIO PH4<br />
|-<br />
|47||style="background:#2099FF" |RXD2||style="background:#2099FF" |uart2 rx||style="background:#FFFF80" |GPH5||style="background:#FFFF80" |GPIO PH5<br />
|-<br />
|48||style="background:#99FF00" |I2CSCL||style="background:#99FF00" |IIC||style="background:#FFFF80" |GPE14||style="background:#FFFF80" |GPIO PE14<br />
|-<br />
|49||style="background:#99FF00" |I2CSDA||style="background:#99FF00" |IIC||style="background:#FFFF80" |GPE15||style="background:#FFFF80" |GPIO PE15<br />
|-<br />
|50||style="background:#FF80FF" |SPIMISO||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE11||style="background:#FFFF80" |GPIO PE11<br />
|-<br />
|51||style="background:#FF80FF" |SPICLK||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE13||style="background:#FFFF80" |GPIO PE13<br />
|-<br />
|52||style="background:#FF80FF" |SPIMOSI||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPE12||style="background:#FFFF80" |GPIO PE12<br />
|-<br />
|53||style="background:#FF80FF" |SPI_nSS||style="background:#FF80FF" |SPI||style="background:#FFFF80" |GPL13||style="background:#FFFF80" |GPIO PL13<br />
|-<br />
|54||style="background:#FFFF40" |VCCRTC||style="background:#FFFF40" |RTC Vcc||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|55||style="background:#99FF00" |SDCLK||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL9||style="background:#FFFF80" |GPIO PL9<br />
|-<br />
|56||style="background:#99FF00" |SDCMD||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL8||style="background:#FFFF80" |GPIO PL8<br />
|-<br />
|57||style="background:#99FF00" |SDDAT0||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL0||style="background:#FFFF80" |GPIO PL0<br />
|-<br />
|58||style="background:#99FF00" |SDDAT1||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL1||style="background:#FFFF80" |GPIO PL1<br />
|-<br />
|59||style="background:#99FF00" |SDDAT2||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL2||style="background:#FFFF80" |GPIO PL2<br />
|-<br />
|60||style="background:#99FF00" |SDDTA3||style="background:#99FF00" |MMC/SD1||style="background:#FFFF80" |GPL3||style="background:#FFFF80" |GPIO PL3<br />
|-<br />
|61||style="background:#2099FF" |XP||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN9||style="background:#FFFF80" |ADC in9<br />
|-<br />
|62||style="background:#2099FF" |YP||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN7||style="background:#FFFF80" |ADC in7<br />
|-<br />
|63||style="background:#2099FF" |XM||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN8||style="background:#FFFF80" |ADC in8<br />
|-<br />
|64||style="background:#2099FF" |YM||style="background:#2099FF" |Touch||style="background:#FFFF80" |AIN6||style="background:#FFFF80" |ADC in6<br />
|-<br />
|65||style="background:#FFFF40" |LCD_PWR||style="background:#FFFF40" |LCD brightness||style="background:#FFFF80" |GPF2||style="background:#FFFF80" |GPIO PF2<br />
|-<br />
|66||style="background:#FFFF40" |BUS_INT||style="background:#FFFF40" |bus int.||style="background:#FFFF80" |GPF1||style="background:#FFFF80" |GPIO PF1<br />
|-<br />
|67||style="background:#FFFF40" |nSD_CD||style="background:#FFFF40" |SD detect||style="background:#FFFF80" |GPF5||style="background:#FFFF80" |GPIO PF5<br />
|-<br />
|68||style="background:#FFFF40" |SPI_INT||style="background:#FFFF40" |SPI int.||style="background:#FFFF80" |GPF0||style="background:#FFFF80" |GPIO PF0<br />
|-<br />
|69||style="background:#FFFF40" |GPIO_INT||style="background:#FFFF40" |GPIO int.||style="background:#FFFF80" |GPF6||style="background:#FFFF80" |GPIO PF6<br />
|-<br />
|70||style="background:#99FF00" |DN1||style="background:#99FF00" |USB device-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|71||style="background:#99FF00" |DP1||style="background:#99FF00" |USB device+||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|72||style="background:#99FF00" |DN0||style="background:#99FF00" |USB Host-||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|73||style="background:red" |VCC3V3||style="background:red" |DC 3.3V in||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|-<br />
|74||style="background:red" |GND||style="background:red" |GND||style="background:#FFFF80" |-||style="background:#FFFF80" |-<br />
|}<br />
<br />
||<br />
<br />
{|border="1"<br />
|+Pinout definition of SOM2416-II(120pin)<br />
!Pin number||Main Function||Note||Alt Function||Note<br />
|-style="background:#80FF80"<br />
| 1||ETX-||ETH TX-||-||-<br />
|-style="background:#80FF80"<br />
| 2||ETX+||ETH TX+||-||-<br />
|-style="background:#80FF80"<br />
| 3||GND||ETH GND||-||-<br />
|-style="background:#80FF80"<br />
| 4||ERX-||ETH RX-||-||-<br />
|-style="background:#80FF80"<br />
| 5||ERX+||ETH RX+||-||-<br />
|-style="background:#80FF80"<br />
| 6||ETH_SPD||ETH SPEED||-||-<br />
|-style="background:#80FF80"<br />
| 7||ETH_LINK||ETH LINK||-||-<br />
|-style="background:red"<br />
| 8||GND||GND||-||-<br />
|-style="background:#FFAA00"<br />
| 9||nRST||System Reset||-||-<br />
|-style="background:#FFFF40"<br />
|10||BUS_CLK||bus clock||-||-<br />
|-style="background:#FFFF40"<br />
|11||nWAIT||bus nWAIT||-||-<br />
|-style="background:#FFFF40"<br />
|12||nOE||bus nOE||-||-<br />
|-style="background:#FFFF40"<br />
|13||nWE||bus nWE||-||-<br />
|-style="background:#FFFF40"<br />
|14||nCS3||bus nCS3||-||-<br />
|-style="background:#FFFF40"<br />
|15||LADDR[0]||bus LADDR[0]||-||-<br />
|-style="background:#FFFF40"<br />
|16||LADDR[1]||bus LADDR[1]||-||-<br />
|-style="background:#FFFF40"<br />
|17||LADDR[2]||bus LADDR[2]||-||-<br />
|-style="background:#FFFF40"<br />
|18||LADDR[3]||bus LADDR[3]||-||-<br />
|-style="background:#FFFF40"<br />
|19||LADDR[4]||bus LADDR[4]||-||-<br />
|-style="background:#FFFF40"<br />
|20||LADDR[5]||bus LADDR[5]||-||-<br />
|-style="background:#FFFF40"<br />
|21||LADDR[6]||bus LADDR[6]||-||-<br />
|-style="background:#FFFF40"<br />
|22||LDATA[0]||bus LDATA[0]||-||-<br />
|-style="background:#FFFF40"<br />
|23||LDATA[1]||bus LDATA[1]||-||-<br />
|-style="background:#FFFF40"<br />
|24||LDATA[2]||bus LDATA[2]||-||-<br />
|-style="background:#FFFF40"<br />
|25||LDATA[3]||bus LDATA[3]||-||-<br />
|-style="background:#FFFF40"<br />
|26||LDATA[4]||bus LDATA[4]||-||-<br />
|-style="background:#FFFF40"<br />
|27||LDATA[5]||bus LDATA[5]||-||-<br />
|-style="background:#FFFF40"<br />
|28||LDATA[6]||bus LDATA[6]||-||-<br />
|-style="background:#FFFF40"<br />
|29||LDATA[7]||bus LDATA[7]||-||-<br />
|-style="background:red"<br />
|30||Vcc||Vcc input 3.3V||-||-<br />
|-style="background:red"<br />
|31||Vcc||Vcc input 3.3V||-||-<br />
|-style="background:#99FF00"<br />
|32||LCD_PWR||lcd Power||-||-<br />
|-style="background:#99FF00"<br />
|33||HSYNC||lcd HSYNC||-||-<br />
|-style="background:#99FF00"<br />
|34||PCLK||lcd PCLK||-||-<br />
|-style="background:#99FF00"<br />
|35||VSYNC||lcd VSYNC||-||-<br />
|-style="background:#99FF00"<br />
|36||VDEN||lcd VDEN||-||-<br />
|-style="background:red"<br />
|37||GND||GND||-||-<br />
|-style="background:#99FF00"<br />
|38||VD[2]||lcd VD[2]||-||-<br />
|-style="background:#99FF00"<br />
|39||VD[3]||lcd VD[3]||-||-<br />
|-style="background:#99FF00"<br />
|40||VD[4]||lcd VD[4]||-||-<br />
|-style="background:#99FF00"<br />
|41||VD[5]||lcd VD[5]||-||-<br />
|-style="background:#99FF00"<br />
|42||VD[6]||lcd VD[6]||-||-<br />
|-style="background:#99FF00"<br />
|43||VD[7]||lcd VD[7]||-||-<br />
|-style="background:#99FF00"<br />
|44||VD[10]||lcd VD[10]||-||-<br />
|-style="background:#99FF00"<br />
|45||VD[11]||lcd VD[11]||-||-<br />
|-style="background:#99FF00"<br />
|46||VD[12]||lcd VD[12]||-||-<br />
|-style="background:#99FF00"<br />
|47||VD[13]||lcd VD[13]||-||-<br />
|-style="background:#99FF00"<br />
|48||VD[14]||lcd VD[14]||-||-<br />
|-style="background:#99FF00"<br />
|49||VD[15]||lcd VD[15]||-||-<br />
|-style="background:#99FF00"<br />
|50||VD[18]||lcd VD[18]||-||-<br />
|-style="background:#99FF00"<br />
|51||VD[19]||lcd VD[19]||-||-<br />
|-style="background:#99FF00"<br />
|52||VD[20]||lcd VD[20]||-||-<br />
|-style="background:#99FF00"<br />
|53||VD[21]||lcd VD[21]||-||-<br />
|-style="background:#99FF00"<br />
|54||VD[22]||lcd VD[22]||-||-<br />
|-style="background:#99FF00"<br />
|55||VD[23]||lcd VD[23]||-||-<br />
|-style="background:#2099FF"<br />
|56||LPOUT||audio LPOUT||-||-<br />
|-style="background:#2099FF"<br />
|57||RPOUT||audio RPOUT||-||-<br />
|-style="background:#2099FF"<br />
|58||MIC||audio MIC||-||-<br />
|-style="background:#2099FF"<br />
|59||LIN||audio LIN||-||-<br />
|-style="background:#2099FF"<br />
|60||RIN||audio RIN||-||-<br />
|-style="background:red"<br />
|61||AGND||audio GND||-||-<br />
|-style="background:#80FF80"<br />
|62||TXD0||uart TXD0||-||-<br />
|-style="background:#80FF80"<br />
|63||RXD0||uart RXD0||-||-<br />
|-style="background:#80FF80"<br />
|64||nRTS0||uart nRTS0||-||-<br />
|-style="background:#80FF80"<br />
|65||nCTS0||uart nCTS0||-||-<br />
|-style="background:#80FF80"<br />
|66||TXD1||uart TXD1||-||-<br />
|-style="background:#80FF80"<br />
|67||RXD1||uart RXD1||-||-<br />
|-style="background:#80FF80"<br />
|68||nRTS1||uart nRTS1||-||-<br />
|-style="background:#80FF80"<br />
|69||nCTS1||uart nCTS1||-||-<br />
|-style="background:#80FF80"<br />
|70||TXD2||uart TXD2||-||-<br />
|-style="background:#80FF80"<br />
|71||RXD2||uart RXD2||-||-<br />
|-style="background:#80FF80"<br />
|72||TXD3||uart TXD3||-||-<br />
|-style="background:#80FF80"<br />
|73||RXD3||uart RXD3||-||-<br />
|-style="background:#FFAA00"<br />
|74||I2C_SCL||iic||-||-<br />
|-style="background:#FFAA00"<br />
|75||I2C_SDA||iic||-||-<br />
|-style="background:#FFFF40"<br />
|76||SPIMISO||spi||-||-<br />
|-style="background:#FFFF40"<br />
|77||SPICLK||spi||-||-<br />
|-style="background:#FFFF40"<br />
|78||SPIMOSI||spi||-||-<br />
|-style="background:#FFFF40"<br />
|79||nSS||spi||-||-<br />
|-style="background:#99FF00"<br />
|80||SD0CLK||sd0||-||-<br />
|-style="background:#99FF00"<br />
|81||SD0CMD||sd0||-||-<br />
|-style="background:#99FF00"<br />
|82||SD0DAT0||sd0||-||-<br />
|-style="background:#99FF00"<br />
|83||SD0DAT1||sd0||-||-<br />
|-style="background:#99FF00"<br />
|84||SD0DAT2||sd0||-||-<br />
|-style="background:#99FF00"<br />
|85||SD0DAT3||sd0||-||-<br />
|-style="background:red"<br />
|86||GND||GND||-||-<br />
|-style="background:red"<br />
|87||VCCRTC||VCCrtc||-||-<br />
|-style="background:#2099FF"<br />
|88||OM3||mode select||-||-<br />
|-style="background:#2099FF"<br />
|89||OM2||mode select||-||-<br />
|-style="background:#2099FF"<br />
|90||OM1||mode select||-||-<br />
|-style="background:#80FF80"<br />
|91||nSD1_CS||sd1 card detect||-||-<br />
|-style="background:#80FF80"<br />
|92||SD1CLK||sd1||-||-<br />
|-style="background:#80FF80"<br />
|93||SD1CMD||sd1||-||-<br />
|-style="background:#80FF80"<br />
|94||SD1DAT0||sd1||-||-<br />
|-style="background:#80FF80"<br />
|95||SD1DAT1||sd1||-||-<br />
|-style="background:#80FF80"<br />
|96||SD1DAT2||sd1||-||-<br />
|-style="background:#80FF80"<br />
|97||SD1DAT3||sd1||-||-<br />
|-style="background:red"<br />
|98||GND||GND||-||-<br />
|-style="background:#FFAA00"<br />
|99||XP||touch||-||-<br />
|-style="background:#FFAA00"<br />
|100||YP||touch||-||-<br />
|-style="background:#FFAA00"<br />
|101||XM||touch||-||-<br />
|-style="background:#FFAA00"<br />
|102||YM||touch||-||-<br />
|-style="background:#FFFF40"<br />
|103||AIN0||ADC||-||-<br />
|-style="background:#FFFF40"<br />
|104||AIN1||ADC||-||-<br />
|-style="background:#99FF00"<br />
|105||EINT0||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|106||EINT3||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|107||EINT5||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|108||EINT6||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|109||EINT7||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|110||EINT8||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|111||EINT9||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|112||EINT10||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|113||EINT11||Ext Int||-||-<br />
|-style="background:#99FF00"<br />
|114||EINT12||Ext Int||-||-<br />
|-style="background:red"<br />
|115||GND||GND||-||-<br />
|-style="background:#2099FF"<br />
|116||DN1||usb device||-||-<br />
|-style="background:#2099FF"<br />
|117||DP1||usb device||-||-<br />
|-style="background:#99FF00"<br />
|118||EINT2||Ext Int||-||-<br />
|-style="background:#80FF80"<br />
|119||DN0||usb host||-||-<br />
|-style="background:#80FF80"<br />
|120||DP0||usb host||-||-<br />
|-<br />
|}<br />
<br />
|-<br />
|}<br />
<br />
==Manual==<br />
* SOM2416-I Hardware Reference Manual released in Aug 22,2009: [http://www.techor.com/SOM/SOM2416_hw_ref_manual_v1.1.pdf SOM2416_hw_ref_manual_v1.1.pdf download here]<br />
* [http://www.techor.com/down/s3c2416x_rev10.rar S3C2416 datasheet Rev1.1 download here]<br />
<br />
==Layout==<br />
<br />
==Errata==<br />
==Clocking==<br />
==Power management==<br />
==Interfacing to Raw LCD Panels==<br />
<br />
=Availability=<br />
<br />
==SOM2416-I([http://www.techor.com/syssite/home/shop/1/pictures/productsimg/big/281.JPG 74pin]) Revision==<br />
===Rev PRELIMINARY===<br />
===Rev 1.0===<br />
==SOM2416-II(120pin) Revision==<br />
===Rev PRELIMINARY===<br />
<br />
==SOM2416-based products==<br />
{|<br />
|'''SOM2416-I''' based 7" DPF ODM design by ourself,<br />
DC 12V in/mini USB connected to PC/4-line AV out<br />
/USB host connected U Disk/Power switch<br />
/SDMMC socket /7" AT070TN84 LCD Panel<br />
/7 push buttons/2 speaker /IrDA remote control<br />
Rev 1.0 in Sept 24,2009<br />
||[[File:SOM2416-I-DPF7-2.JPG|frame|SOM2416-I based 7" DPF,front view,Rev 1.0 in Sept 24,2009]]||[[File:SOM2416-I-DPF7.JPG|frame|SOM2416-I based 7" DPF,back view,Rev 1.0 in Sept 24,2009]]<br />
|-<br />
|Customized '''SOM2416-II''' based 5.6" Industrial Touch Screen HMI,run uCOS/II with miniGUI windows management system,rev 1.0 in Sept 1,2009<br />
||[[File:SOM2416-II-HMI1.JPG|frame|SOM2416-II based Industrial Touch Screen HMI,front and back view]]||[[File:SOM2416-II-HMI.JPG|frame|SOM2416-II based Industrial Touch Screen HMI,run uCOS/II with miniGUI]]<br />
|}<br />
<br />
==SOM2416 ODM cases==<br />
{|border="0" align="center"<br />
|+'''SOM2416 baseded ODM/OEM Cases'''<br />
|'''Industrial HMI Machine''', SOM2416-I directly <br>soldered on top of 2-layer '''App board'''(below)||A Special '''Handheld Measurement Instrument''', <br>Customized 6-layer Main Board based on S3C2416<br />
|-<br />
|[[File:Solution2.jpg|448px|Industrial HMI Machine, SOM2416-I directly <br>soldered on top of 2-layer App board(below)]]||[[File:Solution1.jpg|746px|A Special Handheld Measurement Instrument, <br>Customized 6-layer Main Board based on S3C2416]]<br />
|}<br />
<br />
=App Demo Board=<br />
{|<br />
|[[File:AppBoard800.jpg|frame|<b>AppDemoBoard Rev 1.1</b> carries SOM2416-I]]<br />
|-<br />
|[[File:SOM2416+43TFTLCD.jpg|frame|<b>KIT2416-I</b> := <i>SOM2416-I</i> + <i>AppDemoBoard Rev 1.1</i> + <i>4.3" LCD w/ touch</i> + <i>T-Flash card</i><br><b>Back view</b> of KIT2416-I, running WINCE 5.0 of Microsoft Media Player]]<br />
|}<br />
<br />
=Adapters=<br />
==Expansion boards==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=SOM6410&diff=14680SOM64102009-11-12T17:30:33Z<p>Som2416: </p>
<hr />
<div>[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOM6410&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.samsung.com/global/business/semiconductor SAMSUNG semiconductor's] [http://www.arm.com/products/CPUs/ARM1176.html ARM1176JZF-S] based up-to 667MHz [[S3C6410]] [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C6410 Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_282.html '''SOM6410'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
=Events=<br />
<I><br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM6410] '''Rev PRELIMINARY''' will be released in Oct 30,2009! '''SOM6410''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
[[File:SOM6410msk.jpg|SOM6410 engineering picture, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]][[File:SOM6410-L.JPG|SOM6410 actual sample picture, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
</I><br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOM6410 Revision ==<br />
==SOM6410-based products ==<br />
==SOM6410 ODM cases ==<br />
=5 App Demo Board =<br />
=6 Adapters =<br />
== Expansion boards ==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416https://elinux.org/index.php?title=SOM6410&diff=14679SOM64102009-11-12T17:30:09Z<p>Som2416: </p>
<hr />
<div>[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]<br />
<br />
[http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Felinux.org%2FSOM6410&sl=en&tl=zh-CN&history_state0=&swap=1 <b>【翻译本页成简体中文网页|Translating this page to Simplified Chinese】</b>]<br />
<br />
----<br />
This page collects information about [http://www.samsung.com/global/business/semiconductor SAMSUNG semiconductor's] [http://www.arm.com/products/CPUs/ARM1176.html ARM1176JZF-S] based up-to 667MHz [[S3C6410]] [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C6410 Application Processor] engineering by [http://www.techor.com TECHOR] ''Model Number'' [http://www.techor.com/product_282.html '''SOM6410'''] : [[Computer-on-Module|System On Module,also call ''Embedded_computer'',''Embedded_System_Module'']].<br />
=Events=<br />
<I><br />
'''2009.10.24''': <b>[http://www.techor.com TECHOR]</b> announcing [http://www.techor.com/product_283.html SOM6410] '''Rev PRELIMINARY''' will be released in Oct 30,2009! '''SOM6410''' is 4x4cm size, 120pin 1.27mm pitch QFP-like package<br />
[[File:SOM6410msk.jpg|SOM6410 engineering picture, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]][[File:SOM6410-L.JPG|SOM6410 actual sample picture, Diameter:4x4cm Height:4mm Weight:(nominal) 10g]]<br />
</I><br />
<br />
=How to Purchase =<br />
=Hardware =<br />
==General Info==<br />
==Pinout definitions ==<br />
==Manual ==<br />
==Layout ==<br />
==Errata ==<br />
==Clocking ==<br />
==Power management ==<br />
==Interfacing to LCD Panels ==<br />
=Availability =<br />
==SOM6410 Revision ==<br />
==SOM6410-based products ==<br />
==SOM6410 ODM cases ==<br />
=5 App Demo Board =<br />
=6 Adapters =<br />
== Expansion boards ==<br />
<br />
[[Category:System-On-Module]]<br />
[[Category:ARM Development Boards]]<br />
[[Category:Development Boards]]<br />
[[Category:Categories]]</div>Som2416