eLinux.org - User contributions [en]

BeagleBoardJTAG

2012-11-28T09:57:06Z

Yclinda666: /* XDS100, XDS510, USB560 and CCSV4 */

[[Category: Linux]]
[[Category: OMAP]]
[[Category:Development Boards]]
[[Category: BeagleBoard]]
The page is about [http://en.wikipedia.org/wiki/JTAG JTAG] on OMAP3530 used at [[BeagleBoard|BeagleBoard]].

=Beagle JTAG connection=
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]].

'''Attention: JTAG on BeagleBoard uses 1.8V!'''

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.

The following picture is from a [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf TI OMAP JTAG presentation]:

[[Image:Ti arm jtag.jpg]]

Beagle uses the 14-pin TI header.

Note: TI uses some different pin names. Translation:
* TVD => VREF at Beagle
* TCLKR == RTCK
* TCLKO == TCK
* #### == Key (empty))
* TDIS => GND at Beagle

See [[OMAP3530_ICEPICK|ICEPICK configuration page]] for more details about how OMAP3 JTAG hardware needs to be configured.

== Beagle adapter ==
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:

''' ARM-14-JTAG TI-14-JTAG'''

VREF 1 - - 2 GND JTAG_TMS 1 - - 2 JTAG_nTRST
JTAG_nTRST 3 - - 4 GND JTAG_TDI 3 - - 4 GND
JTAG_TDI 5 - - 6 GND VREF 5 - x 6 KEY (empty)
JTAG_TMS 7 - - 8 GND JTAG_TDO 7 - - 8 GND
JTAG_TCK 9 - - 10 GND JTAG_RTCK 9 - - 10 GND
JTAG_TDO 11 - - 12 JTAG_SRST_N JTAG_TCK 11 - - 12 GND
VREF 13 - - 14 GND JTAG_EMU0 13 - - 14 JTAG_EMU1
FlySwatter TOP Beagle

See [[media:flyswatter-ti-jtag.pdf|14 pin ARM to TI adapter]] for a verified JTAG adapter from [http://www.tincantools.com/ TinCanTools].

* [http://tincantools.com/product.php?productid=16144 TinCanTools BeagleBoard Adapter Kit]
* 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]
* 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]])
* [http://www.flickr.com/photos/51025379@N00/2822556950/in/photostream/ xdaiabx adapter]

= Open source JTAG software=
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.

=JTAG hardware=

For BeagleBoard JTAG debugging, there are some HW interfaces available. Each is covered below.

==TinCanTools Flyswatter2==

[http://www.tincantools.com/ TinCanTools] has a new JTAG debugger at [http://www.tincantools.com/product.php?productid=16153&cat=0&page=1&featured Flyswatter2] that has support for OpenOCD and ARM Cortex A8 processors: OMAP3530 BeagleBoard and DM3730 BeagleBoard-xM. The Flyswatter2 is 5 to 10 times faster than the original Flyswatter.

They also have a [http://www.tincantools.com/product.php?productid=16154&cat=251&page=1 ARM20TI14 JTAG Adapter]. This JTAG adapter board works with the BeagleBoard and BeagleBoard-xM.

The Flyswatter2 can be used with [[BeagleBoardJTAG#Open_source_JTAG_software|OpenOCD]] (Beagle (OMAP3xx) support is complete).

==TinCanTools Flyswatter==

[http://www.tincantools.com/ TinCanTools] has a working JTAG debugger at [http://www.tincantools.com/product.php?productid=16134&cat=0&page=1&featured Flyswatter] that has support for OpenOCD and the OMAP3530 (ARM Cortex A8). They also have a [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit].

Costs:

In case you like to order Flyswatter and Adapter Kit international, here an example for Europe (Germany):

* Flyswatter: US-$ 49.95
* BeagleBoard Adapter Kit: US-$ 18.00
* International shipping: US-$ 27.00 (select USPS, it's the cheapest!)
* Video about using Flyswatter with BeagleBoard

Sum: US-$ 94.95 => EUR 65.28 + EUR 8.76 VAT (Germany) = EUR 74.04

Flyswatter can be used with [[BeagleBoardJTAG#Open_source_JTAG_software|OpenOCD]] (Beagle (OMAP3xx) support is complete).

'''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) because EMU0 and EMU1 must be set in order for the ICEpick JTAG TAP router within the DM37x to be the only device exposed after power on, which is what OpenOCD expects to see).

==BDI 2000==

===Example===

[http://groups.google.com/group/beagleboard/msg/8463086de562ee00 Chuck Fleming] reports:

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:

beagle>reset
- TARGET: processing reset request
- TARGET: BDI executes scan chain init string
- TARGET: Bypass check 0x00000001 => 0x00000002
- TARGET: JTAG exists check passed
- Core#0: ID code is 0x0B6D602F
- Core#0: DP-CSW is 0xF0000000
- Core#0: DBG-AP at 0xD4011000
- Core#0: DIDR is 0x15141012
- TARGET: BDI removes RESET
- TARGET: BDI waits for RESET inactive
- TARGET: Reset sequence passed
- TARGET: resetting target passed
- TARGET: processing target startup ....
- TARGET: processing target startup passed
beagle>halt
Core number : 0
Core state : debug mode (ARM)
Debug entry cause : Debug Request
Current PC : 0x40200000
Current CPSR : 0x000001d3 (Supervisor)
beagle>rdall
User FIQ Superv Abort IRQ Undef
GPR00: 480029fc 480029fc 480029fc 480029fc 480029fc 480029fc
GPR01: 00000000 00000000 00000000 00000000 00000000 00000000
GPR02: 00000001 00000001 00000001 00000001 00000001 00000001
GPR03: 00000060 00000060 00000060 00000060 00000060 00000060
GPR04: 00000000 00000000 00000000 00000000 00000000 00000000
GPR05: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4
GPR06: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4
GPR07: 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88
GPR08: 80e3ffdc 34484608 80e3ffdc 80e3ffdc 80e3ffdc 80e3ffdc
GPR09: 80e3fec8 26a1c132 80e3fec8 80e3fec8 80e3fec8 80e3fec8
GPR10: 00000018 08040f16 00000018 00000018 00000018 00000018
GPR11: 80e3fecc 3c278260 80e3fecc 80e3fecc 80e3fecc 80e3fecc
GPR12: 0000006e 24200625 0000006e 0000006e 0000006e 0000006e
GPR13: 00000000 00000000 80e3feb0 00000000 00000000 d1868045
GPR14: 00000000 00000000 80e84f44 00000000 00000000 d55a4cc8
PC : 40200000
CPSR : 000001d3
SPSR : 00000000 00000000 00000000 00000000 00000000
beagle>md 0x40200000
40200000 : e320f000 e320f000 e320f000 e320f000 .. ... ... ... .
40200010 : e320f000 e320f000 e320f000 eafffffc .. ... ... .....
40200020 : b6273502 e7aa052b 047694c8 91ca77d8 .5'.+.....v..w..
40200030 : 12b9579e ef2eef1b 00543892 494f9bc1 .W.......8T...OI
40200040 : 3f63013d 82eee656 b7adfe8d 993f1368 =.c?V.......h.?.
40200050 : 51f1cf9b 0464a23e bea76e3c 3d275f5c ...Q>.d.<n..\_'=
40200060 : 76554290 6776c892 a6cd088f 6dd4529a .BUv..vg.....R.m
40200070 : 067261b8 e5f80e9e cb4ea075 25a9dd95 .ar.....u.N....%
40200080 : 779db8c6 0496597b 7d5f8d5a 24f44cd6 ...w{Y..Z._}.L.$
40200090 : 99ab46f9 9ddc06d9 fd34567a 2035bab8 .F......zV4...5
402000a0 : a16b6760 fe863cf7 29046202 39fb0d49 `gk..<...b.)I..9
402000b0 : dc9fd18c e50f536c 09ae66dd cad9ff91 ....lS...f......
402000c0 : c46bdbdb be791808 89ff83fa 2d3bc71e ..k...y.......;-
402000d0 : 43f5a3b6 0aed1747 ba3c4752 6af0573a ...CG...RG<.:W.j
402000e0 : 3570da77 9a1dc961 324b876c 5d592060 w.p5a...l.K2` Y]
402000f0 : b870f487 1277c035 4609dcf4 53b534c4 ..p.5.w....F.4.S
beagle>ti
Core number : 0
Core state : debug mode (ARM)
Debug entry cause : Single Step
Current PC : 0x40200004
Current CPSR : 0x000001d3 (Supervisor)
beagle>ti
Core number : 0
Core state : debug mode (ARM)
Debug entry cause : Single Step
Current PC : 0x40200008
Current CPSR : 0x000001d3 (Supervisor)
beagle>

===BDI config===

The [ftp://94.230.212.16/bdigdb/config/arm/cortex-a/ BDI config files] might help getting OpenOCD to work with BeagleBoard.

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)
to enable access to the core:

SCANINIT t1:w1000:t0:w1000: ;toggle TRST,
SCANINIT ch10:w1000: ;clock TCK with TMS high and wait
SCANINIT i6=07:d8=89:i6=02: ;connect and select router
SCANINIT d32=81000080: ;IP control: KeepPowered
SCANINIT d32=a3002048: ;TAP3: DebugConnect, ForcePower, ForceActive
SCANINIT d32=81000081: ;IP control: KeepPowered, SysReset
SCANINIT d32=a3002148: ;enable TAP3
SCANINIT cl10:i10=ffff ;clock 10 times in RTI, scan bypass

==Lauterbach==

Lauterbach Debugger supports [http://www.lauterbach.com/news_288.html OMAP3503/15/25/30].

==XDS100, XDS510, USB560 and CCSV4==

Texas Instruments (TI) offers a set of JTAG emulators for debugging Beagle Board, and related, targets. These include the low-cost XDS100v2, and the higher-priced XDS510 et al. In addition, there is en Eclipse-based IDE called Code Composer Studio (ccs). As of early 2011, the latest version is [http://processors.wiki.ti.com/index.php/CCSv5_Getting_Started_Guide ccsv5], and it can be run on either a [http://processors.wiki.ti.com/index.php/Linux_Host_Support Linux host] or a Windows host. Debugging is possible in both [http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5 run-mode and stop-mode].

[http://www.armkits.com/product/xds100.asp XDS100v2 USB JTAG Emulator] is available from [http://www.armkits.com Embest] which is the second release of the XDS100 JTAG emulator technology supporting debug of a variety of TI devices.

XDS510, BlackHawk USB560 and CCSV4 (code composer studio) can be used to debug OMAP3503/15/25/30.

Some of these tools 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].

For CCS setup you see [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf TI OMAP JTAG presentation], too (start page: 16).

===BeagleBoard Linux Kernel Aware Debugging using CCSV4===
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].

====CCSV4 Current Status ====
* CCSV4 is a Windows based application, which means that Linux Kernel Code compiled an a Linux machine must be shared using NFS for SAMBA.
* 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
* CCSV4 is based on Eclipse V3.1.0, which means that many of the features added through Eclipse based V3.4.2 are missing
* TI are updating CCSV4 to use Eclipse V3.4.2, but have not disclosed a release date
* When TI release CCSV4 using Eclipse V3.4.2, I expect TI to release a CCSV4 plugin for Code Sourcery
* 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.
* 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.

==PEEDI==

[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]

PEEDI has a built-in support for GNU gbd based debuggers and a built-in Flash Programmer.
The Flash Programmer is capable to program:
* NOR Flash devices (over 900)
* NAND and OneNAND Flash devices (small page, larger page, 8/16 bit), various methods of ECC calculation, bad block management.
* DataFlash devices
* SPI DataFlash devices
* images located on a TFTP/FTP/HTTP server or a MMC/SD card (which allows standalone mode).

The PEEDI package includes also an PEEDI to TI14 adapter and an TI20 to TI14 adapter.

===Linux Kernel Aware Debugging using PEEDI Emulator===
* For Linux Aware debugging, PEEDI is a great solution. Here is what you will need:
* PEEDI JTAG emulator
* Firmware version 9.8.216 or later
* Arm Insight Debugger available on the Ronetix CDROM

Note: Enter all commands executed from the Linux Kernel build folder.

====Stopping the Debugger at start_kernel====
* In OMAP3530.CFG, change the hardware breakpoint address in the [INIT_LINUX] section to the address of start_kernel
* To obtain the address of start_kernel, use "nm vmlinux |grep -w start_kernel"
* If your u-boot counts down from 10, you will need to extend the debugger timeout
* Two lines down, change the line to "wait 25000 stop"
* Power up the BeagleBoard and PEEDI
* Let u-boot countdown and load the Linux Kernel
* PEEDI will stop at "start_kernel"
====Launching the Insight Debugger====
* Install the ARM Insight Debbugger from the Ronetix CDROM, which is normally installed in the /opt folder
* From the Linux Kernel build folder type "/opt/arm-linux-4.3.3/bin/arm-linux-insight vmlinux &"
* In the Console Window, type "target remote <xxx.xxx.xxx.xxx>:2000, where <xxx.xxx.xxx.xxx> is the BeagleBoard IP address
* Next, type "ni". The Source Window will load /init/main.c and highlight a line in start_kernel
* Step through the code, or enter breakpoints and run the program.

====Thread List====
* If you are doing multi-threaded debugging, this feature is invaluable
* The PEEDI config file (OMAP3530.CFG) must be setup to read this info from your kernel
* The information needed by Insight GDB is in the [OS_ARM_LINUX_v26] section
* This information is obtained from the Insight GDB Console Window
* print &init_task ; BASE
* print &((struct task_struct*)0)->tasks.next ; NEXT
* print &((struct task_struct*)0)->pid ; PID
* print &((struct task_struct*)0)->comm ; NAME
* print &((struct task_struct*)0)->stack ; second CONTEXT arg
* print &((struct thread_info*)0)->cpu_context ; third CONTEXT arg

For Linux Kernel v2.6.29, this section looks something like this:
* BASE = 4, 0xC066B110
* NEXT = 4, -0x1B8
* PID = 4, 0x1E4
* NAME = 16, 0x2DB
* CONTEXT = 10*4, 0x4, 0x1C

Note: the BASE address will most definitely be different to the one provided here, but the other values should be similar.

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.

==ARM Development Studio 5 (DS-5™)==

The reference software development suite from ARM, [http://www.arm.com/ds5 DS-5], supports JTAG-based debug and ETM trace with Linux kernel awareness on OMAP34XX/OMAP35XX/OMAP36XX/OMAP44XX and other ARM-based devices. Its target connection is called [http://www.arm.com/dstream DSTREAM], and is spec'd to provide reliable and fast run-control debug and 4GB of non-intrusive instruction trace.

For ease of use for Beagle board users, it even provides BB and BB xM [http://www.arm.com/products/tools/software-tools/ds-5/ds-5-downloads.php Linux distribution examples].

=Linux kernel debugging=

If you like to debug Linux kernel (with one of the above JTAG tools?) using GDB have a look to [[Debugging The Linux Kernel Using Gdb]] article.

Board and Chip Vendors

2012-11-28T09:26:57Z

Yclinda666: /* E */

This page has a list of the companies or organizations that make processors or boards for
embedded products. If you are looking for companies who sell Linux software or Linux-related services,
see the [[Vendors]] page. If you are looking for companies who sell end-user products based on
Linux, see [[Companies]]. If you are looking for information about specific development boards, see
[http://elinux.org/Category:Development_Boards Category:Development Boards]

== A ==
* [http://rhombus-tech.net/allwinner_a10/ Allwinner Technology] - An arm soc vendor based in Zhuhai, China
** make low cost arm soc for consumer electronic products, such as [[A1x]].
* [http://www.amcc.com/Embedded/ AMCC] - Applied Micro Circuits Corporation
** makes embedded PowerPC processors??
* AMD
** acquired ATI and now produces MIPS-based embedded processors (Xilleon series)
** Also, used to make Geode chip
* [http://www.analog.com Analog Devices] - [http://en.wikipedia.org/wiki/Analog_Devices Wikipedia entry]
** ADI designs and manufactures the [http://www.analog.com/blackfin Blackfin processor], which has been in the mainline Linux kernel since 2.6.22 (May 2007).
** There is a [http://blackfin.uclinux.org/ central open source site] with a dedicated [http://docs.blackfin.uclinux.org/ documentation wiki]
** Many more Blackfin manufactures can be found in [http://docs.blackfin.uclinux.org/doku.php?id=buy_stuff#other_hardwares_and_providers that wiki] as well
* [http://www.arm.com/ ARM] - [http://en.wikipedia.org/wiki/ARM_Holdings Wikipedia entry]
** ARM designs ARM architecture processors, and license the technology to companies that actually make the chips, they also make a few reference boards for their own technology named [[ARM RealView]], [http://www.arm.com/products/tools/development-boards/versatile/index.php ARM Versatile] and [[ARM Integrator Info]]
* [http://www.armadeus.com Armadeus]
** affordable ARM boards (Freescale i.MX + Xilinx Spartan FPGA)
** Armadeus started as a community project
* [http://www.atmel.com Atmel] - [http://en.wikipedia.org/wiki/Atmel Wikipedia entry]
** Atmel makes [http://www.atmel.com/products/AT91/ AT91SAM 32-bit ARM-based Microcontrollers]
** [http://www.linux4sam.org AT91 Linux gateway]
** Atmel AT91SAM9G45 Single Board Computer[http://www.armkits.com/product/sbc6045.asp English Website]，[http://www.timll.com/chinese/product/SBC6045.asp China Website]

== B ==
* [http://www.bluetechnix.com/ Bluetechnix] makes tiny Blackfin modules to simplify custom board development
* Broadcom - makes ARM chips for mobile phone market

== C ==
* [http://www.calao-systems.com/ CALAO Systems] sells tiny and cheap ARM based boards
* [http://www.camsig.co.uk/ Cambridge Signal Processing] makes tiny Blackfin modules to simplify custom board development
* [http://www.cdatas.com/ C Data Solutions] makes tiny Blackfin modules to simplify custom board development
* [http://www.cirrus.com Cirrus Logic] - [http://en.wikipedia.org/wiki/Cirrus_Logic Wikipedia entry]
** Cirrus Logic makes [http://www.cirrus.com/en/products/pro/techs/T7.html ep93xx and ep73xx 32-bit ARM-based Microcontrollers]

== D ==
* [http://dkc1.digikey.com/us/mkt/beagleboard.html DigiKey] sells the OMAP3 based [http://www.beagleboard.org beagleboard], [http://pandaboard.org/ Pandaboard] and [http://beagleboard.org/bone Beaglebone]

== E ==
* [http://www.eflagtech.com/ EFlag Tech] does custom Blackfin platform designs (software and hardware)
* [http://www.einfochips.com/marvell/ eInfochips - The Solution People] Open-RD based platform
* [http://www3.elphel.com Elphel, Inc] provide high performance Network Cameras based on Free Software and Hardware designs. Axis EtraxFS & Spartan 3e 1200k gates FPGA.
* [http://www.armkits.com Embest] sells Atmel SAM9G45 based [http://www.armkits.com/product/sbc6845.asp SBC6845], TI OMAP3530 based [http://www.armkits.com/product/devkit8000.asp DevKit8000], DM3730 based [http://www.armkits.com/product/devkit8500d.asp DevKit8500D], AM3359 based [http://www.armkits.com/product/devkit8600.asp DevKit8600], AM1808 based [http://www.armkits.com/product/sbc8018.asp SBC8018], Freescale i.MX 6Quad based [http://www.armkits.com/product/sabrelite.asp SABRE Lite], NXP LPC1788 based [http://www.armkits.com/product/SBC1788.asp SBC1788] and [http://www.armkits.com/product/DM-STF4BB.asp Discover-MO:)] modules for STF32F4DISCOVERY board.

== F ==
* [http://www.freescale.com/ Freescale Semiconductor] - [http://en.wikipedia.org/wiki/Freescale_Semiconductor Wikipedia entry]
** Freescale makes the MX31 ARM11-based processor (and associated development boards), among others.
** Freescale makes several PPC-based processors (and associated development boards) as well.

== G ==
* [http://www.gumstix.com/ Gumstix] sells various very small processor and add-on boards. Especially interesting for robotics related projects.

== H ==
* [http://www.developmentboard.net/ HITEG LTD] does custom embedded board ,it focused on IT outsourcing and embedded technology(software and hardware)
* [http://www.hhcn.com/english/enindex.html Hua Heng Tech] does custom Blackfin platform designs (software and hardware)
* [http://www.hvsistemas.com/ HV Sistemas S.L.] makes tiny Blackfin modules to simplify custom board development

== I ==
* [http://www.ibm.com/ IBM] - [http://en.wikipedia.org/wiki/IBM Wikipedia entry]
** Makes embedded PowerPC processor chips, such as the PPC 440 line

== K ==
* [http://www.kwikbyte.com/ KwikByte] sells full-featured ARM based boards:
** Such as the: [http://www.kwikbyte.com/KB9202.html KB9202], [http://www.kwikbyte.com/KB9260.html KB9260] and [http://www.kwikbyte.com/KBAT9261.html KBAT9261]

== M ==
* [http://www.marvell.com Marvell] sells a lot of ARM chips.
** One of the most interesting ones is probably the [[Marvell 88W8618]] which is used in the [[Freecom MusicPal]].

== N ==
* NEC - makes ARM chips, used to make lots of MIPS chips

== Q ==
* [http://www.qualcomm.com Qualcomm] - makes multicore ARM [http://www.qctconnect.com/products/mobile-processors.html MSM] products that support Linux
** Their [http://www.qctconnect.com/products/snapdragon.html Snapdragon] platform provides a 1GHz ARM core and advanced DSP.

== R ==
* [http://www.renesas.com/ Renesas Technology] - [http://en.wikipedia.org/wiki/Renesas_Technology Wikipedia entry]
** Renesas makes the SuperH, M32R, and H8 RISC CPUs, the RX CISC CPUs, and others.

== S ==
* [http://www.samsung.com/ Samsung]
** Samsung Electronics makes the S3C24XX(ARM 9), S3C64XX(ARM 11), S5P64XX(ARM 11), S5PC100(Cortex A8), S5PV210/S5PC110(Cortex A8), EXYNOS4210(Cortex A9) SoCs and others.
** See more [http://www.samsung.com/global/business/semiconductor/products/mobilesoc/Products_ApplicationProcessor.html Samsung Application Processors]
* [http://www.sirf.com SiRF] - Makes besides GPS products also ARM based SoC for location aware devices, like the [http://sirf.com/products/multifunction2.html ARM9 based Atlas III (codename) at4x0a] and the [http://sirf.com/products/multifunction3.html ARM11 based SiRFPrima].
* [http://www.stericsson.com/ ST-Ericsson] make mobile platforms for handset form factors and similar, typically ARM based with cellular modems.
* [http://www.sunplusmm.com/ Sunplus] is a company specialising in chips for multimedia and mobile applications. One of their interesting chips is the [[Sunplus SPMP3050A]] which is used in MP4 players.
* [http://www.surveyor.com/ Surveyor Corporation] makes Blackfin based robot modules for academics, hobbyists, and professionals

== T ==
* [Tianyeit]
** Sell the tiny Package -- Computer In Package base on TI OMAP35x/AM3517/omap4430/omap4460/dm3730/am3359
* [http://www.timll.com Timll]
** Reference Design and customized HW/SW Design Based on TI OMAP35x/AM3517
* [http://www.technexion.com TechNexion]
** Expandable and fully customizable ARM system modules and interface boards
** Embedded x86 boards with coreboot and linux core extensions
* [http://www.ti.com/ Texas Instruments] - [http://en.wikipedia.org/wiki/Texas_Instruments Wikipedia entry]
** Texas Instruments makes the MSP430 MCUs, TMS320 C2000/C5000/C6000 DSPs, [http://linux.davincidsp.com DaVinci]/[http://omap.com OMAP] ARM+DSP-based processors, and others.

[[Category:Hardware]]

Board and Chip Vendors

2012-11-28T09:16:02Z

Yclinda666: /* E */

This page has a list of the companies or organizations that make processors or boards for
embedded products. If you are looking for companies who sell Linux software or Linux-related services,
see the [[Vendors]] page. If you are looking for companies who sell end-user products based on
Linux, see [[Companies]]. If you are looking for information about specific development boards, see
[http://elinux.org/Category:Development_Boards Category:Development Boards]

== A ==
* [http://rhombus-tech.net/allwinner_a10/ Allwinner Technology] - An arm soc vendor based in Zhuhai, China
** make low cost arm soc for consumer electronic products, such as [[A1x]].
* [http://www.amcc.com/Embedded/ AMCC] - Applied Micro Circuits Corporation
** makes embedded PowerPC processors??
* AMD
** acquired ATI and now produces MIPS-based embedded processors (Xilleon series)
** Also, used to make Geode chip
* [http://www.analog.com Analog Devices] - [http://en.wikipedia.org/wiki/Analog_Devices Wikipedia entry]
** ADI designs and manufactures the [http://www.analog.com/blackfin Blackfin processor], which has been in the mainline Linux kernel since 2.6.22 (May 2007).
** There is a [http://blackfin.uclinux.org/ central open source site] with a dedicated [http://docs.blackfin.uclinux.org/ documentation wiki]
** Many more Blackfin manufactures can be found in [http://docs.blackfin.uclinux.org/doku.php?id=buy_stuff#other_hardwares_and_providers that wiki] as well
* [http://www.arm.com/ ARM] - [http://en.wikipedia.org/wiki/ARM_Holdings Wikipedia entry]
** ARM designs ARM architecture processors, and license the technology to companies that actually make the chips, they also make a few reference boards for their own technology named [[ARM RealView]], [http://www.arm.com/products/tools/development-boards/versatile/index.php ARM Versatile] and [[ARM Integrator Info]]
* [http://www.armadeus.com Armadeus]
** affordable ARM boards (Freescale i.MX + Xilinx Spartan FPGA)
** Armadeus started as a community project
* [http://www.atmel.com Atmel] - [http://en.wikipedia.org/wiki/Atmel Wikipedia entry]
** Atmel makes [http://www.atmel.com/products/AT91/ AT91SAM 32-bit ARM-based Microcontrollers]
** [http://www.linux4sam.org AT91 Linux gateway]
** Atmel AT91SAM9G45 Single Board Computer[http://www.armkits.com/product/sbc6045.asp English Website]，[http://www.timll.com/chinese/product/SBC6045.asp China Website]

== B ==
* [http://www.bluetechnix.com/ Bluetechnix] makes tiny Blackfin modules to simplify custom board development
* Broadcom - makes ARM chips for mobile phone market

== C ==
* [http://www.calao-systems.com/ CALAO Systems] sells tiny and cheap ARM based boards
* [http://www.camsig.co.uk/ Cambridge Signal Processing] makes tiny Blackfin modules to simplify custom board development
* [http://www.cdatas.com/ C Data Solutions] makes tiny Blackfin modules to simplify custom board development
* [http://www.cirrus.com Cirrus Logic] - [http://en.wikipedia.org/wiki/Cirrus_Logic Wikipedia entry]
** Cirrus Logic makes [http://www.cirrus.com/en/products/pro/techs/T7.html ep93xx and ep73xx 32-bit ARM-based Microcontrollers]

== D ==
* [http://dkc1.digikey.com/us/mkt/beagleboard.html DigiKey] sells the OMAP3 based [http://www.beagleboard.org beagleboard], [http://pandaboard.org/ Pandaboard] and [http://beagleboard.org/bone Beaglebone]

== E ==
* [http://www.eflagtech.com/ EFlag Tech] does custom Blackfin platform designs (software and hardware)
* [http://www.einfochips.com/marvell/ eInfochips - The Solution People] Open-RD based platform
* [http://www3.elphel.com Elphel, Inc] provide high performance Network Cameras based on Free Software and Hardware designs. Axis EtraxFS & Spartan 3e 1200k gates FPGA.
* [http://www.armkits.com Embest] provides standard single board computers and custom modules based on different ARM processors from Atmel, Freescale, NXP, Samsung, STMicroelectronics and Texas Instruments for ARM embedded applications.

== F ==
* [http://www.freescale.com/ Freescale Semiconductor] - [http://en.wikipedia.org/wiki/Freescale_Semiconductor Wikipedia entry]
** Freescale makes the MX31 ARM11-based processor (and associated development boards), among others.
** Freescale makes several PPC-based processors (and associated development boards) as well.

== G ==
* [http://www.gumstix.com/ Gumstix] sells various very small processor and add-on boards. Especially interesting for robotics related projects.

== H ==
* [http://www.developmentboard.net/ HITEG LTD] does custom embedded board ,it focused on IT outsourcing and embedded technology(software and hardware)
* [http://www.hhcn.com/english/enindex.html Hua Heng Tech] does custom Blackfin platform designs (software and hardware)
* [http://www.hvsistemas.com/ HV Sistemas S.L.] makes tiny Blackfin modules to simplify custom board development

== I ==
* [http://www.ibm.com/ IBM] - [http://en.wikipedia.org/wiki/IBM Wikipedia entry]
** Makes embedded PowerPC processor chips, such as the PPC 440 line

== K ==
* [http://www.kwikbyte.com/ KwikByte] sells full-featured ARM based boards:
** Such as the: [http://www.kwikbyte.com/KB9202.html KB9202], [http://www.kwikbyte.com/KB9260.html KB9260] and [http://www.kwikbyte.com/KBAT9261.html KBAT9261]

== M ==
* [http://www.marvell.com Marvell] sells a lot of ARM chips.
** One of the most interesting ones is probably the [[Marvell 88W8618]] which is used in the [[Freecom MusicPal]].

== N ==
* NEC - makes ARM chips, used to make lots of MIPS chips

== Q ==
* [http://www.qualcomm.com Qualcomm] - makes multicore ARM [http://www.qctconnect.com/products/mobile-processors.html MSM] products that support Linux
** Their [http://www.qctconnect.com/products/snapdragon.html Snapdragon] platform provides a 1GHz ARM core and advanced DSP.

== R ==
* [http://www.renesas.com/ Renesas Technology] - [http://en.wikipedia.org/wiki/Renesas_Technology Wikipedia entry]
** Renesas makes the SuperH, M32R, and H8 RISC CPUs, the RX CISC CPUs, and others.

== S ==
* [http://www.samsung.com/ Samsung]
** Samsung Electronics makes the S3C24XX(ARM 9), S3C64XX(ARM 11), S5P64XX(ARM 11), S5PC100(Cortex A8), S5PV210/S5PC110(Cortex A8), EXYNOS4210(Cortex A9) SoCs and others.
** See more [http://www.samsung.com/global/business/semiconductor/products/mobilesoc/Products_ApplicationProcessor.html Samsung Application Processors]
* [http://www.sirf.com SiRF] - Makes besides GPS products also ARM based SoC for location aware devices, like the [http://sirf.com/products/multifunction2.html ARM9 based Atlas III (codename) at4x0a] and the [http://sirf.com/products/multifunction3.html ARM11 based SiRFPrima].
* [http://www.stericsson.com/ ST-Ericsson] make mobile platforms for handset form factors and similar, typically ARM based with cellular modems.
* [http://www.sunplusmm.com/ Sunplus] is a company specialising in chips for multimedia and mobile applications. One of their interesting chips is the [[Sunplus SPMP3050A]] which is used in MP4 players.
* [http://www.surveyor.com/ Surveyor Corporation] makes Blackfin based robot modules for academics, hobbyists, and professionals

== T ==
* [Tianyeit]
** Sell the tiny Package -- Computer In Package base on TI OMAP35x/AM3517/omap4430/omap4460/dm3730/am3359
* [http://www.timll.com Timll]
** Reference Design and customized HW/SW Design Based on TI OMAP35x/AM3517
* [http://www.technexion.com TechNexion]
** Expandable and fully customizable ARM system modules and interface boards
** Embedded x86 boards with coreboot and linux core extensions
* [http://www.ti.com/ Texas Instruments] - [http://en.wikipedia.org/wiki/Texas_Instruments Wikipedia entry]
** Texas Instruments makes the MSP430 MCUs, TMS320 C2000/C5000/C6000 DSPs, [http://linux.davincidsp.com DaVinci]/[http://omap.com OMAP] ARM+DSP-based processors, and others.

[[Category:Hardware]]

Vendors

2012-11-28T09:13:37Z

Yclinda666: /* Overview */

== Overview ==

This page lists companies who offer services around embedded Linux, such as training, support, etc. We also list companies who provide Linux distributions specifically targeting embedded uses. If you are looking for companies who build and sell devices with Linux as their operating system, please see the [[Companies]] page.

* [http://www.A2eTechnologies.com/ A2e Technologies], USA (San Diego & Boston)
* [http://www.adeneo-embedded.com/ Adeneo Embedded], France
* [http://www.armadeus.com Armadeus Systems], France
* [http://bluewatersys.com Bluewater Systems], New Zealand
* [http://bec-systems.com/ BEC Systems], USA
* [http://www.calao-systems.com CALAO Systems], France
* [http://www.codefidence.com/ Codefidence Ltd.], world wide
* [http://www.cogentembedded.com/ Cogent Embedded], USA, Europe
* [http://www.cwlinux.com/ CWLinux], Hong Kong
* [http://www.denx.de/ DENX Software Engineering]
* [http://www.drivingdevices.com/ Driving Devices Limited], United Kingdom
* [http://www.e-consystems.com/embeddedlinux.asp e-con Systems Inc.], world wide
* [http://www.embeddedalley.com/ Embedded Alley], world wide (gone - was acquired by Mentor Graphics)
* [http://www.armkits.com/ Embest], China (acquired by Premier Farnell/element14)
* [http://www.esfnet.co.uk/ Embedded Software Foundry Limited], Sheffield, UK (gone - acquired by William Matthew Limited)
* [http://www.mind.be/ Essensium/Mind], Belgium
* [http://www.femtolinux.com FemtoLinux], Israel
* [http://www.free-electrons.com Free-Electrons], France
* [http://holoscopio.com/ Holoscópio Tecnologia Ltda.], Brazil
* [http://www.intellimetrix.us/ Intellimetrix]
* [http://www.katdc.com KAT Digital Corp.]
* [http://www.koansoftware.com/ KOAN sas], Bergamo, Italy
* [http://www.lineo.co.jp/eng/index.html Lineo Solutions], Japan
* [http://www.linkodas.com/ Linkodas], Lithuania
* [http://www.linutronix.de/ Linutronix], Germany
* [http://www.mentor.com/products/embedded_software/ Mentor Graphics (embedded software group)], worldwide
* [http://www.mvista.com/ MontaVista], world wide
* [http://www.mpc-data.co.uk/embedded-linux/ MPC Data], UK
* [http://www.opersys.com/ Opersys], North America
* [http://www.pengutronix.de/ Pengutronix], Germany
* [http://www.practicalcontrol.co.uk/ Practical Control], UK
* [http://www.ridgerun.com RidgeRun]
* [http://www.secretlab.ca/ Secret Lab], North America
* [http://www.sidebranch.com Sidebranch], The Netherlands.
* [http://www.simantinee.com/ Simantinee Embedded System], India
* [http://www.sporetools.com/ Spore Tools], New Zealand
* [http://www.sysgo.com/ SYSGO], Germany
* [http://www.team-embedded.com/ Team Embedded], Netherlands
* [http://www.timesys.com/ TimeSys], USA
* [http://www.timll.com Timll], China
* [http://whitequeue.com WhiteQueue Consulting], New Zealand
* [http://www.wmltd.co.uk/ William Matthew Limited], United Kingdom
* [http://www.windriver.com/ Wind River], world wide
* [http://www.zeta2.ch/ Zeta2 GmbH], Switzerland

[[Category:Companies]]

Companies

2012-11-28T09:11:10Z

Yclinda666: /* E */

== Overview ==

This page provides information about companies that build and sell consumer electronics devices with Linux as their operating system. If you're looking for companies that build and sell Linux distributions for embedded devices or who provide services around embedded Linux, please see the [[Vendors]] page.

You may also want to look at the [[Source code download sites]] page, which has a list of places to get open source software
from different companies.

== A ==

*[http://www.aldebaran-robotics.com/ Aldebaran Robotics]

*[http://www.archos.com Archos]

[http://www.atmark-techno.com/en Atmark Techno]
* [http://www.atmark-techno.com/en/products/armadillo Armadillo Series]
* [http://www.atmark-techno.com/en/products/suzaku SUZAKU Series]

[http://www.armadeus.com/english/index.html ARMadeus Systems]
* [http://www.armadeus.com/english/products-processor_boards-apf27.html APF27 Series (i.MX27 + Spartan3A based boards)]
* [http://www.armadeus.com/english/products-processor_boards-apf9328.html APF9328 Series (i.MXL + Spartan3 based boards)]
* [http://www.armadeus.org The Armadeus Project: non profit association for embedded Linux geeks]

[http://www.artila.com Artila Electronics]
* [http://www.artila.com/p_matrix.html Matrix series]
* [http://www.artila.com/p_sbc.html System on Module]
* [http://www.artila.com/p_ipac.html PAC series]

== B ==
* [http://bluewatersys.com Bluewater Systems]
** [http://bluewatersys.com/snapper/ ARM based modules running Linux]

== C ==
[http://www.calao-systems.com/ CALAO Systems]
* [http://www.calao-systems.com/articles.php?lng=en&pg=5940 Embedded Computers]
* [http://www.calao-systems.com/articles.php?lng=en&pg=5960 Expansion Boards]
* [http://www.calao-systems.com/articles.php?lng=en&pg=6201 Development Boards]
* [http://www.calao-systems.com/articles.php?lng=en&pg=6100 USB Keys]
* [http://www.calao-systems.com/articles.php?lng=en&pg=6203 Home And Building Automation Controllers]
[http://www.compulab.co.il CompuLab Ltd.]
* [http://www.compulab.co.il/t3530/html/t3530-cm-datasheet.htm ARM based modules running Linux]
* [http://fit-pc2.com/wiki/index.php?title=Main_Page NetTop running Linux]
[http://www.cranksoftware.com/ Crank Software]
* [http://www.cranksoftware.com/storyboard Storyboard Suite Embedded User Interface]
* [http://www.cranksoftware.com/services_support/embedded_development.php Embedded Consulting Services]
* [http://www.cranksoftware.com/services_support/webkit_services.php Embedded WebKit Development]
[http://www.cwlinux.com/ CWLinux]
* [http://www.cwlinux.com/products/sysondimm/7.php Single-board SysOnDIMM computers]
* [http://www.cwlinux.com/experienced/platforms/3.php OEM customized platforms]

== D ==
[http://www.datapatternsindia.com/ DataPatterns India Pvt Ltd]
* [http://www.datapatternsindia.com/content/fu-processors.htm Powerpc Based Single Board Computers]
== E ==
* [http://www.armkits.com Embest] provides standard single board computers and custom modules based on different ARM processors from Atmel, Freescale, NXP, Samsung, STMicroelectronics and Texas Instruments for embedded applications
* [http://www.e2s.net/ Electronic Engineering Solutions]
* [http://www3.elphel.com Elphel, Inc] provide high performance Network Cameras based on Free Software and Hardware designs. Axis EtraxFS & Spartan 3e 1200k gates FPGA.
* [http://www.lanmusic.com/ LanMusic: Linux based Internet radio player for Hotels and home users]
* [http://www.parkhelp.com/ Parkhelp: System that helps users locate parking spaces effectively using a system of Linux based embedded guided information]
* [http://www.einfochips.com/ The Solution People]
* [http://www.einfochips.com/services/embedded_service_CS/Service_IPNetCam.php IPNetCam: Smart IP surveillance camera]
* [http://einfochips.com/services/Security/Handheld_biometric.php HBA: Handheld Biometric Authentication]

== G ==
[http://www.garmin.com/ Garmin]
* [http://developer.garmin.com/linux/ Source code for Linux-based products (Nuvi 8xx and 5xxx series)]

== H ==
[http://www.developmentboard.net/ HITEG LTD] - Company focus on embedded board,single board computer [http://www.developmentboard.net/index.php/productdetail/Development+board/ARM9/SAMSUNG/S3C2440/MINI2440v2+with+MegaDisplay+3.5/info/1/ Developmentboard]

== I ==
[http://www.iendian.com/ iEndian] - Company formed to fund and manage production of [http://www.balloonboard.org/ Balloonboard]

[http://www.intel.com/ Intel] - [http://wikipedia.org/wiki/Intel Wikipedia entry]
* [http://www.intel.com/design/celect/2110/ CE2110 Media Processor]

[http://www.intellimetrix.us/ Intellimetrix] - Computing for Science and Industry
* [http://www.intellimetrix.us/embeddedlinuxkit.htm/ Embedded Linux Learning Kit]

== K ==
[http://www.kernelconcepts.de/en kernel concepts]
* [http://www.kernelconcepts.de/en/services.shtml Linux embedded services, porting and support]
* [http://labs.kernelconcepts.de Open Source projects and news]

[http://www.koansoftware.com KOAN sas]
* [http://www.kaeilos.com KaeilOS industrial grade embedded linux]
* [http://www.koansoftware.com/en/prd_support.htm Linux embedded support]
* [http://www.koansoftware.com/en/prd_svil.htm Device drivers development]

== M ==
[http://moblin.org/ moblin.org] - Home of Intel's "Mobile Linux" distribution and tools

[http://www.motorola.com/ Motorola] - [http://wikipedia.org/wiki/Motorola Wikipedia entry]

[http://www.mvista.com/ MontaVista] - [http://wikipedia.org/wiki/MontaVista Wikipedia entry]

[http://www.mistralsolutions.com Mistral Solutions]

== N ==
[http://www.neurostechnology.com/ Neuros Technology] - [http://wikipedia.org/wiki/Neuros_Technology Wikipedia entry]
* [http://en.wikipedia.org/wiki/Neuros_Technology#Neuros_OSD Neuros OSD]
[http://www.nokia.com/ Nokia] - [http://wikipedia.org/wiki/Nokia Wikipedia entry]
* [http://en.wikipedia.org/wiki/Nokia_N800 N800]
* [http://en.wikipedia.org/wiki/Nokia_770 N770]
[http://www.nxp.com/ NXP Semiconductors] - [http://en.wikipedia.org/wiki/NXP_Semiconductors Wikipedia entry]

== P ==
[http://www.pengutronix.de Pengutronix]
* [http://www.pengutronix.de/development/bsp/index_en.html Linux Kernel Development]
* [http://www.pengutronix.de/development/gui/index_en.html GUI Development, Qt]
* [http://www.ptxdist.org PTXdist Build System]
* [http://www.barebox.org Barebox Bootloader]
* [http://www.pengutronix.de/software/linux-i.MX/index_en.html i.MX Linux Port]
[http://www.pure.com Pure]
* [http://pure.com/products/product.asp?Product=VL-60896&Category= Evoke Flow]
[http://profusion.mobi/about ProFUSION embedded systems]
* [http://profusion.mobi/node/10 Guarana and Enjoy]

== R ==
* [http://www.ridgerun.com RidgeRun]
* [http://www.route495software.com Route 495 Software]

== S ==
[http://www.samsung.com/ Samsung] - [http://wikipedia.org/wiki/Samsung Wikipedia entry]
* too many products to list, see:
** [https://opensource.samsung.com/ Samsung Open Source Release Center]

[http://www.sony.com/Sony Sony] - [http://wikipedia.org/wiki/Sony Wikipedia entry]
* too many products to list, see
** [http://www.sony.net/Products/Linux Global Linux source code download site]
** [http://www.sony.com/linux US Linux source code download site]

[http://www.securecomputing.com Secure Computing] - [http://en.wikipedia.org/wiki/Secure_Computing Wikipedia entry]
SnapGear family of products [http://www.snapgear.com homepage]
Simtec Electronics - Hardware and Software design [http://www.simtec.co.uk/]

== T ==
* [http://www.timll.com Timll] A Chinese company focused on providing standard single board computer and custom modules for ARM embedded applications
* [http://www.technexion.com/ TechNexion]

[http://www.timesys.com TimeSys]
* [http://www.timesys.com/services LinuxLink]
[[TechnologicSystems]] at http://embeddedarm.com
* [http://tkos.co.il Tk Open Systems] BSP's-R-Us, also drivers, even some user-space stuff
[http://www.tomtom.com/ TomTom] [http://en.wikipedia.org/wiki/TomTom Wikipedia entry]

[http://www.tvblob.com/?s=elinux Tvblob]
* [http://www.tvblob.com/?s=elinux vMAX]
* [http://www.tvblob.com/?s=elinux vTALK]
* [http://www.tvblob.com/?s=elinux vLINK]
* [http://www.tvblobbox.com/?s=elinux Tvblob BOX]

== W ==
[http://www.wacom.com/ Wacom] - is a world-wide company that produces graphics tablets and related products. [http://www.wacom-components.com/english/index.html/ Wacom's OEM] sensor technology has been used by many major Tablet PC vendors. A detailed list of Wacom products and their histories can also be found at [http://en.wikipedia.org/wiki/Wacom/ WikiWacom].

== Instructions for submitters ==
Please add company names in alphabetical order, and follow
the existing format. Make a link from your company
name to your main web site. If you have a wikipedia entry, please
link that as well. If you would like to, you may list a few
of your Linux-based products, but please don't go overboard.

[[Category:Companies]]

Products

2012-11-27T08:23:15Z

Yclinda666: /* Development boards */

Here is a list of products which use embedded Linux.

Please see the [[Talk:Products|talk page]] for information about how we want to populate this page.

== Televisions ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Televisions using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Mobile Phones ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Mobile Phones using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:150px" | Download Area
! Proprietary Drivers
! Proprietary Software
|- align="center"
| [http://www.accton.com/homepage/main3/product_range/23_CE/VM1188T.htm VM1188T]
| [http://www.accton.com Accton]
| 2006
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://www.cellon.com/products.jsp?id=18 C8000]
| [http://www.cellon.com/ Cellon]
| 2005
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/news/NS8901223473.html 3G Linux Ref Design]
| [http://www.catt.ac.cn/english/ Datang]
| 2004
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/news/NS4367004471.html E28 FMC phones]
| [http://www.e28.com/eng/ E28]
| 2006
| -
| -
| OMAP 730
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/news/NS5033717348.html E28 E2800]
| [http://www.e28.com/eng/ E28]
| 2003
| 32
| 32
| ARM9
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/news/NS2220873893.html E28 E2800+]
| [http://www.e28.com/eng/ E28]
| 2004
| 64
| 32
| ARM9 300MHz
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://www.g-tekgroup.com/products/pwg_500.asp PWG500]
| [http://www.g-tekgroup.com/ G-Tek]
| 2006
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/articles/AT2559540724.html G500i]
| Grundig
| 2005
| 52 - User
| X
| OMAP850
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
| ?
| ?
|-
|- align="center"
| [http://www.haier.com/products/product.asp?proID=4948 N60]
| [http://www.haier.com Haier]
| 2006
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
| ?
| ?
|-
|- align="center"
| [http://www.imcosys.com/smartphones.html GPS Phone]
| [http://www.imcosys.com/ ImCoSys]
| 2006
| 64
| 64
| OMAP 730
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| [http://www.imcosys.com/English/Download/download.html SDK & Flash Image]
| ?
| ?
|-
|- align="center"
| Openmoko Freerunner
| Openmoko
| 2008
| 128
| 256
| armV4@400Mhz
| [http://wiki.openmoko.org/wiki/Neo_FreeRunner Openmoko wiki], [http://en.wikipedia.org/wiki/Open_hardware open hardware](schematics freely available)
| [http://wiki.openmoko.org/wiki/Distributions multiple distributions]
| None(but 3 proprietary firmwares: gsm,gps and wifi)
| None
|-
|- align="center"
| Nokia N900
| Nokia
| ?
| 256
| 256M NAND +32G eMMC
| OMAP 3430 SoC( 600 MHz ARM Cortex-A8 CPU)
| ?
| ?
| see [http://wiki.maemo.org/Free_Maemo here]
| see [http://wiki.maemo.org/Free_Maemo here]
|-
|- align="center"
| Htc Dream
| HTC
| ?
| 192M(but some reserved for the DSPs)
|
| MSM7201A(armv6-novfp@528Mhz)
| run android by default,GNU/Linux port [http://www.htc-linux.org/wiki/index.php?title=Dream#Kernel_Status in progress](require routing or ADP)
|
| yes by default([http://trac.osuosl.org/trac/replicant/wiki/HTCDreamProprietaryDrivers list here] )
| yes by default
|-
|}
 

== Audio and Video Mobile Players ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Audio and Video Mobile Players using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:150px" | Download Area
! Proprietary Drivers
! style="width:300px" | Proprietary Software
|- align="center"
| PMA430
| Archos
| ?
| 64MB(48MB usable)
| ?(loop image on the hdd used)
| omap1(armv4@74.34 bogomips)
|
| [http://openpma.org/wiki/Main_Page alternative community distribution]
| yes(dm270fb.o(framebuffer driver),mabe others)
| yes(qtopia),you can't change the kernel unless you find or write a replacement for the proprietary drivers
|-
|- align="center"
| Archos 5
| Archos
| ?
| 128 M
| 40G/60G/120G/160G/250G hdd
| OMAP3
|
| [http://www.openaos.org/ openaos(alternative(to android) community distribution)]
comes with android by default,
but thanks to an SDE(special developer edition) firmware GNU/Linux can be installed.
OpenAOS and SDE are based on openembedded.
|?
|?
|-

|-
|- align="center"
| Archos 7
| Archos
| ?
| 128 M
| 160G/320G hdd
| OMAP3
|
| [http://www.openaos.org/ openaos(alternative(to android) community distribution)]
comes with android by default,
but thanks to an SDE(special developer edition) firmware GNU/Linux can be installed.
OpenAOS and SDE are based on openembedded.
|?
|?
|-
|}
 

== Internet tablet ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Internet tablet using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:150px" | Download Area
! Proprietary Drivers
! style="width:300px" | Proprietary Software
|- align="center"
| [[N800]]
| Nokia
| ?
| 128MB
| 256MB
| OMAP2420@400 MHz
|
| yes(wifi(free wifi driver available but still need a calibration binary).dsp,sound )
| can be remplcad by [http://dev.openbossa.org/trac/mamona/wiki mamona] but no wifi and sound
|-
| [http://tabletsetc.com/tablets/4tiitoo-wetab/specs/ WeTab]
| Neofonie/Pegatron
| 2010
| 1 GB
| 16 GB
| 1.66GHz Intel Atom N450
| Running MeeGo
| http://wetab.mobi/en/developers/downloads-and-howtos/
|
|
|-
|}

== Settop Boxes ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Settop Boxes using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| Freedom Jump
| Amino Communications
| 2010
| 1 GB DDR 3
| 512 MB
| Intel® Atom CE4150
| MeeGo platform
| http://www.aminocom.com/products/freedom-jump/
|- align="center"
| Roku SD/HD/HD-XR/XDS
| Roku
| 2010
| ?
| ?
| NXP PNX8935
|
| [http://support.roku.com/entries/246042-roku-player-open-source-resources|Roku open source]
|-
|}
 

== Digital Video Recorders ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Digital Video Recorders using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Game Consoles ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Game Consoles using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| PlayStation 2
| Sony Computer Entertainment
| 2000
| 32MB
| unknown
| MIPS 64-bit R5900
| [http://en.wikipedia.org/wiki/PlayStation_2 PS2 wikipedia page], [http://playstation2-linux.com/ Playstation-linux community site]
| [http://blackrhino.xrhino.com/main.php?page=home Black Rhino Linux distribution site]
|- align="center"
| PlayStation 3
| Sony Computer Entertainment
| 2006
| 512 MB
| unknown
| CELL broadband engine
| [http://en.wikipedia.org/wiki/PlayStation_3 PS3 wikipedia page]
| [http://en.wikipedia.org/wiki/Linux_for_PlayStation_3 wikipedia PS3-linux page]
|- align="center"
| Didj
| LeapFrog Enterprises
| 2008
| 32MB
| 256MB
| [[LF-1000]]/[[Pollux]]
| [[Didj]]
| [[Leapfrog Source Code]]
|- align="center"
| Leapster Explorer
| LeapFrog Enterprises
| 2010
| 64MB
| 512MB
| [[LF-1000]]/[[Pollux]]
| [[Leapster Explorer]]
| [[Leapfrog Source Code]]
|- align="center"
| LeapPad Explorer
| LeapFrog Enterprises
| 2011
| 64MB
| 2GB
| [[LF-1000]]/[[Pollux]]
| [[Leappad Explorer]]
| [[Leapfrog Source Code]]
|-
|}
 

== Network Attached Storage (NAS) ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Network Attached Storage using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| NSLU2
| [http://www.linksys.com Linksys]
| 2004
| 32MB
| 8MB
| Intel XScale IXP420
|
| http://www.nslu2-linux.org (community site with improved firmwares)
|-
|}
 

== Network Camera ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Network Camera using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| NC353L
| [http://www3.elphel.com Elphel, Inc]
| 2007
| 64MB
| 128MB
| Axis EtraxFS
| http://wiki.elphel.com
| http://sourceforge.net/projects/elphel
|-
|}
 
== Networked Media Players ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Networked Media Players using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| [[Freecom MusicPal | MusicPal]]
| [http://www.freecom.com Freecom]
| 2007
| 32MB
| unknown
| [[Marvell 88W8618]]
|
| http://www.musicpal.info (under Legal Notice]
|-
|}
 

== Still and Video Cameras ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Not Yet Categorized devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| HDR-UX1, HDR-SR1 video cameras
| Sony
| 2006
| ??
| ??
| ARM9
| [http://www.sonystyle.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=10551&storeId=10151&langId=-1&productId=11035608 Sonystyle store listing]
| [http://www.sony.net/Products/Linux/Download/HDR-UX1_HDR-SR1.html Sony Linux Download area]
|-
|}

== Assistive Technology ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Assistive Technology devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
| [http://www.toby-churchill.com/en/content/lightwriters-0 Lightwriter SL38]
| [http://www.toby-churchill.com Toby Churchill Ltd]
| 2004
| 64
| 256
| StrongARM SA-1110
| [http://balloonboard.org/ Developer site]
| [http://husaberg.toby-churchill.com/balloon/ code and sources]
|}
 

== Robots and Smart-companions ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Robots and smart-companions using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| [http://fr.wikipedia.org/wiki/Karotz Karotz]
| [http://en.wikipedia.org/wiki/Mindscape_(software_publisher) Mindscape ] then [http://www.aldebaran-robotics.com/ Aldebaran Robotics]
| 2011
| 64
| 256
| Samsung [http://elinux.org/S3C2440 S3C2440] (ARM920T@400Mhz)
| [http://dev.karotz.com/ Developer site]
|
|}
 

== Network devices ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Network devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! Connectivity
! Notes
! style="width:150px" | Source
! style="width:250px" | Download Area
! Proprietary Drivers or software
|-
| Sheevaplug
| [http://en.wikipedia.org/wiki/Marvell_Technology_Group Marvell]
|
| 512M
| 512M
| Kirkwood 88F6281 (armv5@1.2Ghz)
| Ethernet,usb,sdio
|
|
|
| ?
|}
 

== Modular devices ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Modular devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! Connectivity
! Notes
! style="width:150px" | Source
! style="width:250px" | Download Area
! Proprietary Drivers or software
|-
|- align="center"
| [http://www.buglabs.net/bugbase bugbase 1.2]
| [http://www.buglabs.net Bug Labs]
| 2006
| 128
| 32
| imx31(armv6-vfp@533Mhz)
| USB host(on the von hippel module),micro-sd,usb OTG
| Up to 4 modules(802.15.4,motion detector,screen(320x240),sound card,breakout(von hippel),gps modules availables), [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://bugcommunity.com/wiki/index.php/BUGbase schematics] freely available)
| [http://bssvn.buglabs.net/svn/!tree/10763 Bug svn] 
Based on [http://pokylinux.org/ poky linux], 
uses [http://en.wikipedia.org/wiki/Concierge_OSGi concierge OSGI], 
Can use bug 1.3's [http://cgit.openembedded.net/cgit.cgi/openembedded/tree/conf/machine/bug.conf Basic machine support in openembedded]
| http://www.buglabs.net/downloads
| No(the powervr is not used)
|-
|- align="center"
| [http://www.buglabs.net/bugbase bugbase 1.3]
| [http://www.buglabs.net Bug Labs]
| 2009
| 128
| 32
| imx31(armv6-vfp@533Mhz)
| wifi(libertas_sdio),bluetooth,USB(on the von hippel module),micro-sd,usb OTG
| Up to 4 modules(802.15.4,motion detector,screen(320x240),sound card,breakout(von hippel),gps modules availables), [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://bugcommunity.com/wiki/index.php/BUGbase schematics] freely available)
| [http://bssvn.buglabs.net/svn/!tree/10763 Bug svn] 
Based on [http://pokylinux.org/ poky linux], 
uses [http://en.wikipedia.org/wiki/Concierge_OSGi concierge OSGI], 
[http://cgit.openembedded.net/cgit.cgi/openembedded/tree/conf/machine/bug.conf Basic machine support in openembedded]
| http://www.buglabs.net/downloads
| No(the powervr is not used)
|-
|- align="center"
| [http://www.gumstix.com/store/catalog/product_info.php?cPath=27_33&products_id=227 Overo fire]
| [http://www.gumstix.com Gumstix]
| ?
| 256M
| 256M
| OMAP 3530(also contain POWERVR SGX + C64x)
| wifi(libertas),bluetooth,micro-sd,usb OTG+Host(not shure if USB is on the module or only avaliable on extensions boards)
| expansions board available [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://pubs.gumstix.com/boards/ schematics] freely available but only for extension boards)
| [http://cgit.openembedded.net/cgit.cgi/openembedded/tree/conf/machine/overo.conf Machine support in openembedded]
|
| ?
|-
|- align="center"
| [http://www.gumstix.com/store/catalog/product_info.php?products_id=226 overo air]
| [http://www.gumstix.com Gumstix]
| ?
| 256M
| 256M
| OMAP 3503(no 3D acceleration and no DSP)
| wifi(libertas),bluetooth,micro-sd,usb OTG+Host(not shure if USB is on the module or only avaliable on extensions boards)
| expansions board available [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://pubs.gumstix.com/boards/ schematics] freely available but only for extension boards)
|
|
| ?
|-

|- align="center"
| [http://www.gumstix.com/store/catalog/product_info.php?products_id=228 overo water]
| [http://www.gumstix.com Gumstix]
| ?
| 256M
| 256M
| OMAP 3530(also contain POWERVR SGX + C64x)
| micro-sd,usb OTG+Host(not shure if USB is on the module or only avaliable on extensions boards)
| expansions board available [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://pubs.gumstix.com/boards/ schematics] freely available but only for extension boards)
|
|
| ?
|-

|- align="center"
| [http://www.gumstix.com/store/catalog/product_info.php?products_id=211 Overo earth]
| [http://www.gumstix.com Gumstix]
| ?
| 256M
| 256M
| OMAP 3503(no DSP,no 3d acceleration)
| micro-sd,usb OTG+Host(not shure if USB is on the module or only avaliable on extensions boards)
| expansions board available [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://pubs.gumstix.com/boards/ schematics] freely available but only for extension boards)
|
|
| ?
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=5969 TNY-A9G20-LPW-I02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2009
| 64M
| 256M
| AT91SAM9G20(400Mhz)
| Micro-SD, RTC (ext. battery), USB OTG (Full Speed), Serial DBGU (Linux console), JTAG, 2 expansion connectors.
| MotherBoard(s) : MOB-TNY-A9XXX-MD2-CXX, Expansion board(s): GPI2 (1W,I2C, SPI, UART), GPS, GSM/GPRS, GSM/HSDPA, WiFi/BlueTooth, KNX/RF, Wireless MBUS, ZigBee...
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=5885 TNY-A9263-C02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2008
| 64M
| 256M
| AT91SAM9263(200Mhz)
| USB OTG (Full Speed), Serial DBGU (Linux console),2 expansion connectors.
| Motherboard(s) : MOB-TNY-A9XXX-MD2-CXX, Expansion board(s): GPI2 (1W,I2C, SPI, UART), GPS, GSM/GPRS, GSM/HSDPA, WiFi/BlueTooth, KNX/RF, Wireless MBUS, ZigBee...
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=6237 TNY-T3730-ULP-C01]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2011
| 256M
| 256M
| OMAP3730(800Mhz)
| Micro-SD, Battery Charger, USB OTG (Full Speed), UART (Linux Console), Jtag, 2 expansion connectors
| No motherboard(s), No expansion board(s).
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=5933 QIL-A9260-C02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2011
| 64M
| 256M
| AT91SAM9260(200Mhz)
| 2Mbits SPI Serial Flash, 64Kbits SPI E2PROM, Micro-SD, RTC, 2 expansion connectors
| Motherboard(s) : MOB-QIL-A9XXX-CXX, No expansion boards.
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=6113 USB-A9G20-LPW-C02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2011
| 64M
| 256M
| AT91SAM9G20(400Mhz)
| Micro-SD, RTC, USB Debug (Full Speed), USB Device FS, 2x USB Host FS, Ethernet 10/100, expansion connector
| Motherboard(s) : N/A, Expansion boards : GPI2 (1W,I2C, SPI, UART), GPS, GSM/GPRS, GSM/HSDPA, WiFi/BlueTooth, KNX/RF, Wireless MBUS, ZigBee...
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=5932 USB-A9263-C02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2009
| 64M
| 256M
| AT91SAM9263(200Mhz)
| Micro-SD, USB Debug (Full Speed), USB Device FS, 2x USB Host FS, Ethernet 10/100, expansion connector
| Motherboard(s) : N/A, No Expansion board(s)
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|}
 

== Development boards ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Development boards'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! Connectivity
! Notes
! Proprietary Drivers
! style="width:150px" | Source
! style="width:250px" | Download Area
|-
|[http://beagleboard.org/ Beagle Board]
|Texas Instruments
|2008
|256M
|256M
|OMAP3530
|
| lot of informations in the [[BeagleBoard|BeagleBoard wiki page]], 
[http://en.wikipedia.org/wiki/Open_hardware open hardware](schematics freely available)
| The powervr(3d chip) require a proprietary 3d driver for the 3d part
|
|
|-
|[http://beagleboard.org/bone BeagleBone]
|Texas Instruments
|2011
|256MB
|none (MicroSD)
|AM3358
|Ethernet 10/100
|[[BeagleBone|BeagleBone wiki page]], [[BeagleBoard|BeagleBoard wiki page]], 
[http://en.wikipedia.org/wiki/Open_hardware open hardware](schematics freely available)
|The powervr(3d chip) require a proprietary 3d driver for the 3d part
|
|
|-
|[http://pandaboard.org/ Pandaboard]
|Texas Instruments
|2010
|8Gb(x32) x 2ch
|(2G(x32) x4pcs) 2CS/ch
|OMAP4430
|WLAN, Bluetooth, 10/100 Ethernet
| [[PandaBoard|Pandaboard wiki page]],
|
|
|
|-
|[http://www.calao-systems.com/articles.php?lng=fr&pg=6186 Snowball SDK & PDK]
|[http://www.calao-systems.com/ CALAO Systems]
|2011
|1GB
|4GB / 8GB
|ST-Ericsson A9500 Dual Cortex A9 + Mali 400
|WiFi, BlueTooth, GPS, HDMI, CVBS, Ethernet 10/100, Audio In / Out, Micro-SD, Serial Port (Linux console), JTAG, MiPi34, 3D Accelerometer, Magnetometer & Gyrometer, Pressure sensor, 3x expansion connectors
|Expansion Board(s) : MOB-SKY-S9500-AVI-CXX (2x USB OTG HS, LVDS 24Bits, TSC, LED Driver, MiPi DSI, MiPi CSI...), DAB-SKY-S9500-GPI-CXX (CANBus, Modem 2G/3G, 4x Uart, 8x GPIO, 8x ADC)
|[http://www.igloocommunity.org/ Igloo Community]
|[http://www.igloocommunity.org/ Igloo Community]
|[http://www.calao-systems.com/repository/EMBEDDED%20COMPUTERS/SKY-S9500-ULP-XXX/ CALAO Systems Repository]
|-
|-
|[http://www.raspberrypi.org/ US$ 25 Raspberry Pi Computer]
|Raspberry Pi Foundation
|2012
|256
|none (SD Card)
|Broadcom ARM11 (ARM v6) + Videocore GPU
|10/100 Ethernet, HDMI , Composite , Audio, USB Host, GPIO, JTAG , MIPI DSI + CSI
|[[RPi Hub|Phenomenal RPi Hub]]
|[http://www.raspberrypi.org/archives/1839 MPEG-2 and VC-1 Licences]
[https://github.com/raspberrypi/firmware/tree/master/opt/vc OpenGL, OpenMax examples]
|[http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf Schematics]
[http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf CPU Datasheet]
|[http://www.raspberrypi.org/downloads Card Images]
|-
|[http://www.ledato.de/ NanosG20]
|Ledato
|?
|64M/128M
|128M/512M
|
|
|
|
|
|
|}
{| border="1" cellspacing="0" cellpadding="5"
|+'''Development boards'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! style="width:120px" | Processor
! RAM MB
! Flash MB
! style="width:150px" |Video Display
! style="width:250px" |Interfaces
! OS support
! Notes
|-
|[http://www.armkits.com/Product/devkit8000.asp/ DevKit8000]
|[http://www.armkits.com Embest]
|TI OMAP3530
|256MB DDR
|512MB Nand Flash
|LCD, VGA, DVI-D and S-Video
|UART, USB Host, USB OTG, Ethernet, Audio, SD, Keyboard, JTAG
|Linux2.6.28, WinCE6.0
|[[Devkit8000]] wiki page
|-
|[http://www.armkits.com/Product/devkit8500d.asp/ DevKit8500D/A]
|[http://www.armkits.com Embest]
|style="width:120px" |TI DM3730/AM3715
|512MB DDR
|512MB Nand Flash
|LCD, VGA, DVI-D and S-Video
|UART, USB Host, USB OTG, Ethernet, Audio, SD, Keyboard, JTAG
|Linux2.6.28, WinCE6.0, Android2.2
|-
|[http://www.armkits.com/product/devkit8600.asp/ DevKit8600]
|[http://www.armkits.com Embest]
|style="width:120px" |TI AM3359
|512MB DDR3
|512MB Nand Flash
|LCD, VGA
|UART, USB Host, USB OTG, Ethernet, CAN, RS485, WiFi/BT, Audio, TF, JTAG
|Linux3.1.0, Android2.3, WinCE7
|-
|[http://www.armkits.com/product/sabrelite.asp SABRE Lite]
|[http://www.armkits.com Embest]
|stype="width:120px" |Freescale i.MX 6Quad
|1GB DDR3
|2MB SPI Flash
|RGB, LVDS and HDMI
|UART, USB, Ethernet, CAN, SATA, SD, JTAG, I2C, Audio
|Linux3.0.15, Android4.0.4
|
|-
|[http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4102 NGW100]
|[http://www.atmel.com Atmel]
|Atmel AVR32: AT32AP7000
|32M
|8M serial + 8M parallel
|"LCD Controller"
|UARTs, USB slave, 2x 100MBit Ethernet, I2C, SPI, JTAG, AC97
|Linux 2.6 [http://www.avr32linux.org http://www.avr32linux.org]
|
|}
 

== Development Boards with FPGA ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Development Boards with FPGA'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
| [http://www.armadeus.com/english/products-processor_boards-apf27.html APF27]
| [http://www.armadeus.com/ Armadeus Systems]
| 2009
| up to 256
| up to 512
| i.MX27 400MHz + Spartan3a
| [http://www.armadeus.com/english/products-processor_boards-apf27.html Company Site]
| [http://www.armadeus.org Developer Site]
|-
|}
 

== Development Boards with MINI2440v2 with 3.5'' ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Development Boards with MINI2440V2'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
[http://www.developmentboard.net/index.php/productdetail/Development+board/ARM9/SAMSUNG/S3C2440/MINI2440v2+with+MegaDisplay+3.5/info/1]
| [http://www.developmentboard.net]
| 2009
| up to 256
| up to 512
| i.MX27 400MHz + Spartan3a
| [http://www.developmentboard.net/index.php/productdetail/Development+board/ARM9/SAMSUNG/S3C2440/MINI2440v2+with+MegaDisplay+3.5/info/1]
| [http://www.developmentboard.net Developer Site]
|-
|}
 

== Not Yet Categorized ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Not Yet Categorized devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
| Indamixx 2 Audio Tablet
| Indamixx
| 2010
| 2 GB
| 150 GB HDD
| Atom N450
| [http://www.indamixx.com/shop-28.html Company website]
| http://www.indamixx.com/shop-60.html
|-
| [http://www.linuxdevices.com/articles/AT4268573160.html HS210]
| [http://www.ericsson.com Ericsson]
| 2000
| 32
| 32
| StrongARM SA-1110
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| Armadillo-500
| [http://www.atmark-techno.com/en Atmark Techno]
| 2007
| 64
| 16
| i.MX31
| [http://www.atmark-techno.com/en/products/armadillo/a500 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser Armadillo Developer Site]
|-
|- align="center"
| Armadillo-300
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a300 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-300 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-9
| [http://www.atmark-techno.com/en Atmark Techno]
| 2004
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a9 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-9 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-240
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a240 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-240 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-230
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 32
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a230 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-230 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-220
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 32
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a220 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-220 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-210
| [http://www.atmark-techno.com/en Atmark Techno]
| 2005
| 32
| 4
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a210 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-210 Armadillo Developer Site]
|-
|- align="center"
| Eddy v2.1 Series
| [http://www.sysbas.com/ SystemBase]
| 2008
| 32
| 8
| ARM9 210MHz
| [http://www.sysbas.com/e-Products/?sNum=400 Company Site]
| [http://embeddedmodule.com/ Eddy Developer Site]
|-
|- align="center"
| Matrix Series
| [http://www.artila.com/ Artila]
| 2006
| 64
| 16
| ARM9 180MHz
| [http://www.artila.com Company Site]
| [http://www.artila.com/p_matrix.html Matrix Site]
|-
|}
 

== Home And Building Automation, Smart Energy ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''HABA & Smart Energy controllers using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=fr&pg=6114 HABA-KNX-EXPLORER-C01]
| [http://www.calao-systems.com CALAO Systems]
| 2011
| 128
| 256
| AT91SAM9G20 (400MHz)
| [http://www.calao-systems.com/repository/HABA%20CONTROLLERS/HABA-KNX-EXPLORER-XXX/ Repository]
| [http://www.calao-systems.com/repository/HABA%20CONTROLLERS/HABA-KNX-EXPLORER-XXX/ Repository]
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=fr&pg=6257 HABA-KNX-LITE-E01]
| [http://www.calao-systems.com CALAO Systems]
| 2012
| 128
| 256
| AT91SAM9G20 (400MHz)
| [http://www.calao-systems.com/repository/HABA%20CONTROLLERS/HABA-KNX-LITE-XXX/ Repository]
| [http://www.calao-systems.com/repository/HABA%20CONTROLLERS/HABA-KNX-LITE-XXX/ Repository]
|-

|}
 

[[Category:Products]]

Products

2012-11-27T08:19:30Z

Yclinda666: /* Development boards */

Here is a list of products which use embedded Linux.

Please see the [[Talk:Products|talk page]] for information about how we want to populate this page.

== Televisions ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Televisions using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Mobile Phones ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Mobile Phones using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:150px" | Download Area
! Proprietary Drivers
! Proprietary Software
|- align="center"
| [http://www.accton.com/homepage/main3/product_range/23_CE/VM1188T.htm VM1188T]
| [http://www.accton.com Accton]
| 2006
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://www.cellon.com/products.jsp?id=18 C8000]
| [http://www.cellon.com/ Cellon]
| 2005
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/news/NS8901223473.html 3G Linux Ref Design]
| [http://www.catt.ac.cn/english/ Datang]
| 2004
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/news/NS4367004471.html E28 FMC phones]
| [http://www.e28.com/eng/ E28]
| 2006
| -
| -
| OMAP 730
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/news/NS5033717348.html E28 E2800]
| [http://www.e28.com/eng/ E28]
| 2003
| 32
| 32
| ARM9
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/news/NS2220873893.html E28 E2800+]
| [http://www.e28.com/eng/ E28]
| 2004
| 64
| 32
| ARM9 300MHz
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://www.g-tekgroup.com/products/pwg_500.asp PWG500]
| [http://www.g-tekgroup.com/ G-Tek]
| 2006
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/articles/AT2559540724.html G500i]
| Grundig
| 2005
| 52 - User
| X
| OMAP850
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
| ?
| ?
|-
|- align="center"
| [http://www.haier.com/products/product.asp?proID=4948 N60]
| [http://www.haier.com Haier]
| 2006
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
| ?
| ?
|-
|- align="center"
| [http://www.imcosys.com/smartphones.html GPS Phone]
| [http://www.imcosys.com/ ImCoSys]
| 2006
| 64
| 64
| OMAP 730
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| [http://www.imcosys.com/English/Download/download.html SDK & Flash Image]
| ?
| ?
|-
|- align="center"
| Openmoko Freerunner
| Openmoko
| 2008
| 128
| 256
| armV4@400Mhz
| [http://wiki.openmoko.org/wiki/Neo_FreeRunner Openmoko wiki], [http://en.wikipedia.org/wiki/Open_hardware open hardware](schematics freely available)
| [http://wiki.openmoko.org/wiki/Distributions multiple distributions]
| None(but 3 proprietary firmwares: gsm,gps and wifi)
| None
|-
|- align="center"
| Nokia N900
| Nokia
| ?
| 256
| 256M NAND +32G eMMC
| OMAP 3430 SoC( 600 MHz ARM Cortex-A8 CPU)
| ?
| ?
| see [http://wiki.maemo.org/Free_Maemo here]
| see [http://wiki.maemo.org/Free_Maemo here]
|-
|- align="center"
| Htc Dream
| HTC
| ?
| 192M(but some reserved for the DSPs)
|
| MSM7201A(armv6-novfp@528Mhz)
| run android by default,GNU/Linux port [http://www.htc-linux.org/wiki/index.php?title=Dream#Kernel_Status in progress](require routing or ADP)
|
| yes by default([http://trac.osuosl.org/trac/replicant/wiki/HTCDreamProprietaryDrivers list here] )
| yes by default
|-
|}
 

== Audio and Video Mobile Players ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Audio and Video Mobile Players using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:150px" | Download Area
! Proprietary Drivers
! style="width:300px" | Proprietary Software
|- align="center"
| PMA430
| Archos
| ?
| 64MB(48MB usable)
| ?(loop image on the hdd used)
| omap1(armv4@74.34 bogomips)
|
| [http://openpma.org/wiki/Main_Page alternative community distribution]
| yes(dm270fb.o(framebuffer driver),mabe others)
| yes(qtopia),you can't change the kernel unless you find or write a replacement for the proprietary drivers
|-
|- align="center"
| Archos 5
| Archos
| ?
| 128 M
| 40G/60G/120G/160G/250G hdd
| OMAP3
|
| [http://www.openaos.org/ openaos(alternative(to android) community distribution)]
comes with android by default,
but thanks to an SDE(special developer edition) firmware GNU/Linux can be installed.
OpenAOS and SDE are based on openembedded.
|?
|?
|-

|-
|- align="center"
| Archos 7
| Archos
| ?
| 128 M
| 160G/320G hdd
| OMAP3
|
| [http://www.openaos.org/ openaos(alternative(to android) community distribution)]
comes with android by default,
but thanks to an SDE(special developer edition) firmware GNU/Linux can be installed.
OpenAOS and SDE are based on openembedded.
|?
|?
|-
|}
 

== Internet tablet ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Internet tablet using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:150px" | Download Area
! Proprietary Drivers
! style="width:300px" | Proprietary Software
|- align="center"
| [[N800]]
| Nokia
| ?
| 128MB
| 256MB
| OMAP2420@400 MHz
|
| yes(wifi(free wifi driver available but still need a calibration binary).dsp,sound )
| can be remplcad by [http://dev.openbossa.org/trac/mamona/wiki mamona] but no wifi and sound
|-
| [http://tabletsetc.com/tablets/4tiitoo-wetab/specs/ WeTab]
| Neofonie/Pegatron
| 2010
| 1 GB
| 16 GB
| 1.66GHz Intel Atom N450
| Running MeeGo
| http://wetab.mobi/en/developers/downloads-and-howtos/
|
|
|-
|}

== Settop Boxes ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Settop Boxes using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| Freedom Jump
| Amino Communications
| 2010
| 1 GB DDR 3
| 512 MB
| Intel® Atom CE4150
| MeeGo platform
| http://www.aminocom.com/products/freedom-jump/
|- align="center"
| Roku SD/HD/HD-XR/XDS
| Roku
| 2010
| ?
| ?
| NXP PNX8935
|
| [http://support.roku.com/entries/246042-roku-player-open-source-resources|Roku open source]
|-
|}
 

== Digital Video Recorders ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Digital Video Recorders using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Game Consoles ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Game Consoles using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| PlayStation 2
| Sony Computer Entertainment
| 2000
| 32MB
| unknown
| MIPS 64-bit R5900
| [http://en.wikipedia.org/wiki/PlayStation_2 PS2 wikipedia page], [http://playstation2-linux.com/ Playstation-linux community site]
| [http://blackrhino.xrhino.com/main.php?page=home Black Rhino Linux distribution site]
|- align="center"
| PlayStation 3
| Sony Computer Entertainment
| 2006
| 512 MB
| unknown
| CELL broadband engine
| [http://en.wikipedia.org/wiki/PlayStation_3 PS3 wikipedia page]
| [http://en.wikipedia.org/wiki/Linux_for_PlayStation_3 wikipedia PS3-linux page]
|- align="center"
| Didj
| LeapFrog Enterprises
| 2008
| 32MB
| 256MB
| [[LF-1000]]/[[Pollux]]
| [[Didj]]
| [[Leapfrog Source Code]]
|- align="center"
| Leapster Explorer
| LeapFrog Enterprises
| 2010
| 64MB
| 512MB
| [[LF-1000]]/[[Pollux]]
| [[Leapster Explorer]]
| [[Leapfrog Source Code]]
|- align="center"
| LeapPad Explorer
| LeapFrog Enterprises
| 2011
| 64MB
| 2GB
| [[LF-1000]]/[[Pollux]]
| [[Leappad Explorer]]
| [[Leapfrog Source Code]]
|-
|}
 

== Network Attached Storage (NAS) ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Network Attached Storage using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| NSLU2
| [http://www.linksys.com Linksys]
| 2004
| 32MB
| 8MB
| Intel XScale IXP420
|
| http://www.nslu2-linux.org (community site with improved firmwares)
|-
|}
 

== Network Camera ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Network Camera using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| NC353L
| [http://www3.elphel.com Elphel, Inc]
| 2007
| 64MB
| 128MB
| Axis EtraxFS
| http://wiki.elphel.com
| http://sourceforge.net/projects/elphel
|-
|}
 
== Networked Media Players ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Networked Media Players using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| [[Freecom MusicPal | MusicPal]]
| [http://www.freecom.com Freecom]
| 2007
| 32MB
| unknown
| [[Marvell 88W8618]]
|
| http://www.musicpal.info (under Legal Notice]
|-
|}
 

== Still and Video Cameras ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Not Yet Categorized devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| HDR-UX1, HDR-SR1 video cameras
| Sony
| 2006
| ??
| ??
| ARM9
| [http://www.sonystyle.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=10551&storeId=10151&langId=-1&productId=11035608 Sonystyle store listing]
| [http://www.sony.net/Products/Linux/Download/HDR-UX1_HDR-SR1.html Sony Linux Download area]
|-
|}

== Assistive Technology ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Assistive Technology devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
| [http://www.toby-churchill.com/en/content/lightwriters-0 Lightwriter SL38]
| [http://www.toby-churchill.com Toby Churchill Ltd]
| 2004
| 64
| 256
| StrongARM SA-1110
| [http://balloonboard.org/ Developer site]
| [http://husaberg.toby-churchill.com/balloon/ code and sources]
|}
 

== Robots and Smart-companions ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Robots and smart-companions using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| [http://fr.wikipedia.org/wiki/Karotz Karotz]
| [http://en.wikipedia.org/wiki/Mindscape_(software_publisher) Mindscape ] then [http://www.aldebaran-robotics.com/ Aldebaran Robotics]
| 2011
| 64
| 256
| Samsung [http://elinux.org/S3C2440 S3C2440] (ARM920T@400Mhz)
| [http://dev.karotz.com/ Developer site]
|
|}
 

== Network devices ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Network devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! Connectivity
! Notes
! style="width:150px" | Source
! style="width:250px" | Download Area
! Proprietary Drivers or software
|-
| Sheevaplug
| [http://en.wikipedia.org/wiki/Marvell_Technology_Group Marvell]
|
| 512M
| 512M
| Kirkwood 88F6281 (armv5@1.2Ghz)
| Ethernet,usb,sdio
|
|
|
| ?
|}
 

== Modular devices ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Modular devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! Connectivity
! Notes
! style="width:150px" | Source
! style="width:250px" | Download Area
! Proprietary Drivers or software
|-
|- align="center"
| [http://www.buglabs.net/bugbase bugbase 1.2]
| [http://www.buglabs.net Bug Labs]
| 2006
| 128
| 32
| imx31(armv6-vfp@533Mhz)
| USB host(on the von hippel module),micro-sd,usb OTG
| Up to 4 modules(802.15.4,motion detector,screen(320x240),sound card,breakout(von hippel),gps modules availables), [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://bugcommunity.com/wiki/index.php/BUGbase schematics] freely available)
| [http://bssvn.buglabs.net/svn/!tree/10763 Bug svn] 
Based on [http://pokylinux.org/ poky linux], 
uses [http://en.wikipedia.org/wiki/Concierge_OSGi concierge OSGI], 
Can use bug 1.3's [http://cgit.openembedded.net/cgit.cgi/openembedded/tree/conf/machine/bug.conf Basic machine support in openembedded]
| http://www.buglabs.net/downloads
| No(the powervr is not used)
|-
|- align="center"
| [http://www.buglabs.net/bugbase bugbase 1.3]
| [http://www.buglabs.net Bug Labs]
| 2009
| 128
| 32
| imx31(armv6-vfp@533Mhz)
| wifi(libertas_sdio),bluetooth,USB(on the von hippel module),micro-sd,usb OTG
| Up to 4 modules(802.15.4,motion detector,screen(320x240),sound card,breakout(von hippel),gps modules availables), [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://bugcommunity.com/wiki/index.php/BUGbase schematics] freely available)
| [http://bssvn.buglabs.net/svn/!tree/10763 Bug svn] 
Based on [http://pokylinux.org/ poky linux], 
uses [http://en.wikipedia.org/wiki/Concierge_OSGi concierge OSGI], 
[http://cgit.openembedded.net/cgit.cgi/openembedded/tree/conf/machine/bug.conf Basic machine support in openembedded]
| http://www.buglabs.net/downloads
| No(the powervr is not used)
|-
|- align="center"
| [http://www.gumstix.com/store/catalog/product_info.php?cPath=27_33&products_id=227 Overo fire]
| [http://www.gumstix.com Gumstix]
| ?
| 256M
| 256M
| OMAP 3530(also contain POWERVR SGX + C64x)
| wifi(libertas),bluetooth,micro-sd,usb OTG+Host(not shure if USB is on the module or only avaliable on extensions boards)
| expansions board available [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://pubs.gumstix.com/boards/ schematics] freely available but only for extension boards)
| [http://cgit.openembedded.net/cgit.cgi/openembedded/tree/conf/machine/overo.conf Machine support in openembedded]
|
| ?
|-
|- align="center"
| [http://www.gumstix.com/store/catalog/product_info.php?products_id=226 overo air]
| [http://www.gumstix.com Gumstix]
| ?
| 256M
| 256M
| OMAP 3503(no 3D acceleration and no DSP)
| wifi(libertas),bluetooth,micro-sd,usb OTG+Host(not shure if USB is on the module or only avaliable on extensions boards)
| expansions board available [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://pubs.gumstix.com/boards/ schematics] freely available but only for extension boards)
|
|
| ?
|-

|- align="center"
| [http://www.gumstix.com/store/catalog/product_info.php?products_id=228 overo water]
| [http://www.gumstix.com Gumstix]
| ?
| 256M
| 256M
| OMAP 3530(also contain POWERVR SGX + C64x)
| micro-sd,usb OTG+Host(not shure if USB is on the module or only avaliable on extensions boards)
| expansions board available [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://pubs.gumstix.com/boards/ schematics] freely available but only for extension boards)
|
|
| ?
|-

|- align="center"
| [http://www.gumstix.com/store/catalog/product_info.php?products_id=211 Overo earth]
| [http://www.gumstix.com Gumstix]
| ?
| 256M
| 256M
| OMAP 3503(no DSP,no 3d acceleration)
| micro-sd,usb OTG+Host(not shure if USB is on the module or only avaliable on extensions boards)
| expansions board available [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://pubs.gumstix.com/boards/ schematics] freely available but only for extension boards)
|
|
| ?
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=5969 TNY-A9G20-LPW-I02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2009
| 64M
| 256M
| AT91SAM9G20(400Mhz)
| Micro-SD, RTC (ext. battery), USB OTG (Full Speed), Serial DBGU (Linux console), JTAG, 2 expansion connectors.
| MotherBoard(s) : MOB-TNY-A9XXX-MD2-CXX, Expansion board(s): GPI2 (1W,I2C, SPI, UART), GPS, GSM/GPRS, GSM/HSDPA, WiFi/BlueTooth, KNX/RF, Wireless MBUS, ZigBee...
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=5885 TNY-A9263-C02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2008
| 64M
| 256M
| AT91SAM9263(200Mhz)
| USB OTG (Full Speed), Serial DBGU (Linux console),2 expansion connectors.
| Motherboard(s) : MOB-TNY-A9XXX-MD2-CXX, Expansion board(s): GPI2 (1W,I2C, SPI, UART), GPS, GSM/GPRS, GSM/HSDPA, WiFi/BlueTooth, KNX/RF, Wireless MBUS, ZigBee...
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=6237 TNY-T3730-ULP-C01]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2011
| 256M
| 256M
| OMAP3730(800Mhz)
| Micro-SD, Battery Charger, USB OTG (Full Speed), UART (Linux Console), Jtag, 2 expansion connectors
| No motherboard(s), No expansion board(s).
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=5933 QIL-A9260-C02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2011
| 64M
| 256M
| AT91SAM9260(200Mhz)
| 2Mbits SPI Serial Flash, 64Kbits SPI E2PROM, Micro-SD, RTC, 2 expansion connectors
| Motherboard(s) : MOB-QIL-A9XXX-CXX, No expansion boards.
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=6113 USB-A9G20-LPW-C02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2011
| 64M
| 256M
| AT91SAM9G20(400Mhz)
| Micro-SD, RTC, USB Debug (Full Speed), USB Device FS, 2x USB Host FS, Ethernet 10/100, expansion connector
| Motherboard(s) : N/A, Expansion boards : GPI2 (1W,I2C, SPI, UART), GPS, GSM/GPRS, GSM/HSDPA, WiFi/BlueTooth, KNX/RF, Wireless MBUS, ZigBee...
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=5932 USB-A9263-C02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2009
| 64M
| 256M
| AT91SAM9263(200Mhz)
| Micro-SD, USB Debug (Full Speed), USB Device FS, 2x USB Host FS, Ethernet 10/100, expansion connector
| Motherboard(s) : N/A, No Expansion board(s)
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|}
 

== Development boards ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Development boards'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! Connectivity
! Notes
! Proprietary Drivers
! style="width:150px" | Source
! style="width:250px" | Download Area
|-
|[http://beagleboard.org/ Beagle Board]
|Texas Instruments
|2008
|256M
|256M
|OMAP3530
|
| lot of informations in the [[BeagleBoard|BeagleBoard wiki page]], 
[http://en.wikipedia.org/wiki/Open_hardware open hardware](schematics freely available)
| The powervr(3d chip) require a proprietary 3d driver for the 3d part
|
|
|-
|[http://beagleboard.org/bone BeagleBone]
|Texas Instruments
|2011
|256MB
|none (MicroSD)
|AM3358
|Ethernet 10/100
|[[BeagleBone|BeagleBone wiki page]], [[BeagleBoard|BeagleBoard wiki page]], 
[http://en.wikipedia.org/wiki/Open_hardware open hardware](schematics freely available)
|The powervr(3d chip) require a proprietary 3d driver for the 3d part
|
|
|-
|[http://pandaboard.org/ Pandaboard]
|Texas Instruments
|2010
|8Gb(x32) x 2ch
|(2G(x32) x4pcs) 2CS/ch
|OMAP4430
|WLAN, Bluetooth, 10/100 Ethernet
| [[PandaBoard|Pandaboard wiki page]],
|
|
|
|-
|[http://www.calao-systems.com/articles.php?lng=fr&pg=6186 Snowball SDK & PDK]
|[http://www.calao-systems.com/ CALAO Systems]
|2011
|1GB
|4GB / 8GB
|ST-Ericsson A9500 Dual Cortex A9 + Mali 400
|WiFi, BlueTooth, GPS, HDMI, CVBS, Ethernet 10/100, Audio In / Out, Micro-SD, Serial Port (Linux console), JTAG, MiPi34, 3D Accelerometer, Magnetometer & Gyrometer, Pressure sensor, 3x expansion connectors
|Expansion Board(s) : MOB-SKY-S9500-AVI-CXX (2x USB OTG HS, LVDS 24Bits, TSC, LED Driver, MiPi DSI, MiPi CSI...), DAB-SKY-S9500-GPI-CXX (CANBus, Modem 2G/3G, 4x Uart, 8x GPIO, 8x ADC)
|[http://www.igloocommunity.org/ Igloo Community]
|[http://www.igloocommunity.org/ Igloo Community]
|[http://www.calao-systems.com/repository/EMBEDDED%20COMPUTERS/SKY-S9500-ULP-XXX/ CALAO Systems Repository]
|-
|-
|[http://www.raspberrypi.org/ US$ 25 Raspberry Pi Computer]
|Raspberry Pi Foundation
|2012
|256
|none (SD Card)
|Broadcom ARM11 (ARM v6) + Videocore GPU
|10/100 Ethernet, HDMI , Composite , Audio, USB Host, GPIO, JTAG , MIPI DSI + CSI
|[[RPi Hub|Phenomenal RPi Hub]]
|[http://www.raspberrypi.org/archives/1839 MPEG-2 and VC-1 Licences]
[https://github.com/raspberrypi/firmware/tree/master/opt/vc OpenGL, OpenMax examples]
|[http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf Schematics]
[http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf CPU Datasheet]
|[http://www.raspberrypi.org/downloads Card Images]
|-
|[http://www.ledato.de/ NanosG20]
|Ledato
|?
|64M/128M
|128M/512M
|
|
|
|
|
|
|}
{| border="1" cellspacing="0" cellpadding="5"
|+'''Development boards'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! style="width:120px" | Processor
! RAM MB
! Flash MB
! style="width:150px" |Video Display
! style="width:250px" |Interfaces
! OS support
! Notes
|-
|[http://www.armkits.com/Product/devkit8000.asp/ DevKit8000]
|[http://www.armkits.com Embest]
|TI OMAP3530
|256M
|512M
|LCD, VGA, DVI-D and S-Video
|UART, USB Host, USB OTG, Ethernet, Audio, SD, Keyboard, JTAG
|Linux2.6.28, WinCE6.0
|[[Devkit8000]] wiki page
|-
|[http://www.armkits.com/Product/devkit8500d.asp/ DevKit8500D/A]
|[http://www.armkits.com Embest]
|style="width:120px" |TI DM3730/AM3715
|512M
|512M
|LCD, VGA, DVI-D and S-Video
|UART, USB Host, USB OTG, Ethernet, Audio, SD, Keyboard, JTAG
|Linux2.6.28, WinCE6.0, Android2.2
|-
|[http://www.armkits.com/product/devkit8600.asp/ DevKit8600]
|[http://www.armkits.com Embest]
|style="width:120px" |TI AM3359
|512M
|512M
|LCD, VGA
|UART, USB Host, USB OTG, Ethernet, CAN, RS485, WiFi/BT, Audio, TF, JTAG
|Linux3.1.0, Android2.3, WinCE7
|-
|[http://www.armkits.com/product/sabrelite.asp SABRE Lite]
|[http://www.armkits.com Embest]
|stype="width:120px" |Freescale i.MX 6Quad
|1GB DDR3
|2MB SPI Flash
|RGB, LVDS and HDMI
|UART, USB, Ethernet, CAN, SATA, SD, JTAG, I2C, Audio
|Linux3.0.15, Android4.0.4
|
|-
|[http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4102 NGW100]
|[http://www.atmel.com Atmel]
|Atmel AVR32: AT32AP7000
|32M
|8M serial + 8M parallel
|"LCD Controller"
|UARTs, USB slave, 2x 100MBit Ethernet, I2C, SPI, JTAG, AC97
|Linux 2.6 [http://www.avr32linux.org http://www.avr32linux.org]
|
|}
 

== Development Boards with FPGA ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Development Boards with FPGA'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
| [http://www.armadeus.com/english/products-processor_boards-apf27.html APF27]
| [http://www.armadeus.com/ Armadeus Systems]
| 2009
| up to 256
| up to 512
| i.MX27 400MHz + Spartan3a
| [http://www.armadeus.com/english/products-processor_boards-apf27.html Company Site]
| [http://www.armadeus.org Developer Site]
|-
|}
 

== Development Boards with MINI2440v2 with 3.5'' ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Development Boards with MINI2440V2'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
[http://www.developmentboard.net/index.php/productdetail/Development+board/ARM9/SAMSUNG/S3C2440/MINI2440v2+with+MegaDisplay+3.5/info/1]
| [http://www.developmentboard.net]
| 2009
| up to 256
| up to 512
| i.MX27 400MHz + Spartan3a
| [http://www.developmentboard.net/index.php/productdetail/Development+board/ARM9/SAMSUNG/S3C2440/MINI2440v2+with+MegaDisplay+3.5/info/1]
| [http://www.developmentboard.net Developer Site]
|-
|}
 

== Not Yet Categorized ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Not Yet Categorized devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
| Indamixx 2 Audio Tablet
| Indamixx
| 2010
| 2 GB
| 150 GB HDD
| Atom N450
| [http://www.indamixx.com/shop-28.html Company website]
| http://www.indamixx.com/shop-60.html
|-
| [http://www.linuxdevices.com/articles/AT4268573160.html HS210]
| [http://www.ericsson.com Ericsson]
| 2000
| 32
| 32
| StrongARM SA-1110
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| Armadillo-500
| [http://www.atmark-techno.com/en Atmark Techno]
| 2007
| 64
| 16
| i.MX31
| [http://www.atmark-techno.com/en/products/armadillo/a500 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser Armadillo Developer Site]
|-
|- align="center"
| Armadillo-300
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a300 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-300 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-9
| [http://www.atmark-techno.com/en Atmark Techno]
| 2004
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a9 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-9 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-240
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a240 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-240 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-230
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 32
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a230 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-230 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-220
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 32
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a220 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-220 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-210
| [http://www.atmark-techno.com/en Atmark Techno]
| 2005
| 32
| 4
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a210 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-210 Armadillo Developer Site]
|-
|- align="center"
| Eddy v2.1 Series
| [http://www.sysbas.com/ SystemBase]
| 2008
| 32
| 8
| ARM9 210MHz
| [http://www.sysbas.com/e-Products/?sNum=400 Company Site]
| [http://embeddedmodule.com/ Eddy Developer Site]
|-
|- align="center"
| Matrix Series
| [http://www.artila.com/ Artila]
| 2006
| 64
| 16
| ARM9 180MHz
| [http://www.artila.com Company Site]
| [http://www.artila.com/p_matrix.html Matrix Site]
|-
|}
 

== Home And Building Automation, Smart Energy ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''HABA & Smart Energy controllers using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=fr&pg=6114 HABA-KNX-EXPLORER-C01]
| [http://www.calao-systems.com CALAO Systems]
| 2011
| 128
| 256
| AT91SAM9G20 (400MHz)
| [http://www.calao-systems.com/repository/HABA%20CONTROLLERS/HABA-KNX-EXPLORER-XXX/ Repository]
| [http://www.calao-systems.com/repository/HABA%20CONTROLLERS/HABA-KNX-EXPLORER-XXX/ Repository]
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=fr&pg=6257 HABA-KNX-LITE-E01]
| [http://www.calao-systems.com CALAO Systems]
| 2012
| 128
| 256
| AT91SAM9G20 (400MHz)
| [http://www.calao-systems.com/repository/HABA%20CONTROLLERS/HABA-KNX-LITE-XXX/ Repository]
| [http://www.calao-systems.com/repository/HABA%20CONTROLLERS/HABA-KNX-LITE-XXX/ Repository]
|-

|}
 

[[Category:Products]]

Products

2012-11-27T08:07:53Z

Yclinda666: /* Development boards */

Here is a list of products which use embedded Linux.

Please see the [[Talk:Products|talk page]] for information about how we want to populate this page.

== Televisions ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Televisions using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Mobile Phones ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Mobile Phones using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:150px" | Download Area
! Proprietary Drivers
! Proprietary Software
|- align="center"
| [http://www.accton.com/homepage/main3/product_range/23_CE/VM1188T.htm VM1188T]
| [http://www.accton.com Accton]
| 2006
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://www.cellon.com/products.jsp?id=18 C8000]
| [http://www.cellon.com/ Cellon]
| 2005
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/news/NS8901223473.html 3G Linux Ref Design]
| [http://www.catt.ac.cn/english/ Datang]
| 2004
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/news/NS4367004471.html E28 FMC phones]
| [http://www.e28.com/eng/ E28]
| 2006
| -
| -
| OMAP 730
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/news/NS5033717348.html E28 E2800]
| [http://www.e28.com/eng/ E28]
| 2003
| 32
| 32
| ARM9
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/news/NS2220873893.html E28 E2800+]
| [http://www.e28.com/eng/ E28]
| 2004
| 64
| 32
| ARM9 300MHz
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
| ?
| ?
|-
|- align="center"
| [http://www.g-tekgroup.com/products/pwg_500.asp PWG500]
| [http://www.g-tekgroup.com/ G-Tek]
| 2006
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
| ?
| ?
|-
|- align="center"
| [http://linuxdevices.com/articles/AT2559540724.html G500i]
| Grundig
| 2005
| 52 - User
| X
| OMAP850
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
| ?
| ?
|-
|- align="center"
| [http://www.haier.com/products/product.asp?proID=4948 N60]
| [http://www.haier.com Haier]
| 2006
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
| ?
| ?
|-
|- align="center"
| [http://www.imcosys.com/smartphones.html GPS Phone]
| [http://www.imcosys.com/ ImCoSys]
| 2006
| 64
| 64
| OMAP 730
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| [http://www.imcosys.com/English/Download/download.html SDK & Flash Image]
| ?
| ?
|-
|- align="center"
| Openmoko Freerunner
| Openmoko
| 2008
| 128
| 256
| armV4@400Mhz
| [http://wiki.openmoko.org/wiki/Neo_FreeRunner Openmoko wiki], [http://en.wikipedia.org/wiki/Open_hardware open hardware](schematics freely available)
| [http://wiki.openmoko.org/wiki/Distributions multiple distributions]
| None(but 3 proprietary firmwares: gsm,gps and wifi)
| None
|-
|- align="center"
| Nokia N900
| Nokia
| ?
| 256
| 256M NAND +32G eMMC
| OMAP 3430 SoC( 600 MHz ARM Cortex-A8 CPU)
| ?
| ?
| see [http://wiki.maemo.org/Free_Maemo here]
| see [http://wiki.maemo.org/Free_Maemo here]
|-
|- align="center"
| Htc Dream
| HTC
| ?
| 192M(but some reserved for the DSPs)
|
| MSM7201A(armv6-novfp@528Mhz)
| run android by default,GNU/Linux port [http://www.htc-linux.org/wiki/index.php?title=Dream#Kernel_Status in progress](require routing or ADP)
|
| yes by default([http://trac.osuosl.org/trac/replicant/wiki/HTCDreamProprietaryDrivers list here] )
| yes by default
|-
|}
 

== Audio and Video Mobile Players ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Audio and Video Mobile Players using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:150px" | Download Area
! Proprietary Drivers
! style="width:300px" | Proprietary Software
|- align="center"
| PMA430
| Archos
| ?
| 64MB(48MB usable)
| ?(loop image on the hdd used)
| omap1(armv4@74.34 bogomips)
|
| [http://openpma.org/wiki/Main_Page alternative community distribution]
| yes(dm270fb.o(framebuffer driver),mabe others)
| yes(qtopia),you can't change the kernel unless you find or write a replacement for the proprietary drivers
|-
|- align="center"
| Archos 5
| Archos
| ?
| 128 M
| 40G/60G/120G/160G/250G hdd
| OMAP3
|
| [http://www.openaos.org/ openaos(alternative(to android) community distribution)]
comes with android by default,
but thanks to an SDE(special developer edition) firmware GNU/Linux can be installed.
OpenAOS and SDE are based on openembedded.
|?
|?
|-

|-
|- align="center"
| Archos 7
| Archos
| ?
| 128 M
| 160G/320G hdd
| OMAP3
|
| [http://www.openaos.org/ openaos(alternative(to android) community distribution)]
comes with android by default,
but thanks to an SDE(special developer edition) firmware GNU/Linux can be installed.
OpenAOS and SDE are based on openembedded.
|?
|?
|-
|}
 

== Internet tablet ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Internet tablet using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:150px" | Download Area
! Proprietary Drivers
! style="width:300px" | Proprietary Software
|- align="center"
| [[N800]]
| Nokia
| ?
| 128MB
| 256MB
| OMAP2420@400 MHz
|
| yes(wifi(free wifi driver available but still need a calibration binary).dsp,sound )
| can be remplcad by [http://dev.openbossa.org/trac/mamona/wiki mamona] but no wifi and sound
|-
| [http://tabletsetc.com/tablets/4tiitoo-wetab/specs/ WeTab]
| Neofonie/Pegatron
| 2010
| 1 GB
| 16 GB
| 1.66GHz Intel Atom N450
| Running MeeGo
| http://wetab.mobi/en/developers/downloads-and-howtos/
|
|
|-
|}

== Settop Boxes ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Settop Boxes using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| Freedom Jump
| Amino Communications
| 2010
| 1 GB DDR 3
| 512 MB
| Intel® Atom CE4150
| MeeGo platform
| http://www.aminocom.com/products/freedom-jump/
|- align="center"
| Roku SD/HD/HD-XR/XDS
| Roku
| 2010
| ?
| ?
| NXP PNX8935
|
| [http://support.roku.com/entries/246042-roku-player-open-source-resources|Roku open source]
|-
|}
 

== Digital Video Recorders ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Digital Video Recorders using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Game Consoles ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Game Consoles using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| PlayStation 2
| Sony Computer Entertainment
| 2000
| 32MB
| unknown
| MIPS 64-bit R5900
| [http://en.wikipedia.org/wiki/PlayStation_2 PS2 wikipedia page], [http://playstation2-linux.com/ Playstation-linux community site]
| [http://blackrhino.xrhino.com/main.php?page=home Black Rhino Linux distribution site]
|- align="center"
| PlayStation 3
| Sony Computer Entertainment
| 2006
| 512 MB
| unknown
| CELL broadband engine
| [http://en.wikipedia.org/wiki/PlayStation_3 PS3 wikipedia page]
| [http://en.wikipedia.org/wiki/Linux_for_PlayStation_3 wikipedia PS3-linux page]
|- align="center"
| Didj
| LeapFrog Enterprises
| 2008
| 32MB
| 256MB
| [[LF-1000]]/[[Pollux]]
| [[Didj]]
| [[Leapfrog Source Code]]
|- align="center"
| Leapster Explorer
| LeapFrog Enterprises
| 2010
| 64MB
| 512MB
| [[LF-1000]]/[[Pollux]]
| [[Leapster Explorer]]
| [[Leapfrog Source Code]]
|- align="center"
| LeapPad Explorer
| LeapFrog Enterprises
| 2011
| 64MB
| 2GB
| [[LF-1000]]/[[Pollux]]
| [[Leappad Explorer]]
| [[Leapfrog Source Code]]
|-
|}
 

== Network Attached Storage (NAS) ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Network Attached Storage using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| NSLU2
| [http://www.linksys.com Linksys]
| 2004
| 32MB
| 8MB
| Intel XScale IXP420
|
| http://www.nslu2-linux.org (community site with improved firmwares)
|-
|}
 

== Network Camera ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Network Camera using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| NC353L
| [http://www3.elphel.com Elphel, Inc]
| 2007
| 64MB
| 128MB
| Axis EtraxFS
| http://wiki.elphel.com
| http://sourceforge.net/projects/elphel
|-
|}
 
== Networked Media Players ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Networked Media Players using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| [[Freecom MusicPal | MusicPal]]
| [http://www.freecom.com Freecom]
| 2007
| 32MB
| unknown
| [[Marvell 88W8618]]
|
| http://www.musicpal.info (under Legal Notice]
|-
|}
 

== Still and Video Cameras ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Not Yet Categorized devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| HDR-UX1, HDR-SR1 video cameras
| Sony
| 2006
| ??
| ??
| ARM9
| [http://www.sonystyle.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=10551&storeId=10151&langId=-1&productId=11035608 Sonystyle store listing]
| [http://www.sony.net/Products/Linux/Download/HDR-UX1_HDR-SR1.html Sony Linux Download area]
|-
|}

== Assistive Technology ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Assistive Technology devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
| [http://www.toby-churchill.com/en/content/lightwriters-0 Lightwriter SL38]
| [http://www.toby-churchill.com Toby Churchill Ltd]
| 2004
| 64
| 256
| StrongARM SA-1110
| [http://balloonboard.org/ Developer site]
| [http://husaberg.toby-churchill.com/balloon/ code and sources]
|}
 

== Robots and Smart-companions ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Robots and smart-companions using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| [http://fr.wikipedia.org/wiki/Karotz Karotz]
| [http://en.wikipedia.org/wiki/Mindscape_(software_publisher) Mindscape ] then [http://www.aldebaran-robotics.com/ Aldebaran Robotics]
| 2011
| 64
| 256
| Samsung [http://elinux.org/S3C2440 S3C2440] (ARM920T@400Mhz)
| [http://dev.karotz.com/ Developer site]
|
|}
 

== Network devices ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Network devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! Connectivity
! Notes
! style="width:150px" | Source
! style="width:250px" | Download Area
! Proprietary Drivers or software
|-
| Sheevaplug
| [http://en.wikipedia.org/wiki/Marvell_Technology_Group Marvell]
|
| 512M
| 512M
| Kirkwood 88F6281 (armv5@1.2Ghz)
| Ethernet,usb,sdio
|
|
|
| ?
|}
 

== Modular devices ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Modular devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! Connectivity
! Notes
! style="width:150px" | Source
! style="width:250px" | Download Area
! Proprietary Drivers or software
|-
|- align="center"
| [http://www.buglabs.net/bugbase bugbase 1.2]
| [http://www.buglabs.net Bug Labs]
| 2006
| 128
| 32
| imx31(armv6-vfp@533Mhz)
| USB host(on the von hippel module),micro-sd,usb OTG
| Up to 4 modules(802.15.4,motion detector,screen(320x240),sound card,breakout(von hippel),gps modules availables), [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://bugcommunity.com/wiki/index.php/BUGbase schematics] freely available)
| [http://bssvn.buglabs.net/svn/!tree/10763 Bug svn] 
Based on [http://pokylinux.org/ poky linux], 
uses [http://en.wikipedia.org/wiki/Concierge_OSGi concierge OSGI], 
Can use bug 1.3's [http://cgit.openembedded.net/cgit.cgi/openembedded/tree/conf/machine/bug.conf Basic machine support in openembedded]
| http://www.buglabs.net/downloads
| No(the powervr is not used)
|-
|- align="center"
| [http://www.buglabs.net/bugbase bugbase 1.3]
| [http://www.buglabs.net Bug Labs]
| 2009
| 128
| 32
| imx31(armv6-vfp@533Mhz)
| wifi(libertas_sdio),bluetooth,USB(on the von hippel module),micro-sd,usb OTG
| Up to 4 modules(802.15.4,motion detector,screen(320x240),sound card,breakout(von hippel),gps modules availables), [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://bugcommunity.com/wiki/index.php/BUGbase schematics] freely available)
| [http://bssvn.buglabs.net/svn/!tree/10763 Bug svn] 
Based on [http://pokylinux.org/ poky linux], 
uses [http://en.wikipedia.org/wiki/Concierge_OSGi concierge OSGI], 
[http://cgit.openembedded.net/cgit.cgi/openembedded/tree/conf/machine/bug.conf Basic machine support in openembedded]
| http://www.buglabs.net/downloads
| No(the powervr is not used)
|-
|- align="center"
| [http://www.gumstix.com/store/catalog/product_info.php?cPath=27_33&products_id=227 Overo fire]
| [http://www.gumstix.com Gumstix]
| ?
| 256M
| 256M
| OMAP 3530(also contain POWERVR SGX + C64x)
| wifi(libertas),bluetooth,micro-sd,usb OTG+Host(not shure if USB is on the module or only avaliable on extensions boards)
| expansions board available [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://pubs.gumstix.com/boards/ schematics] freely available but only for extension boards)
| [http://cgit.openembedded.net/cgit.cgi/openembedded/tree/conf/machine/overo.conf Machine support in openembedded]
|
| ?
|-
|- align="center"
| [http://www.gumstix.com/store/catalog/product_info.php?products_id=226 overo air]
| [http://www.gumstix.com Gumstix]
| ?
| 256M
| 256M
| OMAP 3503(no 3D acceleration and no DSP)
| wifi(libertas),bluetooth,micro-sd,usb OTG+Host(not shure if USB is on the module or only avaliable on extensions boards)
| expansions board available [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://pubs.gumstix.com/boards/ schematics] freely available but only for extension boards)
|
|
| ?
|-

|- align="center"
| [http://www.gumstix.com/store/catalog/product_info.php?products_id=228 overo water]
| [http://www.gumstix.com Gumstix]
| ?
| 256M
| 256M
| OMAP 3530(also contain POWERVR SGX + C64x)
| micro-sd,usb OTG+Host(not shure if USB is on the module or only avaliable on extensions boards)
| expansions board available [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://pubs.gumstix.com/boards/ schematics] freely available but only for extension boards)
|
|
| ?
|-

|- align="center"
| [http://www.gumstix.com/store/catalog/product_info.php?products_id=211 Overo earth]
| [http://www.gumstix.com Gumstix]
| ?
| 256M
| 256M
| OMAP 3503(no DSP,no 3d acceleration)
| micro-sd,usb OTG+Host(not shure if USB is on the module or only avaliable on extensions boards)
| expansions board available [http://en.wikipedia.org/wiki/Open_hardware open hardware]([http://pubs.gumstix.com/boards/ schematics] freely available but only for extension boards)
|
|
| ?
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=5969 TNY-A9G20-LPW-I02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2009
| 64M
| 256M
| AT91SAM9G20(400Mhz)
| Micro-SD, RTC (ext. battery), USB OTG (Full Speed), Serial DBGU (Linux console), JTAG, 2 expansion connectors.
| MotherBoard(s) : MOB-TNY-A9XXX-MD2-CXX, Expansion board(s): GPI2 (1W,I2C, SPI, UART), GPS, GSM/GPRS, GSM/HSDPA, WiFi/BlueTooth, KNX/RF, Wireless MBUS, ZigBee...
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=5885 TNY-A9263-C02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2008
| 64M
| 256M
| AT91SAM9263(200Mhz)
| USB OTG (Full Speed), Serial DBGU (Linux console),2 expansion connectors.
| Motherboard(s) : MOB-TNY-A9XXX-MD2-CXX, Expansion board(s): GPI2 (1W,I2C, SPI, UART), GPS, GSM/GPRS, GSM/HSDPA, WiFi/BlueTooth, KNX/RF, Wireless MBUS, ZigBee...
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=6237 TNY-T3730-ULP-C01]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2011
| 256M
| 256M
| OMAP3730(800Mhz)
| Micro-SD, Battery Charger, USB OTG (Full Speed), UART (Linux Console), Jtag, 2 expansion connectors
| No motherboard(s), No expansion board(s).
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=5933 QIL-A9260-C02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2011
| 64M
| 256M
| AT91SAM9260(200Mhz)
| 2Mbits SPI Serial Flash, 64Kbits SPI E2PROM, Micro-SD, RTC, 2 expansion connectors
| Motherboard(s) : MOB-QIL-A9XXX-CXX, No expansion boards.
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=6113 USB-A9G20-LPW-C02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2011
| 64M
| 256M
| AT91SAM9G20(400Mhz)
| Micro-SD, RTC, USB Debug (Full Speed), USB Device FS, 2x USB Host FS, Ethernet 10/100, expansion connector
| Motherboard(s) : N/A, Expansion boards : GPI2 (1W,I2C, SPI, UART), GPS, GSM/GPRS, GSM/HSDPA, WiFi/BlueTooth, KNX/RF, Wireless MBUS, ZigBee...
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=en&pg=5932 USB-A9263-C02]
| [http://www.calao-systems.com/index.php?lng=en calao systems]
| 2009
| 64M
| 256M
| AT91SAM9263(200Mhz)
| Micro-SD, USB Debug (Full Speed), USB Device FS, 2x USB Host FS, Ethernet 10/100, expansion connector
| Motherboard(s) : N/A, No Expansion board(s)
| [http://www.calao-systems.com/repository/ repository]
| [http://www.calao-systems.com/repository/ repository]
| No
|-

|}
 

== Development boards ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Development boards'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! Connectivity
! Notes
! Proprietary Drivers
! style="width:150px" | Source
! style="width:250px" | Download Area
|-
|[http://beagleboard.org/ Beagle Board]
|Texas Instruments
|2008
|256M
|256M
|OMAP3530
|
| lot of informations in the [[BeagleBoard|BeagleBoard wiki page]], 
[http://en.wikipedia.org/wiki/Open_hardware open hardware](schematics freely available)
| The powervr(3d chip) require a proprietary 3d driver for the 3d part
|
|
|-
|[http://beagleboard.org/bone BeagleBone]
|Texas Instruments
|2011
|256MB
|none (MicroSD)
|AM3358
|Ethernet 10/100
|[[BeagleBone|BeagleBone wiki page]], [[BeagleBoard|BeagleBoard wiki page]], 
[http://en.wikipedia.org/wiki/Open_hardware open hardware](schematics freely available)
|The powervr(3d chip) require a proprietary 3d driver for the 3d part
|
|
|-
|[http://pandaboard.org/ Pandaboard]
|Texas Instruments
|2010
|8Gb(x32) x 2ch
|(2G(x32) x4pcs) 2CS/ch
|OMAP4430
|WLAN, Bluetooth, 10/100 Ethernet
| [[PandaBoard|Pandaboard wiki page]],
|
|
|
|-
|[http://www.calao-systems.com/articles.php?lng=fr&pg=6186 Snowball SDK & PDK]
|[http://www.calao-systems.com/ CALAO Systems]
|2011
|1GB
|4GB / 8GB
|ST-Ericsson A9500 Dual Cortex A9 + Mali 400
|WiFi, BlueTooth, GPS, HDMI, CVBS, Ethernet 10/100, Audio In / Out, Micro-SD, Serial Port (Linux console), JTAG, MiPi34, 3D Accelerometer, Magnetometer & Gyrometer, Pressure sensor, 3x expansion connectors
|Expansion Board(s) : MOB-SKY-S9500-AVI-CXX (2x USB OTG HS, LVDS 24Bits, TSC, LED Driver, MiPi DSI, MiPi CSI...), DAB-SKY-S9500-GPI-CXX (CANBus, Modem 2G/3G, 4x Uart, 8x GPIO, 8x ADC)
|[http://www.igloocommunity.org/ Igloo Community]
|[http://www.igloocommunity.org/ Igloo Community]
|[http://www.calao-systems.com/repository/EMBEDDED%20COMPUTERS/SKY-S9500-ULP-XXX/ CALAO Systems Repository]
|-
|-
|[http://www.raspberrypi.org/ US$ 25 Raspberry Pi Computer]
|Raspberry Pi Foundation
|2012
|256
|none (SD Card)
|Broadcom ARM11 (ARM v6) + Videocore GPU
|10/100 Ethernet, HDMI , Composite , Audio, USB Host, GPIO, JTAG , MIPI DSI + CSI
|[[RPi Hub|Phenomenal RPi Hub]]
|[http://www.raspberrypi.org/archives/1839 MPEG-2 and VC-1 Licences]
[https://github.com/raspberrypi/firmware/tree/master/opt/vc OpenGL, OpenMax examples]
|[http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf Schematics]
[http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf CPU Datasheet]
|[http://www.raspberrypi.org/downloads Card Images]
|-
|[http://www.ledato.de/ NanosG20]
|Ledato
|?
|64M/128M
|128M/512M
|
|
|
|
|
|
|}
{| border="1" cellspacing="0" cellpadding="5"
|+'''Development boards'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! style="width:120px" | Processor
! RAM MB
! Flash MB
! style="width:150px" |Video Display
! style="width:250px" |Interfaces
! OS support
! Notes
|-
|[http://www.armkits.com/Product/devkit8000.asp/ DevKit8000]
|[http://www.armkits.com Embest]
|TI OMAP3530
|256M
|256M
|LCD, VGA, DVI-D and S-Video
|UART, USB Host, USB OTG, Ethernet, Audio, SD, Keyboard, JTAG
|Linux2.6.28, WinCE6.0
|[[Devkit8000]] wiki page
|-
|[http://www.armkits.com/Product/devkit8500d.asp/ DevKit8500D/A]
|[http://www.armkits.com Embest]
|style="width:120px" |TI DM3730/AM3715
|512M
|512M
|LCD, VGA, DVI-D and S-Video
|UART, USB Host, USB OTG, Ethernet, Audio, SD, Keyboard, JTAG
|Linux2.6.28, WinCE6.0, Android2.2
|-
|[http://www.armkits.com/product/devkit8600.asp/ DevKit8600]
|[http://www.armkits.com Embest]
|style="width:120px" |TI AM3359
|512M
|512M
|LCD, VGA
|UART, USB Host, USB OTG, Ethernet, CAN, RS485, WiFi/BT, TF, JTAG
|Linux3.1.0, Android2.3, WinCE7
|
|-
|[http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4102 NGW100]
|[http://www.atmel.com Atmel]
|Atmel AVR32: AT32AP7000
|32M
|8M serial + 8M parallel
|"LCD Controller"
|UARTs, USB slave, 2x 100MBit Ethernet, I2C, SPI, JTAG, AC97
|Linux 2.6 [http://www.avr32linux.org http://www.avr32linux.org]
|
|}
 

== Development Boards with FPGA ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Development Boards with FPGA'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
| [http://www.armadeus.com/english/products-processor_boards-apf27.html APF27]
| [http://www.armadeus.com/ Armadeus Systems]
| 2009
| up to 256
| up to 512
| i.MX27 400MHz + Spartan3a
| [http://www.armadeus.com/english/products-processor_boards-apf27.html Company Site]
| [http://www.armadeus.org Developer Site]
|-
|}
 

== Development Boards with MINI2440v2 with 3.5'' ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Development Boards with MINI2440V2'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
[http://www.developmentboard.net/index.php/productdetail/Development+board/ARM9/SAMSUNG/S3C2440/MINI2440v2+with+MegaDisplay+3.5/info/1]
| [http://www.developmentboard.net]
| 2009
| up to 256
| up to 512
| i.MX27 400MHz + Spartan3a
| [http://www.developmentboard.net/index.php/productdetail/Development+board/ARM9/SAMSUNG/S3C2440/MINI2440v2+with+MegaDisplay+3.5/info/1]
| [http://www.developmentboard.net Developer Site]
|-
|}
 

== Not Yet Categorized ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Not Yet Categorized devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
| Indamixx 2 Audio Tablet
| Indamixx
| 2010
| 2 GB
| 150 GB HDD
| Atom N450
| [http://www.indamixx.com/shop-28.html Company website]
| http://www.indamixx.com/shop-60.html
|-
| [http://www.linuxdevices.com/articles/AT4268573160.html HS210]
| [http://www.ericsson.com Ericsson]
| 2000
| 32
| 32
| StrongARM SA-1110
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| Armadillo-500
| [http://www.atmark-techno.com/en Atmark Techno]
| 2007
| 64
| 16
| i.MX31
| [http://www.atmark-techno.com/en/products/armadillo/a500 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser Armadillo Developer Site]
|-
|- align="center"
| Armadillo-300
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a300 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-300 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-9
| [http://www.atmark-techno.com/en Atmark Techno]
| 2004
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a9 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-9 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-240
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a240 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-240 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-230
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 32
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a230 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-230 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-220
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 32
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a220 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-220 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-210
| [http://www.atmark-techno.com/en Atmark Techno]
| 2005
| 32
| 4
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a210 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-210 Armadillo Developer Site]
|-
|- align="center"
| Eddy v2.1 Series
| [http://www.sysbas.com/ SystemBase]
| 2008
| 32
| 8
| ARM9 210MHz
| [http://www.sysbas.com/e-Products/?sNum=400 Company Site]
| [http://embeddedmodule.com/ Eddy Developer Site]
|-
|- align="center"
| Matrix Series
| [http://www.artila.com/ Artila]
| 2006
| 64
| 16
| ARM9 180MHz
| [http://www.artila.com Company Site]
| [http://www.artila.com/p_matrix.html Matrix Site]
|-
|}
 

== Home And Building Automation, Smart Energy ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''HABA & Smart Energy controllers using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=fr&pg=6114 HABA-KNX-EXPLORER-C01]
| [http://www.calao-systems.com CALAO Systems]
| 2011
| 128
| 256
| AT91SAM9G20 (400MHz)
| [http://www.calao-systems.com/repository/HABA%20CONTROLLERS/HABA-KNX-EXPLORER-XXX/ Repository]
| [http://www.calao-systems.com/repository/HABA%20CONTROLLERS/HABA-KNX-EXPLORER-XXX/ Repository]
|-

|- align="center"
| [http://www.calao-systems.com/articles.php?lng=fr&pg=6257 HABA-KNX-LITE-E01]
| [http://www.calao-systems.com CALAO Systems]
| 2012
| 128
| 256
| AT91SAM9G20 (400MHz)
| [http://www.calao-systems.com/repository/HABA%20CONTROLLERS/HABA-KNX-LITE-XXX/ Repository]
| [http://www.calao-systems.com/repository/HABA%20CONTROLLERS/HABA-KNX-LITE-XXX/ Repository]
|-

|}
 

[[Category:Products]]

Android on OMAP

2012-11-27T07:38:19Z

Yclinda666: /* Real hardware */

[[Category: Linux]]
[[Category: OMAP]]
[[Category: Android]]

This page collects information about and guides you through the installation of [http://www.google.de/ Google's] [http://code.google.com/android/ Android] on [http://www.ti.com/ TI's] [http://www.arm.com/ ARM] based [http://focus.ti.com/general/docs/wtbu/wtbusplashcontent.tsp?templateId=6123&contentId=4752 OMAP] [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=11988&contentId=4638&DCMP=WTBU&HQS=Other+OT+omap SoCs].

''Note'': Only small parts of this page should be TI OMAP specific. The basic tasks should also apply to all other ARM926 or higher based SoCs at least able to run a 2.6.23 Linux kernel.

''Note'': If you like this page, please see the [[Android Portal]] on this site for much more information about Android systems programming. See [[Android Porting]] for more links to porting information, articles and tutorials.

''Note'': This article assumes that your are familiar with some basics of embedded ARM Linux. E.g. you should know how to use diff & patch, how to boot your embedded ARM SoC with a recent non-Android Linux, how to use a cross compiler etc.

=Android=

==What is Android (not)==
Android is a software stack for mobile devices that includes an operating system, middleware and key applications. See [http://code.google.com/android/what-is-android.html Google's ''What is Android?''] page and [http://benno.id.au/blog/2007/11/26/what-is-android Benno's ''What is Android?'' and ''What Android isn't''] page for more details about Android.

==Versions==

From time to time Google updates their [http://code.google.com/android/download_previous.html Android releases]. At time of writing this article version ''m5-rc14'' was the recent one. You should always use the latest available version. And make sure you use an Android kernel (patch) for your hardware that matches the file system version (see below).

=Hardware=

==Goldfish==
Android SDK isn't targeted for a special (ARM) SoC. Instead, they use [http://fabrice.bellard.free.fr/qemu/ QEMU] to create a virtual ARM SoC called ''Goldfish''. The virtual ARM SoC boots an (currently 2.6.23, m5-rc14) ARM Linux kernel with Goldfish platform support on your (x86) Windows, MacOS X or Linux host.

This virtual ARM SoC comprises:

* ARM926ej-S CPU
* Thumb support
* MMC
* RTC
* Keyboard
* USB Gadget
* Framebuffer
* TTY driver
* NAND
* Software compiled for ARMv5TEJ instruction set (!) with EABI
* no [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0205g/CIAIIFIB.html TLS] [http://marc.info/?l=linux-omap&m=120384694214686&w=2 yet]

==Real hardware==

Running Android on real hardware, some prerequisites should be fulfilled:

* SoC with ARM926 or higher (e.g. ARM11) (check [http://marc.info/?l=linux-omap&m=120394328104000&w=2 ARM MPCore or ARM Cortex] regarding [[Android_on_OMAP#TLS_issue|TLS issue]])
** Note: ARM920T with ARMv4 instruction set [http://benno.id.au/blog/2007/11/21/android-neo1973 will not work]
* You have already a recent (~2.6.23) Linux kernel with Thumb & MMU & EABI etc support running on your target
* Soc/HW has and Linux kernel supports
** Display/frame buffer (touchscreen would be good but optional). Frame buffer ''has'' to support [[Android_on_OMAP#Page_flipping_frame_buffer|double buffer/page flipping]].
** Keyboard
** USB (optional)
** RTC (optional?)
** Serial console
** Some storage, sufficient for ~64MB, e.g. NFS or USB stick or NAND or NOR or MMC/SDcard etc. NFS would be easiest for development
** Sufficient main memory (SDRAM) >=32MB. While 32MB seems to be enough to start, system will be really slow then. Therefore 32MB is sufficient for ''proof of concept'', but not for a usable system.

'''Known to work HW'''
* [http://marc.info/?l=linux-omap&m=120368832309928&w=2 OMAP1 based boards] (ARM v5 ARM926)
* [http://marc.info/?l=linux-omap&m=120368832309928&w=2 OMAP2 based boards] (ARM v6 ARM11)
* [http://www.mistralsolutions.com/pes-support/support-downloads/omap2530-evm-documentation-a-software.html omap2530evm] 2430OSK is renamed as 2530EVM based on TI's recommendation (ARM v6 ARM1136jf-s)
* [http://euedge.com/blog/2007/12/06/google-android-runs-on-sharp-zaurus-sl-c760/ Sharp Zaurus SL-C760(PXA255)]
* [http://androidzaurus.seesaa.net/article/74237419.html Sharp Zaurus SL-C1000(PXA270)]
* [http://androidzaurus.seesaa.net/article/74237419.html Sharp Zaurus SL-C3000](PXA270)
* [http://www.atmark-techno.com/en/products/armadillo/a500 Armadillo-500] and [http://youtube.com/watch?v=eFxnCaEwL_U Armadillo Panel Computer] (Freescale i.MX31L ARM11)
* OMAP1 based [[OSK]] (OMAP5912 ARM926 with only 32MB SDRAM). Really slow, mainly usable as ''proof of concept''.
* AM/DM 37x based Hardware [http://www.mistralsolutions.com/AM37x_EVM AM/DM37xEVM from Mistral]
[http://groups.google.com/group/android-internals/browse_thread/thread/7028432fa76f57e8/1556f431d3eb1e57?hl=en& Android internals ML], [http://marc.info/?l=linux-omap&m=120741537025066&w=2 OMAP ML] and [http://code.google.com/p/android-on-n8xx/ Android on N810] page. Working Android port for Nokia Internet Tablets can be found [http://guug.org/nit/nitdroid/ here].
* OMAP3430 based Hardware [http://www.omappedia.org/wiki/Android_Getting_Started OMAP3430 based Zoom2 from LogicPD]. DSP acceleration for multimedia use cases as well as WLAN is also supported.
* OMAP3530 based Hardware [http://www.mistralsolutions.com/pes-downloads/software-downloads/android-download-for-tmdsevm3530.html OMAP3EVM from Mistral] (Android runs on ARM Cortex™-A8 Core)
* OMAP3530 based [http://beagleboard.org/ BeagleBoard] using [http://groups.google.com/group/beagleboard/browse_thread/thread/e933982889f0441d# code from Rupesh Gujare].
* OMAP3530 based Hardware [http://www.technexion.com/index.php/tao-3530 TAO-3530 from TechNexion] (Android runs on ARM Cortex™-A8 Core)
* OMAP3530 based [http://www.armkits.com/product/devkit8000.asp DevKit8000] from [http://www.armkits.com Embest]
* OMAP3530 based [http://www.armkits.com/Product/sbc8100.asp SBC8100] Single Board Computer from [http://www.armkits.com Embest]
* OMAP3530 Open-source MID Solution '''K7''' from [http://www.opensourcemid.org OpenSourceMID.org]
* TI DM3730 based [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D] from [http://www.armkits.com Embest]
* TI AM3715 based [http://www.armkits.com/Product/devkit8500d.asp DevKit8500A] from [http://www.armkits.com Embest]
* TI AM3359 based [http://www.armkits.com/product/devkit8600.asp DevKit8600] from [http://www.armkits.com Embest]

'''Known to not work HW'''
* [http://benno.id.au/blog/2007/11/21/android-neo1973 Neo 1973] (ARM920T)

=Compiler=
Getting Android working on real hardware, you need an [http://wiki.debian.org/ArmEabiPort ARM EABI] (good EABI description, ignore the Debian specific stuff) compatible development environment. I.e., your tool chain, your kernel and user space must be compatible to ARM EABI. If you don't like to create your own ARM EABI compatible compiler, linker, library etc. you should use [http://www.codesourcery.com/ CodeSourcery's] [http://www.codesourcery.com/gnu_toolchains/arm/download.html '''ARM GNU/Linux''' tool chain].

''Note'': The naming in the CodeSourcery download section is slightly confusing. You need the '''ARM GNU/Linux''' named tool chain which is indeed an ARM GNU/Linux EABI tool chain with glibc. The ''ARM EABI'' named tool chain there is something normally known as arm-elf tool chain ''without'' any Linux support and without glibc.

=Code=

As mentioned above, the Android SDK contains an emulator where a virtual ARM device runs the Android SW on your host PC. The Linux ''kernel'' used in this emulator is available in source code. In contrast, the user space ''file system'' (applications) is currently only available as binary as part of the SDK.

To get Android running on real HW, currently you need both, matching SDK and kernel source. You need kernel source to extract Android specific patches to add them to your SoC specific kernel. And SDK to get Android user space file system binaries. While getting Android kernel patches is somehow straight forward, extracting user space file system with Android applications in it is a little bit tricky.

==Kernel==

On [http://code.google.com/p/android/downloads/list Android project page] the source code of the kernel is available. From full kernel tree with Android modifications included you can extract patches. With this, you have to extract the Android specific patches yourself from the complete kernel tree, use already extracted patches or get kernel patches by git.

===Patch extraction===

See third paragraph of [http://benno.id.au/blog/2007/11/21/android-neo1973 Benno's Android on NEO 1973 article].

* Download matching version (e.g. m5-rc14) of [http://code.google.com/p/android/downloads/list Android kernel source]. Besides complete kernel source this will contain Android specific changes.
* Download matching (e.g. 2.6.23) stock Linux kernel (or use e.g. git to check out stock kernel version) and diff both kernels to get Android related changes.
* As we want to run Android on real hardware, you can throw away all QEMU and Goldfish related changes. If you don't want to use [http://www.yaffs.net/ yaffs2] file system (e.g. cause you don't have NAND or have it already in your tree), throw away yaffs2 related changes as well. If you use m5-rc14 (or higher?) you can remove [[Android_on_OMAP#OpenBinder|OpenBinder related files]] (/driver/binder) as well. [[Android_on_OMAP#Kernel_patch|Result]] should be a generic, no ARM or OMAP specific Android patch you can apply to your (e.g. 2.6.23) kernel for your ARM based SoC.

''Note'': There seems to be [http://marc.info/?l=linux-omap&m=120384694214686&w=2 some effort] to make Android kernel patches available in a easier usable format.

===Extracted patches===

At some locations there are ready made patches available. The advantage of this is that you don't have to extract the patches yourself. The disadvantage is that you can't always be sure that they contain everything you need and that they match your SDK/user space file system ([[Android_on_OMAP#Extracted_binaries|see below]]) version.

* [http://benno.id.au/android/android-noqemu-nogoldfish-noyaffs2.diff Benno's no Qemu no goldfish no yaffs2 patch], as of date of Benno's article most probably based on m3-rc20.

''Note'': Some guys on OMAP mailing list have Android patches extracted (currently from m5-rc14) and [http://marc.info/?l=linux-omap&m=120401478515308&w=2 are willing to share them]. Unfortunately they don't have any permanent web storage yet. If you have and like to help community with providing some web space, contact [http://vger.kernel.org/vger-lists.html#linux-omap OMAP list].

===Git patches===

There are Android kernel patches available using [http://git.android.com/?p=kernel.git;a=shortlog;h=android Android's git] repository. But have a look to [http://marc.info/?l=linux-omap&m=120716474803274&w=2 Brian's notes] regarding this.

==File System==

Getting user space file system binaries running in emulator extracted is slightly tricky. We have to extract the binaries as currently access to source code have only [http://marc.info/?l=linux-omap&m=120368832309928&w=2 Google itself and eventually WindRiver].

Again, there are two ways to get user space binaries: Extracting them your self or taking already extracted ones.

===Binary extraction===

The user space applications compiled for ARMv5 EABI are part of the Android SDK in ''system.img'' and ''userdata.img'' in ''tools/lib/images'' directory of SDK.

* [http://code.google.com/android/download_list.html Download SDK] and unzip it
* system.img and userdata.img are [http://www.yaffs.net/ yaffs2] images. There is no way yet to mount them directly on a host to extract their content. An [http://lists.aleph1.co.uk/lurker/message/20080218.222359.6cc4bd2e.en.html ''unyaffs''] tool is missing, so the only way to get the content is to start the emulator and extract the contents from running emulator.
Recently there is an unyaffs available [http://code.google.com/p/unyaffs/]

* As file system in emulator as no ''cp'' or ''tar'' command, we use a statically linked [http://www.busybox.net/ BusyBox] cross compiled for ARM and use it inside emulator (get it from [http://benno.id.au/blog/2007/11/14/android-busybox Benno] or build it your own with above tool chain).
* Set path to emulator tools

export PATH=${PATH}:<path_to>/android-sdk_m5-rc14_linux-x86/tools

* Create an empty SDcard (image)

[http://code.google.com/android/reference/othertools.html#mksdcard mksdcard] -l card 100M card.img

* Start emulator

[http://code.google.com/android/reference/emulator.html emulator] -sdcard card.img -console -debug-kernel

* You should now see the SDK kernel booting and emulator starting. Wait until the emulator is ready, then send the ARM busybox from the host into the simulated environment:

[http://code.google.com/android/reference/adb.html adb] -d 1 push busybox /data/busybox

* Inside emulation, set tar (and bzip2) links to busybox, tar ''/system'' and ''/data'' directories to sdcard.
* Shutdown emulator, mount card.img

mount -o loop card.img mnt/

and get the images of system and user data.

* If you look at the extracted size of the userdata image, the extracted one is bigger than the original userdata.img. So by the runtime extraction we get some temporary junk in it. For this, untar extracted userdata and remove a least some of the unnecessary stuff:
** Remove all content of ''data/dalvik-cache/''. It holds the decompressed files from the apk packages.
** Remove the static busybox image. We only needed it for extraction and don't need it any more.

''Note'': Anybody likes to hack this [http://lists.aleph1.co.uk/lurker/message/20080218.222359.6cc4bd2e.en.html ''unyaffs''] tool? Then the system.img and userdata.img extraction would be a lot easier.

''Note'': A user reports that he doesn't use the extracted data directory at all. He simply mounts a tempfs to /data as it seems that Android runtime creates most (all?) of the necessary files in /data itself at runtime.

===Extracted binaries===

At some locations there are ready made binaries available. The advantage of this is that you don't have to extract the binaries yourself. The disadvantage is that you can't always be sure that the images contain everything you need and that the images match your kernel patch ([[Android_on_OMAP#Extracted_patches|see above]]) version.

* [http://benno.id.au/blog/2007/11/14/android-filesystems Android file system images], as of date of Benno's article most probably based on m3-rc20.

''Note'': Some guys on OMAP mailing list have Android binaries extracted (currently from m5-rc14) and [http://marc.info/?l=linux-omap&m=120401478515308&w=2 are willing to share them]. Unfortunately they don't have any permanent web storage yet (~30MB). If you have and like to help community with providing some web space, contact [http://vger.kernel.org/vger-lists.html#linux-omap OMAP list].

=Target=

This section describes how to configure the software (kernel, file system) to run Android on real hardware target. Before you do this Android specific steps, you should make sure that everything works without any Android specifics. I.e. make sure that the (EABI) kernel boots, you can access all file systems (e.g. NFS or MMC or NOR or NAND etc.) and necessary drivers (e.g. keyboard, touchscreen etc.). Do this with booting into your normal (EABI) file system you always use. We later switch to Android file system then.

==Kernel configuration==

Make sure your kernel boots normally on your board. Then enable some Android specific configuration (needs [[Android_on_OMAP#Kernel|kernel patch extracted above]]) and make sure that your kernel still boots (with your standard file system).

''Note'': Some of these settings are valid only for m5-rc14 and newer (?) (Binder config, /sys/android_power output) as it changed from older versions to m5-rc14.

'''EABI'''

CONFIG_AEABI=y
# CONFIG_OABI_COMPAT is not set

'''THUMB'''

CONFIG_ARM_THUMB=y

'''Android drivers'''

#
# Android
#
# CONFIG_ANDROID_GADGET is not set
# CONFIG_ANDROID_RAM_CONSOLE is not set
CONFIG_ANDROID_POWER=y
CONFIG_ANDROID_POWER_STAT=y
CONFIG_ANDROID_LOGGER=y
# CONFIG_ANDROID_TIMED_GPIO is not set
CONFIG_ANDROID_BINDER_IPC=y
#AshMem
CONFIG_ASHMEM=y

After you successfully booted the kernel with configuration above (and m5-rc14 kernel patch), make sure you have following /sys files:

/sys/android_power/acquire_partial_wake_lock
/sys/android_power/acquire_full_wake_lock
/sys/android_power/last_user_activity
/sys/android_power/request_sleep
/sys/android_power/acquire_full_wake_lock
/sys/android_power/acquire_partial_wake_lock
/sys/android_power/battery_level
/sys/android_power/battery_level_low
/sys/android_power/battery_level_raw
/sys/android_power/battery_level_scale
/sys/android_power/battery_low_level
/sys/android_power/battery_shutdown_level
/sys/android_power/charging_state
/sys/android_power/release_wake_lock
/sys/android_power/request_state
/sys/android_power/state

==File system configuration==

We now switch to Android file system extracted above. This should be established on a device with enough space (> ~64MB) and which is accessible on your target. Options are e.g. NFS, NOR or NAND file system, hard disk or USB storage. In a first step it is sufficient if you are able to manually mount it from your (temporary) standard root file system. In a second step it is an option to use it directly as root fs.

The Android file system we establish here on one of the the storage from above is built from four parts:

* Content of system data image extracted above
* Content of user data image extracted above (make sure temporary files are removed)
* Content of Android ram disk image
* Device file system

To create Android file system, take (empty) storage you selected and start with ram disk:

Android ram disk image can be found as ramdisk.img in tools/lib/images of Android SDK. This is a gziped cpio archive:

cp ramdisk.img ramdisk.gz
gunzip ramdisk.gz
cd target_fs
cpio -iv < ../ramdisk

Result of this should be an root file system tree with:

data
dev
etc
init
proc
sbin
sys
system
tmp
var

Directories data, dev and system are empty. Extract content of extracted user data image to /data and system image to /system directories. E.g.

tar xvfj ../system_m5_rc14.tar.bz2 system/
tar xvfj ../userdata_m5_rc14.tar.bz2 data/

Note: This depends on how you named and stored extracted user data and system image above.

Last step is to create some device nodes in /dev you need for running from this Android file system. There are several options how to establish this. One option is to extract device file system from running Android emulator as well. Second option is to use the same device file system you normally use in your standard file system. Choose the easiest way. If you did this, make sure you have Android specific device nodes with correct major/minor numbers as well.

Note: Copying device nodes the best way is to tar them at source and untar them then at target. For device nodes, cp command isn't the best option due to special device node format.

==Start up==

Starting Android using the file system and kernel created above, there are three ways:

* Directly boot from Android kernel into the Android file system. I.e. let the Android kernel directly start init etc. from Android file system.
* First boot from Android kernel into your standard file system. Then "manually" switch over to Android file system and start Android. This "manual" switch can be done using some scripts.
* The third way is a mix of the first two ways: Boot into a standard non-Android file system, then switch over to Android but there directly execute init as it would be done by root file system.

===Android root file system===

There are several ways to directly start Android from (root) file system created above:

* Directly point your kernel to /init in Android file system. Then kernel will use Android's init as init program and execute it without any manual interaction
* Use Android's shell and give kernel /system/bin/sh as init program. Then start Android's init manually (/init&) .

===Start via scripts===

This section describes the second way to start Android. First boot into your normal file system and then switch to Android file system and start Android "manually", i.e. with help of some scripts. From the initial description of this method, this way is also known as the a.sh way (search for a.sh). The scripts used for this depend on your local configuration. You can take below scripts as example and adapt them for your local use.

These example scripts are used to first boot into standard root file system (e.g. JFFS2 in NOR) and then to mount (/mnt/usb) and start Android located on an ext2 formatted USB stick.

start_android.sh in standard root file system:

#!/bin/sh -x
echo "Starting Android..."
fsck.ext2 -pv /dev/sda1
mount /dev/sda1 /mnt/usb
rm -f /mnt/usb/tmp/*
umount /proc
umount /sys
mount -t proc proc /mnt/usb/proc
mount -t sysfs sysfs /mnt/usb/sys
umask 000
chroot /mnt/usb/a.sh

a.sh to start Android at Android file system:

#!/system/bin/sh -x

export PATH=/sbin:/system/sbin:/system/bin:$PATH
export LD_LIBRARY_PATH=/system/lib
export ANDROID_ROOT=/system
export ANDROID_ASSETS=/system/app
export ANDROID_DATA=/data
export EXTERNAL_STORAGE=/sdcard
export DRM_CONTENT=/data/drm/content

/system/bin/app_process -Xzygote /system/bin --zygote &
/system/bin/dbus-daemon --system &
runtime &
/system/bin/sh

Notes:

* fsck.ext2 -pv /dev/sda1: Make sure ext2 file system is clean. ext2 doesn't like unclean switch off while debugging Android start up ;)
* rm -f /mnt/usb/tmp/*: Remove Android temporary files before starting Android.
* mount proc and mount sys: This has to be done somewhere. Depending on your scripts, you can do it in a.sh as well.
* runtime: For debugging use here /system/bin/strace -f -ff -tt -s 200 runtime&.
* Starting runtime in background (&) and calling /system/bin/sh afterwards is optional. It gives you the option to have a shell at Android startup to e.g. observe /proc/meminfo, top or ps. Only useful if strace isn't enabled or not so noisy ;)

===Start init via scripts===

This third way is a mixture of the first two ways: Boot into a standard non-Android file system, then switch over to Android but there directly execute init as it would be done by root file system.

From standard non-Android file system this switch can look like:

mount /dev/sda1 /mnt/usb
rm -f /mnt/usb/tmp/*
umask 000
chroot /mnt/usb /init

==Debugging==

* Strace: The main debugging help currently known is [http://benno.id.au/blog/2007/11/18/android-runtime-strace strace]. Again, a statically linked one is used.
** You should invoke strace with [http://marc.info/?l=linux-omap&m=120410568226398&w=2 ''-f -ff -tt -s 200''] options, e.g.

strace -f -ff -tt -s 200 /system/bin/runtime

=FAQ=

===Kernel patch===

'''Q''': Above section about [[Android_on_OMAP#Patch_extraction|kernel patch extraction]] mentioned that not all changes in Android kernel compared to stock kernel are needed for Android on real HW (e.g. Goldfish, QEMU and YAFFS2 related changes). What exactly do I need?

'''A''': Regarding m5-rc14 and kernel 2.6.23 the (changed) files below seem to be sufficient to run Android on real HW:

arch/arm/Kconfig
arch/arm/kernel/process.c
arch/arm/kernel/signal.c
drivers/android/alarm.c
drivers/android/android_gadget.c
drivers/android/android_kernel_debug.c
drivers/android/android_kernel_debug.h
drivers/android/binder.c
drivers/android/Kconfig
drivers/android/logger.c
drivers/android/Makefile
drivers/android/power.c
drivers/android/ram_console.c
drivers/android/timed_gpio.c
drivers/input/evdev.c
drivers/Kconfig
drivers/misc/Kconfig
drivers/misc/lowmemorykiller/lowmemorykiller.c
drivers/misc/lowmemorykiller/Makefile
drivers/misc/Makefile
fs/inotify_user.c
include/linux/android_alarm.h
include/linux/android_gadget.h
include/linux/android_power.h
include/linux/android_timed_gpio.h
include/linux/binder_module.h
include/linux/binder_type_constants.h
include/linux/logger.h
kernel/power/process.c
drivers/Makefile

Kernel patches to run android on n8x0 [http://guug.org/nit/nitdroid/ here].

===OpenBinder===

'''Q''': When I extract the kernel patch, I additionally get a ''drivers/binder/'' directory. Why isn't it listed/needed above?

'''A''': The ''drivers/binder/'' directory seems to contain [http://www.newmobilecomputing.com/story/13674/Introduction-to-OpenBinder-and-Interview-with-Dianne-Hackborn/ OpenBinder]. In Android m5-rc14 this seems to be [http://marc.info/?l=linux-omap&m=120417098706141&w=2 replaced] by ''drivers/android/binder.c''. Therefore we don't need ''drivers/binder/'' with m5-rc14 any more. Note that new binder.c in drivers/android is configured with CONFIG_ANDROID_BINDER_IPC, while drivers/binder was configured by (obsolete) CONFIG_BINDER.

===Devices nodes===

'''Q''': Do I need special devices nodes? Which?

'''A''': [[Android_on_OMAP#File_System|Above]] we only extracted system and userdata image. If you like, you can extract /dev entries as well. However, starting Android's ''runtime'' under [[Android_on_OMAP#Debugging|strace]] control should give you a list which devices will be opened. Besides the standard ones you will need (incomplete?):

crw-rw-rw- 1 root root 10, x Jan 1 00:00 binder
crw-rw-rw- 1 root root 10, x Jan 1 00:00 log/radio
crw-rw-rw- 1 root root 10, x Jan 1 00:00 log/events
crw-rw-rw- 1 root root 10, x Jan 1 00:00 log/main
crw-rw-rw- 1 root root 10, x Jan 1 00:00 alarm
crw-rw-rw- 1 root root 10, x Jan 1 00:00 eac
crw-rw-rw- 1 root root 29, 0 Jan 1 00:00 graphics/fb0
more ?

===/dev/xxx minor numbers===

'''Q''': Which minor number will I need for /dev/xxx entries above? E.g. for /dev/binder?

'''A''': The major number 10 (major number for "misc" devices) above are for new drivers of m5-rc14. The minor numbers [http://marc.info/?l=linux-omap&m=120417584110733&w=2 would be as given] by cat /proc/misc. They are somehow board dependent and may change.

E.g. in m5-rc14 emulator you may get:

# cat /proc/misc
58 binder
59 log_radio
60 log_events
61 log_main
62 alarm
1 psaux
63 eac

With [[Android_on_OMAP#Patch_extraction|kernel patch on real HW]] you may get:

# cat /proc/misc
59 binder
60 log_radio
61 log_events
62 log_main
63 alarm

===/dev/fb0===

'''Q''': I have /dev/fb0, is this correct?

'''A''': With m5-rc14 [http://androidzaurus.seesaa.net/article/84934031.html Google switched frame buffer interface] to /dev/graphics/fb0. So you need:

crw-rw-rw- 1 root root 29, 0 Jan 1 00:00 /dev/graphics/fb0

===Blank screen===

'''Q''': I did all steps like above, [[Android_on_OMAP#Debugging|strace]] output doesn't show any obvious errors, but if I start Android calling ''runtime'' I simply get a blank screen. No output (no ANDROID string, no red cycle eye, nothing), just blank screen. As when the frame buffer screen saver starts after ~10min. I use m5-rc14.

'''A''': With m5-rc14 the frame buffer handling changed. You now need a frame buffer driver which [http://androidzaurus.seesaa.net/article/87808061.html supports double buffer/page flipping]. Observe the output of strace. If you get:

...
writev(4, [{"\4", 1}, {"SurfaceFlinger\", 15}, {"Client API: OpenGL ES\", 22}], 3) = 38
open("/dev/graphics/fb0", O_RDWR|O_LARGEFILE) = 21
ioctl(21, FBIOGET_FSCREENINFO, 0x43145d9c) = 0
ioctl(21, FBIOGET_VSCREENINFO, 0x43145cfc) = 0
ioctl(21, FBIOPUT_VSCREENINFO, 0x43145cfc) = 0
writev(4, [{"\5", 1}, {"EGLDisplaySurface\", 18}, '''{"page flipping not supported (yres_virtual=640, requested=1280)\", 63}], 3)''' = 82
ioctl(21, FBIOGET_VSCREENINFO, 0x43145cfc) = 0
...

your frame buffer driver doesn't support page flipping.

''Note'': For above output, strace has to be invoked with [http://marc.info/?l=linux-omap&m=120410568226398&w=2 ''-f -ff -tt -s 200''] options, else you wouldn't see this.

===Page flipping frame buffer===

'''Q''': Okay, I get this ''page flipping not supported'' message above and have a blank screen. So my frame buffer driver doesn't support double buffer/page flipping. What do I have to change in frame buffer driver to support double buffer/page flipping?

'''A''': This depends on frame buffer driver.
* For OMAP you can try following hack:

Index: linux-omap-2_6_23/drivers/video/omap/omapfb_main.c
===================================================================
--- linux-omap-2_6_23.orig/drivers/video/omap/omapfb_main.c
+++ linux-omap-2_6_23/drivers/video/omap/omapfb_main.c
@@ -168,7 +168,7 @@ static int ctrl_init(struct omapfb_devic
/* 12 bpp is packed in 16 bits */
if (bpp == 12)
bpp = 16;
- def_size = def_vxres * def_vyres * bpp / 8;
+ def_size = def_vxres * def_vyres * 2 * bpp / 8;
fbdev->mem_desc.region_cnt = 1;
fbdev->mem_desc.region[0].size = PAGE_ALIGN(def_size);
}
@@ -415,6 +415,7 @@ static void set_fb_fix(struct fb_info *f
}
fix->accel = FB_ACCEL_OMAP1610;
fix->line_length = var->xres_virtual * bpp / 8;
+ fix->ypanstep = 1;
}

static int set_color_mode(struct omapfb_plane_struct *plane,
@@ -1471,7 +1472,7 @@ static int fbinfo_init(struct omapfb_dev
var->xres = def_vxres;
var->yres = def_vyres;
var->xres_virtual = def_vxres;
- var->yres_virtual = def_vyres;
+ var->yres_virtual = def_vyres * 2;
var->rotate = def_rotate;
var->bits_per_pixel = fbdev->panel->bpp;

(anybody with clean patch? ->[[Android_on_OMAP#Contact|contact]])

* For the new omap2 dss driver (based on 2.6.29), please try following hack:

diff --git a/drivers/video/omap2/omapfb/omapfb-main.c b/drivers/video/omap2/omapfb/omapfb-main.c
index 1042c3b..8f87b78 100644
--- a/drivers/video/omap2/omapfb/omapfb-main.c
+++ b/drivers/video/omap2/omapfb/omapfb-main.c
@@ -1315,7 +1315,7 @@ static int omapfb_alloc_fbmem_display(struct fb_info *fbi, unsigned long size,
oldw, oldh, w, h);
}

- size = w * h * bytespp;
+ size = w * h * bytespp * 2;
}

if (!size)
@@ -1648,7 +1648,7 @@ int omapfb_fb_init(struct omapfb2_device *fbdev, struct fb_info *fbi)
}

var->xres_virtual = var->xres;
- var->yres_virtual = var->yres;
+ var->yres_virtual = var->yres * 2;

if (!var->bits_per_pixel) {
switch (display->get_recommended_bpp(display)) {
@@ -1669,7 +1669,7 @@ int omapfb_fb_init(struct omapfb2_device *fbdev, struct fb_info *fbi)
var->xres = 320;
var->yres = 240;
var->xres_virtual = var->xres;
- var->yres_virtual = var->yres;
+ var->yres_virtual = var->yres * 2;
if (!var->bits_per_pixel)
var->bits_per_pixel = 16;
}

* For Zaurus/pxafb have a look to following [http://androidzaurus.seesaa.net/article/87973048.html solution]. See [http://www.oesf.org/forum/index.php?s=b33968d11c595adb9ac146a6d4c59366&showtopic=25517&st=15&start=15 OESF] as well.

===Android start crashes===

'''Q''': When I start Android like described above, xxx strangely crashes and/or I get strange error messages. I don't use recent (m5-rc14) Android.

'''A''': Make sure that you use kernel patch and file system from most [http://marc.info/?l=linux-omap&m=120392877715554&w=2 recent Android] release (currently m5-rc14). [http://marc.info/?l=linux-omap&m=120400983008672&w=2 Don't mix] kernel patch and file system from different versions.

===Power management===

'''Q''': I did anything like described above. Systems starts properly, I get Android home screen. But then, system goes to suspend mode and never wakes up. Even if I only use [http://marc.info/?l=linux-omap&m=120470400929434&w=2 fake Android power management].

'''A''': unknown yet :( There is some guessing and some workaround.

* Some [http://androidzaurus.seesaa.net/article/87973048.html#comment guess from androidzaurus].

* Workaround reported from [http://marc.info/?l=linux-omap&m=120538179321533&w=2 Anil]:

Adding keypad support (e.g. on Mistral's OSK2530EVM, OMAP2430 based platform) and "waking" Android while it switches to suspend wakes it again. When Android goes into power saving mode, it prints the following messages

android_power_suspend: enter suspend
android_power_suspend: exit suspend, ret = -38
android_power_suspend: pm_suspend returned with no event

And then, if the UP or DOWN key is pressed on the HW keypad, the system comes back to normal mode and resumes activity with the below given console messages

android_power_wakeup 2->0 at 447592867845
active wake lock PowerManagerService
active wake lock KeyEvents
android_power_suspend: done

===TLS issue===

'''Q''': What is this TLS issue?

'''A''': Some newer ARM processors support [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0205g/CIAIIFIB.html TLS] in hardware. With current (m5-rc14) Android release this [http://marc.info/?l=linux-omap&m=120384694214686&w=2 isn't supported] yet.

===TLS issue and processors===

'''Q''': Which processors have this TLS issue?

'''A''': [http://marc.info/?l=linux-omap&m=120394328804005&w=2 ARMv6K (MPCORE) and ARMv7 (Cortex)]. Regarding OMAP, this is OMAP3 (Cortex). OMAP1 (ARM9) and OMAP2 (ARM11) don't have this issue.

===TLS issue workaround===

'''Q''': I'd like to use (m5-rc14) Android on processors with TLS issue, what can I do?

'''A''': On older ARM's the TLS register is emulated (trapped by the kernel) and on newer ARM's the register actually exists. Android (at least the version for Goldfish) is compiled with the assumption that the TLS
register is emulated and thus expects the kernel to trap it. A non-user defined config option called HAS_TLS_REG is set based on the processor version that is configured which controls if the trap code gets added to the kernel. So to get around the TLS issue, you will need to force the option ON even if the processor supports the TLS register. You can force it on for e.g. OMAP3 by doing the following. However, once source is available,
you really don't want to do this as it does cause a performance hit.

diff -Naur 2.6_kernel-orig/arch/arm/mm/Kconfig 2.6_kernel-android/arch/arm/mm/Kconfig
--- 2.6_kernel-orig/arch/arm/mm/Kconfig 2007-11-20 12:09:42.000000000-0600
+++ 2.6_kernel-new/arch/arm/mm/Kconfig 2007-12-08 22:23:04.000000000-0600
@@ -675,7 +675,7 @@
config HAS_TLS_REG
bool
depends on !TLS_REG_EMUL
- default y if SMP || CPU_32v7
+ default y if SMP || CPU_32v7 && !ARCH_OMAP
help
This selects support for the CP15 thread register.
It is defined to be available on some ARMv6 processors (including

(Thanks to Keith Deacon!)

''Note'': A [http://marc.info/?l=linux-omap&m=120400327301855&w=2 user report] wasn't quite successful regarding this.

===Red cycle eye runtime speed===

'''Q''': The red cycle eye runs very fast on my board, and the system_server take almost 100% CPU

'''A''': [http://marc.info/?l=linux-omap&m=120399654528241&w=2 This is usually indicative] of lack of vsync/pageflip in the fb driver. The surfaceflinger believes it will be limited by the vsync rate and the startup animation depends on that.

===File not found===

'''Q''': At Android start up I get some ''File not found ...'' error messages like:

Prepping: /system/app/AlarmClock.apk:/system/app/AlarmProvider.apk:...
File not found: /system/app/AlarmClock.apk
File not found: /system/app/AlarmProvider.apk
File not found: /system/app/Anagrams.apk
...
File not found: /system/app/Vending.apk
File not found: /system/app/VoiceDialer.apk
File not found: /system/app/Voicemail.apk
File not found: /system/app/YouTube.apk
Prep complete

Do I have to care about these?

'''A''': No, it doesn't seem so. See [http://benno.id.au/blog/2007/11/18/android-framework-startup Benno's blog], section Manual startup.

===Limited main memory===

'''Q''': I have only limited main memory (SDRAM, e.g. 32MB). The system basically starts, but it is really sssllllooooowwww, slightly unusable. More or less only a proof of concept. Can I do anything to use Android even on systems with limited main memory?

'''A''': Try to enable lowmemorykiller:

drivers/misc/lowmemorykiller/lowmemorykiller.c

For this, in kernel enable

CONFIG_LOW_MEMORY_KILLER=y

in Device drivers -> Misc devices. At Android startup this then results in messages like

...
send sigkill to 920 (app_process), adj 1, size 1838
...

===Some buttons work, some not===

'''Q''': Some buttons work, some buttons don't work ... wrong mapping. How to see what key codes certain buttons are bound? And how to edit the mapping in Android?

'''A''': From [http://marc.info/?l=linux-omap&m=120749091514894&w=2 Brian at OMAP ML]:

''There's a brute force approach to sorting out input events: run getevent on the emulator and on the target hardware and compare the results. It's in /system/bin. Keylayouts live in /system/usr/keylayout/*.kl and are used to translate from the raw input event codes to android keycodes. Keymaps live in /system/user/keychars/*.kcm.bin (undocumented binary format right now, sorry) and are used to describe how the key events and modifiers and such are related.''

===Filesystem, JFFS2 and SIGSEGV===

'''Q''': Which file system should I use to store Android user files? Is JFFS2 okay? I use JFFS2 and get SIGSEGVs. What can I do?

'''A''': Don't use JFFS2 as file system for Android. [http://groups.google.com/group/android-internals/browse_thread/thread/7028432fa76f57e8/71709fc4adcb2ddd Android does not support JFFS]. Use an ext2/3 formatted medium. Or use YAFFS2 if you use a NAND device (as emulator does).

===Using JFFS2===

'''Q''': Okay, I understand from above that Android doesn't support JFFS2. But, maybe there is a hack to try?

'''A''': You could try what [http://marc.info/?l=linux-omap&m=120946006920397&w=2 Brian] reports:

''Using JFFS2, what you're might seeing here is the property service in init failing to create and mmap it's arena, which it tries to do in /, which in emulator world is initramfs. The android init/boot model is a little different in that android don't pivot over to a root filesystem, android mounts the system, data, etc partitions under the ramfs on /.''

''You might be able to hack around this by editing the string "/system_properties" to "/tmp/em_properties" or something like that, assuming you have tmpfs mounted on /tmp.''

===Nokia N8x0 and Android SDK===

'''Q''': I'd like to run [[Android_on_OMAP#Screenshots|Android on Nokia N8x0]] ([http://groups.google.com/group/android-internals/browse_thread/thread/7028432fa76f57e8/1556f431d3eb1e57 link 1], [http://code.google.com/p/android-on-n8xx/ link 2]). Which [http://code.google.com/p/android/downloads/list Android SDK] should I use? Can I use m5-rc14/15 SDK?

'''A''': You ''have'' to use m3 ''user space''. This works well with m5-rc14/15 kernel patches. So best combination is to use m3 user space with m5 kernel.

m5 user space will '''not''' work, because it needs [[Android_on_OMAP#Page_flipping_frame_buffer|page flipping frame buffer]] and N8x0 fb driver doesn't support this.

For working android port: [http://guug.org/nit/nitdroid/ "Nitdroid"]

===N8x0 and recent OMAP git kernel===
'''Q''': I'd like to use recent OMAP git kernel on N8x0. What do I need to run git kernel on N8x0?

'''A''': Have a look to Tony's [http://www.muru.com/linux/n8x0/ booting nokia N8x0 with current OMAP git kernel].

===N810 keys===

'''Q''': How do I get the N810 keyboard to work with Android?

'''A''': Try the following [http://groups.google.com/group/android-internals/msg/04f842aa0710932a changes] to get most of N810 keys working with Android, except Fn and the numbers:

Just update one file: /system/usr/keylayout/qwerty.kl

-key 158 BACK WAKE_DROPPED
+key 1 BACK WAKE_DROPPED
key 230 SOFT_RIGHT WAKE
key 60 SOFT_RIGHT WAKE
key 107 ENDCALL WAKE_DROPPED
key 62 ENDCALL WAKE_DROPPED
-key 229 SOFT_LEFT WAKE_DROPPED
+key 62 SOFT_LEFT WAKE_DROPPED
key 59 SOFT_LEFT WAKE_DROPPED
key 139 SOFT_LEFT WAKE_DROPPED
key 228 POUND
key 227 STAR
key 231 CALL WAKE_DROPPED
key 61 CALL WAKE_DROPPED
-key 232 DPAD_CENTER WAKE_DROPPED
+key 96 DPAD_CENTER WAKE_DROPPED
key 108 DPAD_DOWN WAKE_DROPPED
key 103 DPAD_UP WAKE_DROPPED
-key 102 HOME WAKE
+key 63 HOME WAKE
key 105 DPAD_LEFT WAKE_DROPPED
key 106 DPAD_RIGHT WAKE_DROPPED
-key 115 VOLUME_UP
-key 114 VOLUME_DOWN
+key 65 VOLUME_UP
+key 66 VOLUME_DOWN

===N8x0 touchscreen===

'''Q''': Is there any way to get N8x0 touchscreen working with Android?

'''A''': Yes. There is a [http://groups.google.com/group/android-internals/msg/7c6ff76e0381e95a patch] you can apply to a nokia+android patched 2.6.21 kernel and you should
have a working touchscreen.

=== Nokia770 support ===

NITdroid project provide some images to flash on your n700, see tutorial and demo at :

http://www.newlc.com/en/nitdroid-demo-gnulinux-android-nokia-n770-0

===HW interfaces support===

'''Q''': Which hardware interfaces or kernel drivers does current Android support?

'''A''': See discussion on [http://marc.info/?l=linux-omap&m=120946406828608&w=2 OMAP ML]:

> I was able to add support for the keypad, touch and network in Android,
> however the interfaces like GPS, Accelerometer, vibrator, hardware 3D
> acceleration, battery etc. are not integrated with Android right now. I
> would appreciate if you could throw some light on these open issues. How
> exactly can these interfaces be integrated with Android?

We're trying to use the standard kernel/driver interfaces when possible,
but for things that may have a good deal of variation in implementation,
we're looking to provide a very thin "hardware interface library" layer
to adapt between the bottom of the userspace stack and the drivers or
whatnot for specific hardware platforms.

We'll continue to adopt standardized kernel solutions as they become
available -- We're now using the power supply framework in 2.6.24 for
monitoring battery/charge state (post M5 SDK -- it'll be in the next
release), for example.

=Links=

* [http://guug.org/nit/nitdroid/ "Nitdroid" -project. Sources and precompiled (ready to use) binaries for Nokia Internet Tablets.]
* [http://www.mistralsolutions.com/android Mistrals' Android Competency Center]
* [http://www.omappedia.com/wiki/Android_Getting_Started Android on the OMAP34x Zoom Mobile Development Kit]
* [http://code.google.com/android/ Android] homepage
* [http://www.e-consystems.com/5MP_hdcamera_omap.asp Android Camera] Application using V4L2 APIs, on OMAP EVM board
* [http://benno.id.au/blog/ Bennos blog] with lot of reverse engineering info about Android
* [http://androidzaurus.seesaa.net/article/74237419.html Android on Zaurus]
* [http://www.kandroid.org Korea Android Community]
''Note'':Connect this site using http://www.google.com/translate website.
* Linux devices about [http://www.linuxdevices.com/news/NS4262102607.html Penguinistas hack Android onto real hardware]
* [http://tree.celinuxforum.org/CelfPubWiki/Jamboree18AndroidDemo Google Android on Working Target]
* [http://code.google.com/android/groups.html Android discussion groups]. These concentrate more on Android application programming. Not really HW and processor related.
* [http://www.oesf.org/forum/index.php?showforum=158 Open Embedded Software Foundation Android forum]. Discussion, support and general information about running Android on a handheld.
* [http://groups.google.lu/group/android-internals/browse_thread/thread/93570c41bce07f16?hl=en Porting Android to real HW at Android internals list]
* [http://nemustech.blogspot.com/2007/12/android-porting-to-real-target-hw.html Android Porting to Real Target HW]
* [http://code.google.com/p/android-on-n8xx/ Android on Nokia 8xx]
* Tony's [http://www.muru.com/linux/n8x0/ booting nokia N8x0 with current OMAP git kernel]
* [http://forums.lugradio.org/viewtopic.php?f=4&t=4094#p41437 Robert Love talks about Google Android]. Recorded at [http://www.lugradio.org/live/USA2008/ LUG Radio Live USA 2008] at the Metreon Theatre, San Francisco.
* [http://groups.google.com/group/beagleboard/browse_thread/thread/e933982889f0441d# Rupesh Gujare announces availability of an Android file system image] for the [http://beagleboard.org/project/android BeagleBoard] and provides a [http://in.youtube.com/watch?v=3cetZMUWBHY video] and [http://embdroid.homeftp.net/ANDROID.tar.bz2 kernel + root file system].

''Note'': Some of the infos in above links are from the first versions of Android. Seems that with newer versions (e.g. m5-rc14) some parts changed, e.g. binder interface and /sys/android_power interface.

=Contact=

See [http://vger.kernel.org/vger-lists.html#linux-omap OMAP mailing list] for more information.

This page is distilled by [mailto:dirk.behme@gmail.com Dirk Behme] and information added by [mailto:leemgs@gmail.com Lim,GeunSik].

=Videos=

[http://guug.org/nit/nitdroid/ Nitdroid] (Android for Nokia Internet Tablets) on Nokia n810:

* [http://video.google.com/videoplay?docid=6988247315953961035&hl=en Using Nitdroid]
* [http://video.google.com/videoplay?docid=-7232749278972911905&hl=en Web-browsing example]

'''(Videos above are outdated and from very early stage)'''

[http://guug.org/nit/nitdroid/ NITdroid] on nokia770 :

* http://www.newlc.com/en/nitdroid-demo-gnulinux-android-nokia-n770-0
* [http://www.youtube.com/watch?v=3MKg8UAxgTE Android Donut Demo on Mistral's TMDSEVM3530]
* [http://www.youtube.com/watch?gl=US&hl=hi&v=IuO0YQfjflY Android Demo on Mistral's TMDXEVM3503]
* [http://www.mistralsolutions.com/technology/android_omap.php Download Android Demo on Mistral's TMDSEVM3530 & TMDXEVM3503]

=Screenshots=

* Android m5-rc14 home screen with kernel 2.6.23 on OMAP5912 [[OSK|OSK]]:

[[Image:Android m5 rc14 omap osk kernel 2 6 23.jpg]]

* Android m5-rc14 kernel + m3 image, on a Nokia N810:

[[Image:Cimg0608.jpg]]

[[Image:Cimg0610.jpg]]

[[Image:Cimg0611.jpg]]

* Android m5-rc15 home screen with kernel 2.6.18 on armadillo-500 1136 ([http://www.youtube.com/watch?v=jGvGl0nOQNo YouTube Movie])

[[Image:androidarmadillo200804.jpg]]

* Android m5-rc14 home screen with kernel 2.6.19 on OMAP2430 [[OSK|OSK]]:
-If you have unstable sdcard, You will meet for Looping of "Red Eye" Status.
[[Image:omap2evm.android.PNG]]

* Android camera application using V4L2 APIs, on TI OMAP EVM board:
[[http://www.e-consystems.com/images/eCAM/5mp_HDcamera_image_capture.jpg]]

* Android m5-rc14(2.6.23) on Nokia's n810 Tablet
[[Image:n810.kandroid200805.PNG]]

* Android Cupcake Ver 1.0(2.6.27) on OMAP3EVM(ARM Cortex-A8)
[[Image:omap3evm3.jpg]]

* NITdroid on nokia770 :

[[http://www.newlc.com/files/preview/6c0a2203f16d30fc3abfed994232f73b.png]] (larger images in tutorial above)

BeagleBoard

2012-11-27T07:30:05Z

Yclinda666: /* JTAG */

[[Category: Linux]]
[[Category: OMAP]]
[[Category:Development Boards]]
[[Category: BeagleBoard]]

This page collects information about [http://beagleboard.org BeagleBoard.org's] open hardware embedded computer boards based on [http://www.ti.com/ TI's] [http://www.arm.com/ ARM] processors. Most of this material is applicable to the BeagleBoard and BeagleBoard-xM. See the [[BeagleBone]] page for information on that board.

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#ffffcc; align:right; ">
'''NEWS:'''
* Limited numbers of Pixel Qi LCD kits and LVDs kits are now available from [http://www.tincantools.com TinCanTools]
* [http://www.tincantools.com TinCanTools] has now discontinued [[BeagleBoard_Zippy2|Zippy2]], [[BeagleBoard_Trainer|Trainer Boards]] and [[BeagleBoard_Zippy|Zippy Boards]].
* [http://www.nxelec.com/products/hmi BeadaFrame] 7" LCD display kits for BeagleBoard and BeagleBone are available now!
* [http://www.chalk-elec.com/ 10" LCD LVDS plug-and-play bundle with capacitance touchscreen and ambient light sensor] is available in stock now!
* LVDS LCD add-on board [http://www.chalk-elec.com/ LVDS LCD] has been released and is available for order
* An [http://www.liquidware.com/shop/show/BB-BT/BeagleTouch OLED touchscreen module "BeagleTouch"] and [http://www.liquidware.com/shop/show/BB-BJC/BeagleJuice lithium battery module "BeagleJuice"] are now available from [http://www.liquidware.com/shop Liquidware]
</div>
 
=Events=
* [http://jefro.wordpress.com/open-source-conferences/ Jeff's list of open source conferences]

{| class="wikitable"
! Event
! Location
! Date
|-
| [http://makerfaire.com/newyork/2012/index.html Maker Faire New York]
| New York Hall of Science, Queens, NY, USA
| Sep 29 - 30, 2012
|-
| [http://www.t-dose.org/ T-Dose]
| Eindhoven, The Netherlands
| Oct 27 - 28, 2012
|-
| [http://e.ubmelectronics.com/armtechcon/index.html ARM Techcon]
| Santa Clara, CA, USA
| Oct 30 - Nov 1, 2012
|-
| [https://events.linuxfoundation.org/events/embedded-linux-conference-europe Embedded Linux Conference Europe]
| Barcelona, Spain
| Nov 5 - 7, 2012
|}

=Hardware=

The BeagleBoard 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 ~600 MHz 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.

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.

==Components==

{|border=0
!Top view of rev B:
!Top view of rev C:
|-
|[[Image:Bb revb top numbered.jpg]]
|[[Image:Bb revc top numbered.jpg]]
|-
|}
{|border=1
!No.
!Name
!Comment
|-
|'''1'''
|[http://www.ti.com/omap35x OMAP3530] processor + 256 MB NAND

+ 128 MB DDR (rev B)

+ 256 MB DDR (rev C)
|PoP: Package-On-Package implementation for Memory Stacking
[http://www.micron.com/products/partdetail?part=MT29C2G24MAKLAJG-6%20IT 256 MB NAND/128 MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1435-ND DigiKey]

([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])

[http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for Beagle Board]
|-
|'''2'''
|[http://focus.ti.com/docs/prod/folders/print/tfp410.html DVI chip (TFP410)]
|
|-
|'''3'''
|[[BeagleBoard#DVI|DVI-D]]
|Connection via HDMI connector
|-
|'''4'''
|[[BeagleBoard#JTAG|14-pin JTAG]]
|1.8V only!
|-
|'''5'''
|Expansion connector: I2C, I2S, SPI, MMC/SD
|User must solder desired header into place
|-
|'''6'''
|[[BeagleBoard#User_button|User button]]
|Allows setting boot order.
|-
|'''7'''
| Reset button
|
|-
| '''8'''
|[[BeagleBoard#EHCI|USB 2.0 EHCI HS]]
|Rev A and B: not working, unpopulated

Rev C: populated and working
|-
|'''9'''
|SD/MMC+
| SDHC cards are supported
|-
|'''10'''
|[[BeagleBoard#RS232|RS-232 serial]]
|
|-
|'''11'''
|Alternate power
|normally powered by USB (unmounted on REV Ax boards, see [[BeagleBoard#Errata|errata]])
|-
|'''12'''
|[[BeagleBoard#OTG|USB 2.0 HS OTG]]
|Mini-AB connector. Board can be powered from port.
|-
|'''13'''
|Stereo In
|
|-
|'''14'''
|Stereo Out
|
|-
|'''15'''
|S-Video
|
|-
|'''16'''
|TWL4030 (Rev A thru C2 inc.)
[http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] (Rev C3 onwards)
|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.
|-
|'''17'''
|LCD
|only rev C
|-
|'''18'''
|USB power
|
|-
|'''19'''
|Host PHY
|
|-
|'''20'''
|32 kHz
|
|-
|'''21'''
|12 MHz
|
|-
|'''22'''
|RS-232 XVCR
|
|-
|'''23'''
|PWR SW
|
|-
|'''24'''
|VBAT
|
|-
|}

* Board size: 3" x 3" (about 76.2 x 76.2 mm)
* Weight: ~37 g
* Currently six-layer PCB; target: four layer PCB

'''Bottom of rev B:'''

[[Image:Beagle_bottom.jpg]]

See [http://www.flickr.com/photos/jadon/sets/72157606050144396/ jadonk's photostream] for some more detailed BeagleBoard pictures.

==Manual==

See [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)].

==Schematic==

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.

==Layout==

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.

==Errata==

# ''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 5 V.) See [http://www.flickr.com/photos/koenkooi/2512038988/ Koen's Beagleboard powermod picture] with short descriptions, too.
# ''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.
# ''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.
# ''Boards revision < A5 only'': There is an issue where on some boards the 1.8 V 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 1 uH. 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" (== 100 uH) they are wrong and have to be exchanged.
# ''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.
# ''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.2 µF 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!
# ''Boards revision A and < B5'': There is some issue with a 32 kHz clock depending on system configuration used to clock some OMAP3 peripherals. From this e.g. GPIOs, GPTIMERs, and USB on BeagleBoard might be affected. See [http://code.google.com/p/beagleboard/issues/detail?id=22 Issue 22]. The symptom from this is that after booting the Linux kernel, the 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 the 32 kHz timer to clock Linux, instead use the MPU timer. (B) Hardware workaround: Remove [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard capacitor C70], which improves the 32 kHz 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.
# ''Random boards, quite rare, revision < B6'': Some random boards and quite rare, show directly after purchasing broken serial communication from the 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 the 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.

For additional (software) issues and enhancement requests see [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker], too.

Note: BeagleBoard revision B6 uses different package for U9/U11.

==Clocking==

Some [http://www.beagleboard.org/irclogs/index.php?date=2008-07-08#T21:12:23 notes] about (ARM processor) clock rates at BeagleBoard:

* ARM Cortex-A8 processor is currently clocked at 500 MHz
* 500 MHz is the default used because it is a balance of performance and longevity
* For OMAP35x 600 MHz is maximum recommended
* An additional 720 MHz overdrive is supported only on high-speed grade OMAP3530/25 devices as fitted to the BeagleBoard C4
* At 600 MHz or higher OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy
* Higher than 600/720 MHz is out of specification and no guarantee it will work at all (or not damage itself)

* 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:

{| border="1"
||'''ARM'''||'''DSP'''||'''core voltage'''
|-
|720 MHz||520 MHz||1.35 V
|-
|600 MHz||430 MHz||1.35 V
|-
|550 MHz||400 MHz||1.27 V
|-
|500 MHz||360 MHz||1.2 V
|}

* 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.
* 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].
* There is a thermal monitor in the core, you could use to scale frequency up and down

To set the CPU clock to 600 MHz, there are two options. Both '''do not''' adjust the voltage, so the system may become unstable:

* The U-Boot command "mw 48004940 0012580c" will temporarily set the CPU clock to 600 MHz (not permanent over reset).
* To permanently set the CPU clock to 600 MHz, include the above command in the "bootcmd" variable or equivalent script.

* To set the DSP clock to 430 MHz use "mw 48004040 0x0009ae0c".

==Power management==

* Detailed OMAP3 Power Management Information can be found [[OMAP_Power_Management|HERE]]
* 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]
* Russ' Beagle HW modifications resulted in [http://groups.google.com/group/beagleboard/browse_thread/thread/197a8ef6b46cc828 8 mW sleep for Beagle Board]

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).

==DLP Pico projector==

Texas Instruments is developing a Pico Video Projector Kit (PVPK) as a peripheral for the BeagleBoard. The stand-alone pico projector will support VGA resolution (640 x 480 pixels), 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.

It is available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23836-ND DigiKey] for $349.

See [http://blog.makezine.com/archive/2009/01/tis-beagleboard-and-dlp-pico-projec.html article from Make], too.

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].

==Interfacing to Raw LCD Panels==

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:

* [[BeagleBoardRawLCD|interfacing to Raw LCD Panels]] article
* [http://digitalsurveyinstruments.com/beagleperiphials/hdmi2parallel/doc/index.htm HDMI-to-parallel] workaround method
* [http://www.harbaum.org/till/dvi2par/index.shtml dvi2par cheap DIY HDMI-to-parallel converter]

=Availability=

BeagleBoard Rev. C3 boards are available from

* [http://www.mouser.com/beagleboard Mouser]
* [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].

BeagleBoard Rev. C4 boards are available from:

* [http://www.liquidware.com/shop/show/BB-C4/BeagleBoard+C4 Liquidware]

Note: For non-US Digi-Key free shipping orders:

* 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
* Select ''Order Online'' for your country
* Add quantity ''1'' and part number ''296-23428-ND''
* Click ''Add to order''

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.

Note: Some users report that they got some questions from DigiKey to be answered before board shipping is done.

Note: While you get free shipping, most probably you have to pay tax, for example, 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.

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).

Note: German (Europe) users can order through German shops, too. For higher price, though.
* [http://shop.embedded-projects.net/product_info.php/info/p159_BeagleBoard--OMAP-3-.html Embedded Projects Shop] sells BeagleBoard for EUR 199.00 + shipping.
* [http://www.handheld-linux.com/wiki.php?page=Beagle%20Board Handheld-Linux] sells BeagleBoard for EUR 159.00 + shipping.
* [http://www.watterott.com/en/BeagleBoard Watterott electronic] sells BeagleBoard for EUR 142,80 + shipping.

See below for ''hardware'' differences of the revisions. There are no ''software'' differences.

==Revision A==

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.

==Revision B==

Revision B is same as revision A, except
* fix for shorted LEDs 0/1
* fix for wrong power jack pinout
* revision B6 uses different package for U9/U11
Still has USB HOST (EHCI) failures. USB HOST (EHCI) connector isn't mounted.

There are 4 revisions of the B board in the field: B4, B5, B6 and B7.

The most notable difference is the use of the ES3.0 silicon in B6 and B7, other changes are not relevant to software developers.

==Revision C2==
Revision C2 is same as revision B7 except:
* USB HOST (EHCI) is operational on revision C2, with standard USB A female connector.
* Add interface for raw LCDs ([http://groups.google.com/group/beagleboard/msg/2e82c3ed6061d9d2 mockup])
* 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:
** 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
* Power measurement feature
* Uses [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] OMAP power controller instead of TWL4030
* 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])
* Revision detection (to be able to identify C2 board from older boards by software, for example, for different pin mux)
* 256 MB RAM ([http://groups.google.com/group/beagleboard/msg/3a38d0f21cefd6b1?hl=en message]) (and still 256 MB NAND like rev B)

Note: Revision C2 is the first production version, and all orders from Digi-Key are shipped as Rev C2.

==Revision C3==
As revision C2 boards are [http://groups.google.com/group/beagleboard/msg/e41d3c97aa7d4951 sold out], revision C3 will ship now.

Revision C3 is same as revision C2 [http://groups.google.com/group/beagleboard/msg/037318fbc44139d5 except]:
* Optional RTC [http://parts.digikey.com/1/parts/1454-battery-lith-coin-3v-12-5mm-vert-vl-1220-vcn.html VL1220 series] backup battery
* Mounting holes conected to ground
* Slightly improved S-Video

==Revision C4==
Revision C4 boards are the same as Revision C3 except:
* Processor is 720 MHz capable OMAP3
* Improved USB Host PHY power rails

==Revision C5==
Revision C5 boards are the same as Revision C4 [http://circuitco.com/support/index.php?title=BeagleBoard#Image_Files except]:
* The memory chip is upgraded to 512 MB NAND

==Clones==
===EBVBeagle===
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/].
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.
More information in [http://www.ebv.com/en/press-print/news-pr/details/news//press-releas-54.html official press release].

===Mini Board===
[[Mini_Board|ICETEK-OMAP3530-Mini]] is a Chinese BeagleBoard clone.

===DevKit8000===
[http://www.armkits.com/Product/devkit8000.asp DevKit8000] is from [http://www.armkits.com Embest], China. It is a compact development board based on TI OMAP3530.

===DevKit8500D===
[http://www.armkits.com/Product/devkit8500d.asp DevKit8500D] is from [http://www.armkits.com Embest], China. It is a high-performance development board based on TI DM3730.

===SBC8530===
[http://www.armkits.com/Product/sbc8530.asp SBC8530] is from [http://www.armkits.com Embest], China. It is a compact single board computer based on TI DM3730 and features UART, 4 USB Host, USB OTG, Ethernet, Audio, TF, WiFi/Bluetooth, LCD/VGA, DVI-D and S-Video.

===Tianyeit CIP312===
[http://www.tianyeit.com CIP312 ] is from [http://www.tianyeit.com Tianyeit], China. It is has many functions ,such as WLAN/BT/ dual 10/100M Ethernet Contoller-LAN9221I/MCP2512 CAN BUS/ Touch Screen Controller/USB HUB/USB host/USB OTG Etc. Our module is base on DM3730/omap3530 all functions are packaged in 40x40x3.5 mm package ; For detailed information, please visit our website
[[Image:http://www.tianyeit.com/download/cip312.jpg]]

===IGEPv2===
[http://www.igep-platform.com/ IGEPv2 Platform] is a Spanish BeagleBoard clone, slightly larger, with additional peripherals like, for example, Ethernet connector, Wi-Fi and Bluetooth.
* 720 MHz OMAP3 Processor
* 512 MB RAM / 512 MB Flash

===SOM3530===
[[SOM3530]] is a Chinese BeagleBoard clone [[System-on-Module]], dimensions 40x40x4 mm, maybe the smallest [http://wiki.davincidsp.com/index.php?title=OMAP3_Overview OMAP3530]-based modules in the world! Including 100 Mbit/s high perfomance Ethernet I/F.

==BeagleBoard-based products==
* [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]

==Beagle case==

*[http://specialcomp.com/beagleboard/ Special Computing acrilyic case]
** [http://groups.google.com/group/beagleboard/browse_thread/thread/1c82316019633e51 SketchUp 3D model]
* [http://www.esawdust.com/product/encl-dh-r1/ eSawdust metal case]
* [http://aspectrt.web.fc2.com/support/ Aspect metal case for BeagleBoard-xM]

=Adapters=

For quite detailed information about all BeagleBoard peripherals see [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)].

See [[BeagleBoardPeripherals| BeagleBoard peripherals and adapters page]] for useful add ons for BeagleBoard.

==Expansion boards==
See [[:Category:BeagleBoard_Expansion_Boards]] for more information about expansion boards

[http://www.nxelec.com/products/hmi BeadaFrame] - A 7" TFT LCD Screen with resistive touch for BeagleBoard and BeagleBone. A plastic (ABS) frame is included also for ease of mounting.

[http://www.chalk-elec.com LVDS LCD] - small add-on board to connect any LVDS LCD panel (like those in notebooks) to BeagleBoard (-xM) and PandaBoard. Also, they offer plug-and-play bundle with 10" 1024x600 LCD with capacitance touchscreen and ambient light sensor for automatic brightness control. The board is open-source.

[http://www.liquidware.com/shop/show/BB-BT/BeagleTouch BeagleTouch] - A modular "shield" that snaps on top of the BeagleBoard and provides a touch-screen OLED interface

[http://www.liquidware.com/shop/show/BB-BJC/BeagleJuice BeagleJuice] - A lithium ion battery module that snaps on the back of the BeagleBoard that powers the BeagleBoard.

[http://www.picklejar.org/lox LOX] - A dual channel internet linking radio (Ham, GMRS, etc.) interface that can run any combination of two repeaters, simplex nodes, or remote bases.

==JTAG==

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.
See [[BeagleBoardJTAG]] for more information.

The [http://www.armkits.com/Product/xds100.asp XDS100v2 USB JTAG Emulator] is available from [http://www.armkits.com Embest] which is the second release of the XDS100 JTAG emulator technology supporting debug of a variety of TI devices.

==RS-232==

The pinout on the BeagleBoard 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.

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.

==USB-to-Serial Converter==

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.

==USB==
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.

===EHCI===
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.

According to the BeagleBoard System Reference Manual Rev C2, the EHCI port can source 5 V at 500 mA 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 5 V external power supply. If the BeagleBoard is powered through the OTG port, the EHCI port sources an "extremely limited" ampount of power (probably 100 mA 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.]

'''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.8 V rail between the OMAP3530 and the power chip was getting noisy. Suggested solution (works on many boards) is adding a 22 µF 0805 package SMT capacitor atop the existing capacitor on C97. If SMT parts are not available, some boards can be repaired by a 22 µF 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.

===OTG===
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.

When using the OTG port in host mode, you must power the BeagleBoard using the +5 V 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.

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".

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.]
<table>
<tr><td>
Since the right cables might be hard to get, you simply can
* 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.
or
* 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.
</td><td>[[Image:usb_otg.png]]</td></tr></table>
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.
See Figure 20 in the BeagleBoard System Reference Manual Rev C2.2.

==DVI==

DVI-D connection on BeagleBoard uses an [http://en.wikipedia.org/wiki/HDMI HDMI connector]:

''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.''

BeagleBoard can be connected to a DVI monitor using an HDMI male to DVI male cable.

The BeagleBoard does not connect the HDMI shell to ground or any other BeagleBoard signal. This is not a problem with high-quality HDMI to DVI cables that connect all the ground wires. However, there are lots of cheap HDMI to HDMI cables that do not connect the ground wires and only use the shell as a combined shield and ground. To use one of these you would need to connect the BeagleBoard's HDMI shell to ground. The BeagleBoard-xM connects the HDMI shell to frame ground, which is in turn connected to system ground through R119. For more information, see this thread: [http://groups.google.com/group/beagleboard/browse_thread/thread/861da101804da56b].

== Arduino ==

* [[BeagleBoard_Trainer|Trainer Board]] from [http://www.tincantools.com TinCanTools] has an Arduino compatible Atmel AVR on board
* Arduino [http://arduino.cc/en/Main/ArduinoBoardNano Nano] uses an FTDI FT-232 based interface which is supported by the ftdi_sio kernel driver- [[BeagleBoard_with_Arduino|How To Notes]]
* Arduino [http://arduino.cc/en/Main/ArduinoBoardUno Uno] uses a Atmel ATmega8U2 based interface which is supported by the cdc_acm kernel driver - [[BeagleBoard_with_Arduino|How To Notes]]

=BootRom=

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 the Initialization chapter of [http://www.ti.com/lit/pdf/spruf98 SPRUF98].

==User button==

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):

* User button ''not'' pressed: NAND -> USB -> UART -> MMC
* User button ''is'' pressed: USB -> UART -> MMC -> NAND

Technically speaking, the user button configures pin SYS.BOOT[5]. See the Initialization chapter of [http://www.ti.com/lit/pdf/spruf98 SPRUF98] for more details.

==Serial and USB boot==

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 environment from Linux]].

===OMAP U-Boot Utils===

Nishanth' [http://code.google.com/p/omap-u-boot-utils/ OMAP U-Boot Utils] provide

* ''pserial'' - OMAP specific utility which downloads a file in response to ASIC ID over serial port.
* ''pusb'' - OMAP specific utility which downloads a file in response to ASIC ID over USB connection.
* ''ucmd'' - Send a command to U-Boot and wait till a specific match appears.
* ''ukermit - Download a file from host without using kermit to U-Boot.

See [http://nishanthmenon.blogspot.com/ Nishanth' blog] and [http://groups.google.com/group/beagleboard/browse_thread/thread/c5bfb1b8ed528b52# announce mail], too.

===Serial boot===

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 is one tool for UART boot:

* [http://groups.google.com/group/beagleboard/browse_thread/thread/80ad3da0eb2aa555 Linux C utility] (not working yet with below target code)

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.

===USB boot===

There is a patch to x-loader to allow it to do a USB boot. It can boot all the way to a Linux login.
It's is used with a new version of omap3_usbload.

* [http://members.efn.org/~rick/pub/x-loader-usb.tar.bz2 x-loader-usb]

Besides Nishanth' ''OMAP U-Boot Utils'', for USB boot, there is currently one (experimental) tool to boot BeagleBoard over USB:

* [http://groups.google.com/group/beagleboard/browse_thread/thread/2b9e99886bb7a747 Linux C utility]

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.

See the [[BeagleBoardRecovery#USB_recovery|USB recovery section]] on how to use USB boot for board recovery.

==NAND boot==

See [[BeagleBoardNAND|NAND boot]] article.

==MMC/SD boot==

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.

===MMC/SD formatting===

As described in above MMC/SD boot description, you have to ''create a bootable partition on MMC/SD Card''. This can be done using, for example, Windows or Linux tools.

'''Windows'''

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.

You can download this tool from [http://www.sysanalyser.com/sp27213.exe here]. Make sure the version is 2.0.6; newer versions may not work.

'''Linux'''

Please see [http://wiki.omap.com/index.php?title=MMC_Boot_Format OMAP3 MMC Boot Format].

===Dual partition card===

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.

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 (for example, in U-Boot using ''setenv bootargs''):

console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait

===U-Boot booting===

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 the BeagleBoard. For example (output from terminal program with 115200 8N1):

...40T.........XH.H.U�..Instruments X-Loader 1.41
Starting on with MMC
Reading boot sector

717948 Bytes Read from MMC
Starting OS Bootloader from MMC...

U-Boot 1.1.4 (Apr 2 2008 - 13:42:13)

OMAP3430-GP rev 2, CPU-OPP2 L3-133MHz
TI 3430Beagle 2.0 Version + mDDR (Boot ONND)
DRAM: 128 MB
Flash: 0 kB
NAND:256 MiB
In: serial
Out: serial
Err: serial
Audio Tone on Speakers ... complete
OMAP3 beagleboard.org #

Using this U-Boot prompt, you now can start kernel uImage stored on MMC card manually:

OMAP3 beagleboard.org # mmc init
OMAP3 beagleboard.org # fatload mmc 0:1 0x80000000 uimage
OMAP3 beagleboard.org # bootm

If you like to make that happen every boot:

OMAP3 beagleboard.org # set bootcmd 'mmc init ; fatload mmc 0:1 0x80000000 uimage ; bootm' ; saveenv

Note: saveenv will not work on the xM. You will need to create a <tt>boot.scr</tt> file in the FAT partition for the xM. See [https://fedoraproject.org/wiki/Architectures/ARM/BeagleBoardxMSDCard#Set_up_u-boot set up u-boot] 
Note2: after a saveenv, u-boot will not read your boot.scr any more. To make it use boot.src again, type "nand erase" in the u-boot promt (works on C4, older versions may need a "nand unlock" too).

===Barebox booting===

You can also use barebox to boot.

On barebox you will have to generate it two time.

The first time as a x-loader via defconfig: omap3530_beagle_xload_defconfig

The second time as the real boot loader omap3530_beagle_defconfig

=Code=

Code and binaries for BeagleBoard are available at various places.

==Binaries==

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.

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:

* [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.bin u-boot.bin]
* [http://www.angstrom-distribution.org/demo/beagleboard/MLO MLO]
* [http://www.angstrom-distribution.org/demo/beagleboard/uImage uImage]
* [http://www.angstrom-distribution.org/demo/beagleboard/Angstrom-Beagleboard-demo-image-glibc-ipk-2009.X-test-20090104-beagleboard.rootfs.tar.bz2 rootfs]

See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat beagle wiki] on how to setup your SD card to use all this goodness.

==Source==
'''Update on April 23 - 2010''': Sources for the X-Loader and U-Boot that ship on the BeagleBoard can be found at [http://gitorious.org/beagleboard-validation/ http://gitorious.org/beagleboard-validation/]. The U-Boot version found in that repository supersedes the one found at [http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/ http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/].

'''Update on March 3 - 2011''': Sources for the SD card shipped with revisions Ax and Bx of the BeagleBoard-xM are in the Angstrom Distribution. The script used to build the sources is documented at http://code.google.com/p/beagleboard/wiki/BeagleBoardDiagnosticsNext. The sources at http://gitorious.org/beagleboard-validation are meant to mimic what was used in the OpenEmbedded-based build.

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.

===X-Loader===

Steve did some work to consolidate and update X-Loader from various sources and put it in a [http://gitorious.org/x-load-omap3 X-Loader git repository]. Get it by

git clone git://gitorious.org/x-loader/x-loader.git xloader
cd xloader/

Build:

make distclean
make omap3530beagle_config
make

Result will be a ~20k sized ''MLO'' in the main directory. This is the signed x-loader and is ready for use.

===U-Boot===

[http://www.denx.de/wiki/U-Boot/WebHome Mainline U-Boot] has good support for BeagleBoard (except for revision C4; see note below). Get it by:

git clone git://git.denx.de/u-boot.git u-boot-main
cd u-boot-main
git checkout --track -b omap3 origin/master

Build (assuming [[ARMCompilers#Recommendations|Code Sourcery GCC]]):

make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper
make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_beagle_config
make CROSS_COMPILE=arm-none-linux-gnueabi-

Result will be a ~160 KB sized ''u-boot.bin'' in the main directory.

Note: Due to (patch and binary) size, the 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].

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:

git clone git://gitorious.org/u-boot-omap3/mainline.git u-boot-omap3
cd u-boot-omap3
git checkout --track -b omap3-dev origin/omap3-dev

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]

Note: For beagleboard revision C4, above sources will not work. USB EHCI does not get powered, hence devices are not detected...
Get a patched version of u-boot from http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/
('''Update on April 23 - 2010''': This repository has been superseded by the U-Boot version found at [http://gitorious.org/beagleboard-validation/ http://gitorious.org/beagleboard-validation/])

Note: If you want to activate I²C from the expansion header, modify board/ti/beagle/beagle.h :

MUX_VAL(CP(I2C2_SCL), (IEN | PTU | EN | M4)) /*GPIO_168*/
MUX_VAL(CP(I2C2_SDA), (IEN | PTU | EN | M4)) /*GPIO_183*/

to

MUX_VAL(CP(I2C2_SCL), (IEN | PTU | DIS | M0)) /*I2C2_SCL*/
MUX_VAL(CP(I2C2_SDA), (IEN | PTU | DIS | M0)) /*I2C2_SDA*/

===Linux kernel===

[http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap.git;a=summary Git repository] of [http://muru.com/linux/omap/ OMAP Linux kernel] contains Beagle support. Get it by:

git clone git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git linux-omap
cd linux-omap

Build:

make distclean
make ARCH=arm omap2plus_defconfig
make ARCH=arm menuconfig # Only needed if you want to change the default configuration
make ARCH=arm uImage

The result will be a ''uImage'' in ''arch/arm/boot/'' directory.

'''Note: The following does not work. There is no defconfig "omap3_beagle_defconfig" nor any omap3 in the tree.'''

If you use the OE toolchain and want to build outside of the OE tree you should do

ARCH=arm
export ARCH
PATH=~/oe/tmp/cross/armv7a/bin:~/oe/tmp/staging/i686-linux/usr/bin:$PATH # add cross tools to your path
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- distclean
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- omap3_beagle_defconfig
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- menuconfig # only needed if you want to change the default configuration
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage

Note: the staging dir in the path is for mkimage. If you've built a kernel before with oe, the program should be there

Note: If you are interested in kernel development have a look to [[BeagleBoardLinuxKernel|manually compiling BeagleBoard kernel]], too.

===Experimental kernel patches and hacks===

Some BeagleBoard developers maintain their own kernel experimental patches and hacks not ready for upstream:

* [http://veter-project.blogspot.com/2012/03/comfortable-kernel-workflow-on.html Build Angstrom 2.6.38 Kernel] to compile kernel modules natively, see [https://groups.google.com/forum/?fromgroups#!searchin/beagleboard/sam/beagleboard/eg6zYMcdMMA/KA3y0CS6n5cJ Angstrom package to natively compile kernel modules post] for corrections to the how-to.
* [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] '''(Broken Link)'''
* [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. '''(broken link)'''
* [http://git.mansr.com/?p=linux-omap;a=summary Mans' kernel tree], a clone of the main OMAP Git repository with additional patches, mainly display & framebuffer related. '''(Link to Unknown Project)'''
* [http://www.bat.org/~tomba/linux-omap.html Tomi's kernel tree], a clone of the main OMAP Git repository with display sub-system patches, replacing the entire display driver with one that is the likely direction moving forward.

=Compiler=

TI OMAP3530 processor on BeagleBoard contains an ARM Cortex-A8 general purpose processor and a TMS320C64x+ DSP.

==ARM==

There is broad compiler support, including GCC - please see [http://www.elinux.org/ARMCompilers ARM Compilers]

==C64x+ DSP==

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).

Note: my.TI account required. You may create an account [https://my.ti.com here]

Note: An pld c6000 Linux compiler is available on the [ftp://ftp.ti.com/pub/cs/linux_cgt500.tar.gz TI FTP site]. It does NOT support c64x+ core in OMAP3 devices. Not recommended.

You can also use 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.

See [[BeagleBoard/DSP_Howto| BeagleBoard DSP howto]] for information about how to use the DSP.

=Cortex A8 ARM features =

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.

It includes a floating point unit (ARM VFPv3 architecture) and the ARM NEON SIMD instruction set.

See [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] article for an introduction into VFP-lite and NEON.

===ARM NEON===

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:
* 64-bit signed/unsigned
* 32-bit signed/unsigned
* 32-bit single precision floating point
* 16-bit signed/unsigned
* 8-bit signed/unsigned

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.

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].

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].

NEON is used by various opensource projects:
* [http://www.libav.org/ Libav] - libavcodec used by mplayer, omapfbplay, and many other Linux applications
* libpixman - used by X.org and Mozilla & Webkit browsers to render text and graphics
* [http://www.bluez.org/ Bluez] - official Linux Bluetooth stack
* [http://eigen.tuxfamily.org/ Eigen2] - C++ template library for linear algebra (matrix math, etc.)
* [http://www.webmproject.org/code/ Webm] - Google's new opensource video codec

Compilation tools support for NEON:
* ARM RVDS
* GCC
* [http://blog.llvm.org/2010/04/arm-advanced-simd-neon-intrinsics-and.html LLVM]

=== ARM Cortex-A8 Floating Point ===

There are two types of instructions in the ARM v7 ISA that handle floating point:

1) '''VFPv3''' Floating point instruction set (used for single/double precision scalar operations).
These is used by GCC for C floating point operations on 'float' and 'double' since ANSI C can only describe scalar floating point, where there is only one operation at a time.

2) '''NEON''' [http://www.arm.com/products/multimedia/neon/ NEON] vectorized single precision operations (two values in a D-register, or four values in a Q-register)
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.

ARM Cortex-A processors have separate floating point pipelines that handle these different instructions.

On Cortex-A8, the designers' focus was on the NEON unit performance which can sustain one cycle/instruction throughput (processing two single-precision values at once) for consumer multimedia. 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.

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:
* Use GCC with -ftree-vectorize (possibly modify source code to make it vector friendly)
* Use NEON instrinsics (#include <arm_neon.h>, float32x2_t datatype and vmul_f32() etc)
* Use NEON assembly language directly

On Cortex-A9, there is a much higher performance floating point unit which can sustain one cycle/instruction throughput, with low result latencies. OMAP4 uses dual-core Cortex-A9+NEON which gives excellent floating-point performance for both FPU and NEON instructions.

=Board recovery=

If you played, for example, with the contents of the [http://www.sakoman.net/omap3/flash%20procedure.txt NAND], it might happen that the BeagleBoard doesn't boot any more (without pressing user button) due to broken NAND content. See [[BeagleBoardRecovery|BeagleBoard recovery]] article how to fix this. Do not panic and think you somehow 'bricked' the board unless you did apply 12 V to it.

=Development environments=

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.

==OpenEmbedded==

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]],[[BeagleBoardOpenEmbeddedDevelopment|OpenEmbedded development]] and [http://wiki.openembedded.org/index.php/Getting_Started OpenEmbedded getting started] as well.

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''.

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.

===One very important note:===

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:
* 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 information on making the SD card.
* Put the SD card in the BeagleBoard, and boot up to the U-Boot prompt.
* Do the first six instructions in the [http://code.google.com/p/beagleboard/wiki/BeagleNANDFlashing Flashing Commands with U-Boot] section.
* Reboot the BeagleBoard to see that the new X-Loader is properly loaded.

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.

==Eclipse==
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]. Information on how RSE is used for, for example, Gumstix development is described in [http://groups.google.com/group/beagleboard/browse_thread/thread/509831f7c24cb79f# this post].

See also [[BeagleBoardEclipse|Using Eclipse with Beagle]] (for JTAG debugging).

==Android==
The [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.

There are several resources for Android on OMAP (Beagle) available:

'''OMAPZOOM'''

You can find Android port for OMAP ZOOM architecture on [https://gforge.ti.com/gf/project/omapandroid/ OMAPZoom.org's wiki page on Android].

'''EMBINUX'''

[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™] Team. The [http://labs.embinux.org/git/ source code] and [http://www.embinux.com/download_beagle.php binaries] are available for download and review.

Detailed instructions, for porting Android on BeagleBoard, are available [http://labs.embinux.org/index.php/Main_Page here]. Current release supports input devices (keyboard/mouse), network and sound.

You can [http://in.youtube.com/watch?v=nADn_vNVEKw watch Android booting] on BeagleBoard.

'''Android on OMAP wiki'''

Wiki page for Andorid on OMAP can be found [[Android on OMAP|here]].

'''0xdroid'''

[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.

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].

You can watch the 0xdroid demo video on the BeagleBoard:
* [http://www.youtube.com/watch?v=v6wdTOHrwQw 0xdroid demo video (1)]
* [http://www.youtube.com/watch?v=ol9LWBKXXwQ 0xdroid demo video (2)]
* [http://www.youtube.com/watch?v=OGpYk1p1UPI 0xdroid demo video (3)]

==Mamona==

[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 BeagleBoard.

==Ubuntu==

See [[BeagleBoardUbuntu|Ubuntu (ARM)]] installation guide how to install Ubuntu (ARM) on BeagleBoard.
* [[BeagleBoardLucid]] Details about Ubuntu Lucid on the BeagleBoard.
* [[BeagleBoardUbuntuKernel]] Details about the Ubuntu Kernel on the BeagleBoard.
* [[BeagleBoard Ubuntu]]
* [[BeagleBoardUbuntuKarmic]]

==Debian ARM==

See [[BeagleBoardDebian|Debian (ARM)]] installation guide how to install Debian (ARM) on BeagleBoard.

==GeeXboX ARM==

See [[GeeXboX|GeeXboX (ARM)]] installation guide how to install GeeXboX on BeagleBoard (including clones).

==Scratchbox==

[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 introduction], too.

=Software hints=

This section collects hints, tips & tricks for various software components running on BeagleBoard.
* [[RPM_jffs2_issue]]

==QEMU==

[[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.

==Linux hints==

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:

* Switching video output between DVI-D and S-Video
* Disabling framebuffer blanking
* Listing USB devices

==lmbench==

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 BeagleBoard.

==Mediaplayer (FFmpeg)==

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 BeagleBoard. Includes compiler hints and patches.

==Java==

===Open source===

When using the [[BeagleBoard#OpenEmbedded|OpenEmbedded]]-based Angstrom image you have the following options of Java support:
* JamVM + GNU Classpath (small vm, fast interpreter, J2SE-like)
* Cacao + GNU Classpath (JIT compiler, J2SE-like)
* PhoneME Advanced Foundation (JIT compiler, CDC)

Java support in OpenEmbedded/Angstrom ([http://wiki.openembedded.net/index.php/Java details]) is provided voluntarily through [http://jalimo.org Jalimo].

See a [http://groups.google.com/group/beagleboard/browse_thread/thread/102f627253919783# post at mailing list], too.

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.

The recipes offer the following functionality:

* OpenJDK + Hotspot (Zero port) (all J2SE functionality, including JVMTI, interpreted only)
* OpenJDK + Cacaco (all J2SE library features, missing JVMTI, decent JIT compiler)
* OpenJDK + Hotspot (Shark port) (not working yet)

[http://camswl.com/ Edward Nevill] from ARM Ltd. is working on interpreter optimization in Zero for ARM.

People interested in getting this stuff working better should contact people on:
* [http://evolvis.org/mail/?group_id=11 Jalimo Mailinglist]
* [http://mail.openjdk.java.net/mailman/listinfo/distro-pkg-dev Icedtea Mailinglist]

You should also check out IcedTea's [http://iced-tea.org/wiki/FrequentlyAskedQuestions FAQ].

===Oracle Java===

As of August 2012, there is a binary version of Oracle JDK 7 available for Linux/ARM under a free (but not open source) license. More information:
* [http://www.oracle.com/technetwork/java/javase/downloads/index.html Download on java.oracle.com]
* [http://www.oracle.com/technetwork/java/javase/7u6-relnotes-1729681.html#LinuxARM Release notes for JDK 7 Update 6]
* [http://www.oracle.com/us/corporate/press/1735645 Original announcement]
* [https://blogs.oracle.com/henrik/entry/oracle_releases_jdk_for_linux Oracle blog with FAQ]
* [http://www.oracle.com/technetwork/java/javase/terms/license/index.html Oracle Binary Code License]

Supported features:
* Java SE 7 compliant
* Almost all development tools from the Linux/x86 JDK
* Client and server JIT compilers
* Swing/AWT support (requires X11R6)
* Softfloat ABI only

Oracle states in the [https://blogs.oracle.com/henrik/entry/oracle_releases_jdk_for_linux FAQ] that they are working on hard float support, as well as a JavaFX 2 port to Linux/ARM.

== Booting Android (TI_Android_DevKit) from a USB stick ==
'''Please note'''
* This procedure was tested on BeagleBoard-xM revision B(A3)
* An SD card will be still needed to load the kernel.
* An SD card will contain boot parameters for the kernel to use a USB stick as the root filesystem

'''Procedure'''
# Download Android Froyo for BeagleBoard-xM from [http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_00_00/index_FDS.html TI]
# Follow the installation procedure for an SD card card.
# Test if Froyo is working with your BeagleBoard-xM with an SD card.
# You will notice that Android has a slow performance. That is why we will install root filesystem on a USB stick.
# Format your USB stick and create one ext3 partition.
# Mount newly created ext3 partition and extract TI's root filesystem to it: sudo tar jxvf rootfs_am37x.tar.bz2 -C /media/ROOT
# Unmount flashdisk and insert it into the BeagleBoard.
# Mount your SD card to your computer.
# Now we need to tell the BeagleBoard to use the root filesystem from the /dev/sda1 partition instead of the SD card partition. That is done by overwriting boot.scr on the SD card with [http://www.apksoft.eu/android/boot.scr this one]
# Unmount the SD card and insert it into the BeagleBoard and test.

=Graphics accelerator=

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.

Tutorial:
* [http://code.google.com/p/beagleboard/wiki/HowtoUseSGXunderAngstrom How to use SGX with Angstrom in OE]
* [http://labs.qt.nokia.com/2009/11/20/building-qt-to-make-use-of-the-beagle-boards-sgx-gpu/ Building Qt to make use of the Beagle board’s SGX GPU]

Some videos:

* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on BeagleBoard working with Linux 2.6.27]
* [http://www.youtube.com/watch?v=24TXpqa9jG0&feature=related OpenGL ES 2.0 shader effects on OMAP3]
* [http://www.youtube.com/watch?v=-UFUbqoNgs8&feature=related 3D User Interface on OMAP3 Platform]
* [http://www.youtube.com/watch?v=8KcNgeUriqA 3D Mapping using OpenGL ES 2.0 on OMAP3 Platform]
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]
* [http://www.hitlabnz.org/wiki/EmbeddedAR An Augmented Reality application combining ARToolkit and OpenGL ES 2.0]
* [http://www.youtube.com/watch?v=cfeqSOYkBJg&feature=player_embedded Video of the Beagle Board turned into a portable battery powered Linux tablet]

=Beginners guide=

You just got your new BeagleBoard, and now? See [[BeagleBoardBeginners|beginners guides]].

=FAQ=

For BeagleBoard frequently asked questions (FAQ) see [[BeagleBoardFAQ|community FAQ]] and "official" [http://beagleboard.org/support/faq BeagleBoard.org FAQ].

=Links=
==Home page==
[http://beagleboard.org/ beagleboard.org] (BeagleBoard home)
* 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>''

==Manuals and resources==
* [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard HW Reference Manual (rev. C2)]
* [http://beagle.s3.amazonaws.com/BBSRM_7_2_0.pdf BeagleBoard HW Reference Manual (rev. B7)]
* [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)]
* [http://www.beagleboard.org/uploads/BBSRM_B5.pdf BeagleBoard HW Reference Manual (rev. B5)]
* [http://www.beagleboard.org/uploads/Beagle_HRM_B4.pdf BeagleBoard HW Reference Manual (rev. B4)]
* [http://www.beagleboard.org/uploads/Beagle_HW_Reference_Manual_A_5.pdf BeagleBoard HW Reference Manual (rev. A5)]
* [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor description and manuals
* [http://code.google.com/p/beagleboard/ Beagle at code.google.com]
* [http://focus.ti.com/dsp/docs/dspsupporttechdocs.tsp?sectionId=3&tabId=409&familyId=1526&documentCategoryId=4&techDoc=4 OMAP3530/25 CBB BSDL Model]
* [http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for BeagleBoard]
* [http://beagleboard.org/resources BeagleBoard resources page with hardware documentation]
* Some [http://www.rasterman.com/ performance comparison] of BeagleBoard Rev. B with some other ARM/PC systems.
* OMAP3 pinmux [http://www.hy-research.com/omap3_pinmux.html setup]
* [http://elinux.org/BeagleBoardPinMux OMAP3 eLinux pinmux page]

==Contact and communication==
* [http://groups.google.com/group/beagleboard BeagleBoard discussion list]
* [http://code.google.com/p/beagleboard/issues/list BeagleBoard open point list and issue tracker]
* [http://beagleboard.blogspot.com/ BeagleBoard blog]
* [http://feeds.feedburner.com/BeagleBoard BeagleBoard RSS feed]
* Chat:
** [http://beagleboard.org/chat BeagleBoard chat]
** IRC: #beagle channel on irc.freenode.net
** [http://www.beagleboard.org/irclogs/index.php IRC archive]
* [http://www.beaglesride.org/ Beagles Ride], a site about building a community around the BeagleBoard focused on in vehicle applications
* [http://www.beagleboard.de/ German BeagleBoard Forum and Wiki]

==TI resources==
* [http://opensource.ti.com/ TI open source page]
* [https://community.ti.com/ TI E2E (Engineer-to-Engineer) Community]
* [http://marc.info/?l=linux-omap&m=120761100810527&w=2 DSP Bridge driver for OMAP3 platform]
* [http://lists.arm.linux.org.uk/lurker/message/20080701.142512.5eeff26b.en.html ARMv7 Oprofile support]
* [http://focus.ti.com/pdfs/wtbu/swpu114g.pdf OMAP34xx Wireless Technical Reference Manual] (swpu114g.pdf, 47 MB)
* [http://amethyst.openembedded.net/~koen/index.php?sort=date&order=desc&path=beagleboard/ Koen's (OpenEmbeded) BeagleBoard source and binaries]
* [http://del.icio.us/tag/beagleboard+peripheral+verified Verified peripherals for BeagleBoard]
* [http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt OMAP3430 Linux Power Management presentation]

==Articles==
* [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article about BeagleBoard]
* [http://www.linuxdevices.com/news/NS8479495970.html LinuxDevices article about Digi-Key launch]
* [http://www.linuxdevices.com/news/NS5682470737.html LinuxDevices article about BeagleBoard Rev C, Beagle MID from HY Research, Touch Book and Sponsored Projects Contest]
* [http://www.linuxjournal.com/article/10607 Linuxjournal article on the BeagleBoard]

==Books==
* [[OMAP_and_DaVinci_Software_for_Dummies|OMAP and DaVinci Software for Dummies]]

==BeagleBoard based training materials==
* http://free-electrons.com/blog/beagle-labs/

==Past BeagleBoard events==
* TIDC, February 26-28, 2008: [http://www.beagleboard.org/uploads/tidc_opensource.pdf Slides from TI developer conference (TIDC) open source session], covering also BeagleBoard
* [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]
* 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]
* [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 BeagleBoard. [http://linuxoutlaws.com/podcast/48 Interview with Linux Outlaws (52:06)] and the [http://www.youtube.com/watch?v=m9xVbntl-DY video]
* [http://osscamp.in/index.php/OSScamp_Bengaluru_Mobile_2008 OSScamp Bengaluru Mobile 2008], July 19, 2008
* [http://www.linuxworldexpo.com LinuxWorld Conference & Expo], August 4 - August 7, 2008: [http://www.flickr.com/photos/jadon/sets/72157606586084668/ pictures with living BeagleBoard] and from [http://www.flickr.com/photos/linuxjournal/2738316951/in/set-72157606634486338/ Linux Journal's photostream]
* BeagleBoard.org event at Jillian's during LinuxWorldExpo, August 5, 2008, 5:30-7:30 pm
* [http://barcamp.pbwiki.com/BarCampHouston3 BarCamp Houston 3], August 9, 2008, 9:00 A.M.: [http://www.flickr.com/photos/jadon/sets/72157606656532041/ pictures]
* NIT Suratkal, India [http://www.nitkieee.com/site/sp-connect2/schedule IEEE SP Connect 2], August 30, 20008
* [http://barcampbangalore.org/wiki/BCB7_Demos BarCamp Bangalore], India, September 13, 2008
* [http://www.ibc.org/ IBC 2008], September 11 - September 16, 2008: [http://www.flickr.com/photos/koenkooi/tags/ibc2008/ pictures]
* 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]
* [http://www.embedded.co.uk/ Embedded Systems Show 2008], Birmingham, UK, October 1-2, 2008
* [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]
* [http://www.rtcgroup.com/arm/2008/ ARM Developers' Conference], Santa Clara Convention Center, Santa Clara, Calif., USA, October 7-9, 2008
* [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]
* [[BeagleBoard/contest|BeagleBoard contest]] #1: Create a cool BeagleBoard application and win a Rev C1! Closed, ran until January 9, 2009
* [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]]
* [[BeagleBoard/contest|BeagleBoard contest #2]], until February 27, 2009: Create a cool BeagleBoard application and win a Rev C2!
* [http://groups.google.com/group/beagleboard/browse_thread/thread/b15cf8a5797c73a2 Silica - Free TI - ARM OMAP Workshop], Brussels, Europe, March 31st 2009
* 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
* 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 BeagleBoard presentation]
* 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])
* 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'').
* 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.
* 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])

==BeagleBoard wiki pages==
* [[BeagleBoardJTAG|BeagleBoard JTAG]] and [[OMAP3530_ICEPICK|OMAP3530_ICEPICK]] about JTAG on BeagleBoard
* [[BeagleBoardOpenOCD|BeagleBoard OpenOCD]] has information about status and usage of open source JTAG software OpenOCD with Beagle
* [[Mount_BeagleBoard_Root_Filesystem_over_NFS_via_USB|Mount BeagleBoard root file system over NFS via USB]]
* [[BeagleBoardSugar|Sugar on BeagleBoard]]
* [[BeagleBoard/gst-openmax|BeagleBoard OpenMAX usage]]
* [[BeagleBoard/video|BeagleBoard video]]
* [[BeagleBoardOpenCV|Using OpenCV computer vision library with BeagleBoard]]
* [[U-boot_musb_gadget_support|U-boot musb gadget support]]
* [[BeagleBoard-JP|Japanese translation of this BeagleBoard page]]
* [[BeagleEPD|BeagleBoard E-Ink Platform Driver]]
* [[BeagleBoardFedora|Random hacking notes for getting Fedora 10 to kinda work with the BeagleBoard]]
* BeagleBoard specific [[BeagleBoard/GSoC|Google Summer of Code 2009]] page, [[BeagleBoard/Ideas-2009|GSoC project ideas]] and [[BeagleBoard/GSoC/Application|GSoc application]]
* [[BeagleBoard/DSP_Clarification|Info about the various Linux DSP systems for OMAP chips]]
* [http://www.hervanta.com/stuff/Beaglebot Beaglebot]: build an experimental robotics project with BeagleBoard
* [http://code.google.com/p/beagleboard/w/list code.google.com BeagleBoard wiki]
* '''[[BeagleBoard/contest|BeagleBoard contest]]'''
* [http://en.wikipedia.org/wiki/Beagle_Board Wikipedia BeagleBoard page]
* [http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board Android port for BeagleBoard]: Instructions for porting Android on BeagleBoard
* [[BeagleBoard/bangalore_user_meet |BeagleBoard Bangalore User Meet]]
* [[Zoom2Beginners|Zoom2 for Beginners]]
* [http://wh1t3s.com/2009/05/11/beagleboard-as-usb-mass-storage-device-via-usb-otg/ BeagleBoard as USB Mass Storage Device via USB OTG]
* [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm BeagleBoard as solar powered computer]
* [http://blog.makezine.com/archive/2009/02/blinking_leds_with_the_beagle_board.html Blinking LEDs with the BeagleBoard] from Make:Online
* [http://www.crashcourse.ca/wiki/index.php/BeagleBoard Robert's private BeagleBoard wiki] (please don't add anything there, do it here. It will help to avoid splittering. Thanks!)
* [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
* [http://www.syspire.de/node/3 Embedded Mediacenter] based on BeagleBoard (German)
* [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] with VFP-lite and NEON introduction
* [http://particolarmente-urgentissimo.blogspot.com/2009/09/beagleboard-setting-date-via-gps.html BeagleBoard setting date via GPS]
* [http://free-electrons.com/blog/beagle-labs/ Complete embedded Linux training labs] on the BeageBoard
* [[BeagleBoardPWM]] Details about PWM on the BeagleBoard.
* [[BeagleBrick]] software defined radio project

==BeagleBoard photos==
* [http://www.flickr.com/groups/beagleboard/pool/ BeagleBoard pictures at flickr]
* [http://www.flickr.com/photos/32615155@N00/2439256116/ BeagleBoard and USRP]
* [http://www.flickr.com/photos/nishanthmenon/2438406603/ Modify SDP3430 QUART cable for BeagleBoard]
* [http://www.flickr.com/photos/koenkooi/2695061759/ MythTV on BeagleBoard]

==BeagleBoard videos==
* [http://uk.youtube.com/watch?v=fL_XMieanSc BeagleBoard Beginnings]
* [http://www.youtube.com/watch?v=cXr-D1wROfQ BeagleBoard in the Living Room]
* [http://uk.youtube.com/watch?v=FuVwh_VrIxk BeagleBoard 3D, Angstrom, and Ubuntu]
* [http://uk.youtube.com/watch?v=TUYOjRGYeYU testsprite with BeagleBoard]
* [http://uk.youtube.com/watch?v=9Z4ZTovtFKk BeagleBoard LED demo]
* [http://uk.youtube.com/watch?v=R33dzREZGEk LCD2USB attached to a BeagleBoard]
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]
* [http://www.youtube.com/watch?v=-tUBXD-KRp4 BeagleBoard Running Angstrom (VGA) on DLP Pico Projector]
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on BeagleBoard working with Linux 2.6.27]
* Not on Beagle OMAP3530: [http://youtube.com/watch?v=5i9cWOK1spw Ubuntu 7.04 on on OMAP3430 SDP]
* [http://in.youtube.com/watch?v=nADn_vNVEKw BeagleBoard booting Android]
* [http://www.youtube.com/watch?v=UHQdUS0i-nw BeagleBoard, SGX, and libfreespace demo]

==BeagleBoard manufacturing==
* [http://www.youtube.com/watch?v=C-CwkjT9z_0&feature=related BeagleBoard Solder Paste Screening]
* [http://www.youtube.com/watch?v=9LLjDovIG2M&feature=related BeagleBoard Assembly Inspection]
* [http://www.youtube.com/watch?v=sbOZfBnoVnM&feature=related BeagleBoard Functional Test]
* [http://www.youtube.com/watch?v=cvDtXmJJcEI&feature=related BeagleBoard Reflow]
* [http://www.youtube.com/watch?v=W2o4NTASxN0&feature=related BeagleBoard Assembly at Circuitco]

=Other OMAP boards=
* OMAP 4430 Based 40X40 mm size [http://www.tianyeit.com CIP410] computer in package from [http://www.tianyeit.com Tianyeit]
* OMAP DM3730/OMAP3530 Based 40X40mm size [http://www.tianyeit.com CIP312] Computer In Package from [http://www.tianyeit.com Tianyeit]
* OMAP 4430 based [[PandaBoard]]
* OMAP-L138 Based [[Hawkboard]]
* OMAP3530 based [http://www.armkits.com/Product/devkit8000.asp DevKit8000] development board from [http://www.armkits.com Embest]
* OMAP3530 based [http://www.armkits.com/Product/sbc8100.asp SBC8100] Single-board computer from [http://www.armkits.com Embest]
* OMAP1 OMAP5912 (ARM9 + C5x DSP) based [[OSK|OSK]] board.
* 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].
* OMAP3 OMAP3530 based [http://www.openpandora.org/ Pandora]
* OMAP3 OMAP3503 based [http://www.gumstix.net/Overo/cat/Overo/115.html Gumstix Overo]
* 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)
* OMAP3 OMAP3430 based [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12013&contentId=28741 Software Development Platform (SDP)]
* OMAP3 OMAP3530 based board from [http://www.magniel.com/omap3.html Magniel Inc.]
* OMAP3 based [http://www.archos.com/products/imt/index.html?country=us&lang=en Archos 5, ARCHOS 5G and ARCHOS 7]
* OMAP3 OMAP35x based [http://www.logicpd.com/products/som/ti/omap35x OMAP35x SOM-LV]
* OMAP3 based [[Mini_Board|ICETEK-OMAP3530-Mini]], a Chinese BeagleBoard clone, with a [[MiniBoardFAQ|FAQ]]
* OMAP3 based [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], a German BeagleBoard clone
* OMAP3530 based [http://www.bsquare.com/products/hardware_solutions/3530.asp BSQUARE’s Dev Kit OMAP3530]
* OMAP3530 based [http://beaversource.oregonstate.edu/projects/cspfl/wiki/CSPFL_Hardware OSWALD]
* OMAP3 BeagleBoard-based [http://www.alwaysinnovating.com/touchbook/ Touch Book]
* OMAP3530 based [http://www.analogue-micro.com/Cobra3530.html Cobra 3530 OMAP3530 module ]
* OMAP3 based [http://www.kwikbyte.com/KBOC.html KwikByte 35XX System Module]
* OMAP3530 based [[DevKit8000]], a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard)
* OMAP3530 based [http://www.igep-platform.com/ IGEPv2 Platform], a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, Wi-Fi and Bluetooth.
* OMAP35x based [http://www.ultratronik.de/mmi-rechnerplattformen.html MMI4 from Ultratronik]
* OMAP35x based [http://www.technexion.com/index.php/tao-3530 TAO-3530 from TechNexion], also sold in North America through [http://www.robotcraft.ca/webshop/index.php?manufacturers_id=21 Robotcraft Systems]
* OMAP35x based [http://www.variscite.com/varomap35xxsbc.html VAR-OM35xxSBC from Variscite]
* OMAP35x based [[EGS3530]],a Chinese BeagleBoard clone from [http://www.ema-tech.com EMA]
* OMAP3 OMAP35x based [http://www.buglabs.net/products BUG] from Bug Labs, Inc.
* OMAP35x System-on-Module [[SOM3530]], the smallest(40x40x4 mm) OMAP35XX-based system on module in the world! (It is not-Gumstix Overo is smaller at 17 mm*58 mm)
* OMAP35x based [http://www.compulab.co.il/t3530/html/t3530-cm-datasheet.htm CM-T3530 from CompuLab]

=Subpages=
<splist
parent=
showparent=no
sort=asc
sortby=title
liststyle=ordered
showpath=no
kidsonly=no
debug=0
/>

BeagleBoard

2012-11-27T07:28:52Z

Yclinda666: /* JTAG */

[[Category: Linux]]
[[Category: OMAP]]
[[Category:Development Boards]]
[[Category: BeagleBoard]]

This page collects information about [http://beagleboard.org BeagleBoard.org's] open hardware embedded computer boards based on [http://www.ti.com/ TI's] [http://www.arm.com/ ARM] processors. Most of this material is applicable to the BeagleBoard and BeagleBoard-xM. See the [[BeagleBone]] page for information on that board.

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#ffffcc; align:right; ">
'''NEWS:'''
* Limited numbers of Pixel Qi LCD kits and LVDs kits are now available from [http://www.tincantools.com TinCanTools]
* [http://www.tincantools.com TinCanTools] has now discontinued [[BeagleBoard_Zippy2|Zippy2]], [[BeagleBoard_Trainer|Trainer Boards]] and [[BeagleBoard_Zippy|Zippy Boards]].
* [http://www.nxelec.com/products/hmi BeadaFrame] 7" LCD display kits for BeagleBoard and BeagleBone are available now!
* [http://www.chalk-elec.com/ 10" LCD LVDS plug-and-play bundle with capacitance touchscreen and ambient light sensor] is available in stock now!
* LVDS LCD add-on board [http://www.chalk-elec.com/ LVDS LCD] has been released and is available for order
* An [http://www.liquidware.com/shop/show/BB-BT/BeagleTouch OLED touchscreen module "BeagleTouch"] and [http://www.liquidware.com/shop/show/BB-BJC/BeagleJuice lithium battery module "BeagleJuice"] are now available from [http://www.liquidware.com/shop Liquidware]
</div>
 
=Events=
* [http://jefro.wordpress.com/open-source-conferences/ Jeff's list of open source conferences]

{| class="wikitable"
! Event
! Location
! Date
|-
| [http://makerfaire.com/newyork/2012/index.html Maker Faire New York]
| New York Hall of Science, Queens, NY, USA
| Sep 29 - 30, 2012
|-
| [http://www.t-dose.org/ T-Dose]
| Eindhoven, The Netherlands
| Oct 27 - 28, 2012
|-
| [http://e.ubmelectronics.com/armtechcon/index.html ARM Techcon]
| Santa Clara, CA, USA
| Oct 30 - Nov 1, 2012
|-
| [https://events.linuxfoundation.org/events/embedded-linux-conference-europe Embedded Linux Conference Europe]
| Barcelona, Spain
| Nov 5 - 7, 2012
|}

=Hardware=

The BeagleBoard 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 ~600 MHz 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.

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.

==Components==

{|border=0
!Top view of rev B:
!Top view of rev C:
|-
|[[Image:Bb revb top numbered.jpg]]
|[[Image:Bb revc top numbered.jpg]]
|-
|}
{|border=1
!No.
!Name
!Comment
|-
|'''1'''
|[http://www.ti.com/omap35x OMAP3530] processor + 256 MB NAND

+ 128 MB DDR (rev B)

+ 256 MB DDR (rev C)
|PoP: Package-On-Package implementation for Memory Stacking
[http://www.micron.com/products/partdetail?part=MT29C2G24MAKLAJG-6%20IT 256 MB NAND/128 MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1435-ND DigiKey]

([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])

[http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for Beagle Board]
|-
|'''2'''
|[http://focus.ti.com/docs/prod/folders/print/tfp410.html DVI chip (TFP410)]
|
|-
|'''3'''
|[[BeagleBoard#DVI|DVI-D]]
|Connection via HDMI connector
|-
|'''4'''
|[[BeagleBoard#JTAG|14-pin JTAG]]
|1.8V only!
|-
|'''5'''
|Expansion connector: I2C, I2S, SPI, MMC/SD
|User must solder desired header into place
|-
|'''6'''
|[[BeagleBoard#User_button|User button]]
|Allows setting boot order.
|-
|'''7'''
| Reset button
|
|-
| '''8'''
|[[BeagleBoard#EHCI|USB 2.0 EHCI HS]]
|Rev A and B: not working, unpopulated

Rev C: populated and working
|-
|'''9'''
|SD/MMC+
| SDHC cards are supported
|-
|'''10'''
|[[BeagleBoard#RS232|RS-232 serial]]
|
|-
|'''11'''
|Alternate power
|normally powered by USB (unmounted on REV Ax boards, see [[BeagleBoard#Errata|errata]])
|-
|'''12'''
|[[BeagleBoard#OTG|USB 2.0 HS OTG]]
|Mini-AB connector. Board can be powered from port.
|-
|'''13'''
|Stereo In
|
|-
|'''14'''
|Stereo Out
|
|-
|'''15'''
|S-Video
|
|-
|'''16'''
|TWL4030 (Rev A thru C2 inc.)
[http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] (Rev C3 onwards)
|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.
|-
|'''17'''
|LCD
|only rev C
|-
|'''18'''
|USB power
|
|-
|'''19'''
|Host PHY
|
|-
|'''20'''
|32 kHz
|
|-
|'''21'''
|12 MHz
|
|-
|'''22'''
|RS-232 XVCR
|
|-
|'''23'''
|PWR SW
|
|-
|'''24'''
|VBAT
|
|-
|}

* Board size: 3" x 3" (about 76.2 x 76.2 mm)
* Weight: ~37 g
* Currently six-layer PCB; target: four layer PCB

'''Bottom of rev B:'''

[[Image:Beagle_bottom.jpg]]

See [http://www.flickr.com/photos/jadon/sets/72157606050144396/ jadonk's photostream] for some more detailed BeagleBoard pictures.

==Manual==

See [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)].

==Schematic==

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.

==Layout==

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.

==Errata==

# ''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 5 V.) See [http://www.flickr.com/photos/koenkooi/2512038988/ Koen's Beagleboard powermod picture] with short descriptions, too.
# ''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.
# ''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.
# ''Boards revision < A5 only'': There is an issue where on some boards the 1.8 V 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 1 uH. 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" (== 100 uH) they are wrong and have to be exchanged.
# ''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.
# ''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.2 µF 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!
# ''Boards revision A and < B5'': There is some issue with a 32 kHz clock depending on system configuration used to clock some OMAP3 peripherals. From this e.g. GPIOs, GPTIMERs, and USB on BeagleBoard might be affected. See [http://code.google.com/p/beagleboard/issues/detail?id=22 Issue 22]. The symptom from this is that after booting the Linux kernel, the 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 the 32 kHz timer to clock Linux, instead use the MPU timer. (B) Hardware workaround: Remove [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard capacitor C70], which improves the 32 kHz 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.
# ''Random boards, quite rare, revision < B6'': Some random boards and quite rare, show directly after purchasing broken serial communication from the 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 the 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.

For additional (software) issues and enhancement requests see [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker], too.

Note: BeagleBoard revision B6 uses different package for U9/U11.

==Clocking==

Some [http://www.beagleboard.org/irclogs/index.php?date=2008-07-08#T21:12:23 notes] about (ARM processor) clock rates at BeagleBoard:

* ARM Cortex-A8 processor is currently clocked at 500 MHz
* 500 MHz is the default used because it is a balance of performance and longevity
* For OMAP35x 600 MHz is maximum recommended
* An additional 720 MHz overdrive is supported only on high-speed grade OMAP3530/25 devices as fitted to the BeagleBoard C4
* At 600 MHz or higher OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy
* Higher than 600/720 MHz is out of specification and no guarantee it will work at all (or not damage itself)

* 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:

{| border="1"
||'''ARM'''||'''DSP'''||'''core voltage'''
|-
|720 MHz||520 MHz||1.35 V
|-
|600 MHz||430 MHz||1.35 V
|-
|550 MHz||400 MHz||1.27 V
|-
|500 MHz||360 MHz||1.2 V
|}

* 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.
* 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].
* There is a thermal monitor in the core, you could use to scale frequency up and down

To set the CPU clock to 600 MHz, there are two options. Both '''do not''' adjust the voltage, so the system may become unstable:

* The U-Boot command "mw 48004940 0012580c" will temporarily set the CPU clock to 600 MHz (not permanent over reset).
* To permanently set the CPU clock to 600 MHz, include the above command in the "bootcmd" variable or equivalent script.

* To set the DSP clock to 430 MHz use "mw 48004040 0x0009ae0c".

==Power management==

* Detailed OMAP3 Power Management Information can be found [[OMAP_Power_Management|HERE]]
* 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]
* Russ' Beagle HW modifications resulted in [http://groups.google.com/group/beagleboard/browse_thread/thread/197a8ef6b46cc828 8 mW sleep for Beagle Board]

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).

==DLP Pico projector==

Texas Instruments is developing a Pico Video Projector Kit (PVPK) as a peripheral for the BeagleBoard. The stand-alone pico projector will support VGA resolution (640 x 480 pixels), 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.

It is available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23836-ND DigiKey] for $349.

See [http://blog.makezine.com/archive/2009/01/tis-beagleboard-and-dlp-pico-projec.html article from Make], too.

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].

==Interfacing to Raw LCD Panels==

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:

* [[BeagleBoardRawLCD|interfacing to Raw LCD Panels]] article
* [http://digitalsurveyinstruments.com/beagleperiphials/hdmi2parallel/doc/index.htm HDMI-to-parallel] workaround method
* [http://www.harbaum.org/till/dvi2par/index.shtml dvi2par cheap DIY HDMI-to-parallel converter]

=Availability=

BeagleBoard Rev. C3 boards are available from

* [http://www.mouser.com/beagleboard Mouser]
* [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].

BeagleBoard Rev. C4 boards are available from:

* [http://www.liquidware.com/shop/show/BB-C4/BeagleBoard+C4 Liquidware]

Note: For non-US Digi-Key free shipping orders:

* 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
* Select ''Order Online'' for your country
* Add quantity ''1'' and part number ''296-23428-ND''
* Click ''Add to order''

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.

Note: Some users report that they got some questions from DigiKey to be answered before board shipping is done.

Note: While you get free shipping, most probably you have to pay tax, for example, 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.

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).

Note: German (Europe) users can order through German shops, too. For higher price, though.
* [http://shop.embedded-projects.net/product_info.php/info/p159_BeagleBoard--OMAP-3-.html Embedded Projects Shop] sells BeagleBoard for EUR 199.00 + shipping.
* [http://www.handheld-linux.com/wiki.php?page=Beagle%20Board Handheld-Linux] sells BeagleBoard for EUR 159.00 + shipping.
* [http://www.watterott.com/en/BeagleBoard Watterott electronic] sells BeagleBoard for EUR 142,80 + shipping.

See below for ''hardware'' differences of the revisions. There are no ''software'' differences.

==Revision A==

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.

==Revision B==

Revision B is same as revision A, except
* fix for shorted LEDs 0/1
* fix for wrong power jack pinout
* revision B6 uses different package for U9/U11
Still has USB HOST (EHCI) failures. USB HOST (EHCI) connector isn't mounted.

There are 4 revisions of the B board in the field: B4, B5, B6 and B7.

The most notable difference is the use of the ES3.0 silicon in B6 and B7, other changes are not relevant to software developers.

==Revision C2==
Revision C2 is same as revision B7 except:
* USB HOST (EHCI) is operational on revision C2, with standard USB A female connector.
* Add interface for raw LCDs ([http://groups.google.com/group/beagleboard/msg/2e82c3ed6061d9d2 mockup])
* 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:
** 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
* Power measurement feature
* Uses [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] OMAP power controller instead of TWL4030
* 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])
* Revision detection (to be able to identify C2 board from older boards by software, for example, for different pin mux)
* 256 MB RAM ([http://groups.google.com/group/beagleboard/msg/3a38d0f21cefd6b1?hl=en message]) (and still 256 MB NAND like rev B)

Note: Revision C2 is the first production version, and all orders from Digi-Key are shipped as Rev C2.

==Revision C3==
As revision C2 boards are [http://groups.google.com/group/beagleboard/msg/e41d3c97aa7d4951 sold out], revision C3 will ship now.

Revision C3 is same as revision C2 [http://groups.google.com/group/beagleboard/msg/037318fbc44139d5 except]:
* Optional RTC [http://parts.digikey.com/1/parts/1454-battery-lith-coin-3v-12-5mm-vert-vl-1220-vcn.html VL1220 series] backup battery
* Mounting holes conected to ground
* Slightly improved S-Video

==Revision C4==
Revision C4 boards are the same as Revision C3 except:
* Processor is 720 MHz capable OMAP3
* Improved USB Host PHY power rails

==Revision C5==
Revision C5 boards are the same as Revision C4 [http://circuitco.com/support/index.php?title=BeagleBoard#Image_Files except]:
* The memory chip is upgraded to 512 MB NAND

==Clones==
===EBVBeagle===
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/].
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.
More information in [http://www.ebv.com/en/press-print/news-pr/details/news//press-releas-54.html official press release].

===Mini Board===
[[Mini_Board|ICETEK-OMAP3530-Mini]] is a Chinese BeagleBoard clone.

===DevKit8000===
[http://www.armkits.com/Product/devkit8000.asp DevKit8000] is from [http://www.armkits.com Embest], China. It is a compact development board based on TI OMAP3530.

===DevKit8500D===
[http://www.armkits.com/Product/devkit8500d.asp DevKit8500D] is from [http://www.armkits.com Embest], China. It is a high-performance development board based on TI DM3730.

===SBC8530===
[http://www.armkits.com/Product/sbc8530.asp SBC8530] is from [http://www.armkits.com Embest], China. It is a compact single board computer based on TI DM3730 and features UART, 4 USB Host, USB OTG, Ethernet, Audio, TF, WiFi/Bluetooth, LCD/VGA, DVI-D and S-Video.

===Tianyeit CIP312===
[http://www.tianyeit.com CIP312 ] is from [http://www.tianyeit.com Tianyeit], China. It is has many functions ,such as WLAN/BT/ dual 10/100M Ethernet Contoller-LAN9221I/MCP2512 CAN BUS/ Touch Screen Controller/USB HUB/USB host/USB OTG Etc. Our module is base on DM3730/omap3530 all functions are packaged in 40x40x3.5 mm package ; For detailed information, please visit our website
[[Image:http://www.tianyeit.com/download/cip312.jpg]]

===IGEPv2===
[http://www.igep-platform.com/ IGEPv2 Platform] is a Spanish BeagleBoard clone, slightly larger, with additional peripherals like, for example, Ethernet connector, Wi-Fi and Bluetooth.
* 720 MHz OMAP3 Processor
* 512 MB RAM / 512 MB Flash

===SOM3530===
[[SOM3530]] is a Chinese BeagleBoard clone [[System-on-Module]], dimensions 40x40x4 mm, maybe the smallest [http://wiki.davincidsp.com/index.php?title=OMAP3_Overview OMAP3530]-based modules in the world! Including 100 Mbit/s high perfomance Ethernet I/F.

==BeagleBoard-based products==
* [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]

==Beagle case==

*[http://specialcomp.com/beagleboard/ Special Computing acrilyic case]
** [http://groups.google.com/group/beagleboard/browse_thread/thread/1c82316019633e51 SketchUp 3D model]
* [http://www.esawdust.com/product/encl-dh-r1/ eSawdust metal case]
* [http://aspectrt.web.fc2.com/support/ Aspect metal case for BeagleBoard-xM]

=Adapters=

For quite detailed information about all BeagleBoard peripherals see [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)].

See [[BeagleBoardPeripherals| BeagleBoard peripherals and adapters page]] for useful add ons for BeagleBoard.

==Expansion boards==
See [[:Category:BeagleBoard_Expansion_Boards]] for more information about expansion boards

[http://www.nxelec.com/products/hmi BeadaFrame] - A 7" TFT LCD Screen with resistive touch for BeagleBoard and BeagleBone. A plastic (ABS) frame is included also for ease of mounting.

[http://www.chalk-elec.com LVDS LCD] - small add-on board to connect any LVDS LCD panel (like those in notebooks) to BeagleBoard (-xM) and PandaBoard. Also, they offer plug-and-play bundle with 10" 1024x600 LCD with capacitance touchscreen and ambient light sensor for automatic brightness control. The board is open-source.

[http://www.liquidware.com/shop/show/BB-BT/BeagleTouch BeagleTouch] - A modular "shield" that snaps on top of the BeagleBoard and provides a touch-screen OLED interface

[http://www.liquidware.com/shop/show/BB-BJC/BeagleJuice BeagleJuice] - A lithium ion battery module that snaps on the back of the BeagleBoard that powers the BeagleBoard.

[http://www.picklejar.org/lox LOX] - A dual channel internet linking radio (Ham, GMRS, etc.) interface that can run any combination of two repeaters, simplex nodes, or remote bases.

==JTAG==

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.
See [[BeagleBoardJTAG]] for more information.

The [http://www.armkits.com/Product/xds100.asp XDS100v2 USB JTAG Emulator] is available from [http://www.armkits.com Embest] which is the second release of the XDS100 JTAG emulator technology supporting debug of a variety of TI devices..

==RS-232==

The pinout on the BeagleBoard 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.

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.

==USB-to-Serial Converter==

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.

==USB==
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.

===EHCI===
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.

According to the BeagleBoard System Reference Manual Rev C2, the EHCI port can source 5 V at 500 mA 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 5 V external power supply. If the BeagleBoard is powered through the OTG port, the EHCI port sources an "extremely limited" ampount of power (probably 100 mA 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.]

'''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.8 V rail between the OMAP3530 and the power chip was getting noisy. Suggested solution (works on many boards) is adding a 22 µF 0805 package SMT capacitor atop the existing capacitor on C97. If SMT parts are not available, some boards can be repaired by a 22 µF 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.

===OTG===
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.

When using the OTG port in host mode, you must power the BeagleBoard using the +5 V 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.

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".

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.]
<table>
<tr><td>
Since the right cables might be hard to get, you simply can
* 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.
or
* 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.
</td><td>[[Image:usb_otg.png]]</td></tr></table>
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.
See Figure 20 in the BeagleBoard System Reference Manual Rev C2.2.

==DVI==

DVI-D connection on BeagleBoard uses an [http://en.wikipedia.org/wiki/HDMI HDMI connector]:

''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.''

BeagleBoard can be connected to a DVI monitor using an HDMI male to DVI male cable.

The BeagleBoard does not connect the HDMI shell to ground or any other BeagleBoard signal. This is not a problem with high-quality HDMI to DVI cables that connect all the ground wires. However, there are lots of cheap HDMI to HDMI cables that do not connect the ground wires and only use the shell as a combined shield and ground. To use one of these you would need to connect the BeagleBoard's HDMI shell to ground. The BeagleBoard-xM connects the HDMI shell to frame ground, which is in turn connected to system ground through R119. For more information, see this thread: [http://groups.google.com/group/beagleboard/browse_thread/thread/861da101804da56b].

== Arduino ==

* [[BeagleBoard_Trainer|Trainer Board]] from [http://www.tincantools.com TinCanTools] has an Arduino compatible Atmel AVR on board
* Arduino [http://arduino.cc/en/Main/ArduinoBoardNano Nano] uses an FTDI FT-232 based interface which is supported by the ftdi_sio kernel driver- [[BeagleBoard_with_Arduino|How To Notes]]
* Arduino [http://arduino.cc/en/Main/ArduinoBoardUno Uno] uses a Atmel ATmega8U2 based interface which is supported by the cdc_acm kernel driver - [[BeagleBoard_with_Arduino|How To Notes]]

=BootRom=

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 the Initialization chapter of [http://www.ti.com/lit/pdf/spruf98 SPRUF98].

==User button==

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):

* User button ''not'' pressed: NAND -> USB -> UART -> MMC
* User button ''is'' pressed: USB -> UART -> MMC -> NAND

Technically speaking, the user button configures pin SYS.BOOT[5]. See the Initialization chapter of [http://www.ti.com/lit/pdf/spruf98 SPRUF98] for more details.

==Serial and USB boot==

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 environment from Linux]].

===OMAP U-Boot Utils===

Nishanth' [http://code.google.com/p/omap-u-boot-utils/ OMAP U-Boot Utils] provide

* ''pserial'' - OMAP specific utility which downloads a file in response to ASIC ID over serial port.
* ''pusb'' - OMAP specific utility which downloads a file in response to ASIC ID over USB connection.
* ''ucmd'' - Send a command to U-Boot and wait till a specific match appears.
* ''ukermit - Download a file from host without using kermit to U-Boot.

See [http://nishanthmenon.blogspot.com/ Nishanth' blog] and [http://groups.google.com/group/beagleboard/browse_thread/thread/c5bfb1b8ed528b52# announce mail], too.

===Serial boot===

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 is one tool for UART boot:

* [http://groups.google.com/group/beagleboard/browse_thread/thread/80ad3da0eb2aa555 Linux C utility] (not working yet with below target code)

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.

===USB boot===

There is a patch to x-loader to allow it to do a USB boot. It can boot all the way to a Linux login.
It's is used with a new version of omap3_usbload.

* [http://members.efn.org/~rick/pub/x-loader-usb.tar.bz2 x-loader-usb]

Besides Nishanth' ''OMAP U-Boot Utils'', for USB boot, there is currently one (experimental) tool to boot BeagleBoard over USB:

* [http://groups.google.com/group/beagleboard/browse_thread/thread/2b9e99886bb7a747 Linux C utility]

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.

See the [[BeagleBoardRecovery#USB_recovery|USB recovery section]] on how to use USB boot for board recovery.

==NAND boot==

See [[BeagleBoardNAND|NAND boot]] article.

==MMC/SD boot==

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.

===MMC/SD formatting===

As described in above MMC/SD boot description, you have to ''create a bootable partition on MMC/SD Card''. This can be done using, for example, Windows or Linux tools.

'''Windows'''

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.

You can download this tool from [http://www.sysanalyser.com/sp27213.exe here]. Make sure the version is 2.0.6; newer versions may not work.

'''Linux'''

Please see [http://wiki.omap.com/index.php?title=MMC_Boot_Format OMAP3 MMC Boot Format].

===Dual partition card===

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.

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 (for example, in U-Boot using ''setenv bootargs''):

console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait

===U-Boot booting===

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 the BeagleBoard. For example (output from terminal program with 115200 8N1):

...40T.........XH.H.U�..Instruments X-Loader 1.41
Starting on with MMC
Reading boot sector

717948 Bytes Read from MMC
Starting OS Bootloader from MMC...

U-Boot 1.1.4 (Apr 2 2008 - 13:42:13)

OMAP3430-GP rev 2, CPU-OPP2 L3-133MHz
TI 3430Beagle 2.0 Version + mDDR (Boot ONND)
DRAM: 128 MB
Flash: 0 kB
NAND:256 MiB
In: serial
Out: serial
Err: serial
Audio Tone on Speakers ... complete
OMAP3 beagleboard.org #

Using this U-Boot prompt, you now can start kernel uImage stored on MMC card manually:

OMAP3 beagleboard.org # mmc init
OMAP3 beagleboard.org # fatload mmc 0:1 0x80000000 uimage
OMAP3 beagleboard.org # bootm

If you like to make that happen every boot:

OMAP3 beagleboard.org # set bootcmd 'mmc init ; fatload mmc 0:1 0x80000000 uimage ; bootm' ; saveenv

Note: saveenv will not work on the xM. You will need to create a <tt>boot.scr</tt> file in the FAT partition for the xM. See [https://fedoraproject.org/wiki/Architectures/ARM/BeagleBoardxMSDCard#Set_up_u-boot set up u-boot] 
Note2: after a saveenv, u-boot will not read your boot.scr any more. To make it use boot.src again, type "nand erase" in the u-boot promt (works on C4, older versions may need a "nand unlock" too).

===Barebox booting===

You can also use barebox to boot.

On barebox you will have to generate it two time.

The first time as a x-loader via defconfig: omap3530_beagle_xload_defconfig

The second time as the real boot loader omap3530_beagle_defconfig

=Code=

Code and binaries for BeagleBoard are available at various places.

==Binaries==

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.

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:

* [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.bin u-boot.bin]
* [http://www.angstrom-distribution.org/demo/beagleboard/MLO MLO]
* [http://www.angstrom-distribution.org/demo/beagleboard/uImage uImage]
* [http://www.angstrom-distribution.org/demo/beagleboard/Angstrom-Beagleboard-demo-image-glibc-ipk-2009.X-test-20090104-beagleboard.rootfs.tar.bz2 rootfs]

See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat beagle wiki] on how to setup your SD card to use all this goodness.

==Source==
'''Update on April 23 - 2010''': Sources for the X-Loader and U-Boot that ship on the BeagleBoard can be found at [http://gitorious.org/beagleboard-validation/ http://gitorious.org/beagleboard-validation/]. The U-Boot version found in that repository supersedes the one found at [http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/ http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/].

'''Update on March 3 - 2011''': Sources for the SD card shipped with revisions Ax and Bx of the BeagleBoard-xM are in the Angstrom Distribution. The script used to build the sources is documented at http://code.google.com/p/beagleboard/wiki/BeagleBoardDiagnosticsNext. The sources at http://gitorious.org/beagleboard-validation are meant to mimic what was used in the OpenEmbedded-based build.

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.

===X-Loader===

Steve did some work to consolidate and update X-Loader from various sources and put it in a [http://gitorious.org/x-load-omap3 X-Loader git repository]. Get it by

git clone git://gitorious.org/x-loader/x-loader.git xloader
cd xloader/

Build:

make distclean
make omap3530beagle_config
make

Result will be a ~20k sized ''MLO'' in the main directory. This is the signed x-loader and is ready for use.

===U-Boot===

[http://www.denx.de/wiki/U-Boot/WebHome Mainline U-Boot] has good support for BeagleBoard (except for revision C4; see note below). Get it by:

git clone git://git.denx.de/u-boot.git u-boot-main
cd u-boot-main
git checkout --track -b omap3 origin/master

Build (assuming [[ARMCompilers#Recommendations|Code Sourcery GCC]]):

make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper
make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_beagle_config
make CROSS_COMPILE=arm-none-linux-gnueabi-

Result will be a ~160 KB sized ''u-boot.bin'' in the main directory.

Note: Due to (patch and binary) size, the 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].

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:

git clone git://gitorious.org/u-boot-omap3/mainline.git u-boot-omap3
cd u-boot-omap3
git checkout --track -b omap3-dev origin/omap3-dev

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]

Note: For beagleboard revision C4, above sources will not work. USB EHCI does not get powered, hence devices are not detected...
Get a patched version of u-boot from http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/
('''Update on April 23 - 2010''': This repository has been superseded by the U-Boot version found at [http://gitorious.org/beagleboard-validation/ http://gitorious.org/beagleboard-validation/])

Note: If you want to activate I²C from the expansion header, modify board/ti/beagle/beagle.h :

MUX_VAL(CP(I2C2_SCL), (IEN | PTU | EN | M4)) /*GPIO_168*/
MUX_VAL(CP(I2C2_SDA), (IEN | PTU | EN | M4)) /*GPIO_183*/

to

MUX_VAL(CP(I2C2_SCL), (IEN | PTU | DIS | M0)) /*I2C2_SCL*/
MUX_VAL(CP(I2C2_SDA), (IEN | PTU | DIS | M0)) /*I2C2_SDA*/

===Linux kernel===

[http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap.git;a=summary Git repository] of [http://muru.com/linux/omap/ OMAP Linux kernel] contains Beagle support. Get it by:

git clone git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git linux-omap
cd linux-omap

Build:

make distclean
make ARCH=arm omap2plus_defconfig
make ARCH=arm menuconfig # Only needed if you want to change the default configuration
make ARCH=arm uImage

The result will be a ''uImage'' in ''arch/arm/boot/'' directory.

'''Note: The following does not work. There is no defconfig "omap3_beagle_defconfig" nor any omap3 in the tree.'''

If you use the OE toolchain and want to build outside of the OE tree you should do

ARCH=arm
export ARCH
PATH=~/oe/tmp/cross/armv7a/bin:~/oe/tmp/staging/i686-linux/usr/bin:$PATH # add cross tools to your path
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- distclean
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- omap3_beagle_defconfig
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- menuconfig # only needed if you want to change the default configuration
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage

Note: the staging dir in the path is for mkimage. If you've built a kernel before with oe, the program should be there

Note: If you are interested in kernel development have a look to [[BeagleBoardLinuxKernel|manually compiling BeagleBoard kernel]], too.

===Experimental kernel patches and hacks===

Some BeagleBoard developers maintain their own kernel experimental patches and hacks not ready for upstream:

* [http://veter-project.blogspot.com/2012/03/comfortable-kernel-workflow-on.html Build Angstrom 2.6.38 Kernel] to compile kernel modules natively, see [https://groups.google.com/forum/?fromgroups#!searchin/beagleboard/sam/beagleboard/eg6zYMcdMMA/KA3y0CS6n5cJ Angstrom package to natively compile kernel modules post] for corrections to the how-to.
* [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] '''(Broken Link)'''
* [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. '''(broken link)'''
* [http://git.mansr.com/?p=linux-omap;a=summary Mans' kernel tree], a clone of the main OMAP Git repository with additional patches, mainly display & framebuffer related. '''(Link to Unknown Project)'''
* [http://www.bat.org/~tomba/linux-omap.html Tomi's kernel tree], a clone of the main OMAP Git repository with display sub-system patches, replacing the entire display driver with one that is the likely direction moving forward.

=Compiler=

TI OMAP3530 processor on BeagleBoard contains an ARM Cortex-A8 general purpose processor and a TMS320C64x+ DSP.

==ARM==

There is broad compiler support, including GCC - please see [http://www.elinux.org/ARMCompilers ARM Compilers]

==C64x+ DSP==

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).

Note: my.TI account required. You may create an account [https://my.ti.com here]

Note: An pld c6000 Linux compiler is available on the [ftp://ftp.ti.com/pub/cs/linux_cgt500.tar.gz TI FTP site]. It does NOT support c64x+ core in OMAP3 devices. Not recommended.

You can also use 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.

See [[BeagleBoard/DSP_Howto| BeagleBoard DSP howto]] for information about how to use the DSP.

=Cortex A8 ARM features =

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.

It includes a floating point unit (ARM VFPv3 architecture) and the ARM NEON SIMD instruction set.

See [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] article for an introduction into VFP-lite and NEON.

===ARM NEON===

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:
* 64-bit signed/unsigned
* 32-bit signed/unsigned
* 32-bit single precision floating point
* 16-bit signed/unsigned
* 8-bit signed/unsigned

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.

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].

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].

NEON is used by various opensource projects:
* [http://www.libav.org/ Libav] - libavcodec used by mplayer, omapfbplay, and many other Linux applications
* libpixman - used by X.org and Mozilla & Webkit browsers to render text and graphics
* [http://www.bluez.org/ Bluez] - official Linux Bluetooth stack
* [http://eigen.tuxfamily.org/ Eigen2] - C++ template library for linear algebra (matrix math, etc.)
* [http://www.webmproject.org/code/ Webm] - Google's new opensource video codec

Compilation tools support for NEON:
* ARM RVDS
* GCC
* [http://blog.llvm.org/2010/04/arm-advanced-simd-neon-intrinsics-and.html LLVM]

=== ARM Cortex-A8 Floating Point ===

There are two types of instructions in the ARM v7 ISA that handle floating point:

1) '''VFPv3''' Floating point instruction set (used for single/double precision scalar operations).
These is used by GCC for C floating point operations on 'float' and 'double' since ANSI C can only describe scalar floating point, where there is only one operation at a time.

2) '''NEON''' [http://www.arm.com/products/multimedia/neon/ NEON] vectorized single precision operations (two values in a D-register, or four values in a Q-register)
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.

ARM Cortex-A processors have separate floating point pipelines that handle these different instructions.

On Cortex-A8, the designers' focus was on the NEON unit performance which can sustain one cycle/instruction throughput (processing two single-precision values at once) for consumer multimedia. 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.

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:
* Use GCC with -ftree-vectorize (possibly modify source code to make it vector friendly)
* Use NEON instrinsics (#include <arm_neon.h>, float32x2_t datatype and vmul_f32() etc)
* Use NEON assembly language directly

On Cortex-A9, there is a much higher performance floating point unit which can sustain one cycle/instruction throughput, with low result latencies. OMAP4 uses dual-core Cortex-A9+NEON which gives excellent floating-point performance for both FPU and NEON instructions.

=Board recovery=

If you played, for example, with the contents of the [http://www.sakoman.net/omap3/flash%20procedure.txt NAND], it might happen that the BeagleBoard doesn't boot any more (without pressing user button) due to broken NAND content. See [[BeagleBoardRecovery|BeagleBoard recovery]] article how to fix this. Do not panic and think you somehow 'bricked' the board unless you did apply 12 V to it.

=Development environments=

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.

==OpenEmbedded==

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]],[[BeagleBoardOpenEmbeddedDevelopment|OpenEmbedded development]] and [http://wiki.openembedded.org/index.php/Getting_Started OpenEmbedded getting started] as well.

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''.

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.

===One very important note:===

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:
* 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 information on making the SD card.
* Put the SD card in the BeagleBoard, and boot up to the U-Boot prompt.
* Do the first six instructions in the [http://code.google.com/p/beagleboard/wiki/BeagleNANDFlashing Flashing Commands with U-Boot] section.
* Reboot the BeagleBoard to see that the new X-Loader is properly loaded.

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.

==Eclipse==
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]. Information on how RSE is used for, for example, Gumstix development is described in [http://groups.google.com/group/beagleboard/browse_thread/thread/509831f7c24cb79f# this post].

See also [[BeagleBoardEclipse|Using Eclipse with Beagle]] (for JTAG debugging).

==Android==
The [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.

There are several resources for Android on OMAP (Beagle) available:

'''OMAPZOOM'''

You can find Android port for OMAP ZOOM architecture on [https://gforge.ti.com/gf/project/omapandroid/ OMAPZoom.org's wiki page on Android].

'''EMBINUX'''

[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™] Team. The [http://labs.embinux.org/git/ source code] and [http://www.embinux.com/download_beagle.php binaries] are available for download and review.

Detailed instructions, for porting Android on BeagleBoard, are available [http://labs.embinux.org/index.php/Main_Page here]. Current release supports input devices (keyboard/mouse), network and sound.

You can [http://in.youtube.com/watch?v=nADn_vNVEKw watch Android booting] on BeagleBoard.

'''Android on OMAP wiki'''

Wiki page for Andorid on OMAP can be found [[Android on OMAP|here]].

'''0xdroid'''

[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.

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].

You can watch the 0xdroid demo video on the BeagleBoard:
* [http://www.youtube.com/watch?v=v6wdTOHrwQw 0xdroid demo video (1)]
* [http://www.youtube.com/watch?v=ol9LWBKXXwQ 0xdroid demo video (2)]
* [http://www.youtube.com/watch?v=OGpYk1p1UPI 0xdroid demo video (3)]

==Mamona==

[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 BeagleBoard.

==Ubuntu==

See [[BeagleBoardUbuntu|Ubuntu (ARM)]] installation guide how to install Ubuntu (ARM) on BeagleBoard.
* [[BeagleBoardLucid]] Details about Ubuntu Lucid on the BeagleBoard.
* [[BeagleBoardUbuntuKernel]] Details about the Ubuntu Kernel on the BeagleBoard.
* [[BeagleBoard Ubuntu]]
* [[BeagleBoardUbuntuKarmic]]

==Debian ARM==

See [[BeagleBoardDebian|Debian (ARM)]] installation guide how to install Debian (ARM) on BeagleBoard.

==GeeXboX ARM==

See [[GeeXboX|GeeXboX (ARM)]] installation guide how to install GeeXboX on BeagleBoard (including clones).

==Scratchbox==

[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 introduction], too.

=Software hints=

This section collects hints, tips & tricks for various software components running on BeagleBoard.
* [[RPM_jffs2_issue]]

==QEMU==

[[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.

==Linux hints==

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:

* Switching video output between DVI-D and S-Video
* Disabling framebuffer blanking
* Listing USB devices

==lmbench==

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 BeagleBoard.

==Mediaplayer (FFmpeg)==

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 BeagleBoard. Includes compiler hints and patches.

==Java==

===Open source===

When using the [[BeagleBoard#OpenEmbedded|OpenEmbedded]]-based Angstrom image you have the following options of Java support:
* JamVM + GNU Classpath (small vm, fast interpreter, J2SE-like)
* Cacao + GNU Classpath (JIT compiler, J2SE-like)
* PhoneME Advanced Foundation (JIT compiler, CDC)

Java support in OpenEmbedded/Angstrom ([http://wiki.openembedded.net/index.php/Java details]) is provided voluntarily through [http://jalimo.org Jalimo].

See a [http://groups.google.com/group/beagleboard/browse_thread/thread/102f627253919783# post at mailing list], too.

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.

The recipes offer the following functionality:

* OpenJDK + Hotspot (Zero port) (all J2SE functionality, including JVMTI, interpreted only)
* OpenJDK + Cacaco (all J2SE library features, missing JVMTI, decent JIT compiler)
* OpenJDK + Hotspot (Shark port) (not working yet)

[http://camswl.com/ Edward Nevill] from ARM Ltd. is working on interpreter optimization in Zero for ARM.

People interested in getting this stuff working better should contact people on:
* [http://evolvis.org/mail/?group_id=11 Jalimo Mailinglist]
* [http://mail.openjdk.java.net/mailman/listinfo/distro-pkg-dev Icedtea Mailinglist]

You should also check out IcedTea's [http://iced-tea.org/wiki/FrequentlyAskedQuestions FAQ].

===Oracle Java===

As of August 2012, there is a binary version of Oracle JDK 7 available for Linux/ARM under a free (but not open source) license. More information:
* [http://www.oracle.com/technetwork/java/javase/downloads/index.html Download on java.oracle.com]
* [http://www.oracle.com/technetwork/java/javase/7u6-relnotes-1729681.html#LinuxARM Release notes for JDK 7 Update 6]
* [http://www.oracle.com/us/corporate/press/1735645 Original announcement]
* [https://blogs.oracle.com/henrik/entry/oracle_releases_jdk_for_linux Oracle blog with FAQ]
* [http://www.oracle.com/technetwork/java/javase/terms/license/index.html Oracle Binary Code License]

Supported features:
* Java SE 7 compliant
* Almost all development tools from the Linux/x86 JDK
* Client and server JIT compilers
* Swing/AWT support (requires X11R6)
* Softfloat ABI only

Oracle states in the [https://blogs.oracle.com/henrik/entry/oracle_releases_jdk_for_linux FAQ] that they are working on hard float support, as well as a JavaFX 2 port to Linux/ARM.

== Booting Android (TI_Android_DevKit) from a USB stick ==
'''Please note'''
* This procedure was tested on BeagleBoard-xM revision B(A3)
* An SD card will be still needed to load the kernel.
* An SD card will contain boot parameters for the kernel to use a USB stick as the root filesystem

'''Procedure'''
# Download Android Froyo for BeagleBoard-xM from [http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_00_00/index_FDS.html TI]
# Follow the installation procedure for an SD card card.
# Test if Froyo is working with your BeagleBoard-xM with an SD card.
# You will notice that Android has a slow performance. That is why we will install root filesystem on a USB stick.
# Format your USB stick and create one ext3 partition.
# Mount newly created ext3 partition and extract TI's root filesystem to it: sudo tar jxvf rootfs_am37x.tar.bz2 -C /media/ROOT
# Unmount flashdisk and insert it into the BeagleBoard.
# Mount your SD card to your computer.
# Now we need to tell the BeagleBoard to use the root filesystem from the /dev/sda1 partition instead of the SD card partition. That is done by overwriting boot.scr on the SD card with [http://www.apksoft.eu/android/boot.scr this one]
# Unmount the SD card and insert it into the BeagleBoard and test.

=Graphics accelerator=

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.

Tutorial:
* [http://code.google.com/p/beagleboard/wiki/HowtoUseSGXunderAngstrom How to use SGX with Angstrom in OE]
* [http://labs.qt.nokia.com/2009/11/20/building-qt-to-make-use-of-the-beagle-boards-sgx-gpu/ Building Qt to make use of the Beagle board’s SGX GPU]

Some videos:

* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on BeagleBoard working with Linux 2.6.27]
* [http://www.youtube.com/watch?v=24TXpqa9jG0&feature=related OpenGL ES 2.0 shader effects on OMAP3]
* [http://www.youtube.com/watch?v=-UFUbqoNgs8&feature=related 3D User Interface on OMAP3 Platform]
* [http://www.youtube.com/watch?v=8KcNgeUriqA 3D Mapping using OpenGL ES 2.0 on OMAP3 Platform]
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]
* [http://www.hitlabnz.org/wiki/EmbeddedAR An Augmented Reality application combining ARToolkit and OpenGL ES 2.0]
* [http://www.youtube.com/watch?v=cfeqSOYkBJg&feature=player_embedded Video of the Beagle Board turned into a portable battery powered Linux tablet]

=Beginners guide=

You just got your new BeagleBoard, and now? See [[BeagleBoardBeginners|beginners guides]].

=FAQ=

For BeagleBoard frequently asked questions (FAQ) see [[BeagleBoardFAQ|community FAQ]] and "official" [http://beagleboard.org/support/faq BeagleBoard.org FAQ].

=Links=
==Home page==
[http://beagleboard.org/ beagleboard.org] (BeagleBoard home)
* 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>''

==Manuals and resources==
* [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard HW Reference Manual (rev. C2)]
* [http://beagle.s3.amazonaws.com/BBSRM_7_2_0.pdf BeagleBoard HW Reference Manual (rev. B7)]
* [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)]
* [http://www.beagleboard.org/uploads/BBSRM_B5.pdf BeagleBoard HW Reference Manual (rev. B5)]
* [http://www.beagleboard.org/uploads/Beagle_HRM_B4.pdf BeagleBoard HW Reference Manual (rev. B4)]
* [http://www.beagleboard.org/uploads/Beagle_HW_Reference_Manual_A_5.pdf BeagleBoard HW Reference Manual (rev. A5)]
* [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor description and manuals
* [http://code.google.com/p/beagleboard/ Beagle at code.google.com]
* [http://focus.ti.com/dsp/docs/dspsupporttechdocs.tsp?sectionId=3&tabId=409&familyId=1526&documentCategoryId=4&techDoc=4 OMAP3530/25 CBB BSDL Model]
* [http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for BeagleBoard]
* [http://beagleboard.org/resources BeagleBoard resources page with hardware documentation]
* Some [http://www.rasterman.com/ performance comparison] of BeagleBoard Rev. B with some other ARM/PC systems.
* OMAP3 pinmux [http://www.hy-research.com/omap3_pinmux.html setup]
* [http://elinux.org/BeagleBoardPinMux OMAP3 eLinux pinmux page]

==Contact and communication==
* [http://groups.google.com/group/beagleboard BeagleBoard discussion list]
* [http://code.google.com/p/beagleboard/issues/list BeagleBoard open point list and issue tracker]
* [http://beagleboard.blogspot.com/ BeagleBoard blog]
* [http://feeds.feedburner.com/BeagleBoard BeagleBoard RSS feed]
* Chat:
** [http://beagleboard.org/chat BeagleBoard chat]
** IRC: #beagle channel on irc.freenode.net
** [http://www.beagleboard.org/irclogs/index.php IRC archive]
* [http://www.beaglesride.org/ Beagles Ride], a site about building a community around the BeagleBoard focused on in vehicle applications
* [http://www.beagleboard.de/ German BeagleBoard Forum and Wiki]

==TI resources==
* [http://opensource.ti.com/ TI open source page]
* [https://community.ti.com/ TI E2E (Engineer-to-Engineer) Community]
* [http://marc.info/?l=linux-omap&m=120761100810527&w=2 DSP Bridge driver for OMAP3 platform]
* [http://lists.arm.linux.org.uk/lurker/message/20080701.142512.5eeff26b.en.html ARMv7 Oprofile support]
* [http://focus.ti.com/pdfs/wtbu/swpu114g.pdf OMAP34xx Wireless Technical Reference Manual] (swpu114g.pdf, 47 MB)
* [http://amethyst.openembedded.net/~koen/index.php?sort=date&order=desc&path=beagleboard/ Koen's (OpenEmbeded) BeagleBoard source and binaries]
* [http://del.icio.us/tag/beagleboard+peripheral+verified Verified peripherals for BeagleBoard]
* [http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt OMAP3430 Linux Power Management presentation]

==Articles==
* [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article about BeagleBoard]
* [http://www.linuxdevices.com/news/NS8479495970.html LinuxDevices article about Digi-Key launch]
* [http://www.linuxdevices.com/news/NS5682470737.html LinuxDevices article about BeagleBoard Rev C, Beagle MID from HY Research, Touch Book and Sponsored Projects Contest]
* [http://www.linuxjournal.com/article/10607 Linuxjournal article on the BeagleBoard]

==Books==
* [[OMAP_and_DaVinci_Software_for_Dummies|OMAP and DaVinci Software for Dummies]]

==BeagleBoard based training materials==
* http://free-electrons.com/blog/beagle-labs/

==Past BeagleBoard events==
* TIDC, February 26-28, 2008: [http://www.beagleboard.org/uploads/tidc_opensource.pdf Slides from TI developer conference (TIDC) open source session], covering also BeagleBoard
* [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]
* 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]
* [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 BeagleBoard. [http://linuxoutlaws.com/podcast/48 Interview with Linux Outlaws (52:06)] and the [http://www.youtube.com/watch?v=m9xVbntl-DY video]
* [http://osscamp.in/index.php/OSScamp_Bengaluru_Mobile_2008 OSScamp Bengaluru Mobile 2008], July 19, 2008
* [http://www.linuxworldexpo.com LinuxWorld Conference & Expo], August 4 - August 7, 2008: [http://www.flickr.com/photos/jadon/sets/72157606586084668/ pictures with living BeagleBoard] and from [http://www.flickr.com/photos/linuxjournal/2738316951/in/set-72157606634486338/ Linux Journal's photostream]
* BeagleBoard.org event at Jillian's during LinuxWorldExpo, August 5, 2008, 5:30-7:30 pm
* [http://barcamp.pbwiki.com/BarCampHouston3 BarCamp Houston 3], August 9, 2008, 9:00 A.M.: [http://www.flickr.com/photos/jadon/sets/72157606656532041/ pictures]
* NIT Suratkal, India [http://www.nitkieee.com/site/sp-connect2/schedule IEEE SP Connect 2], August 30, 20008
* [http://barcampbangalore.org/wiki/BCB7_Demos BarCamp Bangalore], India, September 13, 2008
* [http://www.ibc.org/ IBC 2008], September 11 - September 16, 2008: [http://www.flickr.com/photos/koenkooi/tags/ibc2008/ pictures]
* 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]
* [http://www.embedded.co.uk/ Embedded Systems Show 2008], Birmingham, UK, October 1-2, 2008
* [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]
* [http://www.rtcgroup.com/arm/2008/ ARM Developers' Conference], Santa Clara Convention Center, Santa Clara, Calif., USA, October 7-9, 2008
* [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]
* [[BeagleBoard/contest|BeagleBoard contest]] #1: Create a cool BeagleBoard application and win a Rev C1! Closed, ran until January 9, 2009
* [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]]
* [[BeagleBoard/contest|BeagleBoard contest #2]], until February 27, 2009: Create a cool BeagleBoard application and win a Rev C2!
* [http://groups.google.com/group/beagleboard/browse_thread/thread/b15cf8a5797c73a2 Silica - Free TI - ARM OMAP Workshop], Brussels, Europe, March 31st 2009
* 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
* 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 BeagleBoard presentation]
* 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])
* 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'').
* 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.
* 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])

==BeagleBoard wiki pages==
* [[BeagleBoardJTAG|BeagleBoard JTAG]] and [[OMAP3530_ICEPICK|OMAP3530_ICEPICK]] about JTAG on BeagleBoard
* [[BeagleBoardOpenOCD|BeagleBoard OpenOCD]] has information about status and usage of open source JTAG software OpenOCD with Beagle
* [[Mount_BeagleBoard_Root_Filesystem_over_NFS_via_USB|Mount BeagleBoard root file system over NFS via USB]]
* [[BeagleBoardSugar|Sugar on BeagleBoard]]
* [[BeagleBoard/gst-openmax|BeagleBoard OpenMAX usage]]
* [[BeagleBoard/video|BeagleBoard video]]
* [[BeagleBoardOpenCV|Using OpenCV computer vision library with BeagleBoard]]
* [[U-boot_musb_gadget_support|U-boot musb gadget support]]
* [[BeagleBoard-JP|Japanese translation of this BeagleBoard page]]
* [[BeagleEPD|BeagleBoard E-Ink Platform Driver]]
* [[BeagleBoardFedora|Random hacking notes for getting Fedora 10 to kinda work with the BeagleBoard]]
* BeagleBoard specific [[BeagleBoard/GSoC|Google Summer of Code 2009]] page, [[BeagleBoard/Ideas-2009|GSoC project ideas]] and [[BeagleBoard/GSoC/Application|GSoc application]]
* [[BeagleBoard/DSP_Clarification|Info about the various Linux DSP systems for OMAP chips]]
* [http://www.hervanta.com/stuff/Beaglebot Beaglebot]: build an experimental robotics project with BeagleBoard
* [http://code.google.com/p/beagleboard/w/list code.google.com BeagleBoard wiki]
* '''[[BeagleBoard/contest|BeagleBoard contest]]'''
* [http://en.wikipedia.org/wiki/Beagle_Board Wikipedia BeagleBoard page]
* [http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board Android port for BeagleBoard]: Instructions for porting Android on BeagleBoard
* [[BeagleBoard/bangalore_user_meet |BeagleBoard Bangalore User Meet]]
* [[Zoom2Beginners|Zoom2 for Beginners]]
* [http://wh1t3s.com/2009/05/11/beagleboard-as-usb-mass-storage-device-via-usb-otg/ BeagleBoard as USB Mass Storage Device via USB OTG]
* [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm BeagleBoard as solar powered computer]
* [http://blog.makezine.com/archive/2009/02/blinking_leds_with_the_beagle_board.html Blinking LEDs with the BeagleBoard] from Make:Online
* [http://www.crashcourse.ca/wiki/index.php/BeagleBoard Robert's private BeagleBoard wiki] (please don't add anything there, do it here. It will help to avoid splittering. Thanks!)
* [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
* [http://www.syspire.de/node/3 Embedded Mediacenter] based on BeagleBoard (German)
* [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] with VFP-lite and NEON introduction
* [http://particolarmente-urgentissimo.blogspot.com/2009/09/beagleboard-setting-date-via-gps.html BeagleBoard setting date via GPS]
* [http://free-electrons.com/blog/beagle-labs/ Complete embedded Linux training labs] on the BeageBoard
* [[BeagleBoardPWM]] Details about PWM on the BeagleBoard.
* [[BeagleBrick]] software defined radio project

==BeagleBoard photos==
* [http://www.flickr.com/groups/beagleboard/pool/ BeagleBoard pictures at flickr]
* [http://www.flickr.com/photos/32615155@N00/2439256116/ BeagleBoard and USRP]
* [http://www.flickr.com/photos/nishanthmenon/2438406603/ Modify SDP3430 QUART cable for BeagleBoard]
* [http://www.flickr.com/photos/koenkooi/2695061759/ MythTV on BeagleBoard]

==BeagleBoard videos==
* [http://uk.youtube.com/watch?v=fL_XMieanSc BeagleBoard Beginnings]
* [http://www.youtube.com/watch?v=cXr-D1wROfQ BeagleBoard in the Living Room]
* [http://uk.youtube.com/watch?v=FuVwh_VrIxk BeagleBoard 3D, Angstrom, and Ubuntu]
* [http://uk.youtube.com/watch?v=TUYOjRGYeYU testsprite with BeagleBoard]
* [http://uk.youtube.com/watch?v=9Z4ZTovtFKk BeagleBoard LED demo]
* [http://uk.youtube.com/watch?v=R33dzREZGEk LCD2USB attached to a BeagleBoard]
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]
* [http://www.youtube.com/watch?v=-tUBXD-KRp4 BeagleBoard Running Angstrom (VGA) on DLP Pico Projector]
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on BeagleBoard working with Linux 2.6.27]
* Not on Beagle OMAP3530: [http://youtube.com/watch?v=5i9cWOK1spw Ubuntu 7.04 on on OMAP3430 SDP]
* [http://in.youtube.com/watch?v=nADn_vNVEKw BeagleBoard booting Android]
* [http://www.youtube.com/watch?v=UHQdUS0i-nw BeagleBoard, SGX, and libfreespace demo]

==BeagleBoard manufacturing==
* [http://www.youtube.com/watch?v=C-CwkjT9z_0&feature=related BeagleBoard Solder Paste Screening]
* [http://www.youtube.com/watch?v=9LLjDovIG2M&feature=related BeagleBoard Assembly Inspection]
* [http://www.youtube.com/watch?v=sbOZfBnoVnM&feature=related BeagleBoard Functional Test]
* [http://www.youtube.com/watch?v=cvDtXmJJcEI&feature=related BeagleBoard Reflow]
* [http://www.youtube.com/watch?v=W2o4NTASxN0&feature=related BeagleBoard Assembly at Circuitco]

=Other OMAP boards=
* OMAP 4430 Based 40X40 mm size [http://www.tianyeit.com CIP410] computer in package from [http://www.tianyeit.com Tianyeit]
* OMAP DM3730/OMAP3530 Based 40X40mm size [http://www.tianyeit.com CIP312] Computer In Package from [http://www.tianyeit.com Tianyeit]
* OMAP 4430 based [[PandaBoard]]
* OMAP-L138 Based [[Hawkboard]]
* OMAP3530 based [http://www.armkits.com/Product/devkit8000.asp DevKit8000] development board from [http://www.armkits.com Embest]
* OMAP3530 based [http://www.armkits.com/Product/sbc8100.asp SBC8100] Single-board computer from [http://www.armkits.com Embest]
* OMAP1 OMAP5912 (ARM9 + C5x DSP) based [[OSK|OSK]] board.
* 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].
* OMAP3 OMAP3530 based [http://www.openpandora.org/ Pandora]
* OMAP3 OMAP3503 based [http://www.gumstix.net/Overo/cat/Overo/115.html Gumstix Overo]
* 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)
* OMAP3 OMAP3430 based [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12013&contentId=28741 Software Development Platform (SDP)]
* OMAP3 OMAP3530 based board from [http://www.magniel.com/omap3.html Magniel Inc.]
* OMAP3 based [http://www.archos.com/products/imt/index.html?country=us&lang=en Archos 5, ARCHOS 5G and ARCHOS 7]
* OMAP3 OMAP35x based [http://www.logicpd.com/products/som/ti/omap35x OMAP35x SOM-LV]
* OMAP3 based [[Mini_Board|ICETEK-OMAP3530-Mini]], a Chinese BeagleBoard clone, with a [[MiniBoardFAQ|FAQ]]
* OMAP3 based [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], a German BeagleBoard clone
* OMAP3530 based [http://www.bsquare.com/products/hardware_solutions/3530.asp BSQUARE’s Dev Kit OMAP3530]
* OMAP3530 based [http://beaversource.oregonstate.edu/projects/cspfl/wiki/CSPFL_Hardware OSWALD]
* OMAP3 BeagleBoard-based [http://www.alwaysinnovating.com/touchbook/ Touch Book]
* OMAP3530 based [http://www.analogue-micro.com/Cobra3530.html Cobra 3530 OMAP3530 module ]
* OMAP3 based [http://www.kwikbyte.com/KBOC.html KwikByte 35XX System Module]
* OMAP3530 based [[DevKit8000]], a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard)
* OMAP3530 based [http://www.igep-platform.com/ IGEPv2 Platform], a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, Wi-Fi and Bluetooth.
* OMAP35x based [http://www.ultratronik.de/mmi-rechnerplattformen.html MMI4 from Ultratronik]
* OMAP35x based [http://www.technexion.com/index.php/tao-3530 TAO-3530 from TechNexion], also sold in North America through [http://www.robotcraft.ca/webshop/index.php?manufacturers_id=21 Robotcraft Systems]
* OMAP35x based [http://www.variscite.com/varomap35xxsbc.html VAR-OM35xxSBC from Variscite]
* OMAP35x based [[EGS3530]],a Chinese BeagleBoard clone from [http://www.ema-tech.com EMA]
* OMAP3 OMAP35x based [http://www.buglabs.net/products BUG] from Bug Labs, Inc.
* OMAP35x System-on-Module [[SOM3530]], the smallest(40x40x4 mm) OMAP35XX-based system on module in the world! (It is not-Gumstix Overo is smaller at 17 mm*58 mm)
* OMAP35x based [http://www.compulab.co.il/t3530/html/t3530-cm-datasheet.htm CM-T3530 from CompuLab]

=Subpages=
<splist
parent=
showparent=no
sort=asc
sortby=title
liststyle=ordered
showpath=no
kidsonly=no
debug=0
/>

KR:BeagleBone

2012-11-27T07:17:34Z

Yclinda666: /* 케이프(Capes) */

[[Category: Linux]]
[[Category: OMAP]]
[[Category:Development Boards]]
[[Category: BeagleBoard]]
[[Category: BeagleBone]]

[[File:BeagleBone_256x249.jpg|320px|thumb|right|BeagleBone]]

이 페이지는 [http://beagleboard.org BeagleBoard.org]의 [http://www.ti.com/am335x TI AM335x] [http://www.arm.com/ ARM]을 기반으로 하는 [http://beagleboard.org/bone BeagleBone]의 정보를 모았다.

 
= 이벤트 =
* 진행중인 2009: [[BeagleBoard/contest|비글 스폰서 프로젝트 프로그램]] - 참신한 프로젝트를 추가하고 무료로 비글보드를 얻어가세요!

= 설명 =

'''비글본(BeagleBone)'''은 [http://beagleboard.org/ BeagleBoard] 제품 라인으로 저렴하며 높은 확장성을 가진다. [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344d/DDI0344D_cortex_a8_r2p1_trm.pdf ARM Cortex-A8] 프로세서 코어를 기반으로 [http://www.ti.com/am335x TI AM3358/9] SoC를 사용한다. [http://infocenter.arm.com/help/topic/com.arm.doc.subset.architecture.reference/index.html#v7AR ARMv7-A] 구조를 기반으로 한다. 초기 비글보드의 목적과 유사해서 독립적으로 사용하거나 비글보드나 다른 시스템에 이더넷 연결 확장하여 사용할 수 있다. 비글본은 표준 비글보드도 작으면서도 상당한 성능과 용량을 제공한다.

비글본은 4GB 마이크로 SD카드에 [http://www.angstrom-distribution.org/ Angstrom] ARM Linux 배포판과 함께 제공된다.

입력 전력이 가변적이더라도 안정적인 전압을 생성할 수 있도록 [http://www.ti.com/product/tps65217 TI TPS65217B PMIC]를 사용한다. +5V DC는 배럴 커넥터(barrel connector)나 미니-USB를 통해 공급된다. 이 둘은 모두 RJ45 이더넷 커넥터 근처에 위치하고 있다.

mini-USB type-A OTG 장치 '''클라이언트 모드''' 소켓은 다양한 기능이 있다. 선택 가능한 전원을 제공하며 온보드 프론트 엔드 2포트 USB 클라이언트 사이드 허브에 접근할 수 있게 한다.(나중에 소개할 독립된 '''호스트 모드''' USB 소켓과는 관련이 없다.) 허브 중 하나는 TI AM3358/9 SoC의 '''USB0''' 포트에 직접적으로 연결되지만 다른 포트는 듀얼-포트 [http://www.ftdichip.com/Products/ICs/FT2232H.htm FTDI FT2232H] USB-to-시리얼 컨버터에 연결되며 이는 보드에서 외부 호스트와 시리얼 통신이나 JTAG 디버깅에 이용된다. 비글본의 리눅스 시리얼 콘솔은 이 USB 시리얼 연결을 통해 가능하다.

프론트 엔드 허브에 SoC의 '''USB0''' 연결은 2가지 모드 중에 하나로 동작한다. 언제든 이 2모드 사이에서 토글이 가능하다. 호스트에 마운팅 가능한 USB 저장장치처럼 SD카드나 혹은 [http://www.linux-usb.org/usbnet/ Ethernet-over-USB] 네트워킹 인터페이스를 제공한다. Ethernet-over-USB 기능은 비글본의 기본 10/100 이더넷 인터페이스에 추가되어 있으며 이는 직접 SoC에 구현되어 있다. 제공한 리눅스 시스템에서 완전한 IPv4와 IPv6 네트워킹을 제공한다.

이미 설명한 USB OTG 장치나 '''클라이언트 모드''' 기능 이외에, 비글본은 보드의 다른 가장자리에 '''호스트 모드''' USB type-A 소켓도 제공한다. AM3358/9 SoC에 있는 '''USB1''' 연결이며 마우스나 키보드, 저장장치, wifi, 블루투스 동글, USB 허브 등과 같은 USB 호스트 주변장치에 연결을 제공한다.

= 스펙 =
* 최대 720-MHz superscalar ARM Cortex-A8
* 256-MB DDR2 RAM
* 10/100 이더넷 RJ45 소켓, IPv4 and IPv6 네트워킹
* 마이크로SD 슬롯과 4GB 마이크로SD 카드 제공
* Angstrom ARM 리눅스 배포판
* 단일 USB 2.0 타입 A 호스트 포트
* 듀얼 USB 허브 USB 2.0 타입 mini-A OTG 장치 포트
* On-board USB-to-serial/JTAG 하나의 공유 USB 장치 포트
* Storage-over-USB or Ethernet-over-USB on other USB device port
* Extensive I/O: 2 I2C, 5 UART, SPI, CAN, 66 GPIO, 8 PWM, 8 ADC
* +5V DC power (배럴 커넥터 or USB 장치 포트)
* 2개 46-pin 3.3-V peripheral headers with multiplexed LCD signals
* 보드 크기 : 86.4mm x 53.3mm(3.4" × 2.1") -- Altoid tin에 적합

= 확장 커넥터 =
비글본은 2개의 46핀 2열 확장 커넥트인 "'''Expansion A'''"와 "'''Expansion B'''"로 알려진 "'''P9'''"와 "'''P8'''" 를 제공한다. 이 커넥터의 위치와 핀아웃은 아래에 나와 있다.(크게 볼려면 테이블을 클릭하라). 다른 표시가 없으면 확장 헤더에 모든 신호는 3.3V이다.

=== P9과 P8 - 각 2x23 pins ===
[[File:BeagleBone_P9_256x256.jpg|256px|left|top|border|P9 Header|link=File:BeagleBone_p9_pinout.jpg]]
[[File:BeagleBone_P9_P8_256x256.jpg|256px|top|border|BeagleBone P9 + P8|link=File:BeagleBone_P9_P8_512x512.jpg]]
[[File:BeagleBone_P8_256x256.jpg|256px|top|border|P8 Header|link=File:BeagleBone_p8_pinout.jpg]]
 
위에 2개의 넓은 허더에 추가로 작은 10-pin 2줄 커넥터는 "'''P6'''"과 "'''PMIC Expansion'''"를 제공한다. 다음 핀아웃을 이용해서 TPS65217B Power Management IC로부터 추가 신호를 끌어낸다.

=== P6 - 2x5 pins''' ===
[[File:BeagleBone_P6_464x222.jpg|464px|left|middle|border|P6 MPIC 확장 헤더]]
'''중요'''

P6 다이어그램은 아랫부분 PINOUT을 보여준다.

It is therefore ''' ''laterally inverted'' ''' relative to the photograph.

To obtain the top-side pinout that corresponds to the physical orientation shown in the photograph, swap the two rows of pins so that odd-numbered pins are on the left of even-numbered pins. 

= 확장 보드와 악세사리 =

== 케이프(Capes) ==
'''BeagleBone Cape'''은 BeagleBone의 2개 46핀 2줄 '''확장 헤더'''에 연결할 수 있는 확장보드이다. 유사한 헤더를 차례차례로 케이프 위에 쌓을 수 있다. 한 번에 4개의 케이프까지 쌓을 수 있다. 확장보드는 케이프의 맨 위에 있는 케이프 하고만 맞는 경우는 특별한 경우이다. 하지만 LCD와 같은 확장 보드에는 이 방식이 일반적이다.(다음 섹션 참고)

케이프는 32Kbyte I2C-addressed EEPROM을 제공한다. EEPROM은 보드 이름, 시리얼 넘버, 리비전과 같은 정보를 가지고 있다. 단순한 프로토타이핑 케이프에는 들어가 있지 않다. 또 케이프는 스택에 주소를 선택하기 위해 2-position DIP 스위치를 제공한다. 이것도 프로토타이핑 케이프에는 빠져있는 경우가 많다.

[https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 케이프 등록]페이지에서는 현존하는 모든 케이프와 케이프 컨셉을 찾아볼 수 있다. [https://docs.google.com/spreadsheet/viewform?formkey=dDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc6MQ 등록 페이지]에서 케이프를 목록에 추가할 수 있다.

아래 목록은 구입 가능한 케이프 혹은 오픈하드웨어로 설계된 케이프이다.

* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_DVID CircuitCo BeagleBone DVI-D cape]
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_Breadboard CircuitCo BeagleBone Breadboard cape]
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_Breakout CircuitCo BeagleBone Breakout cape]
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_CANBus CircuitCo BeagleBone CANBus cape]
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_RS232 CircuitCo BeagleBone RS232 cape]
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_Battery CircuitCo BeagleBone Battery cape]
* [http://www.adafruit.com/products/572 Adafruit Proto Cape kit for BeagleBone]
* [http://www.towertech.it/en/products/hardware/tt3201-can-cape/ TowerTech TT3201 Multi-Channel CAN Cape]
* [https://specialcomp.com/beaglebone/BeagleBone_FPGA.html Special Computing Spartan-3A FPGA cape for BeagleBone] -- in development
* [http://syntheticlifeforms.net/?p=43 Thinking Machines LCD-IO Expansion Cape] -- in development
* [https://github.com/piranha32/FlyingBone Open Source BeagleBone Prototyping Board] -- piranha32 GitHub repository
* [http://www.armkits.com/product/beaglebone-hdmicape.asp Embest BeagleBone-HDMI CAPE]

== LCD 디스플레이와 확장 ==
비글본에서 LCD 디스플레이는 일반적으로 케이프로 구현되어 있다. 쉽게 볼 수 있도록 하기 위해 케이프의 위에 ''' "탑 보드(top board)" '''형태로 연결시킨다.이런 디스플레이는 비글본 보다 더 큰 경우가 많다. 물리적인 관계로 봤을 때 연결된 보드가 본체 보드보다 더 커지는 현상이 생긴다. 비글본을 물리적으로 지원하는 확장 보드이다.
* [[File:Beaglebone.jpg|320px|thumb|BeadaFrame]][http://www.nxelec.com/products/hmi/beadaframe-beaglebone NAXING Electronics BeadaFrame] with BeagleBone companion board
:Expanded Hardware Features:
:* 7" 800x480 TFT LCD screen
:* PWM Backlight control
:* Resistive touch panel
:* Plastic frame
:* 256MB Nand flash(K9F2G08)
:* RS232 serial ports(UART1 w/ CTS&RTS)
:* Stereo audio out
:* Micro-phone in
:* 6 x USER buttons
:* PWM Beeper
:* RTC with Battery(DS1302)

* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_LCD3 CircuitCo BeagleBone LCD3 cape and LCD display]
: 3.5" TFT LCD 화면, 해상도 320x240, 4-wire resistive 터치 스크린, 손가락 위치에 잘 맞는 7개 버튼.
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_LCD7 CircuitCo BeagleBone LCD7 cape and LCD display]
: 7" TFT LCD 화면, 해상도 800x480, 4-wire resistive 터치 스크린, 비글본과 케이프에 rear mount

== 케이스 ==
* [http://www.adafruit.com/products/699 Adafruit Bone Box - 비글본 박스]
* [http://www.skpang.co.uk/catalog/acrylic-cover-for-beaglebone-p-1076.html SK Pang 비글본용 아크릴 커버]
* [http://specialcomp.com/beagleboard/BB-Bone-assy2_l.jpg Special Computing Bone 아크릴 케이스]
* [http://www.thingiverse.com/thing:19153 canadaduane's 3D-printable 비글본 케이스 디자인]
* [http://www.thingiverse.com/thing:16195 NinjaBlock's 3D-printable 비글본 전면 패널 디자인]
* [http://www.thingiverse.com/thing:20122 builttospec's 레이저 가공이며 DVI 케이프가 있는 비글본 박스]
* [http://www.built-to-spec.com/blog/2012/03/01/beaglebone-case-update-and-new-kits-page/ Built to Spec 비글본 케이스 업데이트], and [http://builttospecstore.storenvy.com/products/225603-beaglebone-enclosure 최종 제품]

= BeagleBone 운영체제 =
BeagleBone's default operating system is [http://www.angstrom-distribution.org/ Angstrom], which ships with the board. This section provides basic information on Angstrom and other operating systems commonly used on BeagleBone. This information may help in making a preliminary choice, but full details should be obtained from the home sites.
비글본의 기본 운영체제는 [http://www.angstrom-distribution.org/ Angstrom]이다. 보드 구입시 기본 탑재되어 있다. 여기서는 Angstrom에 관한 기본적인 정보와 그외 비글본에서 사용하는 운영체제에 대한 정보를 제공한다. 여기 있는 정보는 처음 선택하는데 도움이 되지만 자세한 정보는 홈페이지에서 얻을 수 있다.

=== Angstrom ===
* 홈페이지: http://www.angstrom-distribution.org/
* 메일링 리스트: [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel angstrom-distro-devel] and [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users angstrom-distro-users]
* IRC 채널: irc://irc.freenode.net/#angstrom
Ångström는 OpenEmbedded, OpenZaurus와 OpenSimpad 프로젝트에서 일하던 사람들의 작은 단체로 시작되었다. 임베디드 장치(핸드헬드, 셋탑박스, 네트웍 기능 스토리지 장치)에 적합한 안정적이고 사용자가 사용하기 쉬운 배포판을 만들기 위해 힘을 합쳤다. Ångström은 4MB 플래쉬를 가지는 장치에도 적합하게 스케일을 줄였다.

Angstrom 커뮤니티는 포럼을 제공하지 않는다. [http://www.angstrom-distribution.org/contact 의도적으로]

Angstrom은 많은 핵심 유틸리티에 [http://www.busybox.net/ Busybox]를 사용한다. 이는 장단점을 가진다. 장점은 저장공간이 적게 필요하다는 것과 공통 유틸리티에 적은 메모리가 사용된다는 것이다. 이로써 시스템 시작과 성능을 개선할 수 있다. 주요 단점은 전체 크기 counterparts를 정확하게 미러링 할 수 없다는 것이다. 이런 차이점은 표준 동작하는 경우 귀찮을 수 있고 이식된 기능에 의존하는 경우 쉘 스크립트가 깨질 수 있다.

Angstrom은 네트워크 연결 관리에 [http://connman.net/ connman]을 사용한다. 하지만 현재 이에 대한 문서가 없다. 또 man이나 man page가 기본으로 제공되지 않는다. strace나 tcpdump와 같은 디버깅 유틸리티도 제공되지 않는다. 따라서 시작하는 경우 어려움을 겪을 수 있고 경험에 의존해야한다.

=== Debian ===
* Home site: [http://wiki.debian.org/ArmEabiPort http://wiki.debian.org/ArmEabiPort]
* Mailing list: http://lists.debian.org/debian-arm/
* IRC channel: irc://irc.debian.org/debian-arm
The ARM EABI port is the default port of the standard Debian distribution of Linux for the ARM architecture ("armel").
EABI ("Embedded ABI") is actually a family of ABIs, and one of the "subABIs" is the GNU EABI for Linux which is used for this port.
A newer port targeted at newer hardware with another ABI ("armhf") is currently under development and is expected to ship with Debian 7.0 (Wheezy).

The [http://www.debian.org/intro/about Debian Project] is strongly committed to software freedom, and has a long pedigree and a good reputation.

=== Ubuntu ===
* [[BeagleBoardUbuntu]] 참조
* 홈페이지: https://wiki.ubuntu.com/ARM
* IRC 채널: irc://irc.freenode.net/#ubuntu-arm
Ubuntu의 목표는 소셜과 경제성이다: 무료 소프트웨어로서 모든 사람이 무료로 사용할 수 있으며 Canonical이 제공하는 서비스의 포트폴리오를 통해 펀드를 받는다.

Ubuntu의 첫번째 버전은 GNOME 데스크탑을 기반으로 했지만 KED, Kubuntu와 server버전이 추가되었다. 우분투의 모든 에디션은 공통 인프라구조와 소프트웨어를 공유하고 있다. 특별한 부분은 넷북, 모바일 컴퓨팅, 데이터 센터용으로 새로운 구조를 가지는 클라우드 버전이다.

=== Fedora ===
* See [[BeagleBoardFedora]].
* Home site: http://fedoraproject.org/wiki/Architectures/ARM
* Mailing list: http://lists.fedoraproject.org/pipermail/arm/
* IRC channel: irc://irc.freenode.net/#fedora-arm
The Fedora Project is sponsored by Red Hat, which invests in its infrastructure and resources to encourage collaboration and incubate innovative new technologies. Some of these technologies may later be integrated into Red Hat products. They are developed in Fedora and produced under a free and open source license from inception, so other free software communities and projects are free to study, adopt, and modify them.

Red Hat has been a major player since the earliest days of Linux distributions, and has earned a good reputation for solidity which continues in Fedora. The Fedora ARM initiative is very active (see mailing list).

=== ArchLinux ===
* Home site: http://archlinuxarm.org/platforms/armv7/beaglebone
* Source repository: https://github.com/archlinuxarm/PKGBUILDs
* IRC channel: irc://irc.freenode.net/#archlinux-arm
Arch Linux for BeagleBone is a version of the Arch Linux ARM distribution. This carries forward the Arch Linux philosophy of simplicity and user-centrism, targeting and accommodating ''competent'' Linux users by giving them complete control and responsibility over the system. Instructions are provided to assist in navigating the nuances of installation on the varied ARM platforms; however, the system itself will offer little assistance to the user.

The entire distribution is on a rolling-release cycle that can be updated daily through small packages instead of huge updates on a defined release schedule. Most packages are unmodified from what the upstream developer originally released.

=== Gentoo ===
* Home site: http://dev.gentoo.org/~armin76/arm/beaglebone/install.xml
* IRC channel: irc://irc.freenode.net/#gentoo-embedded
Gentoo is a source-based '' '''meta'''-distribution'' of Linux. Instead of distributing a standard system image built with predefined options, Gentoo gives each user the means to create their own customized system that doesn't contain unused bloat and with minimum dependencies. Upgrades are incremental and under user control, so a Gentoo system is normally always up-to-date and wholesale upgrades are avoided.

Being a source-based system, the downside of Gentoo for low-power ARM systems is very long install times for large applications. Cross-compilation on x86 machines and [http://www.gentoo.org/doc/en/distcc.xml distcc] can overcome this problem, but they add complexity.

=== Sabayon ===
* Home site: [http://wiki.sabayon.org/index.php?title=Hitchhikers_Guide_to_the_BeagleBone_%28and_ARMv7a%29 wiki.sabayon.org/Hitchhikers Guide to the BeagleBone]
* IRC channel: irc://irc.freenode.net/#sabayon
Sabayon Linux uses the mechanisms of Gentoo to create a pre-configured Linux distribution that can be installed as rapidly as a normal binary distribution, but still retains the benefits of Gentoo's source-based package management. Sabayon on Intel/AMD also provides the Entropy binary package management system, which could in principle greatly ease installation of packages on resource-constrained embedded Linux devices, but this is not yet available for ARM.

Although it is still early days for Sabayon on ARM (and hence on BeagleBone), there is regular progress reported on [http://lxnay.wordpress.com/2012/ lxnay's blog], and contributions from the community would probably accelerate the work.

=== Buildroot ===
* Home site: http://www.zoobab.com/beaglebone
* Source repository: https://github.com/fhunleth/buildroot-beaglebone
* Buildroot project site: http://buildroot.uclibc.org/
Buildroot is a set of Makefiles and patches that makes it easy to generate a complete embedded Linux system. Buildroot can generate any or all of a cross-compilation toolchain, a root filesystem, a kernel image and a bootloader image. Buildroot is useful mainly for people working with small or embedded systems, using various CPU architectures (x86, ARM, MIPS, PowerPC, etc.) : it automates the building process of your embedded system and eases the cross-compilation process.

The resulting root filesystem is mounted read-only, but other filesystems can be mounted read/write for persistence. Although user accounts can be created, in practice almost everything is done as root. Buildroot uses no package manager. Instead, package selection is managed through '''make menuconfig'''.

=== Nerves Erlang/OTP ===
* Home site: http://nerves-project.org/
* Source repository: https://github.com/nerves-project/bbone-erlang-buildroot
* Erlang project site: http://www.erlang.org/
Erlang is a programming language used to build massively scalable soft realtime systems with high availability requirements (5-9’s). Some of its uses are in telecoms, banking, e-commerce, computer telephony and instant messaging. Erlang’s runtime system has built-in support for concurrency, distribution and fault tolerance.

OTP is a set of Erlang libraries and design principles providing middle-ware to develop these systems. It includes its own distributed database, applications to interface towards other languages, debugging and release handling tools.

The Nerves project provides an embedded Linux-based environment for running Erlang and an easy-to-use API to access common I/O interfaces, based on '''Buildroot''' (see above). If you are interested in running an Erlang node on a low power ARM-based board such as BeagleBone, this project can get you started.

= Board recovery =
* See [http://elinux.org/BeagleBoardRecovery#USB_recovery BeagleBoardRecovery] ''--- (*) Check applicability''

= 소프트웨어 개발 =
비글본에서 소프트웨어 개발은 다른 리눅스 플랫폼과 차이가 없고 개발언어놔 사용한 IDE에 따라 달라진다. 따라서 비글본에 한정된 개발 이슈에 대해서만 알아보자.

=== Cloud9 IDE와 본스크립트(Bonescript) ===
''..... description here .....''
* 소스 저장소: https://github.com/jadonk/bonescript
* 언어 문서: http://nodejs.org/

=== 비글본 JTAG 디버깅 ===
''..... description here .....''

= FAQ =

For BeagleBoard frequently asked questions (FAQ) see [[BeagleBoardFAQ|community FAQ]] and "official" [http://beagleboard.org/support/faq BeagleBoard.org FAQ].

= Links =
== 홈페이지와 커뮤니티 ==
* [http://beagleboard.org/ beagleboard.org] -- 비글보드와 비글본 제품 관련 홈페이지
* irc://irc.freenode.net/#beagle -- official combined IRC channel
* [http://beagleboard.org/discuss Google Groups forums/mailing list] -- [https://groups.google.com/forum/?fromgroups#!forum/beagleboard English], [http://groups.google.com/group/pandabeagle-jp 일본], [http://groups.google.com/group/beagleboard-brasil 브라질], [https://groups.google.com/group/beagle-board-turkiye 터키]
* [http://beagleboard.org/project 비글보드와 비글본 프로젝트 목록]
* [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 케이프 등록] and [https://docs.google.com/spreadsheet/viewform?formkey=dDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc6MQ 등록 페이지]
* [http://www.adafruit.com/blog/category/beaglebone/ BeagleBone articles at Adafruit blog] -- products, projects and tutorials
* Use [http://www.google.de/ Google] to search beagleboard.org (including [http://www.beagleboard.org/irclogs/ IRC logs]) using ''site:beagleboard.org <search term>''

== 튜토리얼과 비디오 ==
* [http://beagleboard.org/static/bonescript/bone101/index.html ''비글본: 비글보드-101 소개''] -- 슬라이드 (turn off Javascript for single page)
* [http://www.youtube.com/watch?v=EEnOWR-GXjk ''비글본 소개''], 비디오 by Jason Kridner, Texas Instruments
* [http://www.youtube.com/watch?v=Y0uqRVxismQ ''How-To: 비글본 시작하기''], 비디오 by Matt Richardson, MakeMagazine
* [http://www.youtube.com/watch?v=z6b4zlh0IrE ''비글본 - 개봉, 소개 튜토리얼 및 처음 예제''], 비디오 by Derek Molloy, DCU/EE
* [http://www.youtube.com/watch?v=vFv_-ykLppo ''비글본: Eclipse를 사용한 C/C++ 프로그래밍 소개 for ARM Embedded Linux Development''], 비디오 by Derek Molloy, DCU/EE
* [http://www.youtube.com/watch?v=SaIpz00lE84 ''비글본: GPIO 프로그래밍 on ARM Embedded Linux''], 비디오 by Derek Molloy, DCU/EE
* [http://borderhack.com/?p=1062 비글본과 함께 첫걸음], introductory HOWTO by octavio at borderhack

== Manuals and resources ==
* [http://beagleboard.org/static/beaglebone/a3/Docs/Hardware/BONE_SRM.pdf 비글본 시스템 참고 메뉴얼 (rev. A3_1.0)].
* [http://www.ti.com/am335x Texas Instruments - Sitara ARM Cortex-A8 마이크로프로세서 개요].
* [http://infocenter.arm.com/help/topic/com.arm.doc.subset.architecture.reference/index.html#v7AR ARM/ARMv7-AR 구조] -- ARM Cortex-A8 구조 개요
* [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344d/DDI0344D_cortex_a8_r2p1_trm.pdf ARM Cortex-A8 Technical Reference Manual r2p1]
* [http://www.arm.com/support/university/development-platforms/cortex-a8-development-platforms.php ARM Cortex-A Development Platforms] -- ARM page on Beagle boards
* [http://www.ti.com/product/tps65217 TI TPS65217 Power Management IC], [http://www.ti.com/lit/ds/symlink/tps65217.pdf TPS65217 PMIC datasheet]
* [http://www.ftdichip.com/Products/ICs/FT2232H.htm FTDI FT2232H Hi-Speed Dual USB UART/FIFO IC overview], [http://www.ftdichip.com/Support/Documents/DataSheets/ICs/DS_FT2232H.pdf FT2232H datasheet]
* [http://www.linux-usb.org/gadget/index.html Linux-USB Gadget API Framework] and [http://www.linux-usb.org/gadget/h2-otg.html USB OTG], and [http://forums.gentoo.org/viewtopic-t-843255.html kernel config] -- Ethernet-over-USB

== Errata ==

= Subpages =
<splist
parent=
showparent=no
sort=desc
sortby=title
liststyle=ordered
showpath=no
kidsonly=no
debug=0
/>

BeagleBone

2012-11-27T07:08:10Z

Yclinda666: /* Capes */

[[Category: Linux]]
[[Category: OMAP]]
[[Category:Development Boards]]
[[Category: BeagleBoard]]
[[Category: BeagleBone]]

[[File:BeagleBone_256x249.jpg|320px|thumb|right|BeagleBone]]

This page collects information about [http://beagleboard.org BeagleBoard.org's] [http://www.ti.com/am335x TI AM335x] [http://www.arm.com/ ARM]-based [http://beagleboard.org/bone BeagleBone] board.

 
= Events =
* ongoing 2009: [[BeagleBoard/contest|Beagle Sponsored Project Program]] - add a cool project and get a free BeagleBoard to realize it!

= Description =
The '''BeagleBone''' is a low-cost, high-expansion board from the [http://beagleboard.org/ BeagleBoard] product line. It uses the [http://www.ti.com/am335x TI AM3358/9] SoC based on an [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344d/DDI0344D_cortex_a8_r2p1_trm.pdf ARM Cortex-A8] processor core using the [http://infocenter.arm.com/help/topic/com.arm.doc.subset.architecture.reference/index.html#v7AR ARMv7-A] architecture. It is similar in purpose to earlier BeagleBoards, and can be used either standalone or as a USB or Ethernet-connected expansion for a BeagleBoard or any other system. The BeagleBone is small even by BeagleBoard standards yet still provides much of the performance and capabilities of the larger BeagleBoards.

BeagleBone ships with a 4GB micro-SD card preloaded with the [http://www.angstrom-distribution.org/ Angstrom] ARM Linux distribution.

The board uses a [http://www.ti.com/product/tps65217 TI TPS65217B PMIC] to generate stable supply voltages regardless of input power variation. +5V DC power can be supplied to the BeagleBone through a barrel connector or from the mini-USB, both of which are located near the large RJ45 Ethernet connector.

The mini-USB type-A OTG/device '''client-mode''' socket is multi-functional. In addition to providing an alternative source of power, it gives access to an on-board front-end two-port USB client-side hub. (This is not related to the separate '''host-mode''' USB socket described later). One port of the hub goes directly to the '''USB0''' port of the TI AM3358/9 SoC, while the other port connects to a dual-port [http://www.ftdichip.com/Products/ICs/FT2232H.htm FTDI FT2232H] USB-to-serial converter to provide board-to-external-host serial communications and/or JTAG debugging. The BeagleBone's Linux serial console is available through this USB serial connection.

The SoC's '''USB0''' connection to the front-end hub works in one of two modes, and you can toggle between them at any time: it either presents the SD card as a mountable USB storage device to the host, or it provides an [http://www.linux-usb.org/usbnet/ Ethernet-over-USB] networking interface which yields a simple method of quick-start. The Ethernet-over-USB facility is additional to the BeagleBone's normal 10/100 Ethernet interface, which is directly implemented in the SoC rather than hanging off USB as in some other designs. Full IPv4 and IPv6 networking is provided by the supplied Linux system out of the box.

In addition to the USB OTG Device or '''client-mode''' facilities already described, BeagleBone also provides one '''host-mode''' USB type-A socket on the other end of the board. This is driven from the '''USB1''' connection on the AM3358/9 SoC, and provides access to USB host peripherals such as mice, keyboards, storage, and wifi or Bluetooth dongles, or a USB hub for further expansion.

= Specifications =
* Up to 720-MHz superscalar ARM Cortex-A8
* 256-MB DDR2 RAM
* 10/100 Ethernet RJ45 socket, IPv4 and IPv6 networking
* MicroSD slot and 4GB microSD card supplied
* Preloaded with Angstrom ARM Linux Distribution
* Single USB 2.0 type A host port
* Dual USB hub on USB 2.0 type mini-A OTG device port
* On-board USB-to-serial/JTAG over one shared USB device port
* Storage-over-USB or Ethernet-over-USB on other USB device port
* Extensive I/O: 2 I2C, 5 UART, SPI, CAN, 66 GPIO, 8 PWM, 8 ADC
* +5V DC power from barrel connector or USB device port
* Two 46-pin 3.3-V peripheral headers with multiplexed LCD signals
* Board size: 3.4" × 2.1" (86.4mm x 53.3mm) -- fits in an Altoid tin

= Expansion Connectors =
The BeagleBone provides two 46-pin dual-row expansion connectors "'''P9'''" and "'''P8'''" which are also known as "'''Expansion A'''" and "'''Expansion B'''", respectively. The location and pinout of these connectors is illustrated below (click tables to enlarge). All signals on expansion headers are 3.3V except where indicated otherwise.

=== P9 and P8 - Each 2x23 pins ===
[[File:BeagleBone_P9_256x256.jpg|256px|left|top|border|P9 Header|link=File:BeagleBone_p9_pinout.jpg]]
[[File:BeagleBone_P9_P8_256x256.jpg|256px|top|border|BeagleBone P9 + P8|link=File:BeagleBone_P9_P8_512x512.jpg]]
[[File:BeagleBone_P8_256x256.jpg|256px|top|border|P8 Header|link=File:BeagleBone_p8_pinout.jpg]]
 
In addition to the two large headers above, a small 10-pin dual-row connector provides "'''P6'''" provides a "'''PMIC Expansion'''" that brings out some additional signals from the TPS65217B Power Management IC, using the following pinout:

=== P6 - 2x5 pins''' ===
[[File:BeagleBone_P6_464x222.jpg|464px|left|middle|border|P6 MPIC Expansion Header]]
'''IMPORTANT'''

This diagram of P6 provides an '''UNDERSIDE PINOUT''' view.

It is therefore ''' ''laterally inverted'' ''' relative to the photograph.

To obtain the top-side pinout that corresponds to the physical orientation shown in the photograph, swap the two rows of pins so that odd-numbered pins are on the left of even-numbered pins. 

= Expansion Boards and Accessories =

== Capes ==
A '''BeagleBone Cape''' is an expansion board which can be plugged into the BeagleBone's two 46-pin dual-row '''Expansion Headers''' and which in turns provides similar headers onto which further capes can be stacked. Up to four capes at a time can be stacked on top of a BeagleBone. An expansion board which can be fitted only at the top of a stack of capes (usually for physical reasons) is a special case of "cape", but this usage is common for display expansion boards such as LCDs (see next section).

Capes are required to provide a 32Kbyte I2C-addressed EEPROM which holds board information such as board name, serial number and revision, although this is typically omitted on simple prototyping capes. Capes are also expected to provide a 2-position DIP switch to select their address in the stack, although this too is often omitted in prototyping capes.

The [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 Capes Registry] seeks to index all existing capes and cape concepts, including private projects. A [https://docs.google.com/spreadsheet/viewform?formkey=dDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc6MQ registration page] is available to help add capes to the list.

This section lists only those capes which are available commercially or which are close to a production release, as well as open hardware designs.

* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_DVID CircuitCo BeagleBone DVI-D cape]
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_Breadboard CircuitCo BeagleBone Breadboard cape]
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_Breakout CircuitCo BeagleBone Breakout cape]
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_CANBus CircuitCo BeagleBone CANBus cape]
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_RS232 CircuitCo BeagleBone RS232 cape]
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_Battery CircuitCo BeagleBone Battery cape]
* [http://www.adafruit.com/products/572 Adafruit Proto Cape kit for BeagleBone]
* [http://www.towertech.it/en/products/hardware/tt3201-can-cape/ TowerTech TT3201 Multi-Channel CAN Cape]
* [https://specialcomp.com/beaglebone/BeagleBone_FPGA.html Special Computing Spartan-3A FPGA cape for BeagleBone] -- in development
* [http://syntheticlifeforms.net/?p=43 Thinking Machines LCD-IO Expansion Cape] -- in development
* [https://github.com/piranha32/FlyingBone Open Source BeagleBone Prototyping Board] -- piranha32 GitHub repository
* [http://www.armkits.com/product/beaglebone-hdmicape.asp Embest BeagleBone HDMI cape]

== LCD Displays and Other Expansions ==
LCD displays for the BeagleBone are typically implemented as capes which plug in as the ''' ''top board'' ''' in a stack of capes, for reasons of visibility. Such displays are often larger than the BeagleBone itself, so the normal physical relationship in which a daughterboard is smaller than its host board is inverted. In this arrangement it is the expansion board that provides the physical support for the BeagleBone.

* [[File:Beaglebone.jpg|320px|thumb|BeadaFrame]][http://www.nxelec.com/products/hmi/beadaframe-beaglebone NAXING Electronics BeadaFrame] with BeagleBone companion board
:Expanded Hardware Features:
:* 7" 800x480 TFT LCD screen
:* PWM Backlight control
:* Resistive touch panel
:* Plastic frame
:* 256MB Nand flash(K9F2G08)
:* RS232 serial ports(UART1 w/ CTS&RTS)
:* Stereo audio out
:* Micro-phone in
:* 6 x USER buttons
:* PWM Beeper
:* RTC with Battery(DS1302)

* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_LCD3 CircuitCo BeagleBone LCD3 cape and LCD display]
: 3.5" TFT LCD screen, resolution 320x240, 4-wire resistive touchscreen, seven buttons at finger-friendly positions.
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_LCD7 CircuitCo BeagleBone LCD7 cape and LCD display]
: 7" TFT LCD screen, resolution 800x480, 4-wire resistive touchscreen, rear mount for BeagleBone and capes.

== Cases ==
* [http://www.adafruit.com/products/699 Adafruit Bone Box - Enclosure for Beagle Bone]
* [http://www.skpang.co.uk/catalog/acrylic-cover-for-beaglebone-p-1076.html SK Pang Acrylic Cover for BeagleBone]
* [http://specialcomp.com/beagleboard/BB-Bone-assy2_l.jpg Special Computing Bone Acrylic Case]
* [http://www.thingiverse.com/thing:19153 canadaduane's 3D-printable BeagleBone Case design]
* [http://www.thingiverse.com/thing:16195 NinjaBlock's 3D-printable Beaglebone front panel design]
* [http://www.thingiverse.com/thing:20122 builttospec's laser-cut design for BeagleBone Enclosure with DVI Cape]
* [http://www.built-to-spec.com/blog/2012/03/01/beaglebone-case-update-and-new-kits-page/ Built to Spec BeagleBone Case Update], and [http://builttospecstore.storenvy.com/products/225603-beaglebone-enclosure final product]

= BeagleBone Operating Systems =
BeagleBone's default operating system is [http://www.angstrom-distribution.org/ Angstrom], which ships with the board. This section provides basic information on Angstrom and other operating systems commonly used on BeagleBone. This information may help in making a preliminary choice, but full details should be obtained from the home sites.

=== Angstrom ===
* Home site: http://www.angstrom-distribution.org/
* Mailing lists: [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel angstrom-distro-devel] and [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users angstrom-distro-users]
* IRC channel: irc://irc.freenode.net/#angstrom
Ångström was started by a small group of people who worked on the OpenEmbedded, OpenZaurus and OpenSimpad projects to unify their effort to make a stable and user-friendly distribution for embedded devices like handhelds, set top boxes and network-attached storage devices.
Ångström can scale down to devices with only 4MB of flash storage.

The Angstrom community does not provide a forum, [http://www.angstrom-distribution.org/contact intentionally].

Angstrom uses [http://www.busybox.net/ Busybox] for many key utilities, which has both pros and cons. Advantages include requiring less storage space and a smaller memory footprint for many common utilities, which also improves system startup time and performance. The main disadvantages stem from those utilities not mirroring exactly their full-size counterparts. These differences can be annoying if one is used to standard behavior, and may also break shell scripts that rely on portable functionality.

Angstrom uses [http://connman.net/ connman] for network connection management, but no documentation is available for this currently. Also, man(1) and man pages are not provided by default, nor debugging utilities like strace(1) and tcpdump(1). Getting started may therefore present difficulties, depending on experience.

=== Debian ===
* See [[BeagleBoardDebian]]
* Home site: [http://wiki.debian.org/ArmEabiPort http://wiki.debian.org/ArmEabiPort]
* Mailing list: http://lists.debian.org/debian-arm/
* IRC channel: irc://irc.debian.org/debian-arm
The ARM EABI port is the default port of the standard Debian distribution of Linux for the ARM architecture ("armel").
EABI ("Embedded ABI") is actually a family of ABIs, and one of the "subABIs" is the GNU EABI for Linux which is used for this port.
A newer port targeted at newer hardware with another ABI ("armhf") is currently under development and is expected to ship with Debian 7.0 (Wheezy).

The [http://www.debian.org/intro/about Debian Project] is strongly committed to software freedom, and has a long pedigree and a good reputation.

=== Ubuntu ===
* See [[BeagleBoardUbuntu]]
* Home site: https://wiki.ubuntu.com/ARM
* IRC channel: irc://irc.freenode.net/#ubuntu-arm
The vision for Ubuntu is part social and part economic: free software, available free of charge to everybody on the same terms, and funded through a portfolio of services provided by Canonical.

The first version of Ubuntu was based on the GNOME desktop, but has since added a KDE edition, Kubuntu, and a server edition. All of the editions of Ubuntu share common infrastructure and software. In recent years, special emphasis has been placed on netbooks for lightweight, connected, mobile computing, and on the cloud as a new architecture for data centres.

=== Fedora ===
* See [[BeagleBoardFedora]].
* Home site: http://fedoraproject.org/wiki/Architectures/ARM
* Mailing list: http://lists.fedoraproject.org/pipermail/arm/
* IRC channel: irc://irc.freenode.net/#fedora-arm
The Fedora Project is sponsored by Red Hat, which invests in its infrastructure and resources to encourage collaboration and incubate innovative new technologies. Some of these technologies may later be integrated into Red Hat products. They are developed in Fedora and produced under a free and open source license from inception, so other free software communities and projects are free to study, adopt, and modify them.

Red Hat has been a major player since the earliest days of Linux distributions, and has earned a good reputation for solidity which continues in Fedora. The Fedora ARM initiative is very active (see mailing list).

=== ArchLinux ===
* Home site: http://archlinuxarm.org/platforms/armv7/beaglebone
* Source repository: https://github.com/archlinuxarm/PKGBUILDs
* IRC channel: irc://irc.freenode.net/#archlinux-arm
Arch Linux for BeagleBone is a version of the Arch Linux ARM distribution. This carries forward the Arch Linux philosophy of simplicity and user-centrism, targeting and accommodating ''competent'' Linux users by giving them complete control and responsibility over the system. Instructions are provided to assist in navigating the nuances of installation on the varied ARM platforms; however, the system itself will offer little assistance to the user.

The entire distribution is on a rolling-release cycle that can be updated daily through small packages instead of huge updates on a defined release schedule. Most packages are unmodified from what the upstream developer originally released.

=== Gentoo ===
* Home site: http://dev.gentoo.org/~armin76/arm/beaglebone/install.xml
* IRC channel: irc://irc.freenode.net/#gentoo-embedded
Gentoo is a source-based '' '''meta'''-distribution'' of Linux. Instead of distributing a standard system image built with predefined options, Gentoo gives each user the means to create their own customized system that doesn't contain unused bloat and with minimum dependencies. Upgrades are incremental and under user control, so a Gentoo system is normally always up-to-date and wholesale upgrades are avoided.

Being a source-based system, the downside of Gentoo for low-power ARM systems is very long install times for large applications. Cross-compilation on x86 machines and [http://www.gentoo.org/doc/en/distcc.xml distcc] can overcome this problem, but they add complexity.

=== Sabayon ===
* Home site: [http://wiki.sabayon.org/index.php?title=Hitchhikers_Guide_to_the_BeagleBone_%28and_ARMv7a%29 wiki.sabayon.org/Hitchhikers Guide to the BeagleBone]
* IRC channel: irc://irc.freenode.net/#sabayon
Sabayon Linux uses the mechanisms of Gentoo to create a pre-configured Linux distribution that can be installed as rapidly as a normal binary distribution, but still retains the benefits of Gentoo's source-based package management. Sabayon on Intel/AMD also provides the Entropy binary package management system, which could in principle greatly ease installation of packages on resource-constrained embedded Linux devices, but this is not yet available for ARM.

Although it is still early days for Sabayon on ARM (and hence on BeagleBone), there is regular progress reported on [http://lxnay.wordpress.com/2012/ lxnay's blog], and contributions from the community would probably accelerate the work.

=== Buildroot ===
* Home site: http://www.zoobab.com/beaglebone
* Source repository: https://github.com/fhunleth/buildroot-beaglebone
* Buildroot project site: http://buildroot.uclibc.org/
Buildroot is a set of Makefiles and patches that makes it easy to generate a complete embedded Linux system. Buildroot can generate any or all of a cross-compilation toolchain, a root filesystem, a kernel image and a bootloader image. Buildroot is useful mainly for people working with small or embedded systems, using various CPU architectures (x86, ARM, MIPS, PowerPC, etc.) : it automates the building process of your embedded system and eases the cross-compilation process.

The resulting root filesystem is mounted read-only, but other filesystems can be mounted read/write for persistence. Although user accounts can be created, in practice almost everything is done as root. Buildroot uses no package manager. Instead, package selection is managed through '''make menuconfig'''.

=== Nerves Erlang/OTP ===
* Home site: http://nerves-project.org/
* Source repository: https://github.com/nerves-project/bbone-erlang-buildroot
* Erlang project site: http://www.erlang.org/
Erlang is a programming language used to build massively scalable soft realtime systems with high availability requirements (5-9’s). Some of its uses are in telecoms, banking, e-commerce, computer telephony and instant messaging. Erlang’s runtime system has built-in support for concurrency, distribution and fault tolerance.

OTP is a set of Erlang libraries and design principles providing middle-ware to develop these systems. It includes its own distributed database, applications to interface towards other languages, debugging and release handling tools.

The Nerves project provides an embedded Linux-based environment for running Erlang and an easy-to-use API to access common I/O interfaces, based on '''Buildroot''' (see above). If you are interested in running an Erlang node on a low power ARM-based board such as BeagleBone, this project can get you started.

= Board recovery =
* See [http://elinux.org/BeagleBoardRecovery#USB_recovery BeagleBoardRecovery] ''--- (*) Check applicability''

= Software Development =
Software development on the BeagleBone is normally no different to any other Linux platform, and typically varies with language and with the IDE used, if any. This section deals only with development issues that are specific to BeagleBone, or mostly so.

=== Cloud9 IDE and Bonescript ===
''..... description here .....''
* Source repository: https://github.com/jadonk/bonescript
* Language documentation: http://nodejs.org/

=== BeagleBone JTAG Debugging ===
''..... description here .....''

===Using Netbeans to remotely compile and debug C/C++===

When developing c/c++ on a linux desktop, a toolchain is available for cross-compiling the code for arm. However no such toolchain is readily available for windows. Netbeans can be used to write the code on your desktop, save it in a location accessible to the beagle, and then automatically compile it on the beagle itself using ssh and the built in compiler on the beaglebone's OS.

Netbeans can also use GDB for remote debugging over ssh.

Requirements:

* Set up a samba / smb network share through which code can be shared between both desktop and beagle
* Give netbeans the SSh login details of the beagle
* Give netbeans the path mapping so it can translate between the desktop code folder and beagle code folder
* Setup only takes a few minutes.

====More info====

* Download Netbeans (Windows/Linux/OS-X/Solaris): http://www.netbeans.org/
* Example tutorial on setting this up: http://mechomaniac.com/BeagleboardDevelopmentWithNetbeans

= FAQ =

For BeagleBoard frequently asked questions (FAQ) see [[BeagleBoardFAQ|community FAQ]] and "official" [http://beagleboard.org/support/faq BeagleBoard.org FAQ].

= Links =
== Home page and Community ==
* [http://beagleboard.org/ beagleboard.org] -- home for BeagleBoard and BeagleBone products
* irc://irc.freenode.net/#beagle -- official combined IRC channel
* [http://beagleboard.org/discuss Google Groups forums/mailing list] -- [https://groups.google.com/forum/?fromgroups#!forum/beagleboard English], [http://groups.google.com/group/pandabeagle-jp Japan], [http://groups.google.com/group/beagleboard-brasil Brasil], [https://groups.google.com/group/beagle-board-turkiye Turkey]
* [http://beagleboard.org/project BeagleBoard and BeagleBone projects list]
* [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 Capes Registry] and its [https://docs.google.com/spreadsheet/viewform?formkey=dDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc6MQ registration page]
* [http://www.adafruit.com/blog/category/beaglebone/ BeagleBone articles at Adafruit blog] -- products, projects and tutorials
* Use [http://www.google.de/ Google] to search beagleboard.org (including [http://www.beagleboard.org/irclogs/ IRC logs]) using ''site:beagleboard.org <search term>''

== Tutorials and Videos ==
* [http://beagleboard.org/static/bonescript/bone101/index.html ''BeagleBone: BeagleBoard-101 Intro''] -- slides (turn off Javascript for single page)
* [http://www.youtube.com/watch?v=EEnOWR-GXjk ''BeagleBone Intro''], video by Jason Kridner, Texas Instruments
* [http://www.youtube.com/watch?v=Y0uqRVxismQ ''How-To: Get Started with the BeagleBone''], video by Matt Richardson, MakeMagazine
* [http://www.youtube.com/watch?v=z6b4zlh0IrE ''The Beaglebone - Unboxing, Introduction Tutorial and First Example''], video by Derek Molloy, DCU/EE
* [http://www.youtube.com/watch?v=vFv_-ykLppo ''Beaglebone: C/C++ Programming Introduction for ARM Embedded Linux Development using Eclipse''], video by Derek Molloy, DCU/EE
* [http://www.youtube.com/watch?v=SaIpz00lE84 ''Beaglebone: GPIO Programming on ARM Embedded Linux''], video by Derek Molloy, DCU/EE
* [https://gist.github.com/4013192 ''C code for GPIO polling''], sample code by Andrew Montag
* [http://borderhack.com/?p=1062 First steps with the Beaglebone], introductory HOWTO by octavio at borderhack
* [http://learn.adafruit.com/beaglebone Adafruit Learning System - BeagleBone] -- web page

== Manuals and resources ==
* [http://beagleboard.org/static/beaglebone/a3/Docs/Hardware/BONE_SRM.pdf BeagleBone System Reference Manual (rev. A3_1.0)].
* [http://www.ti.com/am335x Texas Instruments - Sitara ARM Cortex-A8 Microprocessor overview].
* [http://infocenter.arm.com/help/topic/com.arm.doc.subset.architecture.reference/index.html#v7AR ARM/ARMv7-AR Architecture] -- ARM Cortex-A8 architecture overview
* [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344d/DDI0344D_cortex_a8_r2p1_trm.pdf ARM Cortex-A8 Technical Reference Manual r2p1]
* [http://www.arm.com/support/university/development-platforms/cortex-a8-development-platforms.php ARM Cortex-A Development Platforms] -- ARM page on Beagle boards
* [http://www.ti.com/product/tps65217 TI TPS65217 Power Management IC], [http://www.ti.com/lit/ds/symlink/tps65217.pdf TPS65217 PMIC datasheet]
* [http://www.ftdichip.com/Products/ICs/FT2232H.htm FTDI FT2232H Hi-Speed Dual USB UART/FIFO IC overview], [http://www.ftdichip.com/Support/Documents/DataSheets/ICs/DS_FT2232H.pdf FT2232H datasheet]
* [http://www.linux-usb.org/gadget/index.html Linux-USB Gadget API Framework] and [http://www.linux-usb.org/gadget/h2-otg.html USB OTG], and [http://forums.gentoo.org/viewtopic-t-843255.html kernel config] -- Ethernet-over-USB
== Translations ==
* 한국어:[[KR:BeagleBone]]

== Errata ==

= Subpages =
<splist
parent=
showparent=no
sort=desc
sortby=title
liststyle=ordered
showpath=no
kidsonly=no
debug=0
/>

SBC8018 en

2012-02-21T09:32:40Z

Yclinda666:

[http://www.elinux.org/SBC8018 '''中文版本''''']

'''Numbers of [http://www.armkits.com/product/sbc8018.asp '''SBC8018'''] Development Board wiht 128MB DDR and 128MB Nand Flash based on [http://www.ti.com/product/am1808 TI AM1808] industrial processor are provided by Embest now. Call us to get more information.'''

:SBC8018 Single Board Computer an industrial application of ARM Embedded Single Board Computer designed by Embest Info&Tech Co.,LTD..SBC8018 boards 128MB DDR, 128MB NAND Flash, except some interface used normally, an SATA interface is offered to supply large data storage applications. SBC8018 is a low power, low cost and high-performance's industrial application. SBC8018 can be used many industries to designed products quickly such as portable navigation multimedia devices,portable data acquisition devices,industrial automation and smart house, and so and.
----
This article is writed to introduce the hardware and software about the SBC8018 Single Board Computer and provide an exchange platform for sharing experience of TI AM1808. It can help users to learn the SBC8018 quickly, to summarize and answer the problem
you may encounter probably.

'''New (Date:21-02-2012): the problem that the board could not boot from Nand Flash stably in WinCE OS has been settled, please download the software patches from'''[http://www.embedinfo.com/english/download/SBC8018_patch_20120221.zip here]
 
 
=='''General Description'''==

==='''General Description'''===

:The SBC8018 Single Board Computer is a compact, low-cost with high-performance controller board designed by Embest. It is based on TI’s AM1808 ARM9 low-power application processor which enables OEMs and ODMs to quickly bring to market devices featuring robust operating systems support, rich user interfaces, and high processing performance life through the maximum flexibility of a fully integrated mixed processor solution.

:The SBC8018 Single Board Computer takes full features of the AM1808 microprocessor and has 128MB Mobile DDR SDRAM and 128MB Nand Flash on board. It has exposed many other hardware interfaces including Serial port, LCD/TSP, USB Host/OTG, Ethernet, Audio, SATA, two Camera, TF card, etc. It has one 14-pin JTAG interface which can be used with XDS100v2 emulator available from Embest. Embest also offers 4.3” and 7” LCD display with touch screen as optional modules for this board.

:The board is a ready-to-run solution which is provided with Linux 2.6.33 and WinCE 6.0 BSP. It would be an ideal development platform for customers requiring a low power ARM9 processor with cost-effective price point and small form factor for consumer, embedded industrial, medical and other embedded connectivity applications.
 
::- 375MHz TI AM1808 ARM926 Microprocessor

::- Onboard 128MByte DDR SDRAM + 128MByte NAND Flash

::- UART, USB, Ethernet, LCD/TSP, SATA, Camera, Audio, TF, JTAG,...

::- Optional WiFi, Camera and 3G Modules

::- Ready-to-Run Linux2.6.33 and WinCE 6.0 OS

:::[[File:Sbc8018-L.jpg|SBC8018]]

==='''Interfaces and Peripherals'''===

::::[[File:Sbc8018con.gif|SBC8018 interface and peripherals]]

=='''Hardware Features'''==

==='''Processor'''===

:*TI AM1808 ARM9 microprocessor

:*375-MHz ARM926EJ-S RISC MPU, also supports 456MHz operation

:*ARM926EJ-S Core

:*ARM9 Memory Architecture

:*Enhanced Direct-Memory-Access Controller 3 (EDMA3)

:*128K-Byte On-chip Memory

:*1.8V or 3.3V LVCMOS IOs (except for USB and DDR2 interfaces)

:*Two External Memory Interfaces

:*Three Configurable 16550 type UART Modules

:*LCD Controller

:*Two Serial Peripheral Interfaces (SPI) Each With Multiple Chip-Selects

:*Two MMC/SD Card Interface with Secure Data I/O (SDIO) Interfaces

==='''Memory'''===

:*128MByte Mobile DDR SDRAM

:*128MByte NAND Flash (on the rear of the board)

==='''Audio/Video Interfaces'''===

:*Audio input interface (Mic In)

:*Two-channel Audio output interface (Line Out)

:*Two Camera interfaces (30-pin FPC connector on the rear of the board, supports CCD or CMOS camera)

:*LCD/Touch Screen interface (50-pin FPC connector, support resolution up to 2048*2048)

==='''Data Transfer Interfaces and Other Facilities'''===

:*1 x 5 line Debug serial port, RS232 voltage (brings out by DB9 connector)

:*2 x 3 line serial ports, TTL voltage (brings out by extension connector)

:*1 x USB2.0 OTG port, High-speed (Mini USB type)

:*1 x USB1.1 Host port, Full-speed (USB-A type)

:*1 x TF card slot

:*1 x Serial ATA connector, supports both SATA I (1.5 Gbps) and SATA II (3.0 Gbps)

:*1 x 10/100Mbps Ethernet interface (RJ45 connector)

:*1 x RESET button

:*1 x BACK button

:*1 x HOME button

:*1 x MENU button

:*1 x 14-pin JTAG connector (for using TI’s XDS100v2 Emulator)

:*2 x 40-pin extension connectors (SPI, I2C, McBSP, UART, 1.8V, 3.3V, 5V, GPIO are brought out from these connectors)

:*Battery backed RTC (User needs to prepare battery himself, CR1220 model is ok)

==='''Mechanical Parameters'''===

:*Dimensions: 112.24mm x 82.29mm

:*Working temperature: 0~70 Celsius

:*Input Voltage: +5V

:*Humidity Range: 20%~90%

:*Power Consumption: 0.22A@5V (working without LCD)

==='''Interfaces'''===

[[Image:XDS100-P.jpg]]

[http://www.armkits.com/product/xds100.asp XDS100v2 USB JTAG Emulator]

:The XDS100v2 USB JTAG Emulator is the second release of the XDS100 JTAG emulator technology supporting debug of a variety of TI devices. It allows the user direct access between the host computer and the DSP through a 14-pin JTAG header. It is compatible with Code Composer Studio (CCS) V4 IDE from Texas Instruments and compatible with Windows 2000/XP/Vista.

[[Image:CAM8000-P.jpg]]

[http://www.timll.com/chinese/product/CAMERA.asp Analog camera moduleCAM8000-A]

:Standard resolution of 720*576 PAL standard,connect SBC8018 by 30PIN FFC cable, connect the camera equipment by other side of the BNC connector, achieved through the camera input function.

[[Image:WIFI8000-P.jpg]]

[http://www.timll.com/chinese/product/WiFi.asp USB WiFi wireless module WF8000-U]

:A wireless communication module that base on USB connector ,can be used for all product designed by Embest. With the technology of wirelessly connection for personal computer terminals and based on the IEEE 802.11 standard wireless network protocol, this module is highly integrated with MAC/BBP and 2.4GHz radio single chip.With a wide range of wireless connectivity and large throughput,the module meets the IEEE 802.11 b/g standard. After all,it makes WF8000-U WIFI module good performance and low power consumption with superior radio architecture and optimization algorithms.

[[Image:CDMA-S.jpg‎]]

[http://www.timll.com/chinese/product/CDMA8000-U.asp CDMA8000-U 3G wireless communication module]

:CDMA8000 is a 3G wireless communication module issued by Embest.Embest based on the newest UMUTS standard developed by the MSM6290 platform.This module is applied in the network of EDGE ,GRRS ,GSM and WCDMA(HSPA),which can achieve global roaming. General USB interface and powerful software support platform make the module have friendly secondary development of software and hardware platform.It can support a variety of peripheral devices and meet the user’s rich requirement of sevice function.

[[Image:WCDMA8000.jpg]]

[http://www.timll.com/chinese/product/WCDMA8000-U.asp WCDMA8000-U 3G wireless communication module]

:WCDMA8000 is a 3G wireless communication module issued by Embest based on the newest UMUTS standard developed by the MSM6280 platform. This module is applied in the network of EDGE ,GRRS ,GSM and WCDMA(HSPA), which can achieve global roaming. General USB interface and powerful software support platform make the module have friendly secondary development of software and hardware platform. It can support a variety of peripheral devices and meet the user’s rich requirement of service function.

'''LCD Screen Interface'''

:24bit LCD screen interface,true color RGB signal output,R:B:G=8:8:8.
:The connector is a 50-pin FPC connector which is 0.5mm pitch
:Signal types:

:{| border= "1"
|RGB data||LCD control data||SPI signal||IIC singal||Touch-screen signal||Output voltage
|-
|24bit||6bit||4bit||2bit||4bit||5bit
|-
|R:G:B=8:8:8||Control signals for rows and other controls||Standard SPI signals||2 bits IIC singal||4 bit touch-screen singal||output voltage is 5V,3.3V and 1.8V
|}

'''Camera Interface'''

:{| border = 1
|Pin Number||Singal||Function
|-
|1 ||GND|| GND
|-
|2 ||D0|| Test Point
|-
|3 ||D1|| Test Point
|-
|4 ||R_CAM_D0|| VPIF capture data bit 0
|-
|5 ||R_CAM_D1|| VPIF capture data bit 1
|-
|6 ||R_CAM_D2|| VPIF capture data bit 2
|-
|7 ||R_CAM_D3|| VPIF capture data bit 3
|-
|8 ||R_CAM_D4|| VPIF capture data bit 4
|-
|9 ||R_CAM_D5|| VPIF capture data bit 5
|-
|10 ||R_CAM_D6|| VPIF capture data bit 6
|-
|11 ||R_CAM_D7|| VPIF capture data bit 7
|-
|12 ||D10 ||Test Point
|-
|13 ||D11|| Test Point
|-
|14 ||GND|| GND
|-
|15 ||PCLK|| Pixel clock
|-
|16 ||GND|| GND
|-
|17 ||CAM_HS_A0|| Horizontal synchronization
|-
|18 ||+5VDC_IN|| +5V
|-
|19 ||CAM_VS_A0|| Vertical synchronization
|-
|20 ||+3P3V|| +3.3V
|-
|21 ||CAM_XCLKA_A0|| Test Point
|-
|22 ||CAM_XCLKB_A0|| Test Point
|-
|23 ||GND|| GND
|-
|24 ||CAM_FLD_A0|| Test Piont
|-
|25 ||uP_CAM_WEN0|| Test Piont
|-
|26 ||uP_CAM_STR|| Test Piont
|-
|27 ||CAM_SDA|| I2C0 serial data
|-
|28 ||CAM_SCL|| I2C0 serial clock
|-
|29 ||GND|| GND
|-
|30 ||+1P8V_LDO|| +1.8V
|}

'''SATA Interface'''

:{| border = 1
|Pin Number||Singal||Function
|-
|1 ||GND|| GND
|-
|2 ||SATA_TXP|| SATA receive data(positive)
|-
|3 ||SATA_TXN|| SATA receive data(negative)
|-
|4 ||GND|| GND
|-
|5 ||SATA_RXN|| SATA transmit data(negative)
|-
|6 ||SATA_RXP|| SATA transmit data(positive)
|-
|7 ||GND|| GND
|-
|8 ||NC|| NC
|-
|9 ||GND|| GND
|-
|}

'''JTAG Interface'''

:{| border = 1
|Pin Number||Singal||Fuction
|-
|1 ||TMS|| Test mode select
|-
|2 ||NTRST|| Test system reset
|-
|3 ||TDI|| Test data input
|-
|4 ||GND|| GND
|-
|5 ||VIO|| 1.8V
|-
|6 ||NC|| NC
|-
|7 ||TDO|| TDO
|-
|8 ||GND|| GND
|-
|9 ||RTCK|| RTCK
|-
|10 ||GND|| GND
|-
|11 ||TCK|| Test clock
|-
|12 ||GND|| GND
|-
|13 ||EMU0|| Test emulation 0
|-
|14 ||EMU1|| Test emulation 1
|-
|}

'''The first Extended Interface'''

:{| border = 1
|Pin Number||Singal||Function
|-
|1 ||GND|| GND
|-
|2 ||GND|| GND
|-
|3 ||EMA_A_16_EXP|| GPIO
|-
|4 ||EMA_D_15_EXP|| GPIO
|-
|5 ||EMA_A_15_EXP|| GPIO
|-
|6 ||EMA_D_14_EXP|| GPIO
|-
|7 ||EMA_A_14_EXP|| GPIO
|-
|8 ||EMA_D_13_EXP|| GPIO
|-
|9 ||EMA_A_13_EXP|| GPIO
|-
|10 ||EMA_D_12_EXP|| GPIO
|-
|11 ||EMA_A_0_EXP|| GPIO
|-
|12 ||EMA_D_11_EXP|| GPIO
|-
|13 ||EMA_BA_1_EXP|| GPIO
|-
|14 ||EMA_D_10_EXP|| GPIO
|-
|15 ||EPWMN1_TZ0|| GPIO
|-
|16 ||EMA_D_9_EXP|| GPIO
|-
|17 ||ECAP2_APWM2|| GPIO
|-
|18 ||EMA_D_8_EXP|| GPIO
|-
|19 ||AFSX / GPIO0[12]|| GPIO
|-
|20 ||EMA_CLK_EXP|| GPIO
|-
|21 ||AFSR|| GPIO
|-
|22 ||EMA_SDCKE_EXP|| GPIO
|-
|23 ||AHCLKX/USB_REFCLKIN/UART1_CTSN/GPIO0[10]|| GPIO
|-
|24 ||EMA_CSn_5_EXP|| GPIO
|-
|25 ||GND|| GND
|-
|26 ||EMA_CSn_4_EXP|| GPIO
|-
|27 ||ACLKX/GPIO0[14]|| GPIO
|-
|28 ||EMA_CSn_2_EXP|| GPIO
|-
|29 ||ACLKR/GPIO0[15]|| GPIO
|-
|30 ||EMA_CSn_0_EXP|| GPIO
|-
|31 ||GND|| GND
|-
|32 ||EMA_WAIT_1_EXP|| GPIO
|-
|33 ||GND|| GND
|-
|34 ||GND|| GND
|-
|35 ||+5VDC_IN|| +5V
|-
|36 ||GND|| GND
|-
|37 ||+3P3V|| 3.3V
|-
|38 ||+1P8V_LDO|| 1.8V
|-
|39 ||GND|| GND
|-
|40 ||GND|| GND
|-
|}

'''The Second Extended Interface'''

:{| border = 1
|Pin Number||Singal||Function
|-
|1 ||GND|| GND
|-
|2 ||GND|| GND
|-
|3 ||uP_SPI1_CLK|| SPI1 clock
|-
|4 ||uP_McBSP1_CLKR_EXP|| McBSP1 receive clock
|-
|5 ||uP_SPI1_SOMI|| SPI1 data slave-out-master-in
|-
|6 ||uP_McBSP1_CLKX_EXP|| McBSP1 transmit clock
|-
|7 ||uP_SPI1_SIMO|| SPI1 data slave-in-master-out
|-
|8 ||uP_McBSP0_CLKS_EXP|| McBSP1 sample rate generator clock input
|-
|9 ||uP_SPI1_SCSn0|| SPI1 chip selects
|-
|10 ||AIC_DOUT|| McBSP1 receive frame sync
|-
|11 ||uP_SPI1_ENAN|| SPI1 enable
|-
|12 ||AIC_DIN|| McBSP1 transmit frame sync
|-
|13 ||GND|| GND
|-
|14 ||uP_McBSP0_DR_EXP|| McBSP1 receive data
|-
|15 ||UART1_RXD|| UART1 receive data
|-
|16 ||uP_McBSP0_DX_EXP|| McBSP1 transmit data
|-
|17 ||UART1_TXD|| UART1 transmit data
|-
|18 ||GND|| GND
|-
|19 ||UART1_RTSn|| UART1 ready-to-send output
|-
|20 ||UART2_RXD|| UART2 receive data
|-
|21 ||AIC_MCL|| UART1 clear-to-send input
|-
|22 ||UART2_TXD|| UART2 transmit data
|-
|23 ||GND|| GND
|-
|24 ||I2C0_SCL|| I2C0 serial clock
|-
|25 ||GND|| GND
|-
|26 ||I2C0_SDA|| I2C0 serial data
|-
|27 ||GND|| GND
|-
|28 ||GND|| GND
|-
|29 ||GND|| GND
|-
|30 ||uP_SPI0_CLK|| SPI0 clock
|-
|31 ||GDN|| GND
|-
|32 ||uP_SPI0_SOMI|| SPI0 data slave-out-master-in
|-
|33 ||GND|| GND
|-
|34 ||uP_SPI0_SIMO|| SPI0 data slave-in-master-out
|-
|35 ||GND|| GND
|-
|36 ||uP_SPI0_SCSn0|| SPI0 chip selects
|-
|37 ||+5VDC_IN|| +5V
|-
|38 ||uP_SPI0_ENAN|| 1.8V
|-
|39 ||+3P3V|| +3.3V
|-
|40 ||+1P8V_LDO|| +1.8V
|-
|}

===Physical Dimensions===

[[File:SBC8018size.JPG|The Physical Dimensions Of SBC8018]]

===Board Characteristics===

[[File:SBC8018K.png|The Board Characteristics Of SBC8018]]

=='''Software Features '''==
:{| border="1"
!colspan="1"|OS
!colspan="2"|Item
!colspan="1"|remark
|-
|rowspan="14"|Linux
|rowspan="10"|BIOS
|-
|rowspan="4"|x-loader
|-
|NAND/ONENAND
|-
|MMC/SD
|-
|FAT
|-
|rowspan="5"|U-BOOT
|-
|NAND/ONENAND
|-
|MMC/SD
|-
|FAT
|-
|NET
|-
|rowspan="2"|Kernel
|-
|Linux 2.6.33
|Supports ROM/CRAM/EXT2/EXT3/FAT/ NFS/ JFFS2/UBIFS file systems
|-
|rowspan="2"|Device Driver
|-
|colspan="2"|Serial port, RTC, Ethernet, Nand Flash, LCD, Touch screen, TF card, USB OTG, USB Host, SATA, Audio input/output, key, LED
|-
|rowspan="16"|WinCE
|rowspan="10"|BIOS
|-
|rowspan="4"|x-loader
|-
|NAND / ONENAND
|-
|MMC / SD
|-
|FAT
|-
|rowspan="5"|e-boot
|-
|NAND / ONENAND
|-
|MMC / SD
|-
|FAT
|-
|NET
|-
|rowspan="3"|Device Driver
|-
|colspan="2"|Serial port, RTC, Ethernet, Nand Flash, LCD, Touch screen, TF card, USB OTG, USB Host, Audio input/output, key, LED
|-
|colspan="2"|Power Management (backlight, battery, Sleep/Wakeup, PWM, ADC)
|-
|app
|application module
|Flash Player plug-in and Flash player
|-
|}

==Applications==

:*Portable navigation multimedia devices

:*Digital video set-top boxes

:*Portable game consoles

:*Consumer Design

:*Portable data acquisition devices

:*Embedded

:*And so and

==Information Of Evaluation Kit==

:{|border="1"
|-
|Product Number
|T6010162
|-
|Product Name
|SBC8018 Single Board Computer
|-
|Standard Accessories
|1.SBC8018 Single Board Computer *1

2.5V/2A Power Adapter *1

3.Cross Serial cable *1

4.CD（PDF Schematic,Linux Source Of Driver,WinCE BSP Source,WinCE application source code,Driver for Interface and so and）*1
|-
|Optional Accessories
|1、7-inch LCD screen([http://www.timll.com/chinese/product/lcd8000-70T.asp LCD8000-70T]，Resolution is 800*480)

2、4.3-inch LCD screen([http://www.timll.com/chinese/product/lcd8000-43T.asp LCD8000-43T]，Resolution is 480*272)
|-
|}

'''More information about SBC8018 and how to buy a SBC8018 please visit our website:
http://www.armkits.com/product/sbc8018.asp'''

='''Other [http://www.armkits.com Embest] Products based on TI Processors'''=
[http://www.armkits.com Embest] has designed several products based on TI's ARM9 and ARM Cortex-A8 processors. [http://www.armkits.com Embest]also offers customer design service according to customer's requirements. Whether you need to reduce, add or modify to existing hardwares or generate a new solution, Embest will help customers with expert competence and rich experience. 
* [[DevKit8500]] Evalution Board based on TI's DM3730 or AM3715 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8530.asp SBC8530] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100 Plus] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100] Single Board Computer based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/soc8200.asp SOC8200] Single Board Computer based on TI's AM3517 Sitara ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8510.asp Mini8510] Processor Card based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8100.asp Mini8100] Processor Card based on TI's OMAP3530 ARM Cortex-A8 processor

SBC8018 en

2012-02-21T09:30:09Z

Yclinda666:

[http://www.elinux.org/SBC8018 '''中文版本''''']

'''Numbers of [http://www.armkits.com/product/sbc8018.asp '''SBC8018'''] Development Board wiht 128MB DDR and 128MB Nand Flash based on [http://www.ti.com/product/am1808 TI AM1808] industrial processor are provided by Embest now. Call us to get more information.'''

:SBC8018 Single Board Computer an industrial application of ARM Embedded Single Board Computer designed by Embest Info&Tech Co.,LTD..SBC8018 boards 128MB DDR, 128MB NAND Flash, except some interface used normally, an SATA interface is offered to supply large data storage applications. SBC8018 is a low power, low cost and high-performance's industrial application. SBC8018 can be used many industries to designed products quickly such as portable navigation multimedia devices,portable data acquisition devices,industrial automation and smart house, and so and.
----
This article is writed to introduce the hardware and software about the SBC8018 Single Board Computer and provide an exchange platform for sharing experience of TI AM1808. It can help users to learn the SBC8018 quickly, to summarize and answer the problem
you may encounter probably.

New: the problem that the board could not boot from Nand Flash stably in WinCE OS has been settled, please download the software patches from below [http://www.embedinfo.com/english/download/SBC8018_patch_20120221.zip here]
 
 
=='''General Description'''==

==='''General Description'''===

:The SBC8018 Single Board Computer is a compact, low-cost with high-performance controller board designed by Embest. It is based on TI’s AM1808 ARM9 low-power application processor which enables OEMs and ODMs to quickly bring to market devices featuring robust operating systems support, rich user interfaces, and high processing performance life through the maximum flexibility of a fully integrated mixed processor solution.

:The SBC8018 Single Board Computer takes full features of the AM1808 microprocessor and has 128MB Mobile DDR SDRAM and 128MB Nand Flash on board. It has exposed many other hardware interfaces including Serial port, LCD/TSP, USB Host/OTG, Ethernet, Audio, SATA, two Camera, TF card, etc. It has one 14-pin JTAG interface which can be used with XDS100v2 emulator available from Embest. Embest also offers 4.3” and 7” LCD display with touch screen as optional modules for this board.

:The board is a ready-to-run solution which is provided with Linux 2.6.33 and WinCE 6.0 BSP. It would be an ideal development platform for customers requiring a low power ARM9 processor with cost-effective price point and small form factor for consumer, embedded industrial, medical and other embedded connectivity applications.
 
::- 375MHz TI AM1808 ARM926 Microprocessor

::- Onboard 128MByte DDR SDRAM + 128MByte NAND Flash

::- UART, USB, Ethernet, LCD/TSP, SATA, Camera, Audio, TF, JTAG,...

::- Optional WiFi, Camera and 3G Modules

::- Ready-to-Run Linux2.6.33 and WinCE 6.0 OS

:::[[File:Sbc8018-L.jpg|SBC8018]]

==='''Interfaces and Peripherals'''===

::::[[File:Sbc8018con.gif|SBC8018 interface and peripherals]]

=='''Hardware Features'''==

==='''Processor'''===

:*TI AM1808 ARM9 microprocessor

:*375-MHz ARM926EJ-S RISC MPU, also supports 456MHz operation

:*ARM926EJ-S Core

:*ARM9 Memory Architecture

:*Enhanced Direct-Memory-Access Controller 3 (EDMA3)

:*128K-Byte On-chip Memory

:*1.8V or 3.3V LVCMOS IOs (except for USB and DDR2 interfaces)

:*Two External Memory Interfaces

:*Three Configurable 16550 type UART Modules

:*LCD Controller

:*Two Serial Peripheral Interfaces (SPI) Each With Multiple Chip-Selects

:*Two MMC/SD Card Interface with Secure Data I/O (SDIO) Interfaces

==='''Memory'''===

:*128MByte Mobile DDR SDRAM

:*128MByte NAND Flash (on the rear of the board)

==='''Audio/Video Interfaces'''===

:*Audio input interface (Mic In)

:*Two-channel Audio output interface (Line Out)

:*Two Camera interfaces (30-pin FPC connector on the rear of the board, supports CCD or CMOS camera)

:*LCD/Touch Screen interface (50-pin FPC connector, support resolution up to 2048*2048)

==='''Data Transfer Interfaces and Other Facilities'''===

:*1 x 5 line Debug serial port, RS232 voltage (brings out by DB9 connector)

:*2 x 3 line serial ports, TTL voltage (brings out by extension connector)

:*1 x USB2.0 OTG port, High-speed (Mini USB type)

:*1 x USB1.1 Host port, Full-speed (USB-A type)

:*1 x TF card slot

:*1 x Serial ATA connector, supports both SATA I (1.5 Gbps) and SATA II (3.0 Gbps)

:*1 x 10/100Mbps Ethernet interface (RJ45 connector)

:*1 x RESET button

:*1 x BACK button

:*1 x HOME button

:*1 x MENU button

:*1 x 14-pin JTAG connector (for using TI’s XDS100v2 Emulator)

:*2 x 40-pin extension connectors (SPI, I2C, McBSP, UART, 1.8V, 3.3V, 5V, GPIO are brought out from these connectors)

:*Battery backed RTC (User needs to prepare battery himself, CR1220 model is ok)

==='''Mechanical Parameters'''===

:*Dimensions: 112.24mm x 82.29mm

:*Working temperature: 0~70 Celsius

:*Input Voltage: +5V

:*Humidity Range: 20%~90%

:*Power Consumption: 0.22A@5V (working without LCD)

==='''Interfaces'''===

[[Image:XDS100-P.jpg]]

[http://www.armkits.com/product/xds100.asp XDS100v2 USB JTAG Emulator]

:The XDS100v2 USB JTAG Emulator is the second release of the XDS100 JTAG emulator technology supporting debug of a variety of TI devices. It allows the user direct access between the host computer and the DSP through a 14-pin JTAG header. It is compatible with Code Composer Studio (CCS) V4 IDE from Texas Instruments and compatible with Windows 2000/XP/Vista.

[[Image:CAM8000-P.jpg]]

[http://www.timll.com/chinese/product/CAMERA.asp Analog camera moduleCAM8000-A]

:Standard resolution of 720*576 PAL standard,connect SBC8018 by 30PIN FFC cable, connect the camera equipment by other side of the BNC connector, achieved through the camera input function.

[[Image:WIFI8000-P.jpg]]

[http://www.timll.com/chinese/product/WiFi.asp USB WiFi wireless module WF8000-U]

:A wireless communication module that base on USB connector ,can be used for all product designed by Embest. With the technology of wirelessly connection for personal computer terminals and based on the IEEE 802.11 standard wireless network protocol, this module is highly integrated with MAC/BBP and 2.4GHz radio single chip.With a wide range of wireless connectivity and large throughput,the module meets the IEEE 802.11 b/g standard. After all,it makes WF8000-U WIFI module good performance and low power consumption with superior radio architecture and optimization algorithms.

[[Image:CDMA-S.jpg‎]]

[http://www.timll.com/chinese/product/CDMA8000-U.asp CDMA8000-U 3G wireless communication module]

:CDMA8000 is a 3G wireless communication module issued by Embest.Embest based on the newest UMUTS standard developed by the MSM6290 platform.This module is applied in the network of EDGE ,GRRS ,GSM and WCDMA(HSPA),which can achieve global roaming. General USB interface and powerful software support platform make the module have friendly secondary development of software and hardware platform.It can support a variety of peripheral devices and meet the user’s rich requirement of sevice function.

[[Image:WCDMA8000.jpg]]

[http://www.timll.com/chinese/product/WCDMA8000-U.asp WCDMA8000-U 3G wireless communication module]

:WCDMA8000 is a 3G wireless communication module issued by Embest based on the newest UMUTS standard developed by the MSM6280 platform. This module is applied in the network of EDGE ,GRRS ,GSM and WCDMA(HSPA), which can achieve global roaming. General USB interface and powerful software support platform make the module have friendly secondary development of software and hardware platform. It can support a variety of peripheral devices and meet the user’s rich requirement of service function.

'''LCD Screen Interface'''

:24bit LCD screen interface,true color RGB signal output,R:B:G=8:8:8.
:The connector is a 50-pin FPC connector which is 0.5mm pitch
:Signal types:

:{| border= "1"
|RGB data||LCD control data||SPI signal||IIC singal||Touch-screen signal||Output voltage
|-
|24bit||6bit||4bit||2bit||4bit||5bit
|-
|R:G:B=8:8:8||Control signals for rows and other controls||Standard SPI signals||2 bits IIC singal||4 bit touch-screen singal||output voltage is 5V,3.3V and 1.8V
|}

'''Camera Interface'''

:{| border = 1
|Pin Number||Singal||Function
|-
|1 ||GND|| GND
|-
|2 ||D0|| Test Point
|-
|3 ||D1|| Test Point
|-
|4 ||R_CAM_D0|| VPIF capture data bit 0
|-
|5 ||R_CAM_D1|| VPIF capture data bit 1
|-
|6 ||R_CAM_D2|| VPIF capture data bit 2
|-
|7 ||R_CAM_D3|| VPIF capture data bit 3
|-
|8 ||R_CAM_D4|| VPIF capture data bit 4
|-
|9 ||R_CAM_D5|| VPIF capture data bit 5
|-
|10 ||R_CAM_D6|| VPIF capture data bit 6
|-
|11 ||R_CAM_D7|| VPIF capture data bit 7
|-
|12 ||D10 ||Test Point
|-
|13 ||D11|| Test Point
|-
|14 ||GND|| GND
|-
|15 ||PCLK|| Pixel clock
|-
|16 ||GND|| GND
|-
|17 ||CAM_HS_A0|| Horizontal synchronization
|-
|18 ||+5VDC_IN|| +5V
|-
|19 ||CAM_VS_A0|| Vertical synchronization
|-
|20 ||+3P3V|| +3.3V
|-
|21 ||CAM_XCLKA_A0|| Test Point
|-
|22 ||CAM_XCLKB_A0|| Test Point
|-
|23 ||GND|| GND
|-
|24 ||CAM_FLD_A0|| Test Piont
|-
|25 ||uP_CAM_WEN0|| Test Piont
|-
|26 ||uP_CAM_STR|| Test Piont
|-
|27 ||CAM_SDA|| I2C0 serial data
|-
|28 ||CAM_SCL|| I2C0 serial clock
|-
|29 ||GND|| GND
|-
|30 ||+1P8V_LDO|| +1.8V
|}

'''SATA Interface'''

:{| border = 1
|Pin Number||Singal||Function
|-
|1 ||GND|| GND
|-
|2 ||SATA_TXP|| SATA receive data(positive)
|-
|3 ||SATA_TXN|| SATA receive data(negative)
|-
|4 ||GND|| GND
|-
|5 ||SATA_RXN|| SATA transmit data(negative)
|-
|6 ||SATA_RXP|| SATA transmit data(positive)
|-
|7 ||GND|| GND
|-
|8 ||NC|| NC
|-
|9 ||GND|| GND
|-
|}

'''JTAG Interface'''

:{| border = 1
|Pin Number||Singal||Fuction
|-
|1 ||TMS|| Test mode select
|-
|2 ||NTRST|| Test system reset
|-
|3 ||TDI|| Test data input
|-
|4 ||GND|| GND
|-
|5 ||VIO|| 1.8V
|-
|6 ||NC|| NC
|-
|7 ||TDO|| TDO
|-
|8 ||GND|| GND
|-
|9 ||RTCK|| RTCK
|-
|10 ||GND|| GND
|-
|11 ||TCK|| Test clock
|-
|12 ||GND|| GND
|-
|13 ||EMU0|| Test emulation 0
|-
|14 ||EMU1|| Test emulation 1
|-
|}

'''The first Extended Interface'''

:{| border = 1
|Pin Number||Singal||Function
|-
|1 ||GND|| GND
|-
|2 ||GND|| GND
|-
|3 ||EMA_A_16_EXP|| GPIO
|-
|4 ||EMA_D_15_EXP|| GPIO
|-
|5 ||EMA_A_15_EXP|| GPIO
|-
|6 ||EMA_D_14_EXP|| GPIO
|-
|7 ||EMA_A_14_EXP|| GPIO
|-
|8 ||EMA_D_13_EXP|| GPIO
|-
|9 ||EMA_A_13_EXP|| GPIO
|-
|10 ||EMA_D_12_EXP|| GPIO
|-
|11 ||EMA_A_0_EXP|| GPIO
|-
|12 ||EMA_D_11_EXP|| GPIO
|-
|13 ||EMA_BA_1_EXP|| GPIO
|-
|14 ||EMA_D_10_EXP|| GPIO
|-
|15 ||EPWMN1_TZ0|| GPIO
|-
|16 ||EMA_D_9_EXP|| GPIO
|-
|17 ||ECAP2_APWM2|| GPIO
|-
|18 ||EMA_D_8_EXP|| GPIO
|-
|19 ||AFSX / GPIO0[12]|| GPIO
|-
|20 ||EMA_CLK_EXP|| GPIO
|-
|21 ||AFSR|| GPIO
|-
|22 ||EMA_SDCKE_EXP|| GPIO
|-
|23 ||AHCLKX/USB_REFCLKIN/UART1_CTSN/GPIO0[10]|| GPIO
|-
|24 ||EMA_CSn_5_EXP|| GPIO
|-
|25 ||GND|| GND
|-
|26 ||EMA_CSn_4_EXP|| GPIO
|-
|27 ||ACLKX/GPIO0[14]|| GPIO
|-
|28 ||EMA_CSn_2_EXP|| GPIO
|-
|29 ||ACLKR/GPIO0[15]|| GPIO
|-
|30 ||EMA_CSn_0_EXP|| GPIO
|-
|31 ||GND|| GND
|-
|32 ||EMA_WAIT_1_EXP|| GPIO
|-
|33 ||GND|| GND
|-
|34 ||GND|| GND
|-
|35 ||+5VDC_IN|| +5V
|-
|36 ||GND|| GND
|-
|37 ||+3P3V|| 3.3V
|-
|38 ||+1P8V_LDO|| 1.8V
|-
|39 ||GND|| GND
|-
|40 ||GND|| GND
|-
|}

'''The Second Extended Interface'''

:{| border = 1
|Pin Number||Singal||Function
|-
|1 ||GND|| GND
|-
|2 ||GND|| GND
|-
|3 ||uP_SPI1_CLK|| SPI1 clock
|-
|4 ||uP_McBSP1_CLKR_EXP|| McBSP1 receive clock
|-
|5 ||uP_SPI1_SOMI|| SPI1 data slave-out-master-in
|-
|6 ||uP_McBSP1_CLKX_EXP|| McBSP1 transmit clock
|-
|7 ||uP_SPI1_SIMO|| SPI1 data slave-in-master-out
|-
|8 ||uP_McBSP0_CLKS_EXP|| McBSP1 sample rate generator clock input
|-
|9 ||uP_SPI1_SCSn0|| SPI1 chip selects
|-
|10 ||AIC_DOUT|| McBSP1 receive frame sync
|-
|11 ||uP_SPI1_ENAN|| SPI1 enable
|-
|12 ||AIC_DIN|| McBSP1 transmit frame sync
|-
|13 ||GND|| GND
|-
|14 ||uP_McBSP0_DR_EXP|| McBSP1 receive data
|-
|15 ||UART1_RXD|| UART1 receive data
|-
|16 ||uP_McBSP0_DX_EXP|| McBSP1 transmit data
|-
|17 ||UART1_TXD|| UART1 transmit data
|-
|18 ||GND|| GND
|-
|19 ||UART1_RTSn|| UART1 ready-to-send output
|-
|20 ||UART2_RXD|| UART2 receive data
|-
|21 ||AIC_MCL|| UART1 clear-to-send input
|-
|22 ||UART2_TXD|| UART2 transmit data
|-
|23 ||GND|| GND
|-
|24 ||I2C0_SCL|| I2C0 serial clock
|-
|25 ||GND|| GND
|-
|26 ||I2C0_SDA|| I2C0 serial data
|-
|27 ||GND|| GND
|-
|28 ||GND|| GND
|-
|29 ||GND|| GND
|-
|30 ||uP_SPI0_CLK|| SPI0 clock
|-
|31 ||GDN|| GND
|-
|32 ||uP_SPI0_SOMI|| SPI0 data slave-out-master-in
|-
|33 ||GND|| GND
|-
|34 ||uP_SPI0_SIMO|| SPI0 data slave-in-master-out
|-
|35 ||GND|| GND
|-
|36 ||uP_SPI0_SCSn0|| SPI0 chip selects
|-
|37 ||+5VDC_IN|| +5V
|-
|38 ||uP_SPI0_ENAN|| 1.8V
|-
|39 ||+3P3V|| +3.3V
|-
|40 ||+1P8V_LDO|| +1.8V
|-
|}

===Physical Dimensions===

[[File:SBC8018size.JPG|The Physical Dimensions Of SBC8018]]

===Board Characteristics===

[[File:SBC8018K.png|The Board Characteristics Of SBC8018]]

=='''Software Features '''==
:{| border="1"
!colspan="1"|OS
!colspan="2"|Item
!colspan="1"|remark
|-
|rowspan="14"|Linux
|rowspan="10"|BIOS
|-
|rowspan="4"|x-loader
|-
|NAND/ONENAND
|-
|MMC/SD
|-
|FAT
|-
|rowspan="5"|U-BOOT
|-
|NAND/ONENAND
|-
|MMC/SD
|-
|FAT
|-
|NET
|-
|rowspan="2"|Kernel
|-
|Linux 2.6.33
|Supports ROM/CRAM/EXT2/EXT3/FAT/ NFS/ JFFS2/UBIFS file systems
|-
|rowspan="2"|Device Driver
|-
|colspan="2"|Serial port, RTC, Ethernet, Nand Flash, LCD, Touch screen, TF card, USB OTG, USB Host, SATA, Audio input/output, key, LED
|-
|rowspan="16"|WinCE
|rowspan="10"|BIOS
|-
|rowspan="4"|x-loader
|-
|NAND / ONENAND
|-
|MMC / SD
|-
|FAT
|-
|rowspan="5"|e-boot
|-
|NAND / ONENAND
|-
|MMC / SD
|-
|FAT
|-
|NET
|-
|rowspan="3"|Device Driver
|-
|colspan="2"|Serial port, RTC, Ethernet, Nand Flash, LCD, Touch screen, TF card, USB OTG, USB Host, Audio input/output, key, LED
|-
|colspan="2"|Power Management (backlight, battery, Sleep/Wakeup, PWM, ADC)
|-
|app
|application module
|Flash Player plug-in and Flash player
|-
|}

==Applications==

:*Portable navigation multimedia devices

:*Digital video set-top boxes

:*Portable game consoles

:*Consumer Design

:*Portable data acquisition devices

:*Embedded

:*And so and

==Information Of Evaluation Kit==

:{|border="1"
|-
|Product Number
|T6010162
|-
|Product Name
|SBC8018 Single Board Computer
|-
|Standard Accessories
|1.SBC8018 Single Board Computer *1

2.5V/2A Power Adapter *1

3.Cross Serial cable *1

4.CD（PDF Schematic,Linux Source Of Driver,WinCE BSP Source,WinCE application source code,Driver for Interface and so and）*1
|-
|Optional Accessories
|1、7-inch LCD screen([http://www.timll.com/chinese/product/lcd8000-70T.asp LCD8000-70T]，Resolution is 800*480)

2、4.3-inch LCD screen([http://www.timll.com/chinese/product/lcd8000-43T.asp LCD8000-43T]，Resolution is 480*272)
|-
|}

'''More information about SBC8018 and how to buy a SBC8018 please visit our website:
http://www.armkits.com/product/sbc8018.asp'''

='''Other [http://www.armkits.com Embest] Products based on TI Processors'''=
[http://www.armkits.com Embest] has designed several products based on TI's ARM9 and ARM Cortex-A8 processors. [http://www.armkits.com Embest]also offers customer design service according to customer's requirements. Whether you need to reduce, add or modify to existing hardwares or generate a new solution, Embest will help customers with expert competence and rich experience. 
* [[DevKit8500]] Evalution Board based on TI's DM3730 or AM3715 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8530.asp SBC8530] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100 Plus] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100] Single Board Computer based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/soc8200.asp SOC8200] Single Board Computer based on TI's AM3517 Sitara ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8510.asp Mini8510] Processor Card based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8100.asp Mini8100] Processor Card based on TI's OMAP3530 ARM Cortex-A8 processor

DevKit8500

2012-01-03T02:23:46Z

Yclinda666: /* Extension Modules/Emulator Support */

[http://www.elinux.org/Devkit8500 elinux_Devkit8500_中文版本页面]
='''Devkit8500D/A Board Overview'''=
[http://www.armkits.com Embest] [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D] Evaluation Board takes full features of the 1GHz [http://focus.ti.com/docs/prod/folders/print/dm3730.html Texas Instruments' DM3730] ARM Cortex-A8 DaVinci™ digital media processor and supports up to 512MByte DDR SDRAM and 512MByte NAND Flash as well as a reserved iNAND design to expand the flash storage capabilities. The board has exposed many other hardware interfaces including serial ports, LCD/TSP, DVI-D, S-Video, Ethernet, USB, TF, keyboard, camera, SPI, I2C and JTAG. The board is able to support for Linux 2.6.32 and WinCE 6.0 operating systems. It has two methods to boot Linux and WinCE systems from either TF card or NAND flash. Besides, it is provided with Android 2.2 demo with driver source code. [http://www.armkits.com Embest] gives instructions on how to boot Android demo image from NAND flash with TF card.

The board supports using [http://www.armkits.com/Product/xds100.asp XDS100v2] USB JTAG Emulator for debugging which is available from [http://www.armkits.com Embest]. [http://www.armkits.com Embest] also offers 4.3-inch or 7-inch LCD with touch screen and various modules for options including VGA, WiFi, Analog Camera, GPS, GPRS, 3G and Digital Camera modules which greatly extends the functions of the board and would be flexible for customer selection to meet their own needs.

The [http://focus.ti.com/docs/prod/folders/print/dm3730.html TI's DM3730] processor is pin-to-pin compatible with [http://www.ti.com/product/am3715 TI's AM3715] processor, Embest also supplies the board with the AM3715 CPU and this board is called [http://www.armkits.com/Product/devkit8500d.asp DevKit8500A].

[[Image:Devkit8500d.gif]]

='''Hardware'''=
==Onboard Interfaces and Connectors==
[[File:devkit8500header.gif]]

==Hardware Features==
===Mechanical Parameters===
* Dimensions: 136.2mm x 105.3mm
* Power Supply: +5V
* Working Temp.: 0~70°C
* TI DM3730 DaVinci Digital Media Processor (pin-to-pin compatible with TI AM3715) 
===Processor===
- Up to 1-GHz ARM® Cortex™-A8 Core, also supports 300, 600, and 800-MHz operation 
- Up to 800-MHz TMS320C64x+™ DSP Core, Also supports 260, 520 and 660-MHz operation 
- NEON™ SIMD Coprocessor (DM3730 only) 
- POWERVR SGX™ Graphics Accelerator 
- ARM: 32KB I-Cache; 32KB D-Cache; 256KB L2 Cache 
- Onchip 32KB ROM and 64KB Shared SDRAM 
===Memory and Storage===
* 512MB DDR SDRAM, 32bit, 200MHz
* 512MB NAND Flash, 16bit
* 2GB iNAND, 4bit (Default: not soldered, optional, reserved for soldering)
===Audio/Video Interfaces===
* LCD/Touch Screen interface (50-pin FPC connector, support resolution up to 2048*2048)
* DVI high-resolution image output port (HDMI interface, support 720p, 30fps signal)
* One S-Video display interface
* One audio input interface (3.5mm audio jack)
* One 2-channel audio output interface (3.5mm audio jack)
* One camera interface (30-pin FPC connector, support CCD or CMOS camera)
===Data Transfer Interfaces===
* One 5 line Debug serial port, RS232 (DB9 connector)
* One 10/100M Ethernet interface (RJ45)
* One High-speed USB2.0 OTG port (Mini USB type interface)
* Four High-speed USB2.0 Host port (USB A type interface)
* TF card slot
===Input/Output Interfaces and Other Facilities===
* 6*6 keyboard interface
* One 14-pin Jtag interface
* Four buttons (One for Reset, one for Wakeup and two for User defined)
* One expansion connector (2.0mm 40-pin SMT Female Pin Header) 
- Two 5 line serial ports, TTL voltage 
- One channel McSPI Interface (Multichannel Serial Port Interface) 
- One channel McBSP interface (Multi-Channel Buffered Serial Port) 
- One channel I2C interface 
- One channel HDQ interface (HDQ/1-Wire) 
* GPIO (there are total 33 GPIOs if the expansion interface pins are all used for GPIOs)

=Extension Modules/Emulator Support=
'''PS: *=provided with source code, #=no source code provided'''

{|border=2
|Item
|Linux
|Android
|WinCE
|Remark
|-
|VGA8000 (RGB converts to VGA module) [[Image:VGA-P.jpg]]
|YES*
|NO
|YES*
|Provided in DevKit8500 DVD
|-
|WF8000-U (WiFi USB module) [[Image:WIFI8000-P.jpg]]
|YES*
|YES*
|YES#
|Provided in single CD
|-
|GPRS8000-S (Supports SIM card Dial, message sending) [[Image:GPS8000-P.jpg]]
|YES*
|NO
|YES*
|[http://www.timll.com/chinese/uploadFile/GPRS8000.rar Click and Download]
|-
|GPS8000-S (Real-time acquisition of GPS signal) [[Image:GPRS8000-P.jpg]]
|YES*
|YES*
|YES*
|[http://www.timll.com/chinese/uploadFile/GPS8000.rar Click and Download]
|-
|CAM8000-A (Real-time acquisition of analog camera signal, PAL/NTSC, BT.656 communication) [[Image:CAM8000-P.jpg]]
|YES*
|NO
|YES*
|Provided in DevKit8500 DVD
|-
|CAM8000-D (Real-time acquisition of digital camera singal, 2 megapixel, BT.601 communication) 
|YES#
|YES#
|YES*
|Provided in single CD
|-
|CAM8100-U (Real-time acquisition of digital camera singal, 1.3 megapixel, USB communication) 
|YES*
|YES*
|YES#
|Provided in single CD
|-
|CDMA8000-U (supports CDMA internet surf）
|YES*
|YES*
|YES#
|[http://www.timll.com/chinese/uploadFile/cdma8000.rar Click and Download]
|-
|WCDMA8000-U (supports WCDMA internet surf)
|YES*
|YES*
|YES#
|[http://www.timll.com/chinese/uploadFile/WCDMA8000.zip Click and Download]
|-
|COM8018-S(Extension serial port module: extend SPI to serial ports)
|YES*
|YES*
|YES#
|Provided in single CD
|-
|XDS100V2 Emulator (supports non-OS ARM and DSP debugging) [[Image:XDS100-P.jpg]]
|N/A
|N/A
|N/A
|Provided in single CD
|-
|TDS560PLUS (supports non-OS ARM and DSP debugging) [[Image:TDS560-P.jpg]]

|N/A
|N/A
|N/A
|Provided in single CD
|}

='''FAQ'''=
If you have got some problems when using [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D/A] board, please refer to [[Devkit8500FAQ]]. 

='''Other [http://www.armkits.com Embest] Products based on TI Processors'''=
[http://www.armkits.com Embest] has designed several products based on TI's ARM9 and ARM Cortex-A8 processors. [http://www.armkits.com Embest]also offers customer design service according to customer's requirements. Whether you need to reduce, add or modify to existing hardwares or generate a new solution, Embest will help customers with expert competence and rich experience. 
* [http://www.armkits.com/product/sbc8530.asp SBC8530] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100 Plus] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8018.asp SBC8018] Single Board Computer based on TI's AM1808 ARM926EJ-S processor
* [[Devkit8000]] Evalution Board based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100] Single Board Computer based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/soc8200.asp SOC8200] Single Board Computer based on TI's AM3517 Sitara ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8510.asp Mini8510] Processor Card based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8100.asp Mini8100] Processor Card based on TI's OMAP3530 ARM Cortex-A8 processor

[[Category:Development Boards]][[Category:Linux]][[Category:DevKit8500]][[Category:Devkit8000]]

DevKit8500

2012-01-03T02:20:03Z

Yclinda666: /* Extension Modules/Emulator Support */

[http://www.elinux.org/Devkit8500 elinux_Devkit8500_中文版本页面]
='''Devkit8500D/A Board Overview'''=
[http://www.armkits.com Embest] [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D] Evaluation Board takes full features of the 1GHz [http://focus.ti.com/docs/prod/folders/print/dm3730.html Texas Instruments' DM3730] ARM Cortex-A8 DaVinci™ digital media processor and supports up to 512MByte DDR SDRAM and 512MByte NAND Flash as well as a reserved iNAND design to expand the flash storage capabilities. The board has exposed many other hardware interfaces including serial ports, LCD/TSP, DVI-D, S-Video, Ethernet, USB, TF, keyboard, camera, SPI, I2C and JTAG. The board is able to support for Linux 2.6.32 and WinCE 6.0 operating systems. It has two methods to boot Linux and WinCE systems from either TF card or NAND flash. Besides, it is provided with Android 2.2 demo with driver source code. [http://www.armkits.com Embest] gives instructions on how to boot Android demo image from NAND flash with TF card.

The board supports using [http://www.armkits.com/Product/xds100.asp XDS100v2] USB JTAG Emulator for debugging which is available from [http://www.armkits.com Embest]. [http://www.armkits.com Embest] also offers 4.3-inch or 7-inch LCD with touch screen and various modules for options including VGA, WiFi, Analog Camera, GPS, GPRS, 3G and Digital Camera modules which greatly extends the functions of the board and would be flexible for customer selection to meet their own needs.

The [http://focus.ti.com/docs/prod/folders/print/dm3730.html TI's DM3730] processor is pin-to-pin compatible with [http://www.ti.com/product/am3715 TI's AM3715] processor, Embest also supplies the board with the AM3715 CPU and this board is called [http://www.armkits.com/Product/devkit8500d.asp DevKit8500A].

[[Image:Devkit8500d.gif]]

='''Hardware'''=
==Onboard Interfaces and Connectors==
[[File:devkit8500header.gif]]

==Hardware Features==
===Mechanical Parameters===
* Dimensions: 136.2mm x 105.3mm
* Power Supply: +5V
* Working Temp.: 0~70°C
* TI DM3730 DaVinci Digital Media Processor (pin-to-pin compatible with TI AM3715) 
===Processor===
- Up to 1-GHz ARM® Cortex™-A8 Core, also supports 300, 600, and 800-MHz operation 
- Up to 800-MHz TMS320C64x+™ DSP Core, Also supports 260, 520 and 660-MHz operation 
- NEON™ SIMD Coprocessor (DM3730 only) 
- POWERVR SGX™ Graphics Accelerator 
- ARM: 32KB I-Cache; 32KB D-Cache; 256KB L2 Cache 
- Onchip 32KB ROM and 64KB Shared SDRAM 
===Memory and Storage===
* 512MB DDR SDRAM, 32bit, 200MHz
* 512MB NAND Flash, 16bit
* 2GB iNAND, 4bit (Default: not soldered, optional, reserved for soldering)
===Audio/Video Interfaces===
* LCD/Touch Screen interface (50-pin FPC connector, support resolution up to 2048*2048)
* DVI high-resolution image output port (HDMI interface, support 720p, 30fps signal)
* One S-Video display interface
* One audio input interface (3.5mm audio jack)
* One 2-channel audio output interface (3.5mm audio jack)
* One camera interface (30-pin FPC connector, support CCD or CMOS camera)
===Data Transfer Interfaces===
* One 5 line Debug serial port, RS232 (DB9 connector)
* One 10/100M Ethernet interface (RJ45)
* One High-speed USB2.0 OTG port (Mini USB type interface)
* Four High-speed USB2.0 Host port (USB A type interface)
* TF card slot
===Input/Output Interfaces and Other Facilities===
* 6*6 keyboard interface
* One 14-pin Jtag interface
* Four buttons (One for Reset, one for Wakeup and two for User defined)
* One expansion connector (2.0mm 40-pin SMT Female Pin Header) 
- Two 5 line serial ports, TTL voltage 
- One channel McSPI Interface (Multichannel Serial Port Interface) 
- One channel McBSP interface (Multi-Channel Buffered Serial Port) 
- One channel I2C interface 
- One channel HDQ interface (HDQ/1-Wire) 
* GPIO (there are total 33 GPIOs if the expansion interface pins are all used for GPIOs)

=Extension Modules/Emulator Support=
'''PS: *=provided with source code, #=no source code provided'''

{|border=2
|Item
|Linux
|Android
|WinCE
|Remark
|-
|VGA8000 (RGB converts to VGA module) [[Image:VGA-P.jpg]]
|YES*
|NO
|YES*
|Provided in DevKit8500 DVD
|-
|WF8000-U (WiFi USB module) [[Image:WIFI8000-P.jpg]]
|YES*
|YES*
|YES#
|Provided in single CD
|-
|GPRS8000-S (Supports SIM card Dial, message sending) [[Image:GPS8000-P.jpg]]
|YES*
|NO
|YES*
|[http://www.timll.com/chinese/uploadFile/GPRS8000.rar Click and Download]
|-
|GPS8000-S (Real-time acquisition of GPS signal) [[Image:GPRS8000-P.jpg]]
|YES*
|YES*
|YES*
|[http://www.timll.com/chinese/uploadFile/GPS8000.rar Click and Download]
|-
|CAM8000-A (Real-time acquisition of analog camera signal, PAL/NTSC, BT.656 communication) [[Image:CAM8000-P.jpg]]
|YES*
|NO
|YES*
|Provided in DevKit8500 DVD
|-
|CAM8000-D (Real-time acquisition of digital camera singal, 2 megapixel, BT.601 communication) 
|YES#
|YES#
|YES*
|Provided in single CD
|-
|CAM8100-U (Real-time acquisition of digital camera singal, 1.3 megapixel, USB communication)|YES*
|YES*
|YES#
|Provided in single CD
|-
|CDMA8000-U (supports CDMA internet surf）
|YES*
|YES*
|YES#
|[http://www.timll.com/chinese/uploadFile/cdma8000.rar Click and Download]
|-
|WCDMA8000-U (supports WCDMA internet surf)
|YES*
|YES*
|YES#
|[http://www.timll.com/chinese/uploadFile/WCDMA8000.zip Click and Download]
|-
|COM8018-S(Extension serial port module: extend SPI to serial ports)
|YES*
|YES*
|YES#
|Provided in single CD
|-
|XDS100V2 Emulator (supports non-OS ARM and DSP debugging) [[Image:XDS100-P.jpg]]
|N/A
|N/A
|N/A
|Provided in single CD
|-
|TDS560PLUS (supports non-OS ARM and DSP debugging) [[Image:TDS560-P.jpg]]

|N/A
|N/A
|N/A
|Provided in single CD
|}

='''FAQ'''=
If you have got some problems when using [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D/A] board, please refer to [[Devkit8500FAQ]]. 

='''Other [http://www.armkits.com Embest] Products based on TI Processors'''=
[http://www.armkits.com Embest] has designed several products based on TI's ARM9 and ARM Cortex-A8 processors. [http://www.armkits.com Embest]also offers customer design service according to customer's requirements. Whether you need to reduce, add or modify to existing hardwares or generate a new solution, Embest will help customers with expert competence and rich experience. 
* [http://www.armkits.com/product/sbc8530.asp SBC8530] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100 Plus] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8018.asp SBC8018] Single Board Computer based on TI's AM1808 ARM926EJ-S processor
* [[Devkit8000]] Evalution Board based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100] Single Board Computer based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/soc8200.asp SOC8200] Single Board Computer based on TI's AM3517 Sitara ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8510.asp Mini8510] Processor Card based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8100.asp Mini8100] Processor Card based on TI's OMAP3530 ARM Cortex-A8 processor

[[Category:Development Boards]][[Category:Linux]][[Category:DevKit8500]][[Category:Devkit8000]]

DevKit8500

2012-01-03T02:17:42Z

Yclinda666: /* Extension Modules/Emulator Support */

[http://www.elinux.org/Devkit8500 elinux_Devkit8500_中文版本页面]
='''Devkit8500D/A Board Overview'''=
[http://www.armkits.com Embest] [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D] Evaluation Board takes full features of the 1GHz [http://focus.ti.com/docs/prod/folders/print/dm3730.html Texas Instruments' DM3730] ARM Cortex-A8 DaVinci™ digital media processor and supports up to 512MByte DDR SDRAM and 512MByte NAND Flash as well as a reserved iNAND design to expand the flash storage capabilities. The board has exposed many other hardware interfaces including serial ports, LCD/TSP, DVI-D, S-Video, Ethernet, USB, TF, keyboard, camera, SPI, I2C and JTAG. The board is able to support for Linux 2.6.32 and WinCE 6.0 operating systems. It has two methods to boot Linux and WinCE systems from either TF card or NAND flash. Besides, it is provided with Android 2.2 demo with driver source code. [http://www.armkits.com Embest] gives instructions on how to boot Android demo image from NAND flash with TF card.

The board supports using [http://www.armkits.com/Product/xds100.asp XDS100v2] USB JTAG Emulator for debugging which is available from [http://www.armkits.com Embest]. [http://www.armkits.com Embest] also offers 4.3-inch or 7-inch LCD with touch screen and various modules for options including VGA, WiFi, Analog Camera, GPS, GPRS, 3G and Digital Camera modules which greatly extends the functions of the board and would be flexible for customer selection to meet their own needs.

The [http://focus.ti.com/docs/prod/folders/print/dm3730.html TI's DM3730] processor is pin-to-pin compatible with [http://www.ti.com/product/am3715 TI's AM3715] processor, Embest also supplies the board with the AM3715 CPU and this board is called [http://www.armkits.com/Product/devkit8500d.asp DevKit8500A].

[[Image:Devkit8500d.gif]]

='''Hardware'''=
==Onboard Interfaces and Connectors==
[[File:devkit8500header.gif]]

==Hardware Features==
===Mechanical Parameters===
* Dimensions: 136.2mm x 105.3mm
* Power Supply: +5V
* Working Temp.: 0~70°C
* TI DM3730 DaVinci Digital Media Processor (pin-to-pin compatible with TI AM3715) 
===Processor===
- Up to 1-GHz ARM® Cortex™-A8 Core, also supports 300, 600, and 800-MHz operation 
- Up to 800-MHz TMS320C64x+™ DSP Core, Also supports 260, 520 and 660-MHz operation 
- NEON™ SIMD Coprocessor (DM3730 only) 
- POWERVR SGX™ Graphics Accelerator 
- ARM: 32KB I-Cache; 32KB D-Cache; 256KB L2 Cache 
- Onchip 32KB ROM and 64KB Shared SDRAM 
===Memory and Storage===
* 512MB DDR SDRAM, 32bit, 200MHz
* 512MB NAND Flash, 16bit
* 2GB iNAND, 4bit (Default: not soldered, optional, reserved for soldering)
===Audio/Video Interfaces===
* LCD/Touch Screen interface (50-pin FPC connector, support resolution up to 2048*2048)
* DVI high-resolution image output port (HDMI interface, support 720p, 30fps signal)
* One S-Video display interface
* One audio input interface (3.5mm audio jack)
* One 2-channel audio output interface (3.5mm audio jack)
* One camera interface (30-pin FPC connector, support CCD or CMOS camera)
===Data Transfer Interfaces===
* One 5 line Debug serial port, RS232 (DB9 connector)
* One 10/100M Ethernet interface (RJ45)
* One High-speed USB2.0 OTG port (Mini USB type interface)
* Four High-speed USB2.0 Host port (USB A type interface)
* TF card slot
===Input/Output Interfaces and Other Facilities===
* 6*6 keyboard interface
* One 14-pin Jtag interface
* Four buttons (One for Reset, one for Wakeup and two for User defined)
* One expansion connector (2.0mm 40-pin SMT Female Pin Header) 
- Two 5 line serial ports, TTL voltage 
- One channel McSPI Interface (Multichannel Serial Port Interface) 
- One channel McBSP interface (Multi-Channel Buffered Serial Port) 
- One channel I2C interface 
- One channel HDQ interface (HDQ/1-Wire) 
* GPIO (there are total 33 GPIOs if the expansion interface pins are all used for GPIOs)

=Extension Modules/Emulator Support=
'''PS: *=provided with source code, #=no source code provided'''

{|border=2
|Item
|Linux
|Android
|WinCE
|Remark
|-
|VGA8000 (RGB converts to VGA module) [[Image:VGA-P.jpg]]
|YES*
|NO
|YES*
|Provided in DevKit8500 DVD
|-
|WF8000-U (WiFi USB module) [[Image:WIFI8000-P.jpg]]
|YES*
|YES*
|YES#
|Provided in single CD
|-
|GPRS8000-S (Supports SIM card Dial, message sending) [[Image:GPS8000-P.jpg]]
|YES*
|NO
|YES*
|[http://www.timll.com/chinese/uploadFile/GPRS8000.rar Click and Download]
|-
|GPS8000-S (Real-time acquisition of GPS signal) [[Image:GPRS8000-P.jpg]]
|YES*
|YES*
|YES*
|[http://www.timll.com/chinese/uploadFile/GPS8000.rar Click and Download]
|-
|CAM8000-A (Real-time acquisition of analog camera signal, PAL/NTSC, BT.656 communication) [[Image:CAM8000-P.jpg]]
|YES*
|NO
|YES*
|Provided in DevKit8500 DVD
|-
|CAM8000-D (Real-time acquisition of digital camera singal, 2 megapixel, BT.601 communication)
|YES#
|YES#
|YES*
|Provided in single CD
|-
|CAM8100-U (Real-time acquisition of digital camera singal, 1.3 megapixel, USB communication)|YES*
|YES*
|YES#
|Provided in single CD
|-
|CDMA8000-U (supports CDMA internet surf）
|YES*
|YES*
|YES#
|[http://www.timll.com/chinese/uploadFile/cdma8000.rar Click and Download]
|-
|WCDMA8000-U (supports WCDMA internet surf)
|YES*
|YES*
|YES#
|[http://www.timll.com/chinese/uploadFile/WCDMA8000.zip Click and Download]
|-
|COM8018-S(Extension serial port module: extend SPI to serial ports)
|YES*
|YES*
|YES#
|Provided in single CD
|-
|XDS100V2 Emulator (supports non-OS ARM and DSP debugging) [[Image:XDS100-P.jpg]]
|N/A
|N/A
|N/A
|Provided in single CD
|-
|TDS560PLUS (supports non-OS ARM and DSP debugging) [[Image:TDS560-P.jpg]]

|N/A
|N/A
|N/A
|Provided in single CD
|}

='''FAQ'''=
If you have got some problems when using [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D/A] board, please refer to [[Devkit8500FAQ]]. 

='''Other [http://www.armkits.com Embest] Products based on TI Processors'''=
[http://www.armkits.com Embest] has designed several products based on TI's ARM9 and ARM Cortex-A8 processors. [http://www.armkits.com Embest]also offers customer design service according to customer's requirements. Whether you need to reduce, add or modify to existing hardwares or generate a new solution, Embest will help customers with expert competence and rich experience. 
* [http://www.armkits.com/product/sbc8530.asp SBC8530] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100 Plus] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8018.asp SBC8018] Single Board Computer based on TI's AM1808 ARM926EJ-S processor
* [[Devkit8000]] Evalution Board based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100] Single Board Computer based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/soc8200.asp SOC8200] Single Board Computer based on TI's AM3517 Sitara ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8510.asp Mini8510] Processor Card based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8100.asp Mini8100] Processor Card based on TI's OMAP3530 ARM Cortex-A8 processor

[[Category:Development Boards]][[Category:Linux]][[Category:DevKit8500]][[Category:Devkit8000]]

DevKit8500

2012-01-03T02:16:30Z

Yclinda666:

[http://www.elinux.org/Devkit8500 elinux_Devkit8500_中文版本页面]
='''Devkit8500D/A Board Overview'''=
[http://www.armkits.com Embest] [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D] Evaluation Board takes full features of the 1GHz [http://focus.ti.com/docs/prod/folders/print/dm3730.html Texas Instruments' DM3730] ARM Cortex-A8 DaVinci™ digital media processor and supports up to 512MByte DDR SDRAM and 512MByte NAND Flash as well as a reserved iNAND design to expand the flash storage capabilities. The board has exposed many other hardware interfaces including serial ports, LCD/TSP, DVI-D, S-Video, Ethernet, USB, TF, keyboard, camera, SPI, I2C and JTAG. The board is able to support for Linux 2.6.32 and WinCE 6.0 operating systems. It has two methods to boot Linux and WinCE systems from either TF card or NAND flash. Besides, it is provided with Android 2.2 demo with driver source code. [http://www.armkits.com Embest] gives instructions on how to boot Android demo image from NAND flash with TF card.

The board supports using [http://www.armkits.com/Product/xds100.asp XDS100v2] USB JTAG Emulator for debugging which is available from [http://www.armkits.com Embest]. [http://www.armkits.com Embest] also offers 4.3-inch or 7-inch LCD with touch screen and various modules for options including VGA, WiFi, Analog Camera, GPS, GPRS, 3G and Digital Camera modules which greatly extends the functions of the board and would be flexible for customer selection to meet their own needs.

The [http://focus.ti.com/docs/prod/folders/print/dm3730.html TI's DM3730] processor is pin-to-pin compatible with [http://www.ti.com/product/am3715 TI's AM3715] processor, Embest also supplies the board with the AM3715 CPU and this board is called [http://www.armkits.com/Product/devkit8500d.asp DevKit8500A].

[[Image:Devkit8500d.gif]]

='''Hardware'''=
==Onboard Interfaces and Connectors==
[[File:devkit8500header.gif]]

==Hardware Features==
===Mechanical Parameters===
* Dimensions: 136.2mm x 105.3mm
* Power Supply: +5V
* Working Temp.: 0~70°C
* TI DM3730 DaVinci Digital Media Processor (pin-to-pin compatible with TI AM3715) 
===Processor===
- Up to 1-GHz ARM® Cortex™-A8 Core, also supports 300, 600, and 800-MHz operation 
- Up to 800-MHz TMS320C64x+™ DSP Core, Also supports 260, 520 and 660-MHz operation 
- NEON™ SIMD Coprocessor (DM3730 only) 
- POWERVR SGX™ Graphics Accelerator 
- ARM: 32KB I-Cache; 32KB D-Cache; 256KB L2 Cache 
- Onchip 32KB ROM and 64KB Shared SDRAM 
===Memory and Storage===
* 512MB DDR SDRAM, 32bit, 200MHz
* 512MB NAND Flash, 16bit
* 2GB iNAND, 4bit (Default: not soldered, optional, reserved for soldering)
===Audio/Video Interfaces===
* LCD/Touch Screen interface (50-pin FPC connector, support resolution up to 2048*2048)
* DVI high-resolution image output port (HDMI interface, support 720p, 30fps signal)
* One S-Video display interface
* One audio input interface (3.5mm audio jack)
* One 2-channel audio output interface (3.5mm audio jack)
* One camera interface (30-pin FPC connector, support CCD or CMOS camera)
===Data Transfer Interfaces===
* One 5 line Debug serial port, RS232 (DB9 connector)
* One 10/100M Ethernet interface (RJ45)
* One High-speed USB2.0 OTG port (Mini USB type interface)
* Four High-speed USB2.0 Host port (USB A type interface)
* TF card slot
===Input/Output Interfaces and Other Facilities===
* 6*6 keyboard interface
* One 14-pin Jtag interface
* Four buttons (One for Reset, one for Wakeup and two for User defined)
* One expansion connector (2.0mm 40-pin SMT Female Pin Header) 
- Two 5 line serial ports, TTL voltage 
- One channel McSPI Interface (Multichannel Serial Port Interface) 
- One channel McBSP interface (Multi-Channel Buffered Serial Port) 
- One channel I2C interface 
- One channel HDQ interface (HDQ/1-Wire) 
* GPIO (there are total 33 GPIOs if the expansion interface pins are all used for GPIOs)

=Extension Modules/Emulator Support=
'''PS: *=provided with source code, #=no source code provided'''

{|border=2
|Item
|Linux
|Android
|WinCE
|Remark
|-
|VGA8000 (RGB converts to VGA module) [[Image:VGA-P.jpg]]
|YES*
|NO
|YES*
|Provided in DevKit8500 DVD
|-
|WF8000-U (WiFi USB module) [[Image:WIFI8000-P.jpg]]
|YES*
|YES*
|YES#
|Provided in single CD
|-
|GPRS8000-S (Supports SIM card Dial, message sending) [[Image:GPS8000-P.jpg]]
|YES*
|NO
|YES*
|[http://www.timll.com/chinese/uploadFile/GPRS8000.rar Click and Download]
|-
|GPS8000-S (Real-time acquisition of GPS signal) [[Image:GPRS8000-P.jpg]]
|YES*
|YES*
|YES*
|[http://www.timll.com/chinese/uploadFile/GPS8000.rar Click and Download]
|-
|CAM8000-A (Real-time acquisition of analog camera signal, PAL/NTSC, BT.656 communication) [[Image:CAM8000-P.jpg]]
|YES*
|NO
|YES*
|Provided in DevKit8500 DVD
|-
|CAM8000-D (Real-time acquisition of digital camera singal, 2 megapixel, BT.601 communication)
|YES#
|YES#
|YES*
|Provided in single CD
|-
|CAM8100-U (Real-time acquisition of digital camera singal, 1.3 megapixel, USB communication)|YES*
|YES*
|YES#
|Provided in single CD
|-
|CDMA8000-U (supports CDMA internet surf）
|YES*
|YES*
|YES#
|[http://www.timll.com/chinese/uploadFile/cdma8000.rar Click and Download]
|-
|WCDMA8000-U (supports WCDMA internet surf)
|YES*
|YES*
|YES#
|[http://www.timll.com/chinese/uploadFile/WCDMA8000.zip Click and Download]
|-
|COM8018-S(Extension serial port module: extend SPI to serial ports)
|YES*
|YES*
|YES#
|Provided in single CD
|-
|XDS100V2 Emulator (supports non-OS ARM and DSP debugging) [[Image:XDS100-P.jpg]]
|N/A
|N/A
|N/A
|Provided in single CD
|-
|TDS560PLUS (supports non-OS ARM and DSP debugging) [[Image:TDS560-P.jpg]]

|N/A
|N/A
|N/A
|Provided in single CD
|}

='''FAQ'''=
If you have got some problems when using [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D/A] board, please refer to [[Devkit8500FAQ]]. 

='''Other [http://www.armkits.com Embest] Products based on TI Processors'''=
[http://www.armkits.com Embest] has designed several products based on TI's ARM9 and ARM Cortex-A8 processors. [http://www.armkits.com Embest]also offers customer design service according to customer's requirements. Whether you need to reduce, add or modify to existing hardwares or generate a new solution, Embest will help customers with expert competence and rich experience. 
* [http://www.armkits.com/product/sbc8530.asp SBC8530] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100 Plus] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8018.asp SBC8018] Single Board Computer based on TI's AM1808 ARM926EJ-S processor
* [[Devkit8000]] Evalution Board based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100] Single Board Computer based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/soc8200.asp SOC8200] Single Board Computer based on TI's AM3517 Sitara ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8510.asp Mini8510] Processor Card based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8100.asp Mini8100] Processor Card based on TI's OMAP3530 ARM Cortex-A8 processor

[[Category:Development Boards]][[Category:Linux]][[Category:DevKit8500]][[Category:Devkit8000]]

DevKit8500

2012-01-03T01:58:22Z

Yclinda666: /* Hardware */

[http://www.elinux.org/Devkit8500 elinux_Devkit8500_中文版本页面]
='''Devkit8500D/A Board Overview'''=
[http://www.armkits.com Embest] [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D] Evaluation Board takes full features of the 1GHz [http://focus.ti.com/docs/prod/folders/print/dm3730.html Texas Instruments' DM3730] ARM Cortex-A8 DaVinci™ digital media processor and supports up to 512MByte DDR SDRAM and 512MByte NAND Flash as well as a reserved iNAND design to expand the flash storage capabilities. The board has exposed many other hardware interfaces including serial ports, LCD/TSP, DVI-D, S-Video, Ethernet, USB, TF, keyboard, camera, SPI, I2C and JTAG. The board is able to support for Linux 2.6.32 and WinCE 6.0 operating systems. It has two methods to boot Linux and WinCE systems from either TF card or NAND flash. Besides, it is provided with Android 2.2 demo with driver source code. [http://www.armkits.com Embest] gives instructions on how to boot Android demo image from NAND flash with TF card.

The board supports using [http://www.armkits.com/Product/xds100.asp XDS100v2] USB JTAG Emulator for debugging which is available from [http://www.armkits.com Embest]. [http://www.armkits.com Embest] also offers 4.3-inch or 7-inch LCD with touch screen and various modules for options including VGA, WiFi, Analog Camera, GPS, GPRS, 3G and Digital Camera modules which greatly extends the functions of the board and would be flexible for customer selection to meet their own needs.

The [http://focus.ti.com/docs/prod/folders/print/dm3730.html TI's DM3730] processor is pin-to-pin compatible with [http://www.ti.com/product/am3715 TI's AM3715] processor, Embest also supplies the board with the AM3715 CPU and this board is called [http://www.armkits.com/Product/devkit8500d.asp DevKit8500A].

[[Image:Devkit8500d.gif]]

='''Hardware'''=
==Onboard Interfaces and Connectors==
[[File:devkit8500header.gif]]

==Hardware Features==
===Mechanical Parameters===
* Dimensions: 136.2mm x 105.3mm
* Power Supply: +5V
* Working Temp.: 0~70°C
* TI DM3730 DaVinci Digital Media Processor (pin-to-pin compatible with TI AM3715) 
===Processor===
- Up to 1-GHz ARM® Cortex™-A8 Core, also supports 300, 600, and 800-MHz operation 
- Up to 800-MHz TMS320C64x+™ DSP Core, Also supports 260, 520 and 660-MHz operation 
- NEON™ SIMD Coprocessor (DM3730 only) 
- POWERVR SGX™ Graphics Accelerator 
- ARM: 32KB I-Cache; 32KB D-Cache; 256KB L2 Cache 
- Onchip 32KB ROM and 64KB Shared SDRAM 
===Memory and Storage===
* 512MB DDR SDRAM, 32bit, 200MHz
* 512MB NAND Flash, 16bit
* 2GB iNAND, 4bit (Default: not soldered, optional, reserved for soldering)
===Audio/Video Interfaces===
* LCD/Touch Screen interface (50-pin FPC connector, support resolution up to 2048*2048)
* DVI high-resolution image output port (HDMI interface, support 720p, 30fps signal)
* One S-Video display interface
* One audio input interface (3.5mm audio jack)
* One 2-channel audio output interface (3.5mm audio jack)
* One camera interface (30-pin FPC connector, support CCD or CMOS camera)
===Data Transfer Interfaces===
* One 5 line Debug serial port, RS232 (DB9 connector)
* One 10/100M Ethernet interface (RJ45)
* One High-speed USB2.0 OTG port (Mini USB type interface)
* Four High-speed USB2.0 Host port (USB A type interface)
* TF card slot
===Input/Output Interfaces and Other Facilities===
* 6*6 keyboard interface
* One 14-pin Jtag interface
* Four buttons (One for Reset, one for Wakeup and two for User defined)
* One expansion connector (2.0mm 40-pin SMT Female Pin Header) 
- Two 5 line serial ports, TTL voltage 
- One channel McSPI Interface (Multichannel Serial Port Interface) 
- One channel McBSP interface (Multi-Channel Buffered Serial Port) 
- One channel I2C interface 
- One channel HDQ interface (HDQ/1-Wire) 
* GPIO (there are total 33 GPIOs if the expansion interface pins are all used for GPIOs)

='''FAQ'''=
If you have got some problems when using [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D/A] board, please refer to [[Devkit8500FAQ]]. 

='''Other [http://www.armkits.com Embest] Products based on TI Processors'''=
[http://www.armkits.com Embest] has designed several products based on TI's ARM9 and ARM Cortex-A8 processors. [http://www.armkits.com Embest]also offers customer design service according to customer's requirements. Whether you need to reduce, add or modify to existing hardwares or generate a new solution, Embest will help customers with expert competence and rich experience. 
* [http://www.armkits.com/product/sbc8530.asp SBC8530] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100 Plus] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8018.asp SBC8018] Single Board Computer based on TI's AM1808 ARM926EJ-S processor
* [[Devkit8000]] Evalution Board based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100] Single Board Computer based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/soc8200.asp SOC8200] Single Board Computer based on TI's AM3517 Sitara ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8510.asp Mini8510] Processor Card based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8100.asp Mini8100] Processor Card based on TI's OMAP3530 ARM Cortex-A8 processor

[[Category:Development Boards]][[Category:Linux]][[Category:DevKit8500]][[Category:Devkit8000]]

DevKit8500

2011-12-13T08:54:37Z

Yclinda666: /* Other Embest Products based on TI Processors */

='''Devkit8500D/A Board Overview'''=
[http://www.armkits.com Embest] [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D] Evaluation Board takes full features of the 1GHz [http://focus.ti.com/docs/prod/folders/print/dm3730.html Texas Instruments' DM3730] ARM Cortex-A8 DaVinci™ digital media processor and supports up to 512MByte DDR SDRAM and 512MByte NAND Flash as well as a reserved iNAND design to expand the flash storage capabilities. The board has exposed many other hardware interfaces including serial ports, LCD/TSP, DVI-D, S-Video, Ethernet, USB, TF, keyboard, camera, SPI, I2C and JTAG. The board is able to support for Linux 2.6.32 and WinCE 6.0 operating systems. It has two methods to boot Linux and WinCE systems from either TF card or NAND flash. Besides, it is provided with Android 2.2 demo with driver source code. [http://www.armkits.com Embest] gives instructions on how to boot Android demo image from NAND flash with TF card.

The board supports using [http://www.armkits.com/Product/xds100.asp XDS100v2] USB JTAG Emulator for debugging which is available from [http://www.armkits.com Embest]. [http://www.armkits.com Embest] also offers 4.3-inch or 7-inch LCD with touch screen and various modules for options including VGA, WiFi, Analog Camera, GPS, GPRS, 3G and Digital Camera modules which greatly extends the functions of the board and would be flexible for customer selection to meet their own needs.

The [http://focus.ti.com/docs/prod/folders/print/dm3730.html TI's DM3730] processor is pin-to-pin compatible with [http://www.ti.com/product/am3715 TI's AM3715] processor, Embest also supplies the board with the AM3715 CPU and this board is called [http://www.armkits.com/Product/devkit8500d.asp DevKit8500A].

[[Image:Devkit8500d.gif]]

='''Hardware'''=
==Onboard Interfaces and Connectors==
[[File:devkit8500header.gif]]

==Hardware Features==
* Dimensions: 136.2mm x 105.3mm
* Power Supply: +5V
* Working Temp.: 0~70°C
* TI DM3730 DaVinci Digital Media Processor (pin-to-pin compatible with TI AM3715) 
- Up to 1-GHz ARM® Cortex™-A8 Core, also supports 300, 600, and 800-MHz operation 
- Up to 800-MHz TMS320C64x+™ DSP Core, Also supports 260, 520 and 660-MHz operation 
- NEON™ SIMD Coprocessor (DM3730 only) 
- POWERVR SGX™ Graphics Accelerator 
- ARM: 32KB I-Cache; 32KB D-Cache; 256KB L2 Cache 
- Onchip 32KB ROM and 64KB Shared SDRAM 
* 512MB DDR SDRAM, 32bit, 200MHz
* 512MB NAND Flash, 16bit
* 2GB iNAND, 4bit (Default: not soldered, optional, reserved for soldering)
* TF card slot
* One 10/100M Ethernet interface (RJ45)
* One High-speed USB2.0 OTG port (Mini USB type interface)
* Four High-speed USB2.0 Host port (USB A type interface)
* One 5 line Debug serial port, RS232 (DB9 connector)
* LCD/Touch Screen interface (50-pin FPC connector, support resolution up to 2048*2048)
* DVI high-resolution image output port (HDMI interface, support 720p, 30fps signal)
* One S-Video display interface
* One audio input interface (3.5mm audio jack)
* One 2-channel audio output interface (3.5mm audio jack)
* One camera interface (30-pin FPC connector, support CCD or CMOS camera)
* 6*6 keyboard interface
* One 14-pin Jtag interface
* Four buttons (One for Reset, one for Wakeup and two for User defined)
* One expansion connector (2.0mm 40-pin SMT Female Pin Header) 
- Two 5 line serial ports, TTL voltage 
- One channel McSPI Interface (Multichannel Serial Port Interface) 
- One channel McBSP interface (Multi-Channel Buffered Serial Port) 
- One channel I2C interface 
- One channel HDQ interface (HDQ/1-Wire) 

='''FAQ'''=
If you have got some problems when using [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D/A] board, please refer to [[Devkit8500FAQ]]. 

='''Other [http://www.armkits.com Embest] Products based on TI Processors'''=
[http://www.armkits.com Embest] has designed several products based on TI's ARM9 and ARM Cortex-A8 processors. [http://www.armkits.com Embest]also offers customer design service according to customer's requirements. Whether you need to reduce, add or modify to existing hardwares or generate a new solution, Embest will help customers with expert competence and rich experience. 
* [http://www.armkits.com/product/sbc8530.asp SBC8530] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100 Plus] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8018.asp SBC8018] Single Board Computer based on TI's AM1808 ARM926EJ-S processor
* [[Devkit8000]] Evalution Board based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100] Single Board Computer based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/soc8200.asp SOC8200] Single Board Computer based on TI's AM3517 Sitara ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8510.asp Mini8510] Processor Card based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8100.asp Mini8100] Processor Card based on TI's OMAP3530 ARM Cortex-A8 processor

[[Category:Development Boards]][[Category:Linux]][[Category:DevKit8500]][[Category:Devkit8000]]

DevKit8500

2011-12-13T08:54:22Z

Yclinda666: /* Other Embest Products based on TI Processors */

='''Devkit8500D/A Board Overview'''=
[http://www.armkits.com Embest] [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D] Evaluation Board takes full features of the 1GHz [http://focus.ti.com/docs/prod/folders/print/dm3730.html Texas Instruments' DM3730] ARM Cortex-A8 DaVinci™ digital media processor and supports up to 512MByte DDR SDRAM and 512MByte NAND Flash as well as a reserved iNAND design to expand the flash storage capabilities. The board has exposed many other hardware interfaces including serial ports, LCD/TSP, DVI-D, S-Video, Ethernet, USB, TF, keyboard, camera, SPI, I2C and JTAG. The board is able to support for Linux 2.6.32 and WinCE 6.0 operating systems. It has two methods to boot Linux and WinCE systems from either TF card or NAND flash. Besides, it is provided with Android 2.2 demo with driver source code. [http://www.armkits.com Embest] gives instructions on how to boot Android demo image from NAND flash with TF card.

The board supports using [http://www.armkits.com/Product/xds100.asp XDS100v2] USB JTAG Emulator for debugging which is available from [http://www.armkits.com Embest]. [http://www.armkits.com Embest] also offers 4.3-inch or 7-inch LCD with touch screen and various modules for options including VGA, WiFi, Analog Camera, GPS, GPRS, 3G and Digital Camera modules which greatly extends the functions of the board and would be flexible for customer selection to meet their own needs.

The [http://focus.ti.com/docs/prod/folders/print/dm3730.html TI's DM3730] processor is pin-to-pin compatible with [http://www.ti.com/product/am3715 TI's AM3715] processor, Embest also supplies the board with the AM3715 CPU and this board is called [http://www.armkits.com/Product/devkit8500d.asp DevKit8500A].

[[Image:Devkit8500d.gif]]

='''Hardware'''=
==Onboard Interfaces and Connectors==
[[File:devkit8500header.gif]]

==Hardware Features==
* Dimensions: 136.2mm x 105.3mm
* Power Supply: +5V
* Working Temp.: 0~70°C
* TI DM3730 DaVinci Digital Media Processor (pin-to-pin compatible with TI AM3715) 
- Up to 1-GHz ARM® Cortex™-A8 Core, also supports 300, 600, and 800-MHz operation 
- Up to 800-MHz TMS320C64x+™ DSP Core, Also supports 260, 520 and 660-MHz operation 
- NEON™ SIMD Coprocessor (DM3730 only) 
- POWERVR SGX™ Graphics Accelerator 
- ARM: 32KB I-Cache; 32KB D-Cache; 256KB L2 Cache 
- Onchip 32KB ROM and 64KB Shared SDRAM 
* 512MB DDR SDRAM, 32bit, 200MHz
* 512MB NAND Flash, 16bit
* 2GB iNAND, 4bit (Default: not soldered, optional, reserved for soldering)
* TF card slot
* One 10/100M Ethernet interface (RJ45)
* One High-speed USB2.0 OTG port (Mini USB type interface)
* Four High-speed USB2.0 Host port (USB A type interface)
* One 5 line Debug serial port, RS232 (DB9 connector)
* LCD/Touch Screen interface (50-pin FPC connector, support resolution up to 2048*2048)
* DVI high-resolution image output port (HDMI interface, support 720p, 30fps signal)
* One S-Video display interface
* One audio input interface (3.5mm audio jack)
* One 2-channel audio output interface (3.5mm audio jack)
* One camera interface (30-pin FPC connector, support CCD or CMOS camera)
* 6*6 keyboard interface
* One 14-pin Jtag interface
* Four buttons (One for Reset, one for Wakeup and two for User defined)
* One expansion connector (2.0mm 40-pin SMT Female Pin Header) 
- Two 5 line serial ports, TTL voltage 
- One channel McSPI Interface (Multichannel Serial Port Interface) 
- One channel McBSP interface (Multi-Channel Buffered Serial Port) 
- One channel I2C interface 
- One channel HDQ interface (HDQ/1-Wire) 

='''FAQ'''=
If you have got some problems when using [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D/A] board, please refer to [[Devkit8500FAQ]]. 

='''Other [http://www.armkits.com Embest] Products based on TI Processors'''=
[http://www.armkits.com Embest] has designed several products based on TI's ARM9 and ARM Cortex-A8 processors. [http://www.armkits.com Embest]also offers customer design service according to customer's requirements. Whether you need to reduce, add or modify to existing hardwares or generate a new solution, Embest will help customers with expert competence and rich experience. 
* [http://www.armkits.com/product/sbc8530.asp SBC8530] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100 Plus] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8018.asp SBC8018] Single Board Computer based on TI's AM1808 ARM926EJ-S processor
* [[Devkit8500]] Evalution Board based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100] Single Board Computer based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/soc8200.asp SOC8200] Single Board Computer based on TI's AM3517 Sitara ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8510.asp Mini8510] Processor Card based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8100.asp Mini8100] Processor Card based on TI's OMAP3530 ARM Cortex-A8 processor

[[Category:Development Boards]][[Category:Linux]][[Category:DevKit8500]][[Category:Devkit8000]]

DevKit8500

2011-12-13T08:53:25Z

Yclinda666:

='''Devkit8500D/A Board Overview'''=
[http://www.armkits.com Embest] [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D] Evaluation Board takes full features of the 1GHz [http://focus.ti.com/docs/prod/folders/print/dm3730.html Texas Instruments' DM3730] ARM Cortex-A8 DaVinci™ digital media processor and supports up to 512MByte DDR SDRAM and 512MByte NAND Flash as well as a reserved iNAND design to expand the flash storage capabilities. The board has exposed many other hardware interfaces including serial ports, LCD/TSP, DVI-D, S-Video, Ethernet, USB, TF, keyboard, camera, SPI, I2C and JTAG. The board is able to support for Linux 2.6.32 and WinCE 6.0 operating systems. It has two methods to boot Linux and WinCE systems from either TF card or NAND flash. Besides, it is provided with Android 2.2 demo with driver source code. [http://www.armkits.com Embest] gives instructions on how to boot Android demo image from NAND flash with TF card.

The board supports using [http://www.armkits.com/Product/xds100.asp XDS100v2] USB JTAG Emulator for debugging which is available from [http://www.armkits.com Embest]. [http://www.armkits.com Embest] also offers 4.3-inch or 7-inch LCD with touch screen and various modules for options including VGA, WiFi, Analog Camera, GPS, GPRS, 3G and Digital Camera modules which greatly extends the functions of the board and would be flexible for customer selection to meet their own needs.

The [http://focus.ti.com/docs/prod/folders/print/dm3730.html TI's DM3730] processor is pin-to-pin compatible with [http://www.ti.com/product/am3715 TI's AM3715] processor, Embest also supplies the board with the AM3715 CPU and this board is called [http://www.armkits.com/Product/devkit8500d.asp DevKit8500A].

[[Image:Devkit8500d.gif]]

='''Hardware'''=
==Onboard Interfaces and Connectors==
[[File:devkit8500header.gif]]

==Hardware Features==
* Dimensions: 136.2mm x 105.3mm
* Power Supply: +5V
* Working Temp.: 0~70°C
* TI DM3730 DaVinci Digital Media Processor (pin-to-pin compatible with TI AM3715) 
- Up to 1-GHz ARM® Cortex™-A8 Core, also supports 300, 600, and 800-MHz operation 
- Up to 800-MHz TMS320C64x+™ DSP Core, Also supports 260, 520 and 660-MHz operation 
- NEON™ SIMD Coprocessor (DM3730 only) 
- POWERVR SGX™ Graphics Accelerator 
- ARM: 32KB I-Cache; 32KB D-Cache; 256KB L2 Cache 
- Onchip 32KB ROM and 64KB Shared SDRAM 
* 512MB DDR SDRAM, 32bit, 200MHz
* 512MB NAND Flash, 16bit
* 2GB iNAND, 4bit (Default: not soldered, optional, reserved for soldering)
* TF card slot
* One 10/100M Ethernet interface (RJ45)
* One High-speed USB2.0 OTG port (Mini USB type interface)
* Four High-speed USB2.0 Host port (USB A type interface)
* One 5 line Debug serial port, RS232 (DB9 connector)
* LCD/Touch Screen interface (50-pin FPC connector, support resolution up to 2048*2048)
* DVI high-resolution image output port (HDMI interface, support 720p, 30fps signal)
* One S-Video display interface
* One audio input interface (3.5mm audio jack)
* One 2-channel audio output interface (3.5mm audio jack)
* One camera interface (30-pin FPC connector, support CCD or CMOS camera)
* 6*6 keyboard interface
* One 14-pin Jtag interface
* Four buttons (One for Reset, one for Wakeup and two for User defined)
* One expansion connector (2.0mm 40-pin SMT Female Pin Header) 
- Two 5 line serial ports, TTL voltage 
- One channel McSPI Interface (Multichannel Serial Port Interface) 
- One channel McBSP interface (Multi-Channel Buffered Serial Port) 
- One channel I2C interface 
- One channel HDQ interface (HDQ/1-Wire) 

='''FAQ'''=
If you have got some problems when using [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D/A] board, please refer to [[Devkit8500FAQ]]. 

='''Other [http://www.armkits.com Embest] Products based on TI Processors'''=
[http://www.armkits.com Embest] has designed several products based on TI's ARM9 and ARM Cortex-A8 processors. [http://www.armkits.com Embest]also offers customer design service according to customer's requirements. Whether you need to reduce, add or modify to existing hardwares or generate a new solution, Embest will help customers with expert competence and rich experience. 
* [[DevKit8500]] Evalution Board based on TI's DM3730 or AM3715 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8530.asp SBC8530] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100 Plus] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8018.asp SBC8018] Single Board Computer based on TI's AM1808 ARM926EJ-S processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100] Single Board Computer based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/soc8200.asp SOC8200] Single Board Computer based on TI's AM3517 Sitara ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8510.asp Mini8510] Processor Card based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8100.asp Mini8100] Processor Card based on TI's OMAP3530 ARM Cortex-A8 processor

[[Category:Development Boards]][[Category:Linux]][[Category:DevKit8500]][[Category:Devkit8000]]

Devkit8000

2011-12-13T08:51:54Z

Yclinda666:

='''Devkit8000 Board Overview'''=
[http://www.armkits.com Embest] [http://www.armkits.com/Product/devkit8000.asp DevKit8000] Evaluation Board is a compact board using TI's [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] 600MHz ARM Cortex-A8 (600MHz ARM Cortex-A8 core paired with a 430MHz TMS320C64x+ DSP core) microprocessor. It takes full features of this processor and supports up to 256MByte DDR SDRAM and 256MByte NAND Flash as well as high-speed USB2.0 OTG function. The board has exposed many other hardware interfaces including RS232 serial port, LCD/TSP, DVI-D, S-Video, Ethernet, SD, keyboard, camera, SPI, I2C and JTAG. The board has two methods to boot the system from either SD card or NAND flash. It is able to support WinCE and Linux OS and provided with WinCE6.0 BSP and Linux2.6.28 BSP. Embest also provides demos of Google Android OS, Angstrom (GPE) and DVSDK for user experience.

{|border=0
|[[Image:Devkit8000.jpg]]
|[[Image:Devkit8000_android.jpg]]
|-
! Devkit8000 Evaluation Board
! Devkit8000 + 4.3 inch LCD Android Demo Display
|-
|}

='''Hardware'''=
==Onboard Interfaces and Connectors==
[[File:devkit8000header.gif]]

==Hardware Features==
* Dimensions: 110mm x 95mm
* Working temperature: 0°C to 70°C
* Processor: TI OMAP3530 microprocessor with 600MHz ARM Cortex-A8 RISC Core
* Power supply: +5V
* 256MB DDR SDRAM, 166MHz
* 256MB NAND Flash, 16bit
* LCD/Touch Screen interface (50-pin FPC connector, support resolution up to 2048*2048)
* DVI high-resolution image output port (HDMI interface, support 720p, 30fps signal)
* S-Video display interface
* One audio input interface (3.5mm audio jack)
* One 2-channel audio output interface (3.5mm audio jack)
* One 10/100M Ethernet interface (RJ45)
* One High-speed USB2.0 OTG port (Mini USB type interface)
* One High-speed USB2.0 Host port (USB A type interface)
* Two serial ports (one 3-wire RS232 serial port led out from 2.54mm 10-pin connector and one 5-wire TTL serial port led out from expansion connector)
* SD card interface (supports 3.3V and 1.8V logic voltage)
* One camera interface (30-pin FPC connector, support CCD or CMOS camera)
* 6*6 keyboard interface
* One 14-pin Jtag interface
* Four buttons (Reset, Boot, User defined, On/Off)
* One expansion connector (2.0mm 40-pin SMT Female Pin Header, McSPI, McBSP, I2C, HDQ, GPIO are led out from this connector)

==Main Chip Introduction==
{|border=1
|DevKit8000
|Chip
|Remark
|-
|Processor
|OMAP3530CUS
|0.65mm CUS package
|-
|Memory
|MT29C2G48MAKLCJA-6IT
|256MB DDR/256MB NAND Flash, 137-Ball TFBGA, Mark:JW305, Micron
|-
|Power Management Chip
|TPS65930BZCH
|Extended power management, RTC, USB OTG, Audio, 6*6 Keyboard
|-
|DVI-D
|TFP410
|HDMI connector, output DVI-D signal, not including audio
|-
|Ethernet
|DM9000
|RJ45, 10M/100M adaptive, at present testing speed can reach 36M
|-
|Serial port
|MAX3232 CSE
|RS232
|}

==Video Display==
===DVI-D===
DVI high-resolution display (HDMI interface, 30fps signal), Embest provides a HDMI to DVI-D cable in complete configuration for connection. Signal does not include audio signal. 

===S-video===
S-video display, can output video signal but not including audio signal.

===LCD===
24-bit LCD display, can output true-color RGB signal, R:B:G=8:8:8, can support resolution up to 2048*2048 pixels. (50-pin 0.5mm pitch FPC connector. 
Interface Singal Type 
{| border= "1"
|RGB data signal||LCD control signal||SPI signal||IIC signal||Touch Screen signal||Voltage output
|-
|24bit||6bit||4bit||2bit||4bit||5bit
|-
|R:G:B=8:8:8||row control signal||standard spi signal||2-bit IIC signal||4-wire touch screen||output voltage 5V, 3.3V, 1.8V
|}

==USB OTG (Mini-AB) Wire Map==
1: VB 
2: D- 
3: D+ 
4: ID 
5: GND 
User needs only to short circuited 4 and 5. 

==Camera Interface==
[[Image:DevKit8000_cam.jpg]]

==Expansion Interface==
Embest Devkit8000 uses a 2.0mm 40-pin SMT Female Pin Header to bring out McSPI, McBSP, I2C, HDQ, GPIO from this interface 
{| border = 1
|PIN||Signal||Function Description
|-
|1 ||GND|| GND
|-
|2 ||BSP1_DX|| Transmitted serial data 1
|-
|3 ||BSP1_DR|| Received serial data 1
|-
|4 ||BSP1_CLKR|| Received clock 1
|-
|5 ||BSP1_FSX|| Transmit frame synchronization 1
|-
|6 ||BSP1_CLKX|| Transmit clock 1
|-
|7 ||BSP1_CLKS|| External clock input 1
|-
|8 ||BSP1_FSR|| Receive frame synchronization 1
|-
|9 ||UART1_CTS|| UART1 clear to send
|-
|10 ||UART1_RTS|| UART1 request to send
|-
|11 ||UART1_RX|| UART1 receive data
|-
|12 ||UART1_TX ||UART1 transmit data
|-
|13 ||GND|| GND
|-
|14 ||MMC2_CLK|| MMC2 card clock
|-
|15 ||MMC2_CMD|| MMC2 card command
|-
|16 ||MMC2_D0|| MMC2 card data 0
|-
|17 ||MMC2_D1|| MMC2 card data 1
|-
|18 ||MMC2_D2|| MMC2 card data 2
|-
|19 ||MMC2_D3|| MMC2 card data 3
|-
|20 ||MMC2_D4|| MMC2 card data 4
|-
|21 ||MMC2_D5|| MMC2 card data 5
|-
|22 ||MMC2_D6|| MMC2 card data 6
|-
|23 ||MMC2_D7|| MMC2 card data 7
|-
|24 ||BSP3_DX|| Transmitted serial data 3
|-
|25 ||BSP3_DR|| Received serial data 3
|-
|26 ||BSP3_CLKX|| Transmit clock 3
|-
|27 ||BSP3_FSX|| Transmit frame synchronization 3
|-
|28 ||GND|| GND
|-
|29 ||IIC3_SCL|| IIC3 master serial clock
|-
|30 ||IIC3_SDA|| IIC3 serial bidirectional data
|-
|31 ||SPI1_SIMO|| Slave data in, master data out
|-
|32 ||SPI1_SOMI|| Slave data out, master data in
|-
|33 ||SPI1_CLK|| SPI1 clock
|-
|34 ||SPI1_CS0|| SPI enable 0
|-
|35 ||SPI1_CS3|| SPI enable 3
|-
|36 ||HDQ_SIO|| Bidirectional HDQ
|-
|37 ||VDD33 ||3.3V
|-
|38 ||VDD18|| 1.8V
|-
|39 ||VDD50|| 5V
|-
|40 ||VDD50|| 5V
|}

==LayOut==
The Devkit8000 PCB has 6-layer design, each layer is layout as below:
{|border="1" cellspacing="0"
|-
| 1
| 2
| 3
| 4
| 5
| 6
|-
| Top
| Ground
| Singal
| Power
| Ground
| Bottom
|}

==Dimension Drawing==
[[Image:Devkit8000_chicun.JPG]]

==Function Block Diagram==
[[Image:Devkit8000func.jpg]]

==Optional Function Modules==
* '''VGA Module''' ([http://www.armkits.com/product/vga8000.asp VGA8000])
[[Image:VGA-P.jpg]] 
The VGA8000 module employs PHILIPS 74alvc164245 chip with 240MHz maximum sample rate. It can output standard LCD signal and display smoothly under 1024*768 resolution. 

* '''Analog Camera Module''' ([http://www.armkits.com/product/camera8000.asp CAM8000-A])
[[Image:CAM8000-P.jpg]] 
The CAM8000-A module is designed for using on Devkit8000 Evaluation Board with standard 720*576 PAL resolution. It supports analog camera with BNC connector and connects to Devkit8000 board through an 30-pin FFC cable.

* '''USB WiFi Module''' ([http://www.armkits.com/product/WF8000-U.asp WF8000-U])
[[Image:WIFI8000-P.jpg]] 
The WF8000-U is a USB based WiFi module relying on the WiFi IEEE 802.11 standards. It is applied to be used on all Embest products which shall have USB interface. This module is hgihly integrated with MAC/BBP and 2.4GHz RF chip and builds a wireless network between PCs or some other terminals.

* '''GPS Module''' ([http://www.armkits.com/product/GPS8000-S.asp GPS8000-S])
[[Image:GPS8000-P.jpg]] 
The GPS8000-S is an ARM based embedded GPS module which allows to connect to Devkit8000 board to get position and altitude. It is a high sensitivity module with low power consumption. Devkit8000's UART (the serial port) from the expansion connector is used to communicate with the GPS through a tiny patch board.

* '''GPRS Module''' ([http://www.armkits.com/product/GPRS8000-S.asp GPRS8000-S])
[[Image:GPRS8000-P.jpg]] 
The GPRS8000-S is an ARM based embedded GPS module which allows to connect to Embest Devkit8000 board for GSM/GPRS solution. Devkit8000's UART (the serial port) from the expansion connector is used to communicate with the GPRS module.

* '''CDMA8000-U Module''' ([http://www.armkits.com/product/CDMA8000-U.asp CDMA8000-U])
* '''WCDMA8000-U Module''' ([http://www.armkits.com/product/WCDMA8000-U.asp WCDMA8000-U])
* '''Digital Camera Module''' ([http://www.armkits.com/product/CAM8100-U.asp CAM8100-U])

==JTAG Tool==
[[Image:XDS100-P.jpg]] 
* [http://processors.wiki.ti.com/index.php/XDS100 XDS100v2] - the second release of the XDS100 JTAG emulator technology supporting debug of a variety of TI devices.
Available from [http://www.armkits.com/product/xds100.asp Embest] 

='''Software'''=
==Software Features==
===Linux and WinCE OS support===
[http://www.armkits.com Embest] [http://www.armkits.com/Product/devkit8000.asp DevKit8000] supports for both Linux2.6.28 and WinCE6.0 operating systems. 
<table border="1" cellspacing="0" cellpadding="0" width="90%" height=20>
<tr>
<td valign="top">OS </td>

<td valign="top">Item </td>
<td valign="top">Features </td>
<td valign="top">Description</td>
</tr>
<tr>
<td rowspan="11">Linux </td>
<td rowspan="3">Boot </td>

<td > Version </td>
<td valign="top"> x-load-1.41, u-boot 1.3.3 </td>
</tr>
<tr>
<td > Boot Mode </td>
<td valign="top">Boot Linux from SD card, NAND Flash or Ethernet</td>
</tr>

<tr>
<td > Image Update </td>
<td valign="top"> Support updating image from SD card or Ethernet</td>
</tr>
<tr>
<td rowspan="3"> Kernel and Drivers </td>
<td > Version </td>

<td valign="top"> Linux 2.6.28 </td>
</tr>
<tr>
<td > Support file systems </td>
<td valign="top"> ROM/CRAM/EXT2/EXT3/FAT/NFS/JFFS2/UBIFS </td>
</tr>
<tr>

<td > Drivers </td>
<td valign="top"> Serial, RTC, NET, Nand, LCD, Touch Screen, SD, USB Host, USB OTG, DVI, Keypad, LED, Audio </td>
</tr>
<tr>
<td rowspan="2"> File system </td>
<td > Format </td>
<td valign="top"> Ramdisk, UBI </td>

</tr>
<tr>
<td > Characteristic </td>
<td valign="top"> Provided Lib (ALSA -lib, tslib, glibc), udev support </td>
</tr>
<tr>
<td rowspan="3"> Demo </td>

<td > Angstrom </td>
<td valign="top"> Audio (XMMS), network (firefox), graphics editor (gimp) and document processing software (Abiword) </td>
</tr>
<tr>
<td > Android </td>
<td valign="top">Google developed a platform based on Linux open-source mobile phone operating system. </td>
</tr>

<tr>
<td > DVSDK </td>
<td valign="top">Support MPEG4, MPEG2, H264, mp3, aac audio/video formats and Codecs </td>
</tr>
<tr>
<td rowspan="11"> WinCE </td>
<td rowspan="3"> Boot </td>

<td > Version </td>
<td valign="top"> x-load-1.41, Eboot </td>
</tr>
<tr>
<td > Boot Mode </td>
<td valign="top"> Boot WinCE from SD card, NAND Flash or Ethernet </td>
</tr>

<tr>
<td > Image Update </td>
<td valign="top">Support updating image from SD card or Ethernet </td>
</tr>
<tr>
<td rowspan="8"> System </td>
<td > Characteristic </td>

<td valign="top"> KITL kernel debug, Reboot, Watchdog, RTC</td>
</tr>
<tr>
<td rowspan="2"> Drivers </td>
<td valign="top"> Display driver（DVI, TFT LCD） </td>
</tr>
<tr>

<td valign="top"> SD card, Keyboard, McSPI, McBSP, Audio, NET, NLED, USB Host, USB OTG, WiFi, GPS, GPRS, CDMA </td>
</tr>
<tr>
<td rowspan="3"> Function </td>
<td valign="top"> Power Management (backlight drive, battery-driven, sleep/wake-up function) </td>
</tr>
<tr>

<td valign="top">Hive registry support </td>
</tr>
<tr>
<td valign="top">ROM file system support</td>
</tr>
<tr>
<td rowspan="2">Software features</td>

<td valign="top"> Mediaplayer 9.0, Word and Internet Explorer 6.0</td>
</tr>
<tr>
<td height="20" valign="top">.NET Compact Framework 3.5</td>
</tr>
</table>
Now Linux2.6.29 is ported. Source code download from [http://code.google.com/p/devkit8000/wiki/DVSDK_3_00_02_44_linux_2_6_29?ts=1264641072&updated=DVSDK_3_00_02_44_linux_2_6_29 here] 

==Ubuntu on Devkit8000 (for reference)==
Please refer to [[Devkit8000 Ubuntu]]. 

==Port QT on Devkit8000 (for reference)==
Please refer to [[Devkit8000 QT]] on how to port QT on Devkit8000. 

==Demo (Android/Angstrom/DVSDK)==
===Android===
[[Image:Devkit8000_android.jpg]] 
The DevKit8000 can support Android which is a software platform and operating system for mobile devices, based on the Linux kernel, developed by Google and later the Open Handset Alliance. The board can run various applications based on Android. It supports 4.3" and 7" TFT LCD display and touch panel function. It can use the built-in audio player of Android to play kinds of audio files and transfer data through SD card or USB OTG. 
Please refer to [[Devkit8000 Android]] on how to use and port.

===Angstrom===
[[Image:DevKit8000_angstrom.jpg]] 
DevKit8000 can display Angstrom system on a DVI_D monitor running 720p videos at 30fps.
DevKit8000 can use various software of Angsrtom to implement file editing, internet surfing, audio and video files playing and graphics editing and more other functions. User can use USB mouser to operate on Angstrom system. 
Please refer to [[Devkit8000 Angstrom]] on how to use and port.

===DVSDK (DSP)===
[[Image:Devkit8000_dsp.jpg]] 
[http://www.armkits.com/Product/devkit8000.asp DevKit8000] supports DVSDK package which includes following functions: 
Supports 2D/3D graphics acceleration; 
Supports DSP codec (Supports audio and video hardware decoding); 
Supports S-Video output. 
Please refer to [[Devkit8000_DVSDK]] on how to use and port.

='''Devkit8000 Evaluation Kit Overview'''=
[http://www.armkits.com Embest] [http://www.armkits.com/Product/devkit8000.asp DevKit8000] Evaluation Kit includes the [http://www.armkits.com/Product/devkit8000.asp DevKit8000] evaluation board and all necessary accessories to help users start their design of multimedia applications. The board is preloaded with Linux OS in NAND flash and WinCE OS in SD card. User can display the subsystem using a 4.3" TFT LCD and Touch screen or using a DVI-D monitor through an HDMI to DVI-D cable, or using TV for NTSC/PAL video out. The USB OTG interface can also be used as USB Host function with a Mini-A to Standard-A cable, or used as USB Device function with a Mini-B to Standard-A cable. Along with the kit, [http://www.armkits.com Embest] provides user manual, schematic drawing and datasheet documents to help customers better understand and use the kit. 

[[Image:Devkit8000suite.jpg]] 

==Configurations==
[http://www.armkits.com Embest] [http://www.armkits.com/Product/devkit8000.asp DevKit8000] Evaluation Kit has two configurations: 

===Standard Configuraiton===
The standard configuration is focused on evaluating the basic functions of Devkit8000 board. 
[[Image:Devkit8000standard.gif]] 

===Complete Configuration===
The complete configuration includes complete accessories for Devkit8000 which is convenient for special application development. 
[[Image:Devkit8000access.gif]] 

==Product CD==
The Devkit8000 product CD contains following contents:
* Linux2.6.28 source code (including driver, kernel, startup code and file system)
* WinCE6.0 BSP (including driver, kernel, startup code and file system all in source code)
* Schematic in PDF format
* Onboard chip datasheet
* Linux cross-compile toolchains
* User manual

==Optional accessories==
* [http://www.armkits.com/Product/camera8000.asp CAM8000-A] analog camera module
* [http://www.armkits.com/Product/camera8000.asp Analog camera]
* [http://www.armkits.com/Product/vga8000.asp VGA8000] VGA module
* [http://www.armkits.com/Product/WF8000-U.asp WF8000-U] USB WiFi module
* [http://www.armkits.com/Product/CAM8100-U.asp CAM8100-U] digital camera module
* [http://www.armkits.com/Product/GPS8000-S.asp GPS8000-S] GPS module
* [http://www.armkits.com/Product/GPRS8000-S.asp GPRS8000-S] GPRS module
* [http://www.armkits.com/Product/CDMA8000-U.asp CDMA8000-U] USB 3G module (CDMA2000 standard)
* [http://www.armkits.com/Product/WCDMA8000-U.asp WCDMA8000-U] USB 3G module (WCDMA standard)
* [http://www.armkits.com/Product/xds100.asp XDS100v2] USB JTAG emulator

='''FAQ'''=
If you have got some problems when using Devkit8000, please refer to [[Devkit8000 FAQ]]. 

='''Other [http://www.armkits.com Embest] Products based on TI Processors'''=
[http://www.armkits.com Embest] has designed several products based on TI's ARM9 and ARM Cortex-A8 processors. [http://www.armkits.com Embest]also offers customer design service according to customer's requirements. Whether you need to reduce, add or modify to existing hardwares or generate a new solution, Embest will help customers with expert competence and rich experience. 
* [[DevKit8500]] Evalution Board based on TI's DM3730 or AM3715 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8530.asp SBC8530] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100 Plus] Single Board Computer based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/sbc8018.asp SBC8018] Single Board Computer based on TI's AM1808 ARM926EJ-S processor
* [http://www.armkits.com/product/sbc8100.asp SBC8100] Single Board Computer based on TI's OMAP3530 ARM Cortex-A8 processor
* [http://www.armkits.com/product/soc8200.asp SOC8200] Single Board Computer based on TI's AM3517 Sitara ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8510.asp Mini8510] Processor Card based on TI's DM3730 ARM Cortex-A8 processor
* [http://www.armkits.com/product/mini8100.asp Mini8100] Processor Card based on TI's OMAP3530 ARM Cortex-A8 processor

[[Category:Development Boards]][[Category:OMAP]][[Category:Linux]][[Category:Devkit8000]][[Category:DevKit8500]]

Devkit8500FAQ

2011-12-13T08:33:08Z

Yclinda666:

This page mainly summarizes solutions to some main problems during the development of [http://www.armkits.com Embest] [[DevKit8500]]. Hope it would give you some help. Please find the FAQ in Chinese from [[DevKit8500_FAQ]].

=Hardware problem=

==Why my new bought 7-inch LCD has no display when power on the board?==
Answer: This is a very normal problem. Embest default delivery is preloaded with 4.3-inch LCD image. User needs to change the image for 7-inch LCD. Please follow the document "Devkit8500 Quick User Manual.pdf" included in product DVD. 

==Why the touch screen could not be used when getting into WinCE system?==
Answer: When getting into WinCE system, the LCD displays as below, there is no response if using finger to click the center cross. There might be two reasons: 
1. The touch screen is resistive touch screen, we suggest user using touch pen to click the center cross not finger; 
2. It needs about one second touching for calibration, if touching time is too short, the operation will be invalid. 
 
[[File:EmbestDevkit8500_2.JPG]] 

=Linux problem=

==How to debug audio applications?==
Answer: We are using ALSA audio library, please go to its offical website to download relative material. You would better confirm the ALSA version you used on your target board before downloading. Please get into file system and input: cat /proc/asound/version 
After you confirmed the ALSA version, please download alsa-utils-xxx from: 
http://www.alsa-project.org/main/index.php/Main_Page 
There are source codes of aplay, arecord and more others for your reference. 

=WinCE problem=

==Why need touch screen calibration every time when getting into WinCE system?==
Answer: Because Embest provides 4.3-inch and 7-inch LCDs for the board, different LCDs use different touch screen parameters, so it needs calibration every time. 
However, we can solve the problem as below: 
1. Open the Hyper-terminal and boot the WinCE system, do touch screen calibration once and check the Hyper-terminal information, you will see similar sentence like "CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896"， these are parameters of touch screen. 
2. Please add the touch screen parameters to BSP path: bsp/file/platform.reg 
 
;-- Touch Screen driver -------------------------------------------------------- 
; @CESYSGEN IF CE_MODULES_POINTER 
; @CESYSGEN IF GWES_TCHUI 
; @XIPREGION IF PACKAGE_OEMDRIVERS 
IF BSP_NOTOUCH ! 
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH] 
"DriverName"="touch.dll" 
IF IMGNOCALIBRATION //''mask this line'' 
"CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896" //''These are parameters of your touch screen, please modify it to 4.3inch or 7inch'' 
ENDIF IMGNOCALIBRATION //''mask this line'' 
"MaxCalError"="6" 
"SPIAddr"=dword:0 ; McSPI1 channel 0 
"PenGPIO"=dword:1B ; gpio27// gpio_175 
"PenUpDebounceMS"=dword:28 ; PenUp debounce time in MS, 0 to disable debounce process 
"InitialSamplesDropped"=dword:2 ; Number of samples to be dropped after pen down detection 
; Default is 1 
;"SampleRate"=dword:64 ; samples per second, default is 100 
 
ENDIF BSP_NOTOUCH ! 
; @XIPREGION ENDIF PACKAGE_OEMDRIVERS 
; @CESYSGEN ENDIF GWES_TCHUI 
; @CESYSGEN ENDIF CE_MODULES_POINTER 
 

==Why WinCE BSP could not be compiled successfully?==
Answer: if you had installed WinCE compiling environment and want to rebuild the system, but after fully decompressed BSP to the platform directory of wince600 and also used the sln file attached with the software, it still failed. Please follow below ways to check: 
1. Please read the user manual to check if the compiling tools have been installed completely; if not complete, it will remind some error informaiton for being lack of some head files; We testing BSP carefully before goods delivery, so this part would usually no any problem; 
2. Please check if the folders copied to C:\WINCE600 are right, such as: 
Right: C:\WINCE600\OSDesigns\DevKit8500 
Wrong: C:\WINCE600\OSDesigns\DevKit8500\Devkit8500 
Please do not repeat folders. 
3. Please check if you had selected "Build Solution" in "[Build-> Build Solution]" of vs2005 window for compiling accroding to the user manual; 
4. Please check if you had added some of your own codes to make the compiling unsuccessfully; 
5. After above checking, if you still could not find the problem, please contact Embest support team: support@embedinfo.com, our engineer will give you some help. 

=DVSDK problem=

==Why I can only see one partition after TF card partitioning?==
Answer: when using DVSDK, you need to prepare a TF card with partition. But we could only see one partition, there might be several reasons: 
1. You have seen the only one partition under Windows system, the TF card first partition is FAT, the second partition is EXT3 and EXT3 can only be recognized under Linux, so you can only see FAT partition in Windows; 
2. If you can only see one partition under Linux system, please follow below ways: 
a) Confirm if you had used ROOT right for partition in your operation; 
b) Please operate once again; 
c) Change another TF card (please use TF card with good quality as partitioning requires high-quality TF card). 

==No response when booting u-boot==
Answer: when starting u-boot in DVSDK, the hyper-terminal will appear status below: 
''60 
 
Texas Instruments X-Loader 1.47 (Feb 17 2011 - 17:33:15) 
Devkit8500 xM Rev A 
Starting X-loader on MMC 
Reading boot sector 
 
1153660 Bytes Read from MMC 
Starting OS Bootloader from MMC... 
Starting OS Bootloader... 
 
 
U-Boot 2010.06-rc1-svn ( 5鏈?06 2011 - 10:05:25) 
 
OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz 
OMAP3 Devkit8500 board + LPDDR/NAND 
I2C: ready 
DRAM: 512 MiB 
NAND: 512 MiB 
In: serial 
Out: serial 
Err: serial 
Devkit8500 xM Rev A 
Die ID #2cf600229e3800000163810d19031024 
Net: dm9000 
Hit any key to stop autoboot: 0 （此处在超级终端串口下按下任意按键） 
OMAP3 devkit8500 # setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait mpurate=1000 mem=99M@0x80000000 mem=128M@0x88000000 omapdss.def_disp=lcd omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M 
OMAP3 devkit8500 # setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000' 
OMAP3 devkit8500 # saveenv 
OMAP3 devkit8500 # boot'' 
OMAP3 devkit8500 # 
 
For normal u-boot, if user inputs "boot" in u-boot, it will excute: 
setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000' 
If commands have some syntax errors, it might stop the following excution, the problem might be: 
1. When inputing some commands manually, you have ignored some space input; 
2. You had input more spaces in commands line before inputing other commands; 
We suggest copying and pasting the commands directly from pdf files. 

setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait mpurate=1000 mem=99M@0x80000000 mem=128M@0x88000000 omapdss.def_disp=lcd omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M 
 
setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000' 

[[Category:Linux]][[Category:Development Boards]][[Category:DevKit8500]]

Category:DevKit8500

2011-12-13T08:26:10Z

Yclinda666: Created page with "Category:Linux Category:Development Boards Contains all DevKit8500 articles. See also related categories listed below."

[[Category:Linux]]
[[Category:Development Boards]]

Contains all [[DevKit8500]] articles. See also related categories listed below.

DevKit8500

2011-12-13T08:24:32Z

Yclinda666:

='''Devkit8500D/A Board Overview'''=
[http://www.armkits.com Embest] [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D] Evaluation Board takes full features of the 1GHz [http://focus.ti.com/docs/prod/folders/print/dm3730.html Texas Instruments' DM3730] ARM Cortex-A8 DaVinci™ digital media processor and supports up to 512MByte DDR SDRAM and 512MByte NAND Flash as well as a reserved iNAND design to expand the flash storage capabilities. The board has exposed many other hardware interfaces including serial ports, LCD/TSP, DVI-D, S-Video, Ethernet, USB, TF, keyboard, camera, SPI, I2C and JTAG. The board is able to support for Linux 2.6.32 and WinCE 6.0 operating systems. It has two methods to boot Linux and WinCE systems from either TF card or NAND flash. Besides, it is provided with Android 2.2 demo with driver source code. [http://www.armkits.com Embest] gives instructions on how to boot Android demo image from NAND flash with TF card.

The board supports using [http://www.armkits.com/Product/xds100.asp XDS100v2] USB JTAG Emulator for debugging which is available from [http://www.armkits.com Embest]. [http://www.armkits.com Embest] also offers 4.3-inch or 7-inch LCD with touch screen and various modules for options including VGA, WiFi, Analog Camera, GPS, GPRS, 3G and Digital Camera modules which greatly extends the functions of the board and would be flexible for customer selection to meet their own needs.

The [http://focus.ti.com/docs/prod/folders/print/dm3730.html TI's DM3730] processor is pin-to-pin compatible with [http://www.ti.com/product/am3715 TI's AM3715] processor, Embest also supplies the board with the AM3715 CPU and this board is called [http://www.armkits.com/Product/devkit8500d.asp DevKit8500A].

[[Image:Devkit8500d.gif]]

='''Hardware'''=
==Onboard Interfaces and Connectors==
[[File:devkit8500header.gif]]

==Hardware Features==
* Dimensions: 136.2mm x 105.3mm
* Power Supply: +5V
* Working Temp.: 0~70°C
* TI DM3730 DaVinci Digital Media Processor (pin-to-pin compatible with TI AM3715) 
- Up to 1-GHz ARM® Cortex™-A8 Core, also supports 300, 600, and 800-MHz operation 
- Up to 800-MHz TMS320C64x+™ DSP Core, Also supports 260, 520 and 660-MHz operation 
- NEON™ SIMD Coprocessor (DM3730 only) 
- POWERVR SGX™ Graphics Accelerator 
- ARM: 32KB I-Cache; 32KB D-Cache; 256KB L2 Cache 
- Onchip 32KB ROM and 64KB Shared SDRAM 
* 512MB DDR SDRAM, 32bit, 200MHz
* 512MB NAND Flash, 16bit
* 2GB iNAND, 4bit (Default: not soldered, optional, reserved for soldering)
* TF card slot
* One 10/100M Ethernet interface (RJ45)
* One High-speed USB2.0 OTG port (Mini USB type interface)
* Four High-speed USB2.0 Host port (USB A type interface)
* One 5 line Debug serial port, RS232 (DB9 connector)
* LCD/Touch Screen interface (50-pin FPC connector, support resolution up to 2048*2048)
* DVI high-resolution image output port (HDMI interface, support 720p, 30fps signal)
* One S-Video display interface
* One audio input interface (3.5mm audio jack)
* One 2-channel audio output interface (3.5mm audio jack)
* One camera interface (30-pin FPC connector, support CCD or CMOS camera)
* 6*6 keyboard interface
* One 14-pin Jtag interface
* Four buttons (One for Reset, one for Wakeup and two for User defined)
* One expansion connector (2.0mm 40-pin SMT Female Pin Header) 
- Two 5 line serial ports, TTL voltage 
- One channel McSPI Interface (Multichannel Serial Port Interface) 
- One channel McBSP interface (Multi-Channel Buffered Serial Port) 
- One channel I2C interface 
- One channel HDQ interface (HDQ/1-Wire) 

='''FAQ'''=
If you have got some problems when using [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D/A] board, please refer to [[Devkit8500FAQ]]. 

[[Category:Development Boards]][[Category:Linux]][[Category:DevKit8500]]

Devkit8500FAQ

2011-12-13T08:16:21Z

Yclinda666:

This page mainly summarizes solutions to some main problems during the development of [http://www.armkits.com Embest] [[DevKit8500]]. Hope it would give you some help.

=Hardware problem=

==Why my new bought 7-inch LCD has no display when power on the board?==
Answer: This is a very normal problem. Embest default delivery is preloaded with 4.3-inch LCD image. User needs to change the image for 7-inch LCD. Please follow the document "Devkit8500 Quick User Manual.pdf" included in product DVD. 

==Why the touch screen could not be used when getting into WinCE system?==
Answer: When getting into WinCE system, the LCD displays as below, there is no response if using finger to click the center cross. There might be two reasons: 
1. The touch screen is resistive touch screen, we suggest user using touch pen to click the center cross not finger; 
2. It needs about one second touching for calibration, if touching time is too short, the operation will be invalid. 
 
[[File:EmbestDevkit8500_2.JPG]] 

=Linux problem=

==How to debug audio applications?==
Answer: We are using ALSA audio library, please go to its offical website to download relative material. You would better confirm the ALSA version you used on your target board before downloading. Please get into file system and input: cat /proc/asound/version 
After you confirmed the ALSA version, please download alsa-utils-xxx from: 
http://www.alsa-project.org/main/index.php/Main_Page 
There are source codes of aplay, arecord and more others for your reference. 

=WinCE problem=

==Why need touch screen calibration every time when getting into WinCE system?==
Answer: Because Embest provides 4.3-inch and 7-inch LCDs for the board, different LCDs use different touch screen parameters, so it needs calibration every time. 
However, we can solve the problem as below: 
1. Open the Hyper-terminal and boot the WinCE system, do touch screen calibration once and check the Hyper-terminal information, you will see similar sentence like "CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896"， these are parameters of touch screen. 
2. Please add the touch screen parameters to BSP path: bsp/file/platform.reg 
 
;-- Touch Screen driver -------------------------------------------------------- 
; @CESYSGEN IF CE_MODULES_POINTER 
; @CESYSGEN IF GWES_TCHUI 
; @XIPREGION IF PACKAGE_OEMDRIVERS 
IF BSP_NOTOUCH ! 
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH] 
"DriverName"="touch.dll" 
IF IMGNOCALIBRATION //''mask this line'' 
"CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896" //''These are parameters of your touch screen, please modify it to 4.3inch or 7inch'' 
ENDIF IMGNOCALIBRATION //''mask this line'' 
"MaxCalError"="6" 
"SPIAddr"=dword:0 ; McSPI1 channel 0 
"PenGPIO"=dword:1B ; gpio27// gpio_175 
"PenUpDebounceMS"=dword:28 ; PenUp debounce time in MS, 0 to disable debounce process 
"InitialSamplesDropped"=dword:2 ; Number of samples to be dropped after pen down detection 
; Default is 1 
;"SampleRate"=dword:64 ; samples per second, default is 100 
 
ENDIF BSP_NOTOUCH ! 
; @XIPREGION ENDIF PACKAGE_OEMDRIVERS 
; @CESYSGEN ENDIF GWES_TCHUI 
; @CESYSGEN ENDIF CE_MODULES_POINTER 
 

==Why WinCE BSP could not be compiled successfully?==
Answer: if you had installed WinCE compiling environment and want to rebuild the system, but after fully decompressed BSP to the platform directory of wince600 and also used the sln file attached with the software, it still failed. Please follow below ways to check: 
1. Please read the user manual to check if the compiling tools have been installed completely; if not complete, it will remind some error informaiton for being lack of some head files; We testing BSP carefully before goods delivery, so this part would usually no any problem; 
2. Please check if the folders copied to C:\WINCE600 are right, such as: 
Right: C:\WINCE600\OSDesigns\DevKit8500 
Wrong: C:\WINCE600\OSDesigns\DevKit8500\Devkit8500 
Please do not repeat folders. 
3. Please check if you had selected "Build Solution" in "[Build-> Build Solution]" of vs2005 window for compiling accroding to the user manual; 
4. Please check if you had added some of your own codes to make the compiling unsuccessfully; 
5. After above checking, if you still could not find the problem, please contact Embest support team: support@embedinfo.com, our engineer will give you some help. 

=DVSDK problem=

==Why I can only see one partition after TF card partitioning?==
Answer: when using DVSDK, you need to prepare a TF card with partition. But we could only see one partition, there might be several reasons: 
1. You have seen the only one partition under Windows system, the TF card first partition is FAT, the second partition is EXT3 and EXT3 can only be recognized under Linux, so you can only see FAT partition in Windows; 
2. If you can only see one partition under Linux system, please follow below ways: 
a) Confirm if you had used ROOT right for partition in your operation; 
b) Please operate once again; 
c) Change another TF card (please use TF card with good quality as partitioning requires high-quality TF card). 

==No response when booting u-boot==
Answer: when starting u-boot in DVSDK, the hyper-terminal will appear status below: 
''60 
 
Texas Instruments X-Loader 1.47 (Feb 17 2011 - 17:33:15) 
Devkit8500 xM Rev A 
Starting X-loader on MMC 
Reading boot sector 
 
1153660 Bytes Read from MMC 
Starting OS Bootloader from MMC... 
Starting OS Bootloader... 
 
 
U-Boot 2010.06-rc1-svn ( 5鏈?06 2011 - 10:05:25) 
 
OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz 
OMAP3 Devkit8500 board + LPDDR/NAND 
I2C: ready 
DRAM: 512 MiB 
NAND: 512 MiB 
In: serial 
Out: serial 
Err: serial 
Devkit8500 xM Rev A 
Die ID #2cf600229e3800000163810d19031024 
Net: dm9000 
Hit any key to stop autoboot: 0 （此处在超级终端串口下按下任意按键） 
OMAP3 devkit8500 # setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait mpurate=1000 mem=99M@0x80000000 mem=128M@0x88000000 omapdss.def_disp=lcd omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M 
OMAP3 devkit8500 # setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000' 
OMAP3 devkit8500 # saveenv 
OMAP3 devkit8500 # boot'' 
OMAP3 devkit8500 # 
 
For normal u-boot, if user inputs "boot" in u-boot, it will excute: 
setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000' 
If commands have some syntax errors, it might stop the following excution, the problem might be: 
1. When inputing some commands manually, you have ignored some space input; 
2. You had input more spaces in commands line before inputing other commands; 
We suggest copying and pasting the commands directly from pdf files. 

setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait mpurate=1000 mem=99M@0x80000000 mem=128M@0x88000000 omapdss.def_disp=lcd omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M 
 
setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000' 

[[Category:Linux]][[Category:Development Boards]][[Category:DevKit8500]]

Devkit8500FAQ

2011-12-13T08:15:22Z

Yclinda666: /* No response when booting u-boot */

This page mainly summarizes solutions to some main problems during the development of [http://www.armkits.com Embest] [[Devkit8500]]. Hope it would give you some help.

=Hardware problem=

==Why my new bought 7-inch LCD has no display when power on the board?==
Answer: This is a very normal problem. Embest default delivery is preloaded with 4.3-inch LCD image. User needs to change the image for 7-inch LCD. Please follow the document "Devkit8500 Quick User Manual.pdf" included in product DVD. 

==Why the touch screen could not be used when getting into WinCE system?==
Answer: When getting into WinCE system, the LCD displays as below, there is no response if using finger to click the center cross. There might be two reasons: 
1. The touch screen is resistive touch screen, we suggest user using touch pen to click the center cross not finger; 
2. It needs about one second touching for calibration, if touching time is too short, the operation will be invalid. 
 
[[File:EmbestDevkit8500_2.JPG]] 

=Linux problem=

==How to debug audio applications?==
Answer: We are using ALSA audio library, please go to its offical website to download relative material. You would better confirm the ALSA version you used on your target board before downloading. Please get into file system and input: cat /proc/asound/version 
After you confirmed the ALSA version, please download alsa-utils-xxx from: 
http://www.alsa-project.org/main/index.php/Main_Page 
There are source codes of aplay, arecord and more others for your reference. 

=WinCE problem=

==Why need touch screen calibration every time when getting into WinCE system?==
Answer: Because Embest provides 4.3-inch and 7-inch LCDs for the board, different LCDs use different touch screen parameters, so it needs calibration every time. 
However, we can solve the problem as below: 
1. Open the Hyper-terminal and boot the WinCE system, do touch screen calibration once and check the Hyper-terminal information, you will see similar sentence like "CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896"， these are parameters of touch screen. 
2. Please add the touch screen parameters to BSP path: bsp/file/platform.reg 
 
;-- Touch Screen driver -------------------------------------------------------- 
; @CESYSGEN IF CE_MODULES_POINTER 
; @CESYSGEN IF GWES_TCHUI 
; @XIPREGION IF PACKAGE_OEMDRIVERS 
IF BSP_NOTOUCH ! 
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH] 
"DriverName"="touch.dll" 
IF IMGNOCALIBRATION //''mask this line'' 
"CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896" //''These are parameters of your touch screen, please modify it to 4.3inch or 7inch'' 
ENDIF IMGNOCALIBRATION //''mask this line'' 
"MaxCalError"="6" 
"SPIAddr"=dword:0 ; McSPI1 channel 0 
"PenGPIO"=dword:1B ; gpio27// gpio_175 
"PenUpDebounceMS"=dword:28 ; PenUp debounce time in MS, 0 to disable debounce process 
"InitialSamplesDropped"=dword:2 ; Number of samples to be dropped after pen down detection 
; Default is 1 
;"SampleRate"=dword:64 ; samples per second, default is 100 
 
ENDIF BSP_NOTOUCH ! 
; @XIPREGION ENDIF PACKAGE_OEMDRIVERS 
; @CESYSGEN ENDIF GWES_TCHUI 
; @CESYSGEN ENDIF CE_MODULES_POINTER 
 

==Why WinCE BSP could not be compiled successfully?==
Answer: if you had installed WinCE compiling environment and want to rebuild the system, but after fully decompressed BSP to the platform directory of wince600 and also used the sln file attached with the software, it still failed. Please follow below ways to check: 
1. Please read the user manual to check if the compiling tools have been installed completely; if not complete, it will remind some error informaiton for being lack of some head files; We testing BSP carefully before goods delivery, so this part would usually no any problem; 
2. Please check if the folders copied to C:\WINCE600 are right, such as: 
Right: C:\WINCE600\OSDesigns\DevKit8500 
Wrong: C:\WINCE600\OSDesigns\DevKit8500\Devkit8500 
Please do not repeat folders. 
3. Please check if you had selected "Build Solution" in "[Build-> Build Solution]" of vs2005 window for compiling accroding to the user manual; 
4. Please check if you had added some of your own codes to make the compiling unsuccessfully; 
5. After above checking, if you still could not find the problem, please contact Embest support team: support@embedinfo.com, our engineer will give you some help. 

=DVSDK problem=

==Why I can only see one partition after TF card partitioning?==
Answer: when using DVSDK, you need to prepare a TF card with partition. But we could only see one partition, there might be several reasons: 
1. You have seen the only one partition under Windows system, the TF card first partition is FAT, the second partition is EXT3 and EXT3 can only be recognized under Linux, so you can only see FAT partition in Windows; 
2. If you can only see one partition under Linux system, please follow below ways: 
a) Confirm if you had used ROOT right for partition in your operation; 
b) Please operate once again; 
c) Change another TF card (please use TF card with good quality as partitioning requires high-quality TF card). 

==No response when booting u-boot==
Answer: when starting u-boot in DVSDK, the hyper-terminal will appear status below: 
''60 
 
Texas Instruments X-Loader 1.47 (Feb 17 2011 - 17:33:15) 
Devkit8500 xM Rev A 
Starting X-loader on MMC 
Reading boot sector 
 
1153660 Bytes Read from MMC 
Starting OS Bootloader from MMC... 
Starting OS Bootloader... 
 
 
U-Boot 2010.06-rc1-svn ( 5鏈?06 2011 - 10:05:25) 
 
OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz 
OMAP3 Devkit8500 board + LPDDR/NAND 
I2C: ready 
DRAM: 512 MiB 
NAND: 512 MiB 
In: serial 
Out: serial 
Err: serial 
Devkit8500 xM Rev A 
Die ID #2cf600229e3800000163810d19031024 
Net: dm9000 
Hit any key to stop autoboot: 0 （此处在超级终端串口下按下任意按键） 
OMAP3 devkit8500 # setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait mpurate=1000 mem=99M@0x80000000 mem=128M@0x88000000 omapdss.def_disp=lcd omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M 
OMAP3 devkit8500 # setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000' 
OMAP3 devkit8500 # saveenv 
OMAP3 devkit8500 # boot'' 
OMAP3 devkit8500 # 
 
For normal u-boot, if user inputs "boot" in u-boot, it will excute: 
setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000' 
If commands have some syntax errors, it might stop the following excution, the problem might be: 
1. When inputing some commands manually, you have ignored some space input; 
2. You had input more spaces in commands line before inputing other commands; 
We suggest copying and pasting the commands directly from pdf files. 

setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait mpurate=1000 mem=99M@0x80000000 mem=128M@0x88000000 omapdss.def_disp=lcd omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M 
 
setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000' 

[[Category:Linux]][[Category:Development Boards]][[Category:DevKit8500]]

Devkit8500FAQ

2011-12-13T08:14:01Z

Yclinda666: /* DVSDK problem */

This page mainly summarizes solutions to some main problems during the development of [http://www.armkits.com Embest] [[Devkit8500]]. Hope it would give you some help.

=Hardware problem=

==Why my new bought 7-inch LCD has no display when power on the board?==
Answer: This is a very normal problem. Embest default delivery is preloaded with 4.3-inch LCD image. User needs to change the image for 7-inch LCD. Please follow the document "Devkit8500 Quick User Manual.pdf" included in product DVD. 

==Why the touch screen could not be used when getting into WinCE system?==
Answer: When getting into WinCE system, the LCD displays as below, there is no response if using finger to click the center cross. There might be two reasons: 
1. The touch screen is resistive touch screen, we suggest user using touch pen to click the center cross not finger; 
2. It needs about one second touching for calibration, if touching time is too short, the operation will be invalid. 
 
[[File:EmbestDevkit8500_2.JPG]] 

=Linux problem=

==How to debug audio applications?==
Answer: We are using ALSA audio library, please go to its offical website to download relative material. You would better confirm the ALSA version you used on your target board before downloading. Please get into file system and input: cat /proc/asound/version 
After you confirmed the ALSA version, please download alsa-utils-xxx from: 
http://www.alsa-project.org/main/index.php/Main_Page 
There are source codes of aplay, arecord and more others for your reference. 

=WinCE problem=

==Why need touch screen calibration every time when getting into WinCE system?==
Answer: Because Embest provides 4.3-inch and 7-inch LCDs for the board, different LCDs use different touch screen parameters, so it needs calibration every time. 
However, we can solve the problem as below: 
1. Open the Hyper-terminal and boot the WinCE system, do touch screen calibration once and check the Hyper-terminal information, you will see similar sentence like "CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896"， these are parameters of touch screen. 
2. Please add the touch screen parameters to BSP path: bsp/file/platform.reg 
 
;-- Touch Screen driver -------------------------------------------------------- 
; @CESYSGEN IF CE_MODULES_POINTER 
; @CESYSGEN IF GWES_TCHUI 
; @XIPREGION IF PACKAGE_OEMDRIVERS 
IF BSP_NOTOUCH ! 
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH] 
"DriverName"="touch.dll" 
IF IMGNOCALIBRATION //''mask this line'' 
"CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896" //''These are parameters of your touch screen, please modify it to 4.3inch or 7inch'' 
ENDIF IMGNOCALIBRATION //''mask this line'' 
"MaxCalError"="6" 
"SPIAddr"=dword:0 ; McSPI1 channel 0 
"PenGPIO"=dword:1B ; gpio27// gpio_175 
"PenUpDebounceMS"=dword:28 ; PenUp debounce time in MS, 0 to disable debounce process 
"InitialSamplesDropped"=dword:2 ; Number of samples to be dropped after pen down detection 
; Default is 1 
;"SampleRate"=dword:64 ; samples per second, default is 100 
 
ENDIF BSP_NOTOUCH ! 
; @XIPREGION ENDIF PACKAGE_OEMDRIVERS 
; @CESYSGEN ENDIF GWES_TCHUI 
; @CESYSGEN ENDIF CE_MODULES_POINTER 
 

==Why WinCE BSP could not be compiled successfully?==
Answer: if you had installed WinCE compiling environment and want to rebuild the system, but after fully decompressed BSP to the platform directory of wince600 and also used the sln file attached with the software, it still failed. Please follow below ways to check: 
1. Please read the user manual to check if the compiling tools have been installed completely; if not complete, it will remind some error informaiton for being lack of some head files; We testing BSP carefully before goods delivery, so this part would usually no any problem; 
2. Please check if the folders copied to C:\WINCE600 are right, such as: 
Right: C:\WINCE600\OSDesigns\DevKit8500 
Wrong: C:\WINCE600\OSDesigns\DevKit8500\Devkit8500 
Please do not repeat folders. 
3. Please check if you had selected "Build Solution" in "[Build-> Build Solution]" of vs2005 window for compiling accroding to the user manual; 
4. Please check if you had added some of your own codes to make the compiling unsuccessfully; 
5. After above checking, if you still could not find the problem, please contact Embest support team: support@embedinfo.com, our engineer will give you some help. 

=DVSDK problem=

==Why I can only see one partition after TF card partitioning?==
Answer: when using DVSDK, you need to prepare a TF card with partition. But we could only see one partition, there might be several reasons: 
1. You have seen the only one partition under Windows system, the TF card first partition is FAT, the second partition is EXT3 and EXT3 can only be recognized under Linux, so you can only see FAT partition in Windows; 
2. If you can only see one partition under Linux system, please follow below ways: 
a) Confirm if you had used ROOT right for partition in your operation; 
b) Please operate once again; 
c) Change another TF card (please use TF card with good quality as partitioning requires high-quality TF card). 

==No response when booting u-boot==
Answer: when starting u-boot in DVSDK, the hyper-terminal will appear status below: 
''60 
 
Texas Instruments X-Loader 1.47 (Feb 17 2011 - 17:33:15) 
Devkit8500 xM Rev A 
Starting X-loader on MMC 
Reading boot sector 
 
1153660 Bytes Read from MMC 
Starting OS Bootloader from MMC... 
Starting OS Bootloader... 
 
 
U-Boot 2010.06-rc1-svn ( 5鏈?06 2011 - 10:05:25) 
 
OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz 
OMAP3 Devkit8500 board + LPDDR/NAND 
I2C: ready 
DRAM: 512 MiB 
NAND: 512 MiB 
In: serial 
Out: serial 
Err: serial 
Devkit8500 xM Rev A 
Die ID #2cf600229e3800000163810d19031024 
Net: dm9000 
Hit any key to stop autoboot: 0 （此处在超级终端串口下按下任意按键） 
OMAP3 devkit8500 # setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait mpurate=1000 mem=99M@0x80000000 mem=128M@0x88000000 omapdss.def_disp=lcd omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M 
OMAP3 devkit8500 # setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000' 
OMAP3 devkit8500 # saveenv 
OMAP3 devkit8500 # boot'' 
OMAP3 devkit8500 # 
 
For normal u-boot, if user inputs "boot" in u-boot, it will excute: 
setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000' 
If commands have some syntax errors, it might stop the following excution, the problem might be: 
1. When inputing some commands manually, you have ignored some space input; 
2. You had input more spaces in commands line before inputing other commands; 
We suggest copying and pasting the commands directly from pdf files. 
 
setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait mpurate=1000 mem=99M@0x80000000 mem=128M@0x88000000 omapdss.def_disp=lcd omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M 
 
setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000' 

[[Category:Linux]][[Category:Development Boards]][[Category:DevKit8500]]

Devkit8500FAQ

2011-12-13T08:00:30Z

Yclinda666: /* Why I can only see one partition after TF card partitioning? */

This page mainly summarizes solutions to some main problems during the development of [http://www.armkits.com Embest] [[Devkit8500]]. Hope it would give you some help.

=Hardware problem=

==Why my new bought 7-inch LCD has no display when power on the board?==
Answer: This is a very normal problem. Embest default delivery is preloaded with 4.3-inch LCD image. User needs to change the image for 7-inch LCD. Please follow the document "Devkit8500 Quick User Manual.pdf" included in product DVD. 

==Why the touch screen could not be used when getting into WinCE system?==
Answer: When getting into WinCE system, the LCD displays as below, there is no response if using finger to click the center cross. There might be two reasons: 
1. The touch screen is resistive touch screen, we suggest user using touch pen to click the center cross not finger; 
2. It needs about one second touching for calibration, if touching time is too short, the operation will be invalid. 
 
[[File:EmbestDevkit8500_2.JPG]] 

=Linux problem=

==How to debug audio applications?==
Answer: We are using ALSA audio library, please go to its offical website to download relative material. You would better confirm the ALSA version you used on your target board before downloading. Please get into file system and input: cat /proc/asound/version 
After you confirmed the ALSA version, please download alsa-utils-xxx from: 
http://www.alsa-project.org/main/index.php/Main_Page 
There are source codes of aplay, arecord and more others for your reference. 

=WinCE problem=

==Why need touch screen calibration every time when getting into WinCE system?==
Answer: Because Embest provides 4.3-inch and 7-inch LCDs for the board, different LCDs use different touch screen parameters, so it needs calibration every time. 
However, we can solve the problem as below: 
1. Open the Hyper-terminal and boot the WinCE system, do touch screen calibration once and check the Hyper-terminal information, you will see similar sentence like "CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896"， these are parameters of touch screen. 
2. Please add the touch screen parameters to BSP path: bsp/file/platform.reg 
 
;-- Touch Screen driver -------------------------------------------------------- 
; @CESYSGEN IF CE_MODULES_POINTER 
; @CESYSGEN IF GWES_TCHUI 
; @XIPREGION IF PACKAGE_OEMDRIVERS 
IF BSP_NOTOUCH ! 
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH] 
"DriverName"="touch.dll" 
IF IMGNOCALIBRATION //''mask this line'' 
"CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896" //''These are parameters of your touch screen, please modify it to 4.3inch or 7inch'' 
ENDIF IMGNOCALIBRATION //''mask this line'' 
"MaxCalError"="6" 
"SPIAddr"=dword:0 ; McSPI1 channel 0 
"PenGPIO"=dword:1B ; gpio27// gpio_175 
"PenUpDebounceMS"=dword:28 ; PenUp debounce time in MS, 0 to disable debounce process 
"InitialSamplesDropped"=dword:2 ; Number of samples to be dropped after pen down detection 
; Default is 1 
;"SampleRate"=dword:64 ; samples per second, default is 100 
 
ENDIF BSP_NOTOUCH ! 
; @XIPREGION ENDIF PACKAGE_OEMDRIVERS 
; @CESYSGEN ENDIF GWES_TCHUI 
; @CESYSGEN ENDIF CE_MODULES_POINTER 
 

==Why WinCE BSP could not be compiled successfully?==
Answer: if you had installed WinCE compiling environment and want to rebuild the system, but after fully decompressed BSP to the platform directory of wince600 and also used the sln file attached with the software, it still failed. Please follow below ways to check: 
1. Please read the user manual to check if the compiling tools have been installed completely; if not complete, it will remind some error informaiton for being lack of some head files; We testing BSP carefully before goods delivery, so this part would usually no any problem; 
2. Please check if the folders copied to C:\WINCE600 are right, such as: 
Right: C:\WINCE600\OSDesigns\DevKit8500 
Wrong: C:\WINCE600\OSDesigns\DevKit8500\Devkit8500 
Please do not repeat folders. 
3. Please check if you had selected "Build Solution" in "[Build-> Build Solution]" of vs2005 window for compiling accroding to the user manual; 
4. Please check if you had added some of your own codes to make the compiling unsuccessfully; 
5. After above checking, if you still could not find the problem, please contact Embest support team: support@embedinfo.com, our engineer will give you some help. 

=DVSDK problem=

==Why I can only see one partition after TF card partitioning?==
Answer: when using DVSDK, you need to prepare a TF card with partition. But we could only see one partition, there might be several reasons: 
1. You have seen the only one partition under Windows system, the TF card first partition is FAT, the second partition is EXT3 and EXT3 can only be recognized under Linux, so you can only see FAT partition in Windows; 
2. If you can only see one partition under Linux system, please follow below ways: 
a) Confirm if you had used ROOT right for partition in your operation; 
b) Please operate once again; 
c) Change another TF card (please use TF card with good quality as partitioning requires high-quality TF card). 

[[Category:Linux]][[Category:Development Boards]][[Category:DevKit8500]]

Devkit8500FAQ

2011-12-13T07:59:47Z

Yclinda666: /* Why I can only see one partition after TF card partitioning? */

This page mainly summarizes solutions to some main problems during the development of [http://www.armkits.com Embest] [[Devkit8500]]. Hope it would give you some help.

=Hardware problem=

==Why my new bought 7-inch LCD has no display when power on the board?==
Answer: This is a very normal problem. Embest default delivery is preloaded with 4.3-inch LCD image. User needs to change the image for 7-inch LCD. Please follow the document "Devkit8500 Quick User Manual.pdf" included in product DVD. 

==Why the touch screen could not be used when getting into WinCE system?==
Answer: When getting into WinCE system, the LCD displays as below, there is no response if using finger to click the center cross. There might be two reasons: 
1. The touch screen is resistive touch screen, we suggest user using touch pen to click the center cross not finger; 
2. It needs about one second touching for calibration, if touching time is too short, the operation will be invalid. 
 
[[File:EmbestDevkit8500_2.JPG]] 

=Linux problem=

==How to debug audio applications?==
Answer: We are using ALSA audio library, please go to its offical website to download relative material. You would better confirm the ALSA version you used on your target board before downloading. Please get into file system and input: cat /proc/asound/version 
After you confirmed the ALSA version, please download alsa-utils-xxx from: 
http://www.alsa-project.org/main/index.php/Main_Page 
There are source codes of aplay, arecord and more others for your reference. 

=WinCE problem=

==Why need touch screen calibration every time when getting into WinCE system?==
Answer: Because Embest provides 4.3-inch and 7-inch LCDs for the board, different LCDs use different touch screen parameters, so it needs calibration every time. 
However, we can solve the problem as below: 
1. Open the Hyper-terminal and boot the WinCE system, do touch screen calibration once and check the Hyper-terminal information, you will see similar sentence like "CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896"， these are parameters of touch screen. 
2. Please add the touch screen parameters to BSP path: bsp/file/platform.reg 
 
;-- Touch Screen driver -------------------------------------------------------- 
; @CESYSGEN IF CE_MODULES_POINTER 
; @CESYSGEN IF GWES_TCHUI 
; @XIPREGION IF PACKAGE_OEMDRIVERS 
IF BSP_NOTOUCH ! 
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH] 
"DriverName"="touch.dll" 
IF IMGNOCALIBRATION //''mask this line'' 
"CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896" //''These are parameters of your touch screen, please modify it to 4.3inch or 7inch'' 
ENDIF IMGNOCALIBRATION //''mask this line'' 
"MaxCalError"="6" 
"SPIAddr"=dword:0 ; McSPI1 channel 0 
"PenGPIO"=dword:1B ; gpio27// gpio_175 
"PenUpDebounceMS"=dword:28 ; PenUp debounce time in MS, 0 to disable debounce process 
"InitialSamplesDropped"=dword:2 ; Number of samples to be dropped after pen down detection 
; Default is 1 
;"SampleRate"=dword:64 ; samples per second, default is 100 
 
ENDIF BSP_NOTOUCH ! 
; @XIPREGION ENDIF PACKAGE_OEMDRIVERS 
; @CESYSGEN ENDIF GWES_TCHUI 
; @CESYSGEN ENDIF CE_MODULES_POINTER 
 

==Why WinCE BSP could not be compiled successfully?==
Answer: if you had installed WinCE compiling environment and want to rebuild the system, but after fully decompressed BSP to the platform directory of wince600 and also used the sln file attached with the software, it still failed. Please follow below ways to check: 
1. Please read the user manual to check if the compiling tools have been installed completely; if not complete, it will remind some error informaiton for being lack of some head files; We testing BSP carefully before goods delivery, so this part would usually no any problem; 
2. Please check if the folders copied to C:\WINCE600 are right, such as: 
Right: C:\WINCE600\OSDesigns\DevKit8500 
Wrong: C:\WINCE600\OSDesigns\DevKit8500\Devkit8500 
Please do not repeat folders. 
3. Please check if you had selected "Build Solution" in "[Build-> Build Solution]" of vs2005 window for compiling accroding to the user manual; 
4. Please check if you had added some of your own codes to make the compiling unsuccessfully; 
5. After above checking, if you still could not find the problem, please contact Embest support team: support@embedinfo.com, our engineer will give you some help. 

=DVSDK problem=

==Why I can only see one partition after TF card partitioning?==
Answer: when using DVSDK, you need to prepare a TF card with partition. But we could only see one partition, there might be several reasons: 
1. You have seen the only one partition under Windows system, the TF card first partition is FAT, the second partition is EXT3 and EXT3 can only be recognized under Linux, so you can only see FAT partition in Windows; 
2. If you can only see one partition under Linux system, please follow below ways: 
a) Confirm if you had used ROOT right for partition in your operation; 
b) Please operate once again; 
c) Change another TF card (please use TF card with good quality as partitioning requires high-quality TF card. 

[[Category:Linux]][[Category:Development Boards]][[Category:DevKit8500]]

Devkit8500FAQ

2011-12-13T07:59:04Z

Yclinda666: /* Why I can only see one partition after TF card partitioning? */

This page mainly summarizes solutions to some main problems during the development of [http://www.armkits.com Embest] [[Devkit8500]]. Hope it would give you some help.

=Hardware problem=

==Why my new bought 7-inch LCD has no display when power on the board?==
Answer: This is a very normal problem. Embest default delivery is preloaded with 4.3-inch LCD image. User needs to change the image for 7-inch LCD. Please follow the document "Devkit8500 Quick User Manual.pdf" included in product DVD. 

==Why the touch screen could not be used when getting into WinCE system?==
Answer: When getting into WinCE system, the LCD displays as below, there is no response if using finger to click the center cross. There might be two reasons: 
1. The touch screen is resistive touch screen, we suggest user using touch pen to click the center cross not finger; 
2. It needs about one second touching for calibration, if touching time is too short, the operation will be invalid. 
 
[[File:EmbestDevkit8500_2.JPG]] 

=Linux problem=

==How to debug audio applications?==
Answer: We are using ALSA audio library, please go to its offical website to download relative material. You would better confirm the ALSA version you used on your target board before downloading. Please get into file system and input: cat /proc/asound/version 
After you confirmed the ALSA version, please download alsa-utils-xxx from: 
http://www.alsa-project.org/main/index.php/Main_Page 
There are source codes of aplay, arecord and more others for your reference. 

=WinCE problem=

==Why need touch screen calibration every time when getting into WinCE system?==
Answer: Because Embest provides 4.3-inch and 7-inch LCDs for the board, different LCDs use different touch screen parameters, so it needs calibration every time. 
However, we can solve the problem as below: 
1. Open the Hyper-terminal and boot the WinCE system, do touch screen calibration once and check the Hyper-terminal information, you will see similar sentence like "CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896"， these are parameters of touch screen. 
2. Please add the touch screen parameters to BSP path: bsp/file/platform.reg 
 
;-- Touch Screen driver -------------------------------------------------------- 
; @CESYSGEN IF CE_MODULES_POINTER 
; @CESYSGEN IF GWES_TCHUI 
; @XIPREGION IF PACKAGE_OEMDRIVERS 
IF BSP_NOTOUCH ! 
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH] 
"DriverName"="touch.dll" 
IF IMGNOCALIBRATION //''mask this line'' 
"CalibrationData"="2016,1888 1056,864 992,2912 3040,2976 3072,896" //''These are parameters of your touch screen, please modify it to 4.3inch or 7inch'' 
ENDIF IMGNOCALIBRATION //''mask this line'' 
"MaxCalError"="6" 
"SPIAddr"=dword:0 ; McSPI1 channel 0 
"PenGPIO"=dword:1B ; gpio27// gpio_175 
"PenUpDebounceMS"=dword:28 ; PenUp debounce time in MS, 0 to disable debounce process 
"InitialSamplesDropped"=dword:2 ; Number of samples to be dropped after pen down detection 
; Default is 1 
;"SampleRate"=dword:64 ; samples per second, default is 100 
 
ENDIF BSP_NOTOUCH ! 
; @XIPREGION ENDIF PACKAGE_OEMDRIVERS 
; @CESYSGEN ENDIF GWES_TCHUI 
; @CESYSGEN ENDIF CE_MODULES_POINTER 
 

==Why WinCE BSP could not be compiled successfully?==
Answer: if you had installed WinCE compiling environment and want to rebuild the system, but after fully decompressed BSP to the platform directory of wince600 and also used the sln file attached with the software, it still failed. Please follow below ways to check: 
1. Please read the user manual to check if the compiling tools have been installed completely; if not complete, it will remind some error informaiton for being lack of some head files; We testing BSP carefully before goods delivery, so this part would usually no any problem; 
2. Please check if the folders copied to C:\WINCE600 are right, such as: 
Right: C:\WINCE600\OSDesigns\DevKit8500 
Wrong: C:\WINCE600\OSDesigns\DevKit8500\Devkit8500 
Please do not repeat folders. 
3. Please check if you had selected "Build Solution" in "[Build-> Build Solution]" of vs2005 window for compiling accroding to the user manual; 
4. Please check if you had added some of your own codes to make the compiling unsuccessfully; 
5. After above checking, if you still could not find the problem, please contact Embest support team: support@embedinfo.com, our engineer will give you some help. 

=DVSDK problem=

==Why I can only see one partition after TF card partitioning?==
Answer: when using DVSDK, you need to prepare a TF card with partition. But we could only see one partition, there might be several reasons: 
1. You have seen the only one partition under Windows system, the TF card first partition is FAT, the second partition is EXT3 and EXT3 can only be recognized under Linux, so you can only see FAT partition in Windows; 
2. If you can only see on partition under Linux system, please follow below ways: 
a) Confirm if you had used ROOT right for partition in your operation; 
b) Please operate once again; 
c) Change another TF card (please use TF card with good quality as partitioning requires high-quality TF card. 

[[Category:Linux]][[Category:Development Boards]][[Category:DevKit8500]]

Devkit8500FAQ

2011-12-13T07:57:45Z

DevKit8500

2011-12-13T03:42:46Z

Yclinda666: /* FAQ */

DevKit8500

2011-12-13T03:41:42Z

Yclinda666:

File:Devkit8500header.gif

2011-12-13T03:36:20Z

Yclinda666: uploaded a new version of "File:Devkit8500header.gif": Reverted to version as of 03:10, 13 December 2011

DevKit8500

2011-12-13T03:35:18Z

Yclinda666: