eLinux.org - User contributions [en]

BeagleBoard Trainer

2010-01-11T19:09:57Z

RobertK: k

[[File:trainer.jpg|thumb|right|The BeagleBoard Trainer]]
The Trainer Board is an expansion board for the BeagleBoard that adds:
* I2C interface(+3.3v or +5v selectable)
* SPI(+3.3v)
* GPIO's(+3.3v)
* large 0.1" prototype matrix and power bus.
* Atmega168
** Adruino compatiblle
** +3.3v or +5v selectable
** connected via the second uart to the BeagleBoard

BeagleBoard

2009-03-26T07:25:18Z

RobertK: /* Revision C2 */ price

[[Category: Linux]]
[[Category: OMAP]]
This page collects information about [http://www.ti.com/ TI's] [http://www.arm.com/ ARM] based [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] [http://beagleboard.org Beagle Board].

=Events=
* March 31st 2009 : [http://groups.google.com/group/beagleboard/browse_thread/thread/b15cf8a5797c73a2 Silica - Free TI - ARM OMAP Workshop], Brussels, Europe
* [http://code.google.com/soc/ Google Summer of Code 2009]: [[BeagleBoard/GSoC|BeagleBoard.org specific page]]

=Hardware=

The Beagle Board is ''a low-cost, fan-less single-board computer based on TIs 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 Core ~600MHz paired with a TMS320C64x+ DSP ~430MHz. Also included on the die is 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|Target price is US-$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 it's capabilities.

==Components==

'''Top view of rev B:'''

[[Image:Beagle_top_notes.jpg]]
{|border=1
!No.
!Name
!Comment
|-
|'''1'''
|[http://www.ti.com/omap35x OMAP3530] processor + 128MB DDR + 256MB NAND
|PoP: Package-On-Package implementation for Memory Stacking
[http://www.micron.com/products/partdetail?part=MT29C2G24MAKLAJG-6%20IT 256MB NAND/128MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1435-ND DigiKey]

([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]]
|
|-
|'''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]]
|Currently not working in rev A or B boards; Rev C planned.
|-
|'''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
|Audio CODEC, USB port, power-on reset and power management, pin-compatible with the [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] chip
|-
|}

* Board size: 3" x 3" (about 76.2 x 76.2 mm)
* Currently 6 layer PCB; target: 4 layer

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

'''Top view of rev C2:'''

[[Image:Beaglec2.jpg]]

==Manual==

See [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard HW Reference Manual (rev. B7.2)].

==Schematic==

Schematic of BeagleBoard Rev. B7 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard HW Reference Manual (rev. B7.2)], from [http://beagleboard.org/hardware/design BeagleBoard.org design page] or in [http://xgoat.com/proj/beagleboard/schematic.pdf 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. B7 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard HW Reference Manual (rev. B7.2)] or from [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 5V.) 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.8V has excessive noise on it. This is the result of two incorrect parts L1 and L3 being installed on the board. The inductors that were initially installed in the switchers are 100uH and need to be 1uH. This change will require that the board be returned for update. To check for correct parts, have a look to bottom of BeagleBoard. L1 - L3 are the larger parts there. They all have to be labeled with "102" (== 1uH). If any of these three inductors are labeled with "104" (== 100uH) they are wrong and have to be exchanged.
# ''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 will be without the EHCI USB connector mounted and in a few weeks having a different SKU for the Rev. C2 boards with the EHCI USB fixed. Won't be fixed for Rev. A and Rev. B boards. Needs different PHY. 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.2uF ceramic capacitor to D3, see [http://www.sakoman.net/omap3/beagle/vbus-mod-d3.jpg VBUS modification D3 picture]. Revision B4 boards and newer have this fix applied. Thanks to [http://groups.google.com/group/beagleboard/msg/eb789e15c99a673d Steve] for debugging this!
# ''Boards revision A and < B5'': There is some issue with 32kHz clock depending on system configuration used to clock some OMAP3 peripherals. From this e.g. GPIOs, GPTIMERs, and USB on Beagle might be affected. See [http://code.google.com/p/beagleboard/issues/detail?id=22 Issue 22]. Symptom from this is that after booting Linux kernel serial console hangs after some time and no serial input/output is possible any more. There is one software workaround and one hardware fix for this: (A) Software workaround: Don't use 32kHz timer to clock Linux, instead use MPU timer. (B) Hardware workaround: Remove [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard capacitor C70], which improves the 32kHz clock quality and avoids hang-up. Note: Revision A boards have capacitor C70 [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard at the same location] as rev. B boards. Note: Board revision >= B5 removes capacitor C70.
# ''Random boards, quite rare, revision < B6'': Some random boards and quite rare, show directly after purchasing broken serial communication from host PC to BeagleBoard. Symptom is that you get a new board, get serial output from BeagleBoard in terminal program, but can't type anything at U-Boot prompt (Note: Don't mix this with errata #7. With errata #7 you are able to use U-Boot normally, but Linux prompt input stops after some time). Most users don't have this issue, though. So, first double check your serial configuration ([[BeagleBoardFAQ#Serial_connection_.231|FAQ1]], [[BeagleBoardFAQ#Serial_connection_.232|FAQ2]] and [[BeagleBoardFAQ#Serial_connection_.233|FAQ3]]). Only if you are really, really sure that anything with your serial connection is fine, consider sending the board back doing a [http://beagleboard.org/support/rma RMA request]. This issue was resolved on revision B6 and later boards.

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 processor at BeagleBoard currently uses 500MHz
* 500MHz is the default used because it is a balance of performance and longevity
* For OMAP35x 600MHz is max recommended
* At 600MHz OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy
* Higher than 600MHz is out of spec 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 table 3-3 of the [http://focus.ti.com/lit/ds/symlink/omap3530.pdf OMAP3530 data sheet]. Some numbers:

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

* 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

See [http://git.mansr.com/?p=u-boot;a=commitdiff;h=045149ea1076575f773079677a3d1b01ff71757c Mans' hack] to configure clock in U-Boot (V1) to 600MHz.

==DLP Pico projector==

Texas Instruments is developing a Pico Video Projector Kit (PVPK) as a peripheral for the Beagle Board. The stand alone pico projector will support VGA resolution (640 x 480), RGB 888 input through a DVI interface. The physical connector on the projector will be HDMI. See [http://groups.google.com/group/beagleboard/msg/10e218972380ee48 mailing list] and [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector] for more details.

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_projector.html?CMP=OTC-0D6B48984890 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. See [[BeagleBoardRawLCD|interfacing to Raw LCD Panels]] article or [http://digitalsurveyinstruments.com/beagleperiphials/hdmi2parallel/doc/index.htm hdmi to parallel]for a workaround method.

=Availability=

BeagleBoards, currently Rev. B boards, are available from [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].

Note: For non-US 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 e.g. ordering from Europe. Users report that they had to pay EUR ~34 - 44 VAT + importing taxes (depending on european country), resulting in EUR 137 - 147 ordering from Europe.

Note: German (Europe) users can order from a German shop, too. For higher price, though. [http://shop.embedded-projects.net/product_info.php?language=en&info=p140 Embedded Projects Shop] sells BeagleBoard for EUR 199.00 + shipping.

The Rev. B boards currently orderable do not have support for the USB EHCI port (see [[BeagleBoard#Errata|hardware erratum #5]]) and are not yet fully supported by the [http://source.mvista.com/git/?p=linux-omap-2.6.git;a=summary linux-omap git] tree. These boards are being targeted only for early adopter developers. Rev. C boards (see below) will be available later under a different part number.

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) will be operational on revision C2.
* Add interface for raw LCDs ([http://groups.google.com/group/beagleboard/msg/2e82c3ed6061d9d2 mockup])
* It will use updated OMAP3 revision. BeagleBoard revisions B4+B5 uses OMAP3 ES 2.1 (engineering sample), while BeagleBoard revision C2 is supposed to use ES 3.0. OMAP3 ES 3.0 will fix 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
* Will use [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950]
* 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, e.g. for different pin mux)
* Will have 256MB ram ([http://groups.google.com/group/beagleboard/msg/3a38d0f21cefd6b1?hl=en message]) (and still 256MB NAND like rev B)
* Price will remain the same as Revision B.

Note: Revision C2 is expected end of March 2009. There are some early revision C prototypes out there, but they still have the USB host issue. There are also a few Rev C1D board that have everything listed above except for the additional pin mux option signals for the PWM.

Note: Revision ''C2'' will be for sale, it has working USB HOST (EHCI). Early non-working prototypes are called ''C''. Rev C1D is fully functional.

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

==Beagle cases==

Some nice cases for your BeagleBoard are available from [http://specialcomp.com/beagleboard/ Special Computing]. See [http://groups.google.com/group/beagleboard/browse_thread/thread/1c82316019633e51 SketchUp 3D model] if interested in 3D models from Beagle, too.

=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 Beagle Board.

==Expansion boards==
* [http://www.tincantools.com/ TinCanTools] is in the process of developing an Expansion-Prototype Board for the BeagleBoard, comments and suggestions are welcome. [[Media:bb-expansion.pdf|Schematic]].
* [http://www.hy-research.com/beagle_expansion.html HY Research] has some expansion board basics and example.
* [http://www.hervanta.com/stuff/Beaglebot#Expansion_Board Beaglebot] uses a custom extension board.
* [http://beagleboard.org/leopard Leopard Board], a Beagle buddy web camera
* There is also a VGA DB15 adapter board under development for the Rev C2 board. It should be availble through a yet to be annnounced outlet.

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

==RS232==

The pinout on the beagle board is "AT/Everex" or "IDC10". You can buy [http://www.pccables.com/07120.htm IDC10 to DB9M adapters] in many places as they are commonly used for old PCs. Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available.

==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 HS hub.

===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 +5V power jack. If you connect a USB hub, you'll probably also need external power for the USB hub as well, because according to the Hardware Reference manual the BeagleBoard OTG port only sources 100 mA. This is enough to drive a single low-power device, but probably won't work with multiple devices.

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 would let BeagleBoard unmodified.
</td><td>[[Image:usb_otg.png]]</td></tr></table>

==DVI==

DVI-D connection on BeagleBoard uses a [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 HDMI female to DVI male cable.

=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 [http://www.ti.com/litv/pdf/sprufd6a SPRUFD6].

==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 [http://focus-webapps.ti.com/general/docs/sitesearch/searchsite.tsp?selectedTopic=1653260327&numRecords=25&searchTerm=sprufd6&statusCode=null SPRUFD6] 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 the access the [[u-boot environment variables in linux|u-boot env 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 are two older (experimental) tools for UART boot:

* [http://omapzoom.org/gf/project/omaptools/wiki PC Serial Boot perl script]
* [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===

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 [[BeagleBoardRecovery#USB_recovery|USB recovery section]] 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 e.g. 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.

'''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 (e.g. in uboot 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 beagle board. E.g. (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 # mmcinit
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 'mmcinit ; fatload mmc 0:1 0x80000000 uimage ; bootm' ; saveenv

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

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://www.sakoman.net/cgi-bin/gitweb.cgi?p=x-load-omap3.git;a=summary X-Loader git repository]. Get it by

git clone git://gitorious.org/x-load-omap3/mainline.git xloader
cd xloader/

Build:

make distclean
make omap3530beagle_config
make

Result will be a ~20k sized ''x-load.bin'' in main directory.

===U-Boot===

Currently, Beagle community is working at getting U-Boot patches upstream to [http://www.denx.de/wiki/U-Boot/WebHome mainline U-Boot]. While doing this, Steve set up a [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=summary Beagle U-Boot git repository]. 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

Build (assuming Code Sourcery GCC 2007q3):

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 ~160k sized ''u-boot.bin'' in main directory.

Note: Due to (patch and binary) size, BeagleBoard splash screen was removed from upstream version. If you want it back, use [http://groups.google.com/group/beagleboard/browse_thread/thread/3ad9b803a3418624 U-Boot v1 BeagleBoard splash screen patch].

===Linux kernel===

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

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

Build:

make distclean
make omap3_beagle_defconfig
make menuconfig # only needed if you want to change the default configuration
make uImage

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

If you use the OE toolchain and want to build outside of the OE tree you should do
ARCH=arm
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 build a kernel before with oe, the program should be there

===Experimental kernel patches and hacks===

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

* [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]
* [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.
* [http://git.mansr.com/?p=linux-omap;a=summary Mans' kernel tree], a clone of main OMAP git with additional patches, mainly display & framebuffer related.
* [http://www.bat.org/~tomba/linux-omap.html Tomi's kernel tree], a clone of main OMAP git with display sub-system patches, replacing the entire display driver with one that is the likely direction moving forward.

=Compiler=

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

==Cortex A8 ARM==

[http://www.codesourcery.com/ CodeSourcery's] [http://www.codesourcery.com/gnu_toolchains/arm/download.html '''ARM GNU/Linux''' tool chain] [http://www.codesourcery.com/gnu_toolchains/arm/portal/release313 2007q3 version] is recommended. An [http://people.mozilla.com/~vladimir/misc/cs2007q3-armel.tar.gz ARM-native version of CS2007q3 has been built] as well. You can also install a native tool-chain from Angstrom.

Note: A user reports that he found the use of CodeSourcery tool chain version 2007q1-21 and 2008q1-126 as strange. He has been using [http://www.codesourcery.com/gnu_toolchains/arm/portal/release313 '''2007q3-51'''] for a couple of months now.

Note: Some users report problems using Linux installer version. If installer doesn't work for you, download tar version (section ''Advanced Packages''), copy extracted ''arm-2007q3'' directory to ''/opt/codesourcery/arm-none-linux-gnueabi/'' and add ''/opt/codesourcery/arm-none-linux-gnueabi/arm-2007q3/bin'' to your path.

* Note: CodeSourcery [http://groups.google.com/group/beagleboard/msg/63163389873902c3 2007q3] has an issue with -Os option. There is a [http://groups.google.com/group/beagleboard/msg/d4170b16029920ee fix] (needs recompilation)

* Note: CodeSourcery [http://groups.google.com/group/beagleboard/msg/63163389873902c3? 2008q1] has the following issues:
** Vectorization + NEON is broken
** building static binaries with cortex-a8 flag (or any ARMv7a core) is broken
** some armv6 compilations end in ICE.

* Note: CodeSourcery 2008q3 (now replaced by 2008q3-72) has the following issues:
** [http://hardwarebug.org/2008/10/11/codesourcery-gcc-2008q3-fail/ Broken NEON] support using ''-fmpu=neon -mfloat-abi=softfp -mcpu=cortex-a8 -O3''
** [http://www.beagleboard.org/irclogs/index.php?date=2008-10-11#T20:32:17 Miscompiles] U-Boot

* Note: CodeSourcery 2008q3-72 has the following issues:
** See [http://hardwarebug.org/2008/11/28/codesourcery-fails-again/ small problem with vectorization].

Note: If you will use only [[BeagleBoardAndOpenEmbeddedGit|OpenEmbedded (OE)]] to build code for your Beagle, you don't need to download the CodeSourcery compiler. OE builds a cross-compiler from source as part of the bitbake process.

===ARM NEON===

ARM Cortex A8 used in OMAP3 on BeagleBoard supports [http://www.arm.com/products/CPUs/NEON.html NEON] instruction set. NEON is a wide SIMD vector extension for ARM, which has been architected to be an effective compiler target so easily useable from C as well as from assembly. 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]. ARM RVDS contains a vectorizing compiler documented in ARM's [http://infocenter.arm.com/help/topic/com.arm.doc.dui0348b/DUI0348B_rvct_compiler_ref_guide.pdf RealView Compilation Tools Compiler Reference Guide]. These ARM manuals are available in Japanese, Korean, and simplified Chinese (select the lanuage in your web browser and go to [http://infocenter.arm.com/help/topic/com.arm.doc.subset.swdev.rvds/index.html RVDS Documentation]). Gcc also supports vectorizing compilation ('cc -ftree-vectorize -ftree-vectorizer-verbose=6') and the same [http://gcc.gnu.org/onlinedocs/gcc/ARM-NEON-Intrinsics.html NEON Intrinsics].

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 currently used by
* ffmpeg (libavcodec used by mplayer, omapfbplay, and many other apps)
* libpixman (used by Xorg and browsers to render text and graphics)
* Bluez (official Linux Bluetooth stack)

==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: Old c6000 Linux compiler available on [ftp://ftp.ti.com/pub/cs/linux_cgt500.tar.gz TI FTP site]. Does NOT support c64x+ core in OMAP3 devices. Not recommended.

You can also utilize the [http://focus.ti.com/dsp/docs/dspsupportaut.tsp?familyId=44&sectionId=3&tabId=416&toolTypeId=30 full-CCS free evaluation tools for 120 days], but they currently require purchase to upgrade to service release 9 to support full JTAG debugging with supported JTAG hardware.

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

=Board recovery=

If you played e.g. with the contents of the [http://www.sakoman.net/omap3/flash%20procedure.txt NAND], it might happen that the Board doesn't boot any more (without pressing user button) due to broken NAND content. See [[BeagleBoardRecovery|BeagleBoard recovery]] article how to fix this.

=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]] and [http://wiki.openembedded.net/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 info on making the SD Card.
* Put the SD Card in the Beagle, 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 Beagle 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]. Info on how RSE is used for e.g. Gumstix development is described in [http://groups.google.com/group/beagleboard/browse_thread/thread/509831f7c24cb79f# this post].

==Android==
[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://omapzoom.org/gf/project/omapandroid/wiki/ 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 Beagle Board, 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 Beagle Board.

'''Andorid on OMAP wiki'''

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

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

==Debian ARM==

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

==Handhelds Mojo ARM==

See [[BeagleBoardHandheldsMojo|Handhelds Mojo (ARM)]] (formerly known as Ubuntu (ARM)) installation guide how to install Handhelds Mojo (ARM) port of Ubuntu on BeagleBoard.

=Software hints=

This section collects hints, tips & tricks for various software components running on beagle.

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

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

==Java==

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)

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

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

Some videos:

* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle 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]

=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] (beagle board 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. 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 Beagle Board]
* [http://beagleboard.org/resources Beagleboard resources page with hw docs]
* 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]

==Contact and communication==
* [http://groups.google.com/group/beagleboard Beagle board discussion list]
* [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker]
* [http://beagleboard.blogspot.com/ Beagle board blog]
* [http://feeds.feedburner.com/BeagleBoard Beagle board RSS feed]
* Chat:
** [http://beagleboard.org/chat Beagle Board 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

==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 Beagle]
* [http://www.linuxdevices.com/news/NS8479495970.html LinuxDevices article about Digi-Key launch]
==Past Beagle 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 beagle board
* [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 Beagle. [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 beagle] 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]], unitl February 27, 2009: : Create a cool BeagleBoard application and win a Rev C2!
==Beagle wiki pages==
* [[BeagleBoardBeginners|BeagleBoard beginners guides]]
* [[BeagleBoardAndOpenEmbeddedGit|BeagleBoard and OpenEmbedded Git]] installation guide and [[BeagleBoardOpenEmbeddedDevelopment|OpenEmbedded development]]
* [[BeagleBoardDebian|Debian on BeagleBoard]] usage guide
* [[BeagleBoardHandheldsMojo|Handhelds Mojo (ARM) on BeagleBoard]] usage guide (formerly known as Ubuntu (ARM))
* [[BeagleBoardUbuntu|Ubuntu (ARM EABI) distribution at BeagleBoard]]
* [[BeagleBoardRecovery|BeagleBoard recovery]] about fixing boards not booting any more because of broken NAND content
* [[BeagleBoardJTAG|BeagleBoard JTAG]] and [[OMAP3530_ICEPICK|OMAP3530_ICEPICK]] about JTAG on BeagleBoard
* [[BeagleBoardOpenOCD|BeagleBoard OpenOCD]] has infos about status and usage of open source JTAG software OpenOCD with Beagle
* [[BeagleBoardNAND|BeagleBoard NAND boot]] about how to boot BeagleBoard from NAND flash
* [[BeagleBoardPeripherals|BeagleBoard peripherals and adapters page]] about useful BeagleBoard add ons.
* [[Mount_BeagleBoard_Root_Filesystem_over_NFS_via_USB|Mount BeagleBoard root file system over NFS via USB]]
* [[BeagleBoardFAQ|BeagleBoard FAQ]]
* [[BeagleBoardSugar|Sugar on BeagleBoard]]
* [[BeagleBoard/DSP_Howto|BeagleBoard DSP howto]]
* [[BeagleBoardRawLCD|Interfacing BeagleBoard to Raw LCD]]
* [[BeagleBoard/gst-openmax|BeagleBoard OpenMAX usage]]
* [[BeagleBoard/video|BeagleBoard video]]
* [[BeagleBoardOpenCV|Using OpenCV computer vision library with BeagleBoard]]
* [[BeagleBoard/James|James]]: Just A Miniature Entertainment System
* [[U-boot_musb_gadget_support|U-boot musb gadget support]]
* [[BeagleBoard-JP|Japanese translation of this Beagle 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]]
* [http://www.hervanta.com/stuff/Beaglebot Beaglebot]: build an experimental robotics project with Beagle
* [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

==Beagle photos==
* [http://www.flickr.com/groups/beagleboard/pool/ Beagle board pictures at flickr]
* [http://www.flickr.com/photos/32615155@N00/2439256116/ Beagle board and USRP]
* [http://www.flickr.com/photos/nishanthmenon/2438406603/ Modify SDP3430 QUART cable for beagle]
* [http://www.flickr.com/photos/koenkooi/2695061759/ MythTV on Beagle]
==Beagle videos==
* [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings]
* [http://www.youtube.com/watch?v=cXr-D1wROfQ Beagleboard in the Living Room]
* [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 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 Beagle Running Angstrom (VGA) on DLP Pico Projector]
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle 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 Beagle Board booting Android]

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

=Other OMAP boards=

* OMAP1 OMAP5912 (ARM9 + C5x DSP) based [[OSK|OSK]] board.
* OMAP3 OMAP3430 based [http://www.logicpd.com/products/devkit/ti/zoom_mobile_development_kit Zoom MDK]
* 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 based [http://www.alwaysinnovating.com/touchbook/ Touch Book]

[[Category:Development Boards]]

BeagleBoard/contest

2009-01-12T11:30:43Z

RobertK: /* Winners */ Congratulations

[[Category: Linux]]
[[Category: OMAP]]
[[Image:beagle_first_place.png|thumb|right]]
==Contest #1==
Welcome to [[BeagleBoard]] contest #1. This contest is about give-away one BeagleBoard Rev [[BeagleBoard#Revision_C|C1]] to winner and another to the runner-up. Judges will determine criteria and won't be eligible for winning the contest. Schedule:

* ''Final project updates: Friday, January 9, 2009 (afternoon).'' Contest is closed.
* Voting goes over weekend, end: Sunday, January 11, 2009 (afternoon)
* Shipping board to winner: Monday, January 12, 2009

BeagleBoard revision C1 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get it ~2 month before this revision is publically available by DigiKey (~March 2009).

==Project ideas==
Here are some ideas which projects would be nice to be done by this contest. But don't hesitate to add your cool project [[BeagleBoard/contest#Contest_projects|below]] even if it doesn't match any of these ideas:
* EHCI support
* Stable musb
** ISOCH support
** High-speed USB TV tuner support
** Hot-plug support for OTG (host and client)
* USB Digital TV tuner (either ATSC or DVB-T)
** Hauppauge HVR950 suggested as reference
* Projection TV coupled with the Pico
* Consumer IR remote control via LIRC
* Audio record
* Latest kernel version
* USB camera support
** gspca driver - need to validate with multiple cameras
** UVC driver
* USB support in u-boot
* Fixing bugs listed on code.google.com
* Android port and various applications

==Contest projects==
Please add here your project you like to participate at this contest. Please add the project to [http://beagleboard.org/project beagleboard.org projects], too. If you add a new project here, please append it at the end of list below. Then we can rely on numbering if talking about projects (e.g. "I like project 3.1").

'''Contest is closed. Please don't add new projects.'''

===qemu-omap3===

* '''Title''': support beagle board emulation in qemu
* '''beagleboard.org project''': [http://beagleboard.org/project/qemu-omap3/ qemu-omap3]
* '''Short project description''': Qemu-omap3 is an opensource project which adds omap3 related devices emulation into qemu. Beagle board is the primary devices to emulate.
* '''Homepage''': [http://code.google.com/p/qemu-omap3/ qemu omap3 emulation support]
* '''Expected results''':
** booting linux kernel and rootfs from nand and mmc image
** Wiki page how to run qemu-omap3 for beagle board
* '''Submission''':
** http://code.google.com/p/qemu-omap3/wiki/UserManual
* '''Contact''': yajin AT vm-kernel.org

===openGPS===

* '''Title''': develop open source software to use BeagleBoard as a handheld GPS receiver
* '''beagleboard.org project''': none yet
* '''Short project description''': openGPS is a project to use a basic processing platform with open source software to develop a handheld GPS receiver. Using any of a number of available map data bases, such as Open Street Maps, a handheld GPS receiver would provide new capabilities that are not currently found in commercial receivers. In addition it would provide a platform for a number of customizations and expansion of capabilites.
* '''Homepage''': none yet
* '''Expected results''':
** development of a display app with moving map capabilities
** development of a user interface for handheld apps
** integration with suitable LCD display
** interface to map files on SD card
** Wiki page on GPS receiver functions and features
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''

===Beagle Conference System===

* '''Title''': Use beagle to come up with a conferencing system for home users
* '''beagleboard.org project''': [http://beagleboard.org/project/BeagleConf/ BeagleConf]
* '''Short project description''': This is a project that aims at bringing conferencing into the drawing rooms of users' homes. The idea is to use beagle, interface it with a webcam, internet (through ethernet/ wifi), usb bluetooth (to interface a integrated keyboard/ mouse), audio in and out of beagle interfaced with a microphone and the speakers of the tv (in the living room of the user), and use a conferencing software like Ekiga (or probably Skype?). The device should be extremely affordable (low cost), to bring conferencing to homes of common users.
* '''Homepage''': none yet
* '''Expected results''':
** A 'complete' home conferencing system would include the 'unit' and a keyboard with an integrated mouse. The 'unit' shall consist of beagle, with interfaces exposed for USB webcam, audio in for microphone, audio out to connect to the TV, ethernet interface or another USB port for USB wifi and another USB port for bluetooth.
** When the system is turned on, users shall be presented with a list of contacts that they could dial (probably a customized interface of Ekiga).
** The software shall provide the users, the capability to add/ modify/ delete users and their contact details.
** The software shall also provide for ways to chat (text) with the users.
** The software shall be capable of running through a demo for the users which includes instructions for set up and usage.
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''

===BeagleRC===

* '''Title''': Use a beagle board to drive a remote controlled car.
* '''beagleboard.org project''': None
* '''Short project description''': Connect servos to the beagle board expansion header, 802.11g wireless to the use port, and use joystick on a host to remotely control the servos.
* '''Homepage''': http://chrisd.info/portfolio/indexbeaglerc.shtml
* '''Expected results''':
** Ability to control a RC car using only a beagle board and servos, this will work with both nitro and electric cars with mechanical speed controllers.
* '''Contact''': code at chrisd dot info

===Linux Hard Real-Time (PREEMPT_RT) demo===

* '''Title''': Test hard real-time (-rt) Linux kernel 2.6.28 on the Beagle, report and fix -rt related bugs, create real-time applications demo using OpenEmbedded / Ångström.
* '''beagleboard.org project''': None
* '''Short project description''': Make sure the TI OMAP device driver are -rt safe; Build a typical real-time user land set of application (Ångström based).
* '''Homepage''': http://www.axon.tv/
* '''Note''': Created a 4 months company traineeship position on Beagle Board work which has been filled by a student.
* '''Expected results''': hard sub 300 microseconds (us) scheduling latency for real-time class user space applications (targetting multimedia).
** Real-time scheduled media playback. Less or no frame skips on video. Latency reports.
* '''Contact''': likewise IRC

===USB Support in U-boot ===
* '''Title''': Add MUSB gadget support for OMAP3 to u-boot.
* Homepage: [[U-boot musb gadget support]]
* '''beagleboard.org project''': http://beagleboard.org/project/Uboot+USB+gadget/
* '''Short project description''': Currently people require an extra serial adaptor to interact with u-boot, adding USB gadget support to u-boot enables the use of serial console, saving costs and troubles to BeagleBoard users. This enables as well the future application of the DFU patches to power fast software downloads without requiring MMC (but the DFU patches are a different can of worms to be accepted on mainstream u-boot).
* '''Expected results''': U-boot patch against u-boot omap3 git tree that enables booting beagleboard and appear as an USB serial adaptor (CDC class, so it can be used in Linux/OS x without major problems), and the modified .inf file for windows.
* '''Contact''': ddompe at IRC

=== James ===

* '''Title''': James - Just A Miniature Entertainment System
* '''beagleboard.org project''': To be Added...
* '''Short project description''': James is a home server system aiming at video recording (PVR), storage and playback, but also offering other common home functions, e.g. in the areas of security and IP telephony.
* '''Homepage''': For now [[BeagleBoard/James]]. For the PVR part there is information and a demo through http://www.dse.nl/~meulenbr/pvr/pvr.html
* '''Expected results''': For the contest: the proposal on [[BeagleBoard/James]] and the demo on http://www.dse.nl/~meulenbr/pvr/pvr.html. For the future: a flexible system providing the functionality as described in the proposal.
* '''Contact''': fransmeulenbroeks on gmail

===BeagleBot===

* '''Title''': Beagle Board powered robot
* '''beagleboard.org project''': [http://beagleboard.org/project/beaglebot/ beaglebot]
* '''Short project description''': BeagleBot is a Beagle powered robot. It has few servos, ultrasonic ranger, webcam, wlan...
* '''Homepage''': [http://www.hervanta.com/stuff/Beaglebot BeagleBot homepage]
* '''Expected results''':
** Partly autonomous robot
** PC controlling of the robot
* '''Contact''': antti at hervanta.com

===Android Cupcake for BeagleBoard===

* '''Title''': Android Cupcake for BeagleBoard
* '''beagleboard.org project''': [http://beagleboard.org/project/beagledroid beagledroid]
* '''Short project description''': This is a port of the post-1.0 Cupcake version of Android to the BeagleBoard.
* '''Homepage''': For now, you can download the images from [http://www.nthcode.com/download/sd.img.gz here] and instructions from [http://www.nthcode.com/download/readme.txt here]
* '''Expected results''': Android boots, runs, can browse the Internet, etc. No sound, though.
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''

===FreeBSD port to BeagleBoard===

* '''Title''' : A port of FreeBSD-arm to the BeagleBoard
* '''beagleboard.org project''': [http://beagleboard.org/project/freebsd-bgb/ freebsd-bgb]
* '''Short project description''': This is a port of the FreeBSD operating system to the BeagleBoard, as the first platform for supporting Omap on the OS.
* '''Expected results''': FreeBSD boots and can be used through a serial console + port of a (USB?) ethernet controller driver for NFS boot.
* '''Contact''': AsqYzeron

==Judging==

===Judges===
* Jason Kridner (jkridner)
* Koen Kooi (koen)
* Dirk Behme (dirk2)
* Steve Sakoman (sakoman)
* Hunyue Yau (ds2)
* Mans Rullgard (mru)
* Robert Kuhn (robertk)

===Rules===
* Judges cannot participate in the contest.
* The ruling of the judges is final. Jason Kridner will determine when the ruling of the judges has been provided.
* Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins.
* All voting will be public and logged on this page.
* Jason Kridner will be responsible for getting the boards to the winner and runner-up. Recipients must meet US export control requirements.
* Individuals are limited to a single entry, but may include as many demonstrations as desired within that entry.

===Criteria===
* All new content must be open source as determined by the OSI.
* Submission should be in the form of an easy-to-use image/archive provided via a webpage.
** <1GB 'dd' image for an SD card is recommended. [http://www.beagleboard.org/~arago/mksdimg.txt Instructions]
** Alternatives allowed, such as [http://labs.embinux.org/android-porting-on-beagle.html Android on Beagle], as long as instructions are provided.
* "Wow" or "coolness" factor from usefulness/user experience point of view
* Overall quality of the submission
* Technical complexity
** "Coolness" of the technical solution, even if it isn't useful for all the masses
** Amount of work needed, i.e. x hours or x days?
* Angstrom recipe for image
* Documentation for the demo
* Running power consumption
* Use of DSP
* Ease of use

===Points===

Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins. Points:

{|border=1
| 2009-01-11
!Jason
!Koen
!Dirk
!Steve
!Hunyue
!Mans
!Robert
|'''Sum points'''
|-
|[[BeagleBoard/contest#qemu-omap3|qemu-omap3]]
|3
|
|3
|2
|
|3
|2
!13
|-
|[[BeagleBoard/contest#openGPS|openGPS]]
|
|
|
|
|
|
|
!
|-
|[[BeagleBoard/contest#Beagle_Conference_System|Beagle ConfSys]]
|
|
|
|
|
|
|
!
|-
|[[BeagleBoard/contest#BeagleRC|BeagleRC]]
|1
|
|
|1
|3
|
|2
!7
|-
|[[BeagleBoard/contest#Linux_Hard_Real-Time_.28PREEMPT_RT.29_demo|RT demo]]
|
|2
|2
|
|
|
|1
!5
|-
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]
|2
|3
|2
|3
|2
|3
|2
!17
|-
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]
|2
|2
|3
|4
|3
|4
|3
!21
|-
|[[BeagleBoard/contest#James|James]]
|
|3
|
|
|1
|
|
!4
|-
|[[BeagleBoard/contest#Android_Cupcake_for_BeagleBoard|Android]]
|2
|
|
|
|1
|
|
!3
|-
|[[BeagleBoard/contest#FreeBSD_port_to_BeagleBoard|FreeBSD port]]
|
|
|
|
|
|
|
!
|-
|}

===Winners===

{|border=1
!Contest
!Date
!Winner
!Runner-up
|-
|1
|Monday, January 12, 2009
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]
|-
|}
:Congratulations ;-) [[User:RobertK|RobertK]] 11:30, 12 January 2009 (UTC)

==Other background==
* IRC Log of discussion: http://www.beagleboard.org/irclogs/index.php?date=2008-12-18#T18:40:58

BeagleBoard/contest

2009-01-11T11:43:07Z

RobertK: /* Points */ m

[[Category: Linux]]
[[Category: OMAP]]
[[Image:beagle_first_place.png|thumb|right]]
==Contest #1==
Welcome to [[BeagleBoard]] contest #1. This contest is about give-away one BeagleBoard Rev [[BeagleBoard#Revision_C|C1]] to winner and another to the runner-up. Judges will determine criteria and won't be eligible for winning the contest. Schedule:

* ''Final project updates: Friday, January 9, 2009 (afternoon).'' Contest is closed.
* Voting goes over weekend, end: Sunday, January 11, 2009 (afternoon)
* Shipping board to winner: Monday, January 12, 2009

BeagleBoard revision C1 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get it ~2 month before this revision is publically available by DigiKey (~March 2009).

==Project ideas==
Here are some ideas which projects would be nice to be done by this contest. But don't hesitate to add your cool project [[BeagleBoard/contest#Contest_projects|below]] even if it doesn't match any of these ideas:
* EHCI support
* Stable musb
** ISOCH support
** High-speed USB TV tuner support
** Hot-plug support for OTG (host and client)
* USB Digital TV tuner (either ATSC or DVB-T)
** Hauppauge HVR950 suggested as reference
* Projection TV coupled with the Pico
* Consumer IR remote control via LIRC
* Audio record
* Latest kernel version
* USB camera support
** gspca driver - need to validate with multiple cameras
** UVC driver
* USB support in u-boot
* Fixing bugs listed on code.google.com
* Android port and various applications

==Contest projects==
Please add here your project you like to participate at this contest. Please add the project to [http://beagleboard.org/project beagleboard.org projects], too. If you add a new project here, please append it at the end of list below. Then we can rely on numbering if talking about projects (e.g. "I like project 3.1").

'''Contest is closed. Please don't add new projects.'''

===qemu-omap3===

* '''Title''': support beagle board emulation in qemu
* '''beagleboard.org project''': [http://beagleboard.org/project/qemu-omap3/ qemu-omap3]
* '''Short project description''': Qemu-omap3 is an opensource project which adds omap3 related devices emulation into qemu. Beagle board is the primary devices to emulate.
* '''Homepage''': [http://code.google.com/p/qemu-omap3/ qemu omap3 emulation support]
* '''Expected results''':
** booting linux kernel and rootfs from nand and mmc image
** Wiki page how to run qemu-omap3 for beagle board
* '''Submission''':
** http://code.google.com/p/qemu-omap3/wiki/UserManual
* '''Contact''': yajin AT vm-kernel.org

===openGPS===

* '''Title''': develop open source software to use BeagleBoard as a handheld GPS receiver
* '''beagleboard.org project''': none yet
* '''Short project description''': openGPS is a project to use a basic processing platform with open source software to develop a handheld GPS receiver. Using any of a number of available map data bases, such as Open Street Maps, a handheld GPS receiver would provide new capabilities that are not currently found in commercial receivers. In addition it would provide a platform for a number of customizations and expansion of capabilites.
* '''Homepage''': none yet
* '''Expected results''':
** development of a display app with moving map capabilities
** development of a user interface for handheld apps
** integration with suitable LCD display
** interface to map files on SD card
** Wiki page on GPS receiver functions and features
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''

===Beagle Conference System===

* '''Title''': Use beagle to come up with a conferencing system for home users
* '''beagleboard.org project''': [http://beagleboard.org/project/BeagleConf/ BeagleConf]
* '''Short project description''': This is a project that aims at bringing conferencing into the drawing rooms of users' homes. The idea is to use beagle, interface it with a webcam, internet (through ethernet/ wifi), usb bluetooth (to interface a integrated keyboard/ mouse), audio in and out of beagle interfaced with a microphone and the speakers of the tv (in the living room of the user), and use a conferencing software like Ekiga (or probably Skype?). The device should be extremely affordable (low cost), to bring conferencing to homes of common users.
* '''Homepage''': none yet
* '''Expected results''':
** A 'complete' home conferencing system would include the 'unit' and a keyboard with an integrated mouse. The 'unit' shall consist of beagle, with interfaces exposed for USB webcam, audio in for microphone, audio out to connect to the TV, ethernet interface or another USB port for USB wifi and another USB port for bluetooth.
** When the system is turned on, users shall be presented with a list of contacts that they could dial (probably a customized interface of Ekiga).
** The software shall provide the users, the capability to add/ modify/ delete users and their contact details.
** The software shall also provide for ways to chat (text) with the users.
** The software shall be capable of running through a demo for the users which includes instructions for set up and usage.
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''

===BeagleRC===

* '''Title''': Use a beagle board to drive a remote controlled car.
* '''beagleboard.org project''': None
* '''Short project description''': Connect servos to the beagle board expansion header, 802.11g wireless to the use port, and use joystick on a host to remotely control the servos.
* '''Homepage''': http://chrisd.info/portfolio/indexbeaglerc.shtml
* '''Expected results''':
** Ability to control a RC car using only a beagle board and servos, this will work with both nitro and electric cars with mechanical speed controllers.
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''

===Linux Hard Real-Time (PREEMPT_RT) demo===

* '''Title''': Test hard real-time (-rt) Linux kernel 2.6.28 on the Beagle, report and fix -rt related bugs, create real-time applications demo using OpenEmbedded / Ångström.
* '''beagleboard.org project''': None
* '''Short project description''': Make sure the TI OMAP device driver are -rt safe; Build a typical real-time user land set of application (Ångström based).
* '''Homepage''': http://www.axon.tv/
* '''Note''': Created a 4 months company traineeship position on Beagle Board work which has been filled by a student.
* '''Expected results''': hard sub 300 microseconds (us) scheduling latency for real-time class user space applications (targetting multimedia).
** Real-time scheduled media playback. Less or no frame skips on video. Latency reports.
* '''Contact''': likewise IRC

===USB Support in U-boot ===
* '''Title''': Add MUSB gadget support for OMAP3 to u-boot.
* Homepage: [[U-boot musb gadget support]]
* '''beagleboard.org project''': http://beagleboard.org/project/Uboot+USB+gadget/
* '''Short project description''': Currently people require an extra serial adaptor to interact with u-boot, adding USB gadget support to u-boot enables the use of serial console, saving costs and troubles to BeagleBoard users. This enables as well the future application of the DFU patches to power fast software downloads without requiring MMC (but the DFU patches are a different can of worms to be accepted on mainstream u-boot).
* '''Expected results''': U-boot patch against u-boot omap3 git tree that enables booting beagleboard and appear as an USB serial adaptor (CDC class, so it can be used in Linux/OS x without major problems), and the modified .inf file for windows.
* '''Contact''': ddompe at IRC

=== James ===

* '''Title''': James - Just A Miniature Entertainment System
* '''beagleboard.org project''': To be Added...
* '''Short project description''': James is a home server system aiming at video recording (PVR), storage and playback, but also offering other common home functions, e.g. in the areas of security and IP telephony.
* '''Homepage''': For now [[BeagleBoard/James]]. For the PVR part there is information and a demo through http://www.dse.nl/~meulenbr/pvr/pvr.html
* '''Expected results''': For the contest: the proposal on [[BeagleBoard/James]] and the demo on http://www.dse.nl/~meulenbr/pvr/pvr.html. For the future: a flexible system providing the functionality as described in the proposal.
* '''Contact''': fransmeulenbroeks on gmail

===BeagleBot===

* '''Title''': Beagle Board powered robot
* '''beagleboard.org project''': [http://beagleboard.org/project/beaglebot/ beaglebot]
* '''Short project description''': BeagleBot is a Beagle powered robot. It has few servos, ultrasonic ranger, webcam, wlan...
* '''Homepage''': [http://www.hervanta.com/stuff/Beaglebot BeagleBot homepage]
* '''Expected results''':
** Partly autonomous robot
** PC controlling of the robot
* '''Contact''': antti at hervanta.com

===Android Cupcake for BeagleBoard===

* '''Title''': Android Cupcake for BeagleBoard
* '''beagleboard.org project''': [http://beagleboard.org/project/beagledroid beagledroid]
* '''Short project description''': This is a port of the post-1.0 Cupcake version of Android to the BeagleBoard.
* '''Homepage''': For now, you can download the images from [http://www.nthcode.com/download/sd.img.gz here] and instructions from [http://www.nthcode.com/download/readme.txt here]
* '''Expected results''': Android boots, runs, can browse the Internet, etc. No sound, though.
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''

===FreeBSD port to BeagleBoard===

* '''Title''' : A port of FreeBSD-arm to the BeagleBoard
* '''beagleboard.org project''': [http://beagleboard.org/project/freebsd-bgb/ freebsd-bgb]
* '''Short project description''': This is a port of the FreeBSD operating system to the BeagleBoard, as the first platform for supporting Omap on the OS.
* '''Expected results''': FreeBSD boots and can be used through a serial console + port of a (USB?) ethernet controller driver for NFS boot.
* '''Contact''': AsqYzeron

==Judging==

===Judges===
* Jason Kridner (jkridner)
* Koen Kooi (koen)
* Dirk Behme (dirk2)
* Steve Sakoman (sakoman)
* Hunyue Yau (ds2)
* Mans Rullgard (mru)
* Robert Kuhn (robertk)

===Rules===
* Judges cannot participate in the contest.
* The ruling of the judges is final. Jason Kridner will determine when the ruling of the judges has been provided.
* Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins.
* All voting will be public and logged on this page.
* Jason Kridner will be responsible for getting the boards to the winner and runner-up. Recipients must meet US export control requirements.
* Individuals are limited to a single entry, but may include as many demonstrations as desired within that entry.

===Criteria===
* All new content must be open source as determined by the OSI.
* Submission should be in the form of an easy-to-use image/archive provided via a webpage.
** <1GB 'dd' image for an SD card is recommended. [http://www.beagleboard.org/~arago/mksdimg.txt Instructions]
** Alternatives allowed, such as [http://labs.embinux.org/android-porting-on-beagle.html Android on Beagle], as long as instructions are provided.
* "Wow" or "coolness" factor from usefulness/user experience point of view
* Overall quality of the submission
* Technical complexity
** "Coolness" of the technical solution, even if it isn't useful for all the masses
** Amount of work needed, i.e. x hours or x days?
* Angstrom recipe for image
* Documentation for the demo
* Running power consumption
* Use of DSP
* Ease of use

===Points===

Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins. Points:

{|border=1
!
!Jason
!Koen
!Dirk
!Steve
!Hunyue
!Mans
!Robert
|'''Sum points'''
|-
|[[BeagleBoard/contest#qemu-omap3|qemu-omap3]]
|
|
|3
|
|
|
|2
|
|-
|[[BeagleBoard/contest#openGPS|openGPS]]
|
|
|
|
|
|
|
|
|-
|[[BeagleBoard/contest#Beagle_Conference_System|Beagle ConfSys]]
|
|
|
|
|
|
|
|
|-
|[[BeagleBoard/contest#BeagleRC|BeagleRC]]
|
|
|
|
|3
|
|2
|
|-
|[[BeagleBoard/contest#Linux_Hard_Real-Time_.28PREEMPT_RT.29_demo|RT demo]]
|
|
|2
|
|
|
|1
|
|-
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]
|
|
|2
|
|2
|
|2
|
|-
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]
|
|
|3
|
|3
|
|3
|
|-
|[[BeagleBoard/contest#James|James]]
|
|
|
|
|1
|
|
|
|-
|[[BeagleBoard/contest#Android_Cupcake_for_BeagleBoard|Android]]
|
|
|
|
|1
|
|
|
|-
|[[BeagleBoard/contest#FreeBSD_port_to_BeagleBoard|FreeBSD port]]
|
|
|
|
|
|
|
|
|-
|}

===Winner===

tbd.

Will be known Monday, January 12, 2009.

==Other background==
* IRC Log of discussion: http://www.beagleboard.org/irclogs/index.php?date=2008-12-18#T18:40:58

BeagleBoard/contest

2009-01-11T11:42:14Z

RobertK: /* Points */ +me

[[Category: Linux]]
[[Category: OMAP]]
[[Image:beagle_first_place.png|thumb|right]]
==Contest #1==
Welcome to [[BeagleBoard]] contest #1. This contest is about give-away one BeagleBoard Rev [[BeagleBoard#Revision_C|C1]] to winner and another to the runner-up. Judges will determine criteria and won't be eligible for winning the contest. Schedule:

* ''Final project updates: Friday, January 9, 2009 (afternoon).'' Contest is closed.
* Voting goes over weekend, end: Sunday, January 11, 2009 (afternoon)
* Shipping board to winner: Monday, January 12, 2009

BeagleBoard revision C1 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get it ~2 month before this revision is publically available by DigiKey (~March 2009).

==Project ideas==
Here are some ideas which projects would be nice to be done by this contest. But don't hesitate to add your cool project [[BeagleBoard/contest#Contest_projects|below]] even if it doesn't match any of these ideas:
* EHCI support
* Stable musb
** ISOCH support
** High-speed USB TV tuner support
** Hot-plug support for OTG (host and client)
* USB Digital TV tuner (either ATSC or DVB-T)
** Hauppauge HVR950 suggested as reference
* Projection TV coupled with the Pico
* Consumer IR remote control via LIRC
* Audio record
* Latest kernel version
* USB camera support
** gspca driver - need to validate with multiple cameras
** UVC driver
* USB support in u-boot
* Fixing bugs listed on code.google.com
* Android port and various applications

==Contest projects==
Please add here your project you like to participate at this contest. Please add the project to [http://beagleboard.org/project beagleboard.org projects], too. If you add a new project here, please append it at the end of list below. Then we can rely on numbering if talking about projects (e.g. "I like project 3.1").

'''Contest is closed. Please don't add new projects.'''

===qemu-omap3===

* '''Title''': support beagle board emulation in qemu
* '''beagleboard.org project''': [http://beagleboard.org/project/qemu-omap3/ qemu-omap3]
* '''Short project description''': Qemu-omap3 is an opensource project which adds omap3 related devices emulation into qemu. Beagle board is the primary devices to emulate.
* '''Homepage''': [http://code.google.com/p/qemu-omap3/ qemu omap3 emulation support]
* '''Expected results''':
** booting linux kernel and rootfs from nand and mmc image
** Wiki page how to run qemu-omap3 for beagle board
* '''Submission''':
** http://code.google.com/p/qemu-omap3/wiki/UserManual
* '''Contact''': yajin AT vm-kernel.org

===openGPS===

* '''Title''': develop open source software to use BeagleBoard as a handheld GPS receiver
* '''beagleboard.org project''': none yet
* '''Short project description''': openGPS is a project to use a basic processing platform with open source software to develop a handheld GPS receiver. Using any of a number of available map data bases, such as Open Street Maps, a handheld GPS receiver would provide new capabilities that are not currently found in commercial receivers. In addition it would provide a platform for a number of customizations and expansion of capabilites.
* '''Homepage''': none yet
* '''Expected results''':
** development of a display app with moving map capabilities
** development of a user interface for handheld apps
** integration with suitable LCD display
** interface to map files on SD card
** Wiki page on GPS receiver functions and features
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''

===Beagle Conference System===

* '''Title''': Use beagle to come up with a conferencing system for home users
* '''beagleboard.org project''': [http://beagleboard.org/project/BeagleConf/ BeagleConf]
* '''Short project description''': This is a project that aims at bringing conferencing into the drawing rooms of users' homes. The idea is to use beagle, interface it with a webcam, internet (through ethernet/ wifi), usb bluetooth (to interface a integrated keyboard/ mouse), audio in and out of beagle interfaced with a microphone and the speakers of the tv (in the living room of the user), and use a conferencing software like Ekiga (or probably Skype?). The device should be extremely affordable (low cost), to bring conferencing to homes of common users.
* '''Homepage''': none yet
* '''Expected results''':
** A 'complete' home conferencing system would include the 'unit' and a keyboard with an integrated mouse. The 'unit' shall consist of beagle, with interfaces exposed for USB webcam, audio in for microphone, audio out to connect to the TV, ethernet interface or another USB port for USB wifi and another USB port for bluetooth.
** When the system is turned on, users shall be presented with a list of contacts that they could dial (probably a customized interface of Ekiga).
** The software shall provide the users, the capability to add/ modify/ delete users and their contact details.
** The software shall also provide for ways to chat (text) with the users.
** The software shall be capable of running through a demo for the users which includes instructions for set up and usage.
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''

===BeagleRC===

* '''Title''': Use a beagle board to drive a remote controlled car.
* '''beagleboard.org project''': None
* '''Short project description''': Connect servos to the beagle board expansion header, 802.11g wireless to the use port, and use joystick on a host to remotely control the servos.
* '''Homepage''': http://chrisd.info/portfolio/indexbeaglerc.shtml
* '''Expected results''':
** Ability to control a RC car using only a beagle board and servos, this will work with both nitro and electric cars with mechanical speed controllers.
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''

===Linux Hard Real-Time (PREEMPT_RT) demo===

* '''Title''': Test hard real-time (-rt) Linux kernel 2.6.28 on the Beagle, report and fix -rt related bugs, create real-time applications demo using OpenEmbedded / Ångström.
* '''beagleboard.org project''': None
* '''Short project description''': Make sure the TI OMAP device driver are -rt safe; Build a typical real-time user land set of application (Ångström based).
* '''Homepage''': http://www.axon.tv/
* '''Note''': Created a 4 months company traineeship position on Beagle Board work which has been filled by a student.
* '''Expected results''': hard sub 300 microseconds (us) scheduling latency for real-time class user space applications (targetting multimedia).
** Real-time scheduled media playback. Less or no frame skips on video. Latency reports.
* '''Contact''': likewise IRC

===USB Support in U-boot ===
* '''Title''': Add MUSB gadget support for OMAP3 to u-boot.
* Homepage: [[U-boot musb gadget support]]
* '''beagleboard.org project''': http://beagleboard.org/project/Uboot+USB+gadget/
* '''Short project description''': Currently people require an extra serial adaptor to interact with u-boot, adding USB gadget support to u-boot enables the use of serial console, saving costs and troubles to BeagleBoard users. This enables as well the future application of the DFU patches to power fast software downloads without requiring MMC (but the DFU patches are a different can of worms to be accepted on mainstream u-boot).
* '''Expected results''': U-boot patch against u-boot omap3 git tree that enables booting beagleboard and appear as an USB serial adaptor (CDC class, so it can be used in Linux/OS x without major problems), and the modified .inf file for windows.
* '''Contact''': ddompe at IRC

=== James ===

* '''Title''': James - Just A Miniature Entertainment System
* '''beagleboard.org project''': To be Added...
* '''Short project description''': James is a home server system aiming at video recording (PVR), storage and playback, but also offering other common home functions, e.g. in the areas of security and IP telephony.
* '''Homepage''': For now [[BeagleBoard/James]]. For the PVR part there is information and a demo through http://www.dse.nl/~meulenbr/pvr/pvr.html
* '''Expected results''': For the contest: the proposal on [[BeagleBoard/James]] and the demo on http://www.dse.nl/~meulenbr/pvr/pvr.html. For the future: a flexible system providing the functionality as described in the proposal.
* '''Contact''': fransmeulenbroeks on gmail

===BeagleBot===

* '''Title''': Beagle Board powered robot
* '''beagleboard.org project''': [http://beagleboard.org/project/beaglebot/ beaglebot]
* '''Short project description''': BeagleBot is a Beagle powered robot. It has few servos, ultrasonic ranger, webcam, wlan...
* '''Homepage''': [http://www.hervanta.com/stuff/Beaglebot BeagleBot homepage]
* '''Expected results''':
** Partly autonomous robot
** PC controlling of the robot
* '''Contact''': antti at hervanta.com

===Android Cupcake for BeagleBoard===

* '''Title''': Android Cupcake for BeagleBoard
* '''beagleboard.org project''': [http://beagleboard.org/project/beagledroid beagledroid]
* '''Short project description''': This is a port of the post-1.0 Cupcake version of Android to the BeagleBoard.
* '''Homepage''': For now, you can download the images from [http://www.nthcode.com/download/sd.img.gz here] and instructions from [http://www.nthcode.com/download/readme.txt here]
* '''Expected results''': Android boots, runs, can browse the Internet, etc. No sound, though.
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''

===FreeBSD port to BeagleBoard===

* '''Title''' : A port of FreeBSD-arm to the BeagleBoard
* '''beagleboard.org project''': [http://beagleboard.org/project/freebsd-bgb/ freebsd-bgb]
* '''Short project description''': This is a port of the FreeBSD operating system to the BeagleBoard, as the first platform for supporting Omap on the OS.
* '''Expected results''': FreeBSD boots and can be used through a serial console + port of a (USB?) ethernet controller driver for NFS boot.
* '''Contact''': AsqYzeron

==Judging==

===Judges===
* Jason Kridner (jkridner)
* Koen Kooi (koen)
* Dirk Behme (dirk2)
* Steve Sakoman (sakoman)
* Hunyue Yau (ds2)
* Mans Rullgard (mru)
* Robert Kuhn (robertk)

===Rules===
* Judges cannot participate in the contest.
* The ruling of the judges is final. Jason Kridner will determine when the ruling of the judges has been provided.
* Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins.
* All voting will be public and logged on this page.
* Jason Kridner will be responsible for getting the boards to the winner and runner-up. Recipients must meet US export control requirements.
* Individuals are limited to a single entry, but may include as many demonstrations as desired within that entry.

===Criteria===
* All new content must be open source as determined by the OSI.
* Submission should be in the form of an easy-to-use image/archive provided via a webpage.
** <1GB 'dd' image for an SD card is recommended. [http://www.beagleboard.org/~arago/mksdimg.txt Instructions]
** Alternatives allowed, such as [http://labs.embinux.org/android-porting-on-beagle.html Android on Beagle], as long as instructions are provided.
* "Wow" or "coolness" factor from usefulness/user experience point of view
* Overall quality of the submission
* Technical complexity
** "Coolness" of the technical solution, even if it isn't useful for all the masses
** Amount of work needed, i.e. x hours or x days?
* Angstrom recipe for image
* Documentation for the demo
* Running power consumption
* Use of DSP
* Ease of use

===Points===

Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins. Points:

{|border=1
!
!Jason
!Koen
!Dirk
!Steve
!Hunyue
!Mans
!Robert
|'''Sum points'''
|-
|[[BeagleBoard/contest#qemu-omap3|qemu-omap3]]
|
|
|3
|
|
|
|
|2
|-
|[[BeagleBoard/contest#openGPS|openGPS]]
|
|
|
|
|
|
|
|
|-
|[[BeagleBoard/contest#Beagle_Conference_System|Beagle ConfSys]]
|
|
|
|
|
|
|
|
|-
|[[BeagleBoard/contest#BeagleRC|BeagleRC]]
|
|
|
|
|3
|
|
|2
|-
|[[BeagleBoard/contest#Linux_Hard_Real-Time_.28PREEMPT_RT.29_demo|RT demo]]
|
|
|2
|
|
|
|
|1
|-
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]
|
|
|2
|
|2
|
|
|2
|-
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]
|
|
|3
|
|3
|
|
|3
|-
|[[BeagleBoard/contest#James|James]]
|
|
|
|
|1
|
|
|
|-
|[[BeagleBoard/contest#Android_Cupcake_for_BeagleBoard|Android]]
|
|
|
|
|1
|
|
|
|-
|[[BeagleBoard/contest#FreeBSD_port_to_BeagleBoard|FreeBSD port]]
|
|
|
|
|
|
|
|
|-
|}

===Winner===

tbd.

Will be known Monday, January 12, 2009.

==Other background==
* IRC Log of discussion: http://www.beagleboard.org/irclogs/index.php?date=2008-12-18#T18:40:58

Talk:U-boot environment variables in linux

2008-10-27T12:46:06Z

RobertK:

This article is based on a mail from Frank Agius in the Beagleboard Mailinglist. See [http://groups.google.com/group/beagleboard/browse_thread/thread/a3624b178c985399# here] [[User:RobertK|RobertK]] 12:46, 27 October 2008 (UTC)

U-boot environment variables in linux

2008-10-27T12:14:38Z

RobertK: +cats

[[Category: Linux]]
[[Category: OMAP]]
U-boot makes use of environment variable which can be read and set from the u-boot command line with printenv and setenv. It can be helpful to read and set these variables from linux as well. The u-boot distribution has sources for these commands, named fw_printenv and fw_setenv, but the Angstrom OE distribution does not build the tools automatically. I'm a novice at OE and bitbake, so here are the instructions for building and installing the tools manually. Theses instructions assume that you have already buillt the angstrom distribution for the beagle board. Substitute directories and compiler locations to match your environment.

#cd to the source for u-boot in the OE tree. For me, it is at "../oe/tmp/work/beagleboard-angstrom-linux-gnueabi/u-boot-git-r18.1/git"
#manually build fw_printenv with make: "make env ARCH=arm CROSS_COMPILE= /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnuabi-"
#if the compile succeeded, you should have fw_printenv in the u-boot directory tools/env. Copy fw_printenv to /sbin on the root filesystem of your beagle board.
#the fw_printenv binary also contains the code for fw_setenv. the functions of fw_setenv are run when the program is invoked with the name "fw_setenv". this is most easily accomplished by creating a symbolic link from fw_printenv to fw_setenv, as in "ln -sf /sbin/fw_printenv /sbin/fw_setenv"
#the last and most important step is creating the config file for the utilities. the file name is fw_env.config and it lives in /etc.
to create this file, you need to know information about where u-boot stores its env variables. Specifically, you need the mtd device name, the device offset, the env size and the flash sector size. I found most of what I needed by looking in the file /proc/mtd. here is my fw_env.config file:

# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundand
# environment sector is assumed present.
# MTD device name Device offset Env. size Flash sector size
/dev/mtd2 0x0000 0x20000 0x20000

== Usage ==
=== Printing all the environment variables===

# fw_printenv
bootdelay=1
baudrate=115200
ipaddr=192.168.0.2
serverip=192.168.0.1
netmask=255.255.255.0
bootfile="uImage"
filesize=B81A24
bootcmd=nand read 80200000 280000 400000;bootm 80200000
bootargs=console=ttyS2,115200n8 console=tty0 root=/dev/mtdblock4 rw rootfstyp=jffs2 nohz=off
stdin=serial
stdout=serial
stderr=serial

=== Printing a single environment variable ===
# fw_printenv stdin
stdin=serial

=== Setting and verifying an environment variable ===
WARNING! If the fw_env.config does not point to u-boots env section in flash, running fw_setenv could corrupt your flash. Make sure that fw_printenv works properly and does not return a message about "bad CRC" before running fw_setenv.

# fw_setenv mytestvariable abcdefg
# fw_printenv mytestvariable
mytestenv=abcdefg

Care must be taken when changing env variables as a typo could easily render your boot unbootable. Most problems can be fixed by connecting to the serial console and using u-boots command line to fix bad variable.

U-boot environment variables in linux

2008-10-27T12:13:04Z

RobertK:

U-boot makes use of environment variable which can be read and set from the u-boot command line with printenv and setenv. It can be helpful to read and set these variables from linux as well. The u-boot distribution has sources for these commands, named fw_printenv and fw_setenv, but the Angstrom OE distribution does not build the tools automatically. I'm a novice at OE and bitbake, so here are the instructions for building and installing the tools manually. Theses instructions assume that you have already buillt the angstrom distribution for the beagle board. Substitute directories and compiler locations to match your environment.

#cd to the source for u-boot in the OE tree. For me, it is at "../oe/tmp/work/beagleboard-angstrom-linux-gnueabi/u-boot-git-r18.1/git"
#manually build fw_printenv with make: "make env ARCH=arm CROSS_COMPILE= /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnuabi-"
#if the compile succeeded, you should have fw_printenv in the u-boot directory tools/env. Copy fw_printenv to /sbin on the root filesystem of your beagle board.
#the fw_printenv binary also contains the code for fw_setenv. the functions of fw_setenv are run when the program is invoked with the name "fw_setenv". this is most easily accomplished by creating a symbolic link from fw_printenv to fw_setenv, as in "ln -sf /sbin/fw_printenv /sbin/fw_setenv"
#the last and most important step is creating the config file for the utilities. the file name is fw_env.config and it lives in /etc.
to create this file, you need to know information about where u-boot stores its env variables. Specifically, you need the mtd device name, the device offset, the env size and the flash sector size. I found most of what I needed by looking in the file /proc/mtd. here is my fw_env.config file:

# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundand
# environment sector is assumed present.
# MTD device name Device offset Env. size Flash sector size
/dev/mtd2 0x0000 0x20000 0x20000

== Usage ==
=== Printing all the environment variables===

# fw_printenv
bootdelay=1
baudrate=115200
ipaddr=192.168.0.2
serverip=192.168.0.1
netmask=255.255.255.0
bootfile="uImage"
filesize=B81A24
bootcmd=nand read 80200000 280000 400000;bootm 80200000
bootargs=console=ttyS2,115200n8 console=tty0 root=/dev/mtdblock4 rw rootfstyp=jffs2 nohz=off
stdin=serial
stdout=serial
stderr=serial

=== Printing a single environment variable ===
# fw_printenv stdin
stdin=serial

=== Setting and verifying an environment variable ===
WARNING! If the fw_env.config does not point to u-boots env section in flash, running fw_setenv could corrupt your flash. Make sure that fw_printenv works properly and does not return a message about "bad CRC" before running fw_setenv.

# fw_setenv mytestvariable abcdefg
# fw_printenv mytestvariable
mytestenv=abcdefg

Care must be taken when changing env variables as a typo could easily render your boot unbootable. Most problems can be fixed by connecting to the serial console and using u-boots command line to fix bad variable.

BeagleBoard

2008-10-27T12:10:16Z

RobertK: /* BootRom */ +u-boot environment variables in linux

[[Category: Linux]]
[[Category: OMAP]]
This page collects information about [http://www.ti.com/ TI's] [http://www.arm.com/ ARM] based [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] [http://beagleboard.org Beagle Board].

=Events=
* '''October 26 - October 30, 2008''', Hynes Convention Center, Boston: [http://www.cmp-egevents.com/web/escb Embedded Systems Conference Boston 2008] is hosting a [http://www.cmp-egevents.com/web/escb/beagleboard BeagleBoard Build Your Own Embedded System Track]: [http://jkridner.s3.amazonaws.com/esc/BeagleBoard101_20081025.ppt preview slides]

=Hardware=

The Beagle Board is ''a low-cost, fan-less single-board computer based on TIs 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 Core ~600MHz + TMS320C64x+ DSP ~430MHz + 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|Target price is US-$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 it's capabilities.

==Components==

'''Top view:'''

[[Image:Beagle_top_notes.jpg]]
{|border=1
!No.
!Name
!Comment
|-
|'''1'''
|[http://www.ti.com/omap35x OMAP3530] processor + 128MB DDR + 256MB NAND
|PoP: Package-On-Package implementation for Memory Stacking
|-
|'''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]]
|
|-
|'''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]]
|Currently not working in rev A or B boards; Rev C planned.
|-
|'''9'''
|SD/MMC+
|
|-
|'''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
|
|-
|}

* Board size: 3" x 3"
* Currently 6 layer PCB; target: 4 layer

'''Bottom:'''

[[Image:Beagle_bottom.jpg]]

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

==Manual==

See [http://www.beagleboard.org/uploads/BBSRM_B5.pdf BeagleBoard HW Reference Manual (rev. B5)].

ERRATA

There is an error in the Rev B4 and Rev B5 manuals on tables 17 and 21. The B and C columns are swapped between pins 6 and 10 of the expansion connector. Columm A is correct. You can also refer to the schematic for the correct signals of the alternate functions on these pins.

==Schematic==

Schematic of BeagleBoard Rev. B is available as part of [http://www.beagleboard.org/uploads/BBSRM_B5.pdf BeagleBoard HW Reference Manual (rev. B5)], from [http://beagleboard.org/hardware/design BeagleBoard.org design page] or in [http://xgoat.com/proj/beagleboard/schematic.pdf 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. B is available as part of [http://www.beagleboard.org/uploads/BBSRM_B5.pdf BeagleBoard HW Reference Manual (rev. B5)] or from [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_B5.pdf Beagle HW manual]). But on revision Ax boards the PCB layout has GND on center and DC_5V on sleeve. For this reason it is currently removed. It will be back on the Rev B board. Workaround is to remove wire connecting the two power pins on revision Ax boards and use external [http://amethyst.openembedded.net/~koen/beagleboard/beagle-power-pads.jpg power supply with switched connector] (do not connect anything to the “?” terminal. USB power will be permanently disabled and the board can only be powered from the 5V.) See [http://www.flickr.com/photos/koenkooi/2512038988/ Koen's Beagleboard powermod picture] with short descriptions, too.
# ''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.8V has excessive noise on it. This is the result of two incorrect parts L1 and L3 being installed on the board. The inductors that were initially installed in the switchers are 100uH and need to be 1uH. This change will require that the board be returned for update. To check for correct parts, have a look to bottom of BeagleBoard. L1 - L3 are the larger parts there. They all have to be labeled with "102" (== 1uH). If any of these three inductors are labeled with "104" (== 100uH) they are wrong and have to be exchanged.
# ''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 will be without the EHCI USB connector mounted and in a few weeks having a different SKU for the Rev. C boards with the EHCI USB fixed. Won't be fixed for Rev. A and Rev. B boards. Needs different PHY. 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.2uF ceramic capacitor to D3, see [http://www.sakoman.net/omap3/beagle/vbus-mod-d3.jpg VBUS modification D3 picture]. Revision B4 boards and newer have this fix applied. Thanks to [http://groups.google.com/group/beagleboard/msg/eb789e15c99a673d Steve] for debugging this!
# ''Boards revision A and < B5'': There is some issue with 32kHz clock depending on system configuration used to clock some OMAP3 peripherals. From this e.g. GPIOs, GPTIMERs, and USB on Beagle might be affected. See [http://code.google.com/p/beagleboard/issues/detail?id=22 Issue 22]. Symptom from this is that after booting Linux kernel serial console hangs after some time and no serial input/output is possible any more. There is one software workaround and one hardware fix for this: (A) Software workaround: Don't use 32kHz timer to clock Linux, instead use MPU timer. (B) Hardware workaround: Remove [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard capacitor C70], which improves the 32kHz clock quality and avoids hang-up. Note: Revision A boards have capacitor C70 [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard at the same location] as rev. B boards. Note: Board revision >= B5 removes capacitor C70.
# ''Random boards, quite rare'': Some random boards, quite rare, show directly after purchasing broken serial communication from host PC to BeagleBoard. Symptom is that you get a new board, get serial output from BeagleBoard in terminal program, but can't type anything at U-Boot prompt (Note: Don't mix this with errata #7. With errata #7 you are able to use U-Boot normally, but Linux prompt input stops after some time). Most users don't have this issue, though. So, first double check your serial configuration ([[BeagleBoardFAQ#Serial_connection_.231|FAQ1]], [[BeagleBoardFAQ#Serial_connection_.232|FAQ2]] and [[BeagleBoardFAQ#Serial_connection_.233|FAQ3]]). Only if you are really, really sure that anything with your serial connection is fine, consider sending the board back doing a [http://beagleboard.org/support/rma RMA request].

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

==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 processor at BeagleBoard currently uses 500MHz
* 500MHz is the default used because it is a balance of performance and longevity
* For OMAP35x 600MHz is max recommended
* At 600MHz OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy
* Higher than 600MHz is out of spec 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 table 3-3 of the [http://focus.ti.com/lit/ds/symlink/omap3530.pdf OMAP3530 data sheet]. Some numbers:

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

* There is a thermal monitor in the core, you could use to scale frequency up and down

See [http://git.mansr.com/?p=u-boot;a=commitdiff;h=caccdb772c3028a3e3e801fb1554788150752ffc Mans' hack] to configure clock in U-Boot (V1) to 600MHz.

==DLP Pico projector==

Texas Instruments is developing a Pico Video Projector Kit (PVPK) as a peripheral for the Beagle Board. The stand alone pico projector will support VGA resolution (640 x 480), RGB 888 input through a DVI interface. The physical connector on the projector will be HDMI. See [http://groups.google.com/group/beagleboard/msg/10e218972380ee48 mailing list] and [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector] for more details.

It will be available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23836-ND DigiKey] starting at ~January 2009 for expected price $349.

==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. There are plans to implement access to these lines in Rev C.
See [[BeagleBoardRawLCD|interfacing to Raw LCD Panels]] article for a workaround method.

=Availability=

BeagleBoards, currently Rev. B boards, are available from [http://mkt.digikey.com/ga/pages/beagleboard.html Digi-Key] with part number [http://dkc1.digikey.com/us/en/tod/Texas_Instruments/BeagleBoard.html 296-23428-ND].

Note: For non-US free shipping orders:

* Click the US flag on the top right corner of [http://mkt.digikey.com/ga/pages/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 this results in EUR 103,26 / GBP 81.95 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 e.g. ordering from Europe. Users report that they had to pay EUR ~34 - 44 VAT + importing taxes (depending on european country), resulting in EUR 137 - 147 ordering from europe.

The Rev. B boards currently oderable do not have support for the USB EHCI port (see [[BeagleBoard#Errata|hardware errata #5]]) and are not yet fully supported by the [http://source.mvista.com/git/?p=linux-omap-2.6.git;a=summary linux-omap git] tree. These boards are being targeted only for early adopter developers. Rev. C boards (see below) will be available later under a different part number.

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
Still has USB HOST (EHCI) failures. USB HOST (EHCI) connector isn't mounted.

==Revision C==
Revision C is same as revision B except:
* USB HOST (EHCI) will be operational on revision C.
* It will use updated OMAP3 revision. BeagleBoard revision B uses OMAP3 ES 2.1 (engineering sample), while BeagleBoard revision C is supposed to use ES 3.0. It is said that OMAP3 ES 3.0 will
** contain updated ARM Cortex A8 silicon (r1p3) fixing [http://elinux.org/BeagleBoardFAQ#NEON_performance NEON performance issue]
** have some fixes that improve [http://www.beagleboard.org/irclogs/index.php?date=2008-09-29#T08:45:45 perfomance]
** have [http://www.beagleboard.org/irclogs/index.php?date=2008-10-01#T19:10:58 256MB] instead of 128MB SDRAM
** add interface for raw LCDs ([http://groups.google.com/group/beagleboard/msg/2e82c3ed6061d9d2 mockup])

Note: Revision C is expected earliest at late December 2008 or early January 2009. There are some early revision C prototypes out there, but they still seem to have USB host issue.

==Beagle cases==

Some nice cases for your BeagleBoard are available from [http://specialcomp.com/beagleboard/ Special Computing]. See [http://groups.google.com/group/beagleboard/browse_thread/thread/1c82316019633e51 SketchUp 3D model] if interested in 3D models from Beagle, too.

=Adapters=

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

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

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

==RS232==

The pinout on the beagle board is "AT/Everex" or "IDC10". You can buy [http://www.pccables.com/07120.htm IDC10 to DB9M adapters] in many places as they are commonly used for old PCs. Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available.

==USB==
There are two USB ports on the BeagleBoard, one with an EHCI controller and another with an OTG controller.

===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 HS hub.

===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 +5V power jack. If you connect a USB hub, you'll probably also need external power for the USB hub as well, because according to the Hardware Reference manual the BeagleBoard OTG port only sources 100 mA. This is enough to drive a single low-power device, but probably won't work with multiple devices.

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

==DVI==

DVI-D connection on BeagleBoard uses a [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 HDMI female to DVI male cable.

=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 [http://www.ti.com/litv/pdf/sprufd6 SPRUFD6].

==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 [http://www.ti.com/litv/pdf/sprufd6 SPRUFD6] 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 the access the [[u-boot environment variables in linux|u-boot env 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 are two older (experimental) tools for UART boot:

* [http://omapzoom.org/gf/project/omaptools/wiki PC Serial Boot perl script]
* [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===

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 [[BeagleBoardRecovery#USB_recovery|USB recovery section]] 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 e.g. 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.

'''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 (e.g. in uboot 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 beagle board. E.g. (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 # mmcinit
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 'mmcinit ; fatload mmc 0:1 0x80000000 uimage ; bootm' ; saveenv

=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-2008.1-test-20080823-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==

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://www.sakoman.net/cgi-bin/gitweb.cgi?p=x-load-omap3.git;a=summary X-Loader git repository]. Get it by

git clone git://gitorious.org/x-load-omap3/mainline.git xloader
cd xloader/

Build:

make distclean
make omap3530beagle_config
make

Result will be a ~20k sized ''x-load.bin'' in main directory.

===U-Boot===

Currently, Beagle community is working at getting U-Boot patches upstream to mainline U-Boot. While doing this, Steve set up a [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=shortlog;h=refs/heads/test Beagle U-Boot git repository]. Get it by:

git clone git://gitorious.org/u-boot-omap3/mainline.git u-boot_beagle
cd u-boot_beagle/
git checkout origin/master

Build:

make distclean
make omap3_beagle_config
make

Result will be a ~150k sized ''u-boot.bin'' in main directory.

===Linux kernel===

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

git clone git://source.mvista.com/git/linux-omap-2.6.git

Build:

make distclean
make omap3_beagle_defconfig
make uImage

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

===Experimental kernel patches and hacks===

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

* [http://gitweb.openembedded.net/?p=org.openembedded.dev.git;a=tree;f=packages/linux/linux-omap2-git/beagleboard;h=277d7b6a2a660c5119e3b885a8808f4f9cffc3e1;hb=ab680455026278a5ac117232df0b6e4afe544132 Koen's collection of kernels patches for OE] and the [http://gitweb.openembedded.net/?p=org.openembedded.dev.git;a=blob;f=packages/linux/linux-omap2_git.bb;h=8392ff7308a760dd98227cbbf499545632d8fcb5;hb=ab680455026278a5ac117232df0b6e4afe544132 list of relevant patches]
* [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.
* [http://git.mansr.com/?p=linux-omap;a=summary Mans' kernel tree], a clone of main OMAP git with additional patches, mainly display & framebuffer related.

=Compiler=

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

==Cortex A8 ARM==

[http://www.codesourcery.com/ CodeSourcery's] [http://www.codesourcery.com/gnu_toolchains/arm/download.html '''ARM GNU/Linux''' tool chain] [http://www.codesourcery.com/gnu_toolchains/arm/portal/release313 2007q3 version] is recommended.

Note: A user reports that he found the use of CodeSourcery tool chain version 2007q1-21 and 2008q1-126 as strange. He has been using [http://www.codesourcery.com/gnu_toolchains/arm/portal/release313 '''2007q3-51'''] for a couple of months now.

Note: Some users report problems using Linux installer version. If installer doesn't work for you, download tar version (section ''Advanced Packages''), copy extracted ''arm-2007q3'' directory to ''/opt/codesourcery/arm-none-linux-gnueabi/'' and add ''/opt/codesourcery/arm-none-linux-gnueabi/arm-2007q3/bin'' to your path.

Note: CodeSourcery [http://groups.google.com/group/beagleboard/msg/63163389873902c3? 2008q1] has the following issues:

* Vectorization + NEON is broken
* building static binaries with cortex-a8 flag (or any ARMv7a core) is broken
* some armv6 compilations end in ICE.

Note: CodeSourcery 2008q3 has the following issues:

* [http://hardwarebug.org/2008/10/11/codesourcery-gcc-2008q3-fail/ Broken NEON] support using ''-fmpu=neon -mfloat-abi=softfp -mcpu=cortex-a8 -O3''
* [http://www.beagleboard.org/irclogs/index.php?date=2008-10-11#T20:32:17 Miscompiles] U-Boot

Note: CodeSourcery [http://groups.google.com/group/beagleboard/msg/63163389873902c3 2007q3] has an issue with -Os option. There is a [http://groups.google.com/group/beagleboard/msg/d4170b16029920ee fix] (needs recompilation)

Note: If you will use only [[BeagleBoardAndOpenEmbeddedGit|OpenEmbedded (OE)]] to build code for your Beagle, you don't need to extra download CodeSourcery compiler. OE will build 2007q3 from source while installing.

===ARM NEON===

ARM Cortex A8 used in OMAP3 on BeagleBoard supports [http://www.arm.com/products/CPUs/NEON.html NEON] instruction set. Some information about this can be found in [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0204h/Bcfjicfj.html ARM's RealView Compilation Tools Assembler Guide] and from [http://gcc.gnu.org/onlinedocs/gcc/ARM-NEON-Intrinsics.html GCC's ARM NEON Intrinsics].

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

==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: Old c6000 Linux compiler available on [ftp://ftp.ti.com/pub/cs/linux_cgt500.tar.gz TI FTP site]. Does NOT support c64x+ core in OMAP3 devices. Not recommended.

You can also utilize the [http://focus.ti.com/dsp/docs/dspsupportaut.tsp?familyId=44&sectionId=3&tabId=416&toolTypeId=30 full-CCS free evaluation tools for 120 days], but they currently require purchase to upgrade to service release 9 to support full JTAG debugging with supported JTAG hardware.

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

=Board recovery=

If you played e.g. with the contents of the [http://www.sakoman.net/omap3/flash%20procedure.txt NAND], it might happen that the Board doesn't boot any more (without pressing user button) due to broken NAND content. See [[BeagleBoardRecovery|BeagleBoard recovery]] article how to fix this.

=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]] and [http://wiki.openembedded.net/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 X server resulting in something like [http://scap.linuxtogo.org/files/fc987d4acb2c745fb7e19cf4dca8de70.png this].

===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 B5 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 info on making the SD Card.
* Put the SD Card in the Beagle, 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 Beagle 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]. Info on how RSE is used for e.g. Gumstix development is described in [http://groups.google.com/group/beagleboard/browse_thread/thread/509831f7c24cb79f# this post].

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

==Debian ARM==

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

==Handelds Mojo ARM==

See [[BeagleBoardHandheldsMojo|Handhelds Mojo (ARM)]] (formerly known as Ubuntu (ARM)) installation guide how to install Handhelds Mojo (ARM) port of Ubuntu on BeagleBoard.

=Software hints=

This section collects hints, tips & tricks for various software components running on beagle.

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

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

==Java==

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.

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

Some videos:

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

=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] (beagle board home)
* Using [http://www.google.de/ Google] you can search beagleboard.org (including IRC logs) using ''site:beagleboard.org <search term>''
==Manuals and resources==
* [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]
==Contact and communication==
* [http://groups.google.com/group/beagleboard Beagle board discussion list]
* [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker]
* [http://beagleboard.blogspot.com/ Beagle board blog]
* [http://feeds.feedburner.com/BeagleBoard Beagle board RSS feed]
* Chat:
** [http://beagleboard.org/chat Beagle Board chat on Pibb.com]
** 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
==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 Beagle]
* [http://www.linuxdevices.com/news/NS8479495970.html LinuxDevices article about Digi-Key launch]
==Past Beagle 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 beagle board
* [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 Beagle. [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 beagle] 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
==Beagle wiki pages==
* [[BeagleBoardBeginners|BeagleBoard beginners guides]]
* [[BeagleBoardAndOpenEmbeddedGit|BeagleBoard and OpenEmbedded Git]] installation guide
* [[BeagleBoardDebian|Debian on BeagleBoard]] usage guide
* [[BeagleBoardHandheldsMojo|Handhelds Mojo (ARM) on BeagleBoard]] usage guide (formerly known as Ubuntu (ARM))
* [[BeagleBoardRecovery|BeagleBoard recovery]] about fixing boards not booting any more because of broken NAND content
* [[BeagleBoardJTAG|BeagleBoard JTAG]] and [[OMAP3530_ICEPICK|OMAP3530_ICEPICK]]about JTAG on BeagleBoard
* [[BeagleBoardNAND|BeagleBoard NAND boot]] about how to boot BeagleBoard from NAND flash
* [[BeagleBoardPeripherals|BeagleBoard peripherals and adapters page]] about useful BeagleBoard add ons.
* [[BeagleBoardFAQ|BeagleBoard FAQ]]
* [[BeagleBoardSugar|Sugar on BeagleBoard]]
* [[BeagleBoard/DSP_Howto|BeagleBoard DSP howto]]
* [[BeagleBoardRawLCD|Interfacing BeagleBoard to Raw LCD]]
* [[BeagleBoard/gst-openmax|BeagleBoard OpenMAX usage]]
* [[BeagleBoardOpenCV|Using OpenCV computer vision library with BeagleBoard]]
* [http://code.google.com/p/beagleboard/w/list code.google.com BeagleBoard wiki]
* [http://en.wikipedia.org/wiki/Beagle_Board Wikipedia BeagleBoard page]
==Beagle photos==
* [http://www.flickr.com/groups/beagleboard/pool/ Beagle board pictures at flickr]
* [http://www.flickr.com/photos/32615155@N00/2439256116/ Beagle board and USRP]
* [http://www.flickr.com/photos/nishanthmenon/2438406603/ Modify SDP3430 QUART cable for beagle]
* [http://www.flickr.com/photos/koenkooi/2695061759/ MythTV on Beagle]
==Beagle videos==
* [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings]
* [http://www.youtube.com/watch?v=cXr-D1wROfQ Beagleboard in the Living Room]
* [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 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 Beagle Running Angstrom (VGA) on DLP Pico Projector]
* Not on Beagle OMAP3530: [http://youtube.com/watch?v=5i9cWOK1spw Ubuntu 7.04 on on OMAP3430 SDP]
==Beagle manufacturing==
* [http://www.youtube.com/watch?v=C-CwkjT9z_0&feature=related Beagle Solder Paste Screening]
* [http://www.youtube.com/watch?v=9LLjDovIG2M&feature=related Beagle Assembly Inspection]
* [http://www.youtube.com/watch?v=sbOZfBnoVnM&feature=related Beagle Functional Test]
* [http://www.youtube.com/watch?v=cvDtXmJJcEI&feature=related Beagle Reflow]
* [http://www.youtube.com/watch?v=W2o4NTASxN0&feature=related Beagle Board Assembly at Circuitco]
==Fun==
* Enjoy [http://www.beaglegame.com/ BeagleGame]

=Other OMAP boards=

* OMAP1 OMAP5912 (ARM9 + C5x DSP) based [[OSK|OSK]] board.
* OMAP3 OMAP3430 based [http://www.logicpd.com/products/devkit/ti/zoom_mobile_development_kit Zoom MDK]
* OMAP3 OMAP3530 based [http://pandora.bluwiki.com/ Pandora]
* OMAP3 OMAP3503 based [http://www.gumstix.net/Overo/cat/Overo/115.html Gumstix Overo]
* OMAP3 OMAP35x based EVM from [http://www.mistralsolutions.com/business_divisons/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.arm.com/iqonline/news/partnernews/23036.html Archos 5, ARCHOS 5G and ARCHOS 7]

BeagleBoardAndOpenEmbeddedGit

2008-10-23T12:54:39Z

RobertK: /* Prerequisites */ shorten

[[Category: Linux]]
[[Category: OMAP]]
This guide briefly describes the steps that need to be taken in order to create an [http://www.openembedded.org/ OpenEmbedded] (OE) based image for the [[BeagleBoard]].
It was created while performing an install on ubuntu804jeos (a minimal console only vmware appliance). This guide differs in that the official GettingStarted uses monotone while we will be using git. The second difference is that this guide only focuses on running on Ubuntu and developing for beagle.

The first step is to get a working Open Embedded installation. This can seam a daunting task at first but the rewards are great so here we go. This guide tries to be self containing. We therefore will not push you to use Google or read the other manuals.

=== Prerequisites ===
OE tries to be as self supporting as possible. OE will both compile the cross compiler and the tools needed to compile a whole system. Still some dependencies are to be met using the "host" system. During the install we will be able to run almost all the commands as normal user but right now we will install the basic set of packages that are required to make OE to be happy.

Host tools to install:
sudo apt-get install ccache sed wget cvs subversion git-core coreutils unzip texi2html texinfo libsdl1.2-dev
sudo apt-get install docbook-utils gawk help2man diffstat gtk-doc-tools file g++

Nice to have optional tools to install:
sudo apt-get install python-psyco minicom

OE and many tools and scripts that are used contain bashisms. We therefore want to change the default "/bin/sh" to point to bash.
sudo dpkg-reconfigure dash
#and select no

An other change need need to perform as root is to change some default settings of the kernel.
sudo vi /etc/sysctl.conf
vm.vdso_enabled = 0
vm.mmap_min_addr = 0

Run
sudo sysctl -p

== The effective install ==
We are going install the OpenEmbedded system under the user's home directory in a directory called "oe". We will need about 10 gig of free disk space. Under that we will be putting the different components of the OE system. Those components are [http://bitbake.berlios.de/manual/ Bitbake], the OpenEmbedded meta-data and the beagle configuration. The Bitbake task executor will be put under "opt". The OpenEmbedded meta-data ( Bitbake recipes ), classes ( Bitbake extentions) and configuration (machine and arch setup) will be located under the "org.openembedded.dev" directory. The BeagleBoard configuration will be placed under "org.beagleboard.dev" directory.

=== OpenEmbedded and Bitbake install ===
This part really is not that difficult after all.

Set the dir where everything will be done
export OE_HOME=$HOME/oe

Install Bitbake
mkdir -p $OE_HOME/opt
cd $OE_HOME/opt
svn co svn://svn.berlios.de/bitbake/branches/bitbake-1.8/ bitbake

Install the OpenEmbedded meta-data using git
cd $OE_HOME
git clone git://git.openembedded.net/openembedded

=== Creating the BeagleBoard configuration and profile ===
We now need to tweak OpenEmbedded to fit our Beagle needs. We create a profile script that we can run whenever we feel like playing with beagle. This script will perform a few tasks. It will add bitbake to our PATH so we can run the bitbake command from anywhere. It will then export the BBPATH and BBFILES. This tells bitbake where to find it's meta-data. BBPATH will booth point to our own org.beagleboard.dev files and org.openembedded.dev.

But first we create a local.conf containing the most important choices we need to make. Change at least the MACHINE to beagleboard. Comment the BBFILES variable as we will defines then in our profile script do select angstrom-2008.1 as distro. Remove the last line after that

mkdir -p $OE_HOME/beagleboard/beagleboard/conf
cat > $OE_HOME/beagleboard/beagleboard/conf/local.conf <<_EOF
DISTRO = "angstrom-2008.1"
BBFILES = "$OE_HOME/openembedded/packages/*/*.bb"
TMPDIR = "$OE_HOME/tmp"
MACHINE = "beagleboard"
ENABLE_BINARY_LOCALE_GENERATION = "0"
_EOF

Now we create our profile. There are TWO CHOICES here.

CHOICE 1) If you are going to operate directly connected to the internet (i.e. NO Proxy Firewall), then do:

cd $OE_HOME
cat > $OE_HOME/beagleboard/beagleboard/profile.sh <<_EOF
export OE_HOME=\$HOME/oe
export MY_OE_CONF="beagleboard"
export BBPATH=\$OE_HOME/beagleboard/:\$OE_HOME/beagleboard/\$MY_OE_CONF:\$OE_HOME/openembedded
export BBFILES="\$OE_HOME/openembedded/packages/*/*.bb"
export PATH=\$OE_HOME/opt/bitbake/bin:\$PATH
if [ "\$PS1" ]; then
if [ "\$BASH" ]; then
export PS1="\[\033[01;32m\]OE:\$MY_OE_CONF\[\033[00m\] \${PS1}"
fi
fi
_EOF

CHOICE 2) If you will be operating from behind a Proxy Firewall, then do:

cd $OE_HOME
cat > $OE_HOME/beagleboard/beagleboard/profile.sh <<_EOF
export OE_HOME=\$HOME/oe
export MY_OE_CONF="beagleboard"
export BBPATH=\$OE_HOME/beagleboard/:\$OE_HOME/beagleboard/\$MY_OE_CONF:\$OE_HOME/openembedded
export BBFILES="\$OE_HOME/openembedded/packages/*/*.bb"
export PATH=\$OE_HOME/opt/bitbake/bin:\$PATH
export CVS_TARBALL_STASH="http://oesources.org/sources/current/"
if [ "\$PS1" ]; then
if [ "\$BASH" ]; then
export PS1="\[\033[01;32m\]OE:\$MY_OE_CONF\[\033[00m\] \${PS1}"
fi
fi
_EOF

Now make the profile executable:

chmod +x beagleboard/beagleboard/profile.sh

== Running ==
We now have finished the installation. If everything goes well we can now create images for the BeagleBoard

source beagleboard/beagleboard/profile.sh

Pull down any changes in the git tree.

cd $OE_HOME/openembedded
git pull
git checkout

Now build the console image.

cd $OE_HOME
bitbake console-image

If this goes well your computer will be compiling for a long time. A long time can be several hours.

If you receive an error of the form "ERROR: Unable to open conf/bitbake.conf" check that your profile.sh created earlier has the correct BBPATH setting (copy/pasting from this page may cause a line-break between the export command and the BBPATH var).

== Preparing the system for booting ==
The output of the bitbake command will ultimately be found under the $OE_HOME/tmp/deploy/glibc/images/beagleboard. In there you can find at least 3 interesting files:
* console-image-beagleboard.tar
* console-image-beagleboard.jffs2 and
* uImage-beagleboard.bin

The console images are representations of a full and self containing file system *including* a kernel. The uImage is a linux kernel image that is suitable to be loaded by the U-boot bootloader. The difference between the tar file and the jffs2 image is that the later is better suited to directly put on a raw partition.

We are going to use the U-boot that is already provided in the NAND flash of the beagleboard as that one already support the MMC can load kernel images from a fat file system.
What we will do is to format a SD-card to hold both a fat and an ext2 file system. We will put the kernel in the fat file system as U-boot failed to load the image from a ext2 file system. We will unpack the console-image under the ext2 file system.

===Create partitions and format the SD-card ===
We usually create two partitions, the first one has a FAT partition type and the second one a Linux file system type . We then format them and put content on them.
We are not going the describe the formating other then briefly because it just if to easy to format the wrong partition. There are a few reasons for having a first partition as FAT but his is not the scope of this document ( Think of U-boot, windows , mass-storage ). Instruction for formatting the SD-card correctly can be found at: [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat Boot Disk Format]

Here is the output of the fdisk -l command after creating the new partitions.
Disk /dev/mmcblk0: 2032 MB, 2032664576 bytes
1 heads, 16 sectors/track, 248128 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Disk identifier: 0x2f3dffc4

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 2 12209 97664 b W95 FAT32
/dev/mmcblk0p2 12210 248128 1887352 83 Linux

We now format the file systems ext2 file system under /mnt. Some system will perform a automount of the newly created file system. Try to disable this automount feature if possible (it is not easy) or use gparted
mkfs.vfat /dev/mmcblk0p1
mkfs.ext2 /dev/mmcblk0p2

Mount the ext2 file system and unpack the archive. Do not forget the -C option.
mount /dev/mmcblk0p2 /mnt
tar xvf system/angstrom/deploy/glibc/images/beagleboard/console-image-beagleboard.tar -C /mnt
umount /mnt

Mount the fat file system and copy the kernel image to there.
mount /dev/mmcblk0p1 /mnt
cp system/angstrom/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /mnt/uImage
umount /mnt

== Booting ==
We can put the SD-card in the beagleboard and wait for the U-boot prompt. The kernel we compiled only gave serial output if we first ran the coninfo command we therefore type coninfo and ask U-Boot to initialise
the mmc stack. After that we set the kernel command line telling what the console is and where our root file system is located. We then load the image from the fat file system into memory and boot the kernel

coninfo
mmcinit
setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=1
fatload mmc 0:1 0x80000000 uImage
bootm

===One very important note:===

It's important to have an X-Loader on your Beagleboard that uses the uBoot on the SD Card that goes with the Angstrom uImage. The B5 Beagleboards do not appear to come with such an X-Loader / U-Boot combination (i.e. the B5 standard uBoot will lead to problems with the sound driver and other things, but will not tell you that it's creating a problem).

The fix is to load a new X-Loader which will in turn automatically load the uBoot from the SD card, which again in turn will load the uImage properly.

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 info on making the SD Card.
* Put the SD Card in the Beagle, 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 Beagle to see that the new X-Loader is properly loaded.

This will update the X-Loader to a newer version that will automatically load uBoot from the SD card, and then load uImage from the SD card, rather than always using the uBoot in the Beagleboard NAND.

== Using the OpenEmbedded Environment ==

If you have not used bitbake / OpenEmbedded before, a helpful example for creating packages that can be installed on a beagle linux install (such as the one created above) can be found at [http://www.gumstix.net/Software/view/Build-system-overview/Hello-world-tutorial/111.html Hello World Tutorial for Gumstix].

BeagleBoardAndOpenEmbeddedGit

2008-10-17T12:35:01Z

RobertK: /* Preparing the system for booting */ image is in $OE_HOME/tmp/deploy/glibc/images/beagleboard

[[Category: Linux]]
[[Category: OMAP]]
This guide briefly describes the steps that need to be taken in order to create an [http://www.openembedded.org/ OpenEmbedded] (OE) based image for the [[BeagleBoard]].
It was created while performing an install on ubuntu804jeos (a minimal console only vmware appliance). This guide differs in that the official GettingStarted uses monotone while we will be using git. The second difference is that this guide only focuses on running on Ubuntu and developing for beagle.

The first step is to get a working Open Embedded installation. This can seam a daunting task at first but the rewards are great so here we go. This guide tries to be self containing. We therefore will not push you to use Google or read the other manuals.

=== Prerequisites ===
OE tries to be as self supporting as possible. OE will both compile the cross compiler and the tools needed to compile a whole system. Still some dependencies are to be met using the "host" system. During the install we will be able to run almost all the commands as normal user but right now we will install the basic set of packages that are required to make OE to be happy.

Host tools to install:
sudo apt-get install ccache sed wget cvs subversion git-core coreutils unzip texi2html texinfo libsdl1.2-dev
sudo apt-get install docbook-utils gawk help2man diffstat gtk-doc-tools file g++

Nice to have optional tools to install:
sudo apt-get install python-psyco minicom

OE and many tools and scripts that are used contain bashisms. We therefore want to change the default "/bin/sh" to point to bash.
ln -s /bin/sh
sudo dpkg-reconfigure dash
#and select no
ln -s /bin/sh

An other change need need to perform as root is to change some default settings of the kernel.
sudo vi /etc/sysctl.conf
vm.vdso_enabled = 0
vm.mmap_min_addr = 0

Run
sudo sysctl -p

== The effective install ==
We are going install the OpenEmbedded system under the user's home directory in a directory called "oe". We will need about 10 gig of free disk space. Under that we will be putting the different components of the OE system. Those components are [http://bitbake.berlios.de/manual/ Bitbake], the OpenEmbedded meta-data and the beagle configuration. The Bitbake task executor will be put under "opt". The OpenEmbedded meta-data ( Bitbake recipes ), classes ( Bitbake extentions) and configuration (machine and arch setup) will be located under the "org.openembedded.dev" directory. The BeagleBoard configuration will be placed under "org.beagleboard.dev" directory.

=== OpenEmbedded and Bitbake install ===
This part really is not that difficult after all.

Set the dir where everything will be done
export OE_HOME=$HOME/oe

Install Bitbake
mkdir -p $OE_HOME/opt
cd $OE_HOME/opt
svn co svn://svn.berlios.de/bitbake/branches/bitbake-1.8/ bitbake

Install the OpenEmbedded meta-data using git
cd $OE_HOME
git clone git://git.openembedded.net/openembedded

=== Creating the BeagleBoard configuration and profile ===
We now need to tweak OpenEmbedded to fit our Beagle needs. We create a profile script that we can run whenever we feel like playing with beagle. This script will perform a few tasks. It will add bitbake to our PATH so we can run the bitbake command from anywhere. It will then export the BBPATH and BBFILES. This tells bitbake where to find it's meta-data. BBPATH will booth point to our own org.beagleboard.dev files and org.openembedded.dev.

But first we create a local.conf containing the most important choices we need to make. Change at least the MACHINE to beagleboard. Comment the BBFILES variable as we will defines then in our profile script do select angstrom-2008.1 as distro. Remove the last line after that

mkdir -p $OE_HOME/beagleboard/beagleboard/conf
cat > $OE_HOME/beagleboard/beagleboard/conf/local.conf <<_EOF
DISTRO = "angstrom-2008.1"
BBFILES = "$OE_HOME/openembedded/packages/*/*.bb"
TMPDIR = "$OE_HOME/tmp"
MACHINE = "beagleboard"
ENABLE_BINARY_LOCALE_GENERATION = "0"
_EOF

Now we create our profile. There are TWO CHOICES here.

CHOICE 1) If you are going to operate directly connected to the internet (i.e. NO Proxy Firewall), then do:

cd $OE_HOME
cat > $OE_HOME/beagleboard/beagleboard/profile.sh <<_EOF
export OE_HOME=\$HOME/oe
export MY_OE_CONF="beagleboard"
export BBPATH=\$OE_HOME/beagleboard/:\$OE_HOME/beagleboard/\$MY_OE_CONF:\$OE_HOME/openembedded
export BBFILES="\$OE_HOME/openembedded/packages/*/*.bb"
export PATH=\$OE_HOME/opt/bitbake/bin:\$PATH
if [ "\$PS1" ]; then
if [ "\$BASH" ]; then
export PS1="\[\033[01;32m\]OE:\$MY_OE_CONF\[\033[00m\] \${PS1}"
fi
fi
_EOF

CHOICE 2) If you will be operating from behind a Proxy Firewall, then do:

cd $OE_HOME
cat > $OE_HOME/beagleboard/beagleboard/profile.sh <<_EOF
export OE_HOME=\$HOME/oe
export MY_OE_CONF="beagleboard"
export BBPATH=\$OE_HOME/beagleboard/:\$OE_HOME/beagleboard/\$MY_OE_CONF:\$OE_HOME/openembedded
export BBFILES="\$OE_HOME/openembedded/packages/*/*.bb"
export PATH=\$OE_HOME/opt/bitbake/bin:\$PATH
export CVS_TARBALL_STASH="http://oesources.org/sources/current/"
if [ "\$PS1" ]; then
if [ "\$BASH" ]; then
export PS1="\[\033[01;32m\]OE:\$MY_OE_CONF\[\033[00m\] \${PS1}"
fi
fi
_EOF

Now make the profile executable:

chmod +x beagleboard/beagleboard/profile.sh

== Running ==
We now have finished the installation. If everything goes well we can now create images for the BeagleBoard

source beagleboard/beagleboard/profile.sh

Pull down any changes in the git tree.

cd $OE_HOME/openembedded
git pull
git checkout

Now build the console image.

cd $OE_HOME
bitbake console-image

If this goes well your computer will be compiling for a long time. A long time can be several hours.

If you receive an error of the form "ERROR: Unable to open conf/bitbake.conf" check that your profile.sh created earlier has the correct BBPATH setting (copy/pasting from this page may cause a line-break between the export command and the BBPATH var).

== Preparing the system for booting ==
The output of the bitbake command will ultimately be found under the $OE_HOME/tmp/deploy/glibc/images/beagleboard. In there you can find at least 3 interesting files, console-image-beagleboard.tar
console-image-beagleboard.jffs2 and uImage-beagleboard.bin. The console images are representations of a full and self containing file system *including* a kernel. The uImage is a linux kernel image that is suitable to be loaded by the U-boot bootloader. The difference between the tar file and the jffs2 image is that the later is better suited to directly put on a raw partition. We are going to use the U-boot that is already provided in the nand flash of the beagleboard as that one already support the MMC can load kernel images from a fat file system.
What we will do is to format a SD-card to hold an booth a fat and a ext2 file system. We will put the kernel in the fat file system as U-boot failed to load the image from a ext2 file system.. We will unpack the console-image under the ext2 file system.

===Create partitions and format the SD-card ===
We usually create two partitions, the first one has a FAT partition type and the second one a Linux file system type . We then format them and put content on them.
We are not going the describe the formating other then briefly because it just if to easy to format the wrong partition. There are a few reasons for having a first partition as FAT but his is not the scope of this document ( Think of U-boot, windows , mass-storage ). Instruction for formatting the SD-card correctly can be found at: [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat Boot Disk Format]

Here is the output of the fdisk -l command after creating the new partitions.
Disk /dev/mmcblk0: 2032 MB, 2032664576 bytes
1 heads, 16 sectors/track, 248128 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Disk identifier: 0x2f3dffc4

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 2 12209 97664 b W95 FAT32
/dev/mmcblk0p2 12210 248128 1887352 83 Linux

We now format the file systems ext2 file system under /mnt. Some system will perform a automount of the newly created file system. Try to disable this automount feature if possible (it is not easy) or use gparted
mkfs.vfat /dev/mmcblk0p1
mkfs.ext2 /dev/mmcblk0p2

Mount the ext2 file system and unpack the archive. Do not forget the -C option.
mount /dev/mmcblk0p2 /mnt
tar xvf system/angstrom/deploy/glibc/images/beagleboard/console-image-beagleboard.tar -C /mnt
umount /mnt

Mount the fat file system and copy the kernel image to there.
mount /dev/mmcblk0p1 /mnt
cp system/angstrom/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /mnt/uImage
umount /mnt

== Booting ==
We can put the SD-card in the beagleboard and wait for the U-boot prompt. The kernel we compiled only gave serial output if we first ran the coninfo command we therefore type coninfo and ask U-Boot to initialise
the mmc stack. After that we set the kernel command line telling what the console is and where our root file system is located. We then load the image from the fat file system into memory and boot the kernel

coninfo
mmcinit
setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=1
fatload mmc 0:1 0x80000000 uImage
bootm

===One very important note:===

It's important to have an X-Loader on your Beagleboard that uses the uBoot on the SD Card that goes with the Angstrom uImage. The B5 Beagleboards do not appear to come with such an X-Loader / U-Boot combination (i.e. the B5 standard uBoot will lead to problems with the sound driver and other things, but will not tell you that it's creating a problem).

The fix is to load a new X-Loader which will in turn automatically load the uBoot from the SD card, which again in turn will load the uImage properly.

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 info on making the SD Card.
* Put the SD Card in the Beagle, 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 Beagle to see that the new X-Loader is properly loaded.

This will update the X-Loader to a newer version that will automatically load uBoot from the SD card, and then load uImage from the SD card, rather than always using the uBoot in the Beagleboard NAND.