Please note that User Registration has been temporarily disabled due to a recent increase in automated registrations. If anyone needs an account, please request one here: RequestAccount. Thanks for your patience!--Wmat (talk)
Please email User:Wmat if you experience any issues with the Request Account form.

Difference between revisions of "BeagleBoard Community"

From eLinux.org
Jump to: navigation, search
(Availability: Add Rev C5)
m (Copy edited.)
Line 8: Line 8:
 
<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#ffffcc; align:right; ">
 
<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#ffffcc; align:right; ">
 
'''NEWS:'''
 
'''NEWS:'''
* Limited numbers of Pixel-Qi lcd kits and lvds kits are now available from [http://www.tincantools.com TinCanTools]
+
* Limited numbers of Pixel Qi LCD kits and LVDs kits are now available from [http://www.tincantools.com TinCanTools]
 
* [http://www.tincantools.com TinCanTools] has now discontinued [[BeagleBoard_Zippy2|Zippy2]], [[BeagleBoard_Trainer|Trainer Boards]] and [[BeagleBoard_Zippy|Zippy Boards]].
 
* [http://www.tincantools.com TinCanTools] has now discontinued [[BeagleBoard_Zippy2|Zippy2]], [[BeagleBoard_Trainer|Trainer Boards]] and [[BeagleBoard_Zippy|Zippy Boards]].
* [http://www.nxelec.com/products/hmi BeadaFrame] 7" LCD display kits for Beagleboard and Beaglebone are available now!
+
* [http://www.nxelec.com/products/hmi BeadaFrame] 7" LCD display kits for BeagleBoard and BeagleBone are available now!
 
* [http://www.chalk-elec.com/ 10" LCD LVDS plug-and-play bundle with capacitance touchscreen and ambient light sensor] is available in stock now!
 
* [http://www.chalk-elec.com/ 10" LCD LVDS plug-and-play bundle with capacitance touchscreen and ambient light sensor] is available in stock now!
 
* LVDS LCD add-on board [http://www.chalk-elec.com/ LVDS LCD] has been released and is available for order
 
* LVDS LCD add-on board [http://www.chalk-elec.com/ LVDS LCD] has been released and is available for order
Line 43: Line 43:
 
=Hardware=
 
=Hardware=
  
The Beagle Board is ''a low-cost, fan-less single-board computer based on TI's OMAP3 device family, with all of the expandability of today's desktop machines, but without the bulk, expense, or noise'' (from [http://beagleboard.org/ beagleboard.org]). It uses a TI [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor (ARM Cortex-A8 superscalar core ~600MHz paired with a TMS320C64x+ DSP ~430MHz and an Imagination SGX 2D/3D graphics processor). See [http://focus.ti.com/docs/prod/folders/print/omap3530.html#features OMAP3530 features] for more processor features. [[BeagleBoard#Availability|Price is USD 149]]. The design goal was to make it as simple and cheap as possible, e.g. not having a LCD added, but letting you connect all add-ons available as cheap external components. See [http://beagleboard.org/brief What is Beagle?] and [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article] for more details.
+
The BeagleBoard is ''a low-cost, fan-less single-board computer based on TI's OMAP3 device family, with all of the expandability of today's desktop machines, but without the bulk, expense, or noise'' (from [http://beagleboard.org/ beagleboard.org]). It uses a TI [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor (ARM Cortex-A8 superscalar core ~600&nbsp;MHz paired with a TMS320C64x+ DSP ~430MHz and an Imagination SGX 2D/3D graphics processor). See [http://focus.ti.com/docs/prod/folders/print/omap3530.html#features OMAP3530 features] for more processor features. [[BeagleBoard#Availability|Price is USD 149]]. The design goal was to make it as simple and cheap as possible, e.g. not having a LCD added, but letting you connect all add-ons available as cheap external components. See [http://beagleboard.org/brief What is Beagle?] and [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article] for more details.
  
 
The videos [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings] and [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu] give you a good intro about what BeagleBoard is about and its capabilities.
 
The videos [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings] and [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu] give you a good intro about what BeagleBoard is about and its capabilities.
Line 63: Line 63:
 
|-
 
|-
 
|'''1'''
 
|'''1'''
|[http://www.ti.com/omap35x OMAP3530] processor + 256MB NAND
+
|[http://www.ti.com/omap35x OMAP3530] processor + 256&nbsp;MB NAND
  
+ 128MB DDR (rev B)
+
+ 128&nbsp;MB DDR (rev B)
  
+ 256MB DDR (rev C)
+
+ 256&nbsp;MB DDR (rev C)
 
|PoP: Package-On-Package implementation for Memory Stacking
 
|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=MT29C2G24MAKLAJG-6%20IT 256&nbsp;MB NAND/128&nbsp;MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1435-ND DigiKey]
  
 
([http://www.micron.com/products/partdetail?part=MT29C4G48MAPLCJI-6%20IT 512MB NAND/256MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1436-ND DigiKey])
 
([http://www.micron.com/products/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])
Line 136: Line 136:
 
|TWL4030 (Rev A thru C2 inc.)
 
|TWL4030 (Rev A thru C2 inc.)
 
[http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] (Rev C3 onwards)
 
[http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] (Rev C3 onwards)
|Audio CODEC, USB port, power-on reset and power management. The TWL4030 is pin-compatible with the [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] chip and was used due to the very limited availability of the TPS65950 in early board revisions.
+
|Audio CODEC, USB port, power-on reset and power management. The TWL4030 is pin-compatible with the [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] chip and was used due to the very limited availability of the TPS65950 in early board revisions.
 
|-
 
|-
 
|'''17'''
 
|'''17'''
Line 151: Line 151:
 
|-
 
|-
 
|'''20'''
 
|'''20'''
|32kHz
+
|32&nbsp;kHz
 
|
 
|
 
|-
 
|-
 
|'''21'''
 
|'''21'''
|12MHz
+
|12&nbsp;MHz
 
|
 
|
 
|-
 
|-
 
|'''22'''
 
|'''22'''
|RS232 XVCR
+
|RS-232 XVCR
 
|
 
|
 
|-
 
|-
Line 172: Line 172:
 
|}
 
|}
 
   
 
   
* Board size: 3" x 3" (about 76.2 x 76.2 mm)
+
* Board size: 3" x 3" (about 76.2 x 76.2&nbsp;mm)
* Weight: ~37g
+
* Weight: ~37&nbsp;g
* Currently 6 layer PCB; target: 4 layer
+
* Currently six-layer PCB; target: four layer PCB
  
 
'''Bottom of rev B:'''
 
'''Bottom of rev B:'''
Line 188: Line 188:
 
==Schematic==
 
==Schematic==
  
Schematic of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous are also available from [http://beagleboard.org/hardware/design BeagleBoard.org design page] including in PDF format. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.
+
Schematic of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous are also available from [http://beagleboard.org/hardware/design BeagleBoard.org design page] including in PDF format. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.
  
 
==Layout==  
 
==Layout==  
Line 196: Line 196:
 
==Errata==
 
==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 A only'': The DC power jack pinout is incorrect on the PCB layout. DC_5V and GND are switched on PCB layout. Normally, the power jack has DC_5V on the center pin and GND on the sleeve (see Figure 20 of [http://www.beagleboard.org/uploads/BBSRM_6.pdf Beagle HW manual]). But on revision Ax boards the PCB layout has GND on center and DC_5V on sleeve. For this reason it is currently removed. It will be back on the Rev B board. Workaround is to remove wire connecting the two power pins on revision Ax boards and use external [http://amethyst.openembedded.net/~koen/beagleboard/beagle-power-pads.jpg power supply with switched connector] (do not connect anything to the “?” terminal. USB power will be permanently disabled and the board can only be powered from the 5&nbsp;V.) See [http://www.flickr.com/photos/koenkooi/2512038988/ Koen's Beagleboard powermod picture] with short descriptions, too.
# ''Boards revision < A5 only'': There is excess voltage drop across R6 which is used to measure the current consumption on the board. This needs to be a .1 ohm instead of a 1 ohm resistor (SMD 0805). All revision A5 boards have been updated to .1. You can also just solder in a jumper to J2 bypassing the current read point. This issue can cause issues with the USB host port as the voltage supplied to that port can be too low.
+
# ''Boards revision < 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&nbsp;ohm instead of a 1&nbsp;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 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 < A5 only'': There is an issue where on some boards the 1.8&nbsp;V has excessive noise on it. This is the result of two incorrect parts L1 and L3 being installed on the board. The inductors that were initially installed in the switchers are 100uH and need to be 1&nbsp;uH. This change will require that the board be returned for update. To check for correct parts, have a look to bottom of BeagleBoard. L1 - L3 are the larger parts there. They all have to be labeled with "102" (== 1uH). If any of these three inductors are labeled with "104" (== 100&nbsp;uH) they are wrong and have to be exchanged.
 
# ''Boards revision A and B'': USB HOST (EHCI) failures. See [http://code.google.com/p/beagleboard/issues/detail?id=15 issue 15] and [http://code.google.com/p/beagleboard/wiki/USBHostTestREPRODUCE USB host test reproduce]. This is a hardware defect. [http://www.beagleboard.org/irclogs/index.php?date=2008-05-29#T00:27:06 Most probably] Rev. B board does not have the EHCI USB connector mounted. Workaround: Use [[BeagleBoard#OTG|OTG port]] with something like [http://trisoft.de/pics/ZHost.JPG mini A to USB A adapter] instead.
 
# ''Boards revision A and B'': USB HOST (EHCI) failures. See [http://code.google.com/p/beagleboard/issues/detail?id=15 issue 15] and [http://code.google.com/p/beagleboard/wiki/USBHostTestREPRODUCE USB host test reproduce]. This is a hardware defect. [http://www.beagleboard.org/irclogs/index.php?date=2008-05-29#T00:27:06 Most probably] Rev. B board does not have the EHCI USB connector mounted. Workaround: Use [[BeagleBoard#OTG|OTG port]] with something like [http://trisoft.de/pics/ZHost.JPG mini A to USB A adapter] instead.
# ''Boards revision A and < B4'': Plugging in a USB OTG cable will prevent Beagle from booting (with git kernel), see [http://code.google.com/p/beagleboard/issues/detail?id=19 issue #19], too. This is due to missing filtering capacitor at USB OTG VBUS. When the kernel driver detects that a USB OTG cable is inserted it enables the charge pump to generate VBUS. With no filtering VBUS looks like any switching regulator output with no filtering -- a huge voltage spike when the switch is on, followed by a rapid decay to a low voltage until the next switch on period. The capacitor is there to store energy between the output switch ON and OFF time, the feedback loop in the regulator does sample the cap voltage. Fix is to piggy-back solder a 0603 2.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 < B4'': Plugging in a USB OTG cable will prevent Beagle from booting (with Git kernel), see [http://code.google.com/p/beagleboard/issues/detail?id=19 issue #19], too. This is due to missing filtering capacitor at USB OTG VBUS. When the kernel driver detects that a USB OTG cable is inserted it enables the charge pump to generate VBUS. With no filtering VBUS looks like any switching regulator output with no filtering -- a huge voltage spike when the switch is on, followed by a rapid decay to a low voltage until the next switch on period. The capacitor is there to store energy between the output switch ON and OFF time, the feedback loop in the regulator does sample the cap voltage. Fix is to piggy-back solder a 0603 2.2&nbsp;µF ceramic capacitor to D3, see [http://www.sakoman.net/omap3/beagle/vbus-mod-d3.jpg VBUS modification D3 picture]. Revision B4 boards and newer have this fix applied. Thanks to [http://groups.google.com/group/beagleboard/msg/eb789e15c99a673d Steve] for debugging this!
# ''Boards revision A and < B5'': There is some issue with 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.
+
# ''Boards revision A and < B5'': There is some issue with a 32&nbsp;kHz clock depending on system configuration used to clock some OMAP3 peripherals. From this e.g. GPIOs, GPTIMERs, and USB on BeagleBoard might be affected. See [http://code.google.com/p/beagleboard/issues/detail?id=22 Issue 22]. The symptom from this is that after booting the Linux kernel, the serial console hangs after some time and no serial input/output is possible any more. There is one software workaround and one hardware fix for this: (A) Software workaround: Don't use the 32&nbsp;kHz timer to clock Linux, instead use the MPU timer. (B) Hardware workaround: Remove [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard capacitor C70], which improves the 32&nbsp;kHz clock quality and avoids hang-up. Note: Revision A boards have capacitor C70 [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard at the same location] as rev. B boards. Note: Board revision >= B5 removes capacitor C70.
# ''Random boards, quite rare, revision < B6'': Some random boards and quite rare, show directly after purchasing broken serial communication from 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.
+
# ''Random boards, quite rare, revision < B6'': Some random boards and quite rare, show directly after purchasing broken serial communication from the host PC to BeagleBoard. Symptom is that you get a new board, get serial output from BeagleBoard in terminal program, but can't type anything at U-Boot prompt (Note: Don't mix this with errata #7. With errata #7 you are able to use U-Boot normally, but the Linux prompt input stops after some time). Most users don't have this issue, though. So, first double check your serial configuration ([[BeagleBoardFAQ#Serial_connection_.231|FAQ1]], [[BeagleBoardFAQ#Serial_connection_.232|FAQ2]] and [[BeagleBoardFAQ#Serial_connection_.233|FAQ3]]). Only if you are really, really sure that anything with your serial connection is fine, consider sending the board back doing a [http://beagleboard.org/support/rma RMA request]. This issue was resolved on revision B6 and later boards.
  
 
For additional (software) issues and enhancement requests see [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker], too.
 
For additional (software) issues and enhancement requests see [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker], too.
Line 213: Line 213:
 
Some [http://www.beagleboard.org/irclogs/index.php?date=2008-07-08#T21:12:23 notes] about (ARM processor) clock rates at BeagleBoard:
 
Some [http://www.beagleboard.org/irclogs/index.php?date=2008-07-08#T21:12:23 notes] about (ARM processor) clock rates at BeagleBoard:
  
* ARM Cortex-A8 processor is currently clocked at 500MHz
+
* ARM Cortex-A8 processor is currently clocked at 500&nbsp;MHz
* 500MHz is the default used because it is a balance of performance and longevity
+
* 500&nbsp;MHz is the default used because it is a balance of performance and longevity
* For OMAP35x 600MHz is max recommended
+
* For OMAP35x 600&nbsp;MHz is maximum recommended
* An additional 720MHz overdrive is supported only on high-speed grade OMAP3530/25 devices as fitted to the Beagleboard C4
+
* An additional 720&nbsp;MHz overdrive is supported only on high-speed grade OMAP3530/25 devices as fitted to the BeagleBoard C4
* At 600MHz or higher OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy
+
* At 600&nbsp;MHz or higher OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy
* Higher than 600/720MHz is out of spec and no guarantee it will work at all (or not damage itself)
+
* Higher than 600/720&nbsp;MHz is out of specification and no guarantee it will work at all (or not damage itself)
  
 
* Also keep in mind that if you go higher you probably want to increase the core voltage. Some of this is mentioned in tables 3-3, 4-15 and 4-16 of the [http://focus.ti.com/lit/ds/symlink/omap3530.pdf OMAP3530 data sheet]. Some numbers:
 
* Also keep in mind that if you go higher you probably want to increase the core voltage. Some of this is mentioned in tables 3-3, 4-15 and 4-16 of the [http://focus.ti.com/lit/ds/symlink/omap3530.pdf OMAP3530 data sheet]. Some numbers:
Line 225: Line 225:
 
||'''ARM'''||'''DSP'''||'''core voltage'''
 
||'''ARM'''||'''DSP'''||'''core voltage'''
 
|-
 
|-
|720 MHz||520 MHz||1.35V
+
|720&nbsp;MHz||520&nbsp;MHz||1.35&nbsp;V
 
|-
 
|-
|600 MHz||430 MHz||1.35V
+
|600&nbsp;MHz||430&nbsp;MHz||1.35&nbsp;V
 
|-
 
|-
|550 MHz||400 MHz||1.27V
+
|550&nbsp;MHz||400&nbsp;MHz||1.27&nbsp;V
 
|-
 
|-
|500 MHz||360 MHz||1.2V
+
|500&nbsp;MHz||360&nbsp;MHz||1.2&nbsp;V
 
|}
 
|}
  
Line 238: Line 238:
 
* There is a thermal monitor in the core, you could use to scale frequency up and down
 
* There is a thermal monitor in the core, you could use to scale frequency up and down
  
To set CPU clock to 600 MHz, there are two options. Both '''do not''' adjust the voltage, so the system may become unstable:
+
To set the CPU clock to 600&nbsp;MHz, there are two options. Both '''do not''' adjust the voltage, so the system may become unstable:
  
* The u-boot command "mw 48004940 0012580c" will temporarily set the CPU clock to 600 MHz (not permanent over reset).
+
* The U-Boot command "mw 48004940 0012580c" will temporarily set the CPU clock to 600&nbsp;MHz (not permanent over reset).
* To permanently set the CPU clock to 600 MHz, include the above command in the "bootcmd" variable or equivalent script.
+
* To permanently set the CPU clock to 600&nbsp;MHz, include the above command in the "bootcmd" variable or equivalent script.
  
* To set the DSP clock to 430 Mhz use "mw 48004040 0x0009ae0c".
+
* To set the DSP clock to 430&nbsp;MHz use "mw 48004040 0x0009ae0c".
  
 
==Power management==
 
==Power management==
Line 249: Line 249:
 
* Detailed OMAP3 Power Management Information can be found [[OMAP_Power_Management|HERE]]
 
* Detailed OMAP3 Power Management Information can be found [[OMAP_Power_Management|HERE]]
 
* Latest Linux kernel power management development for TI OMAP SoCs is maintained in [http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git;a=summary Kevin's linux-omap-pm git tree]
 
* Latest Linux kernel power management development for TI OMAP SoCs is maintained in [http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git;a=summary Kevin's linux-omap-pm git tree]
* Russ' Beagle HW modifications resulted in [http://groups.google.com/group/beagleboard/browse_thread/thread/197a8ef6b46cc828 8mW sleep for Beagle Board]
+
* Russ' Beagle HW modifications resulted in [http://groups.google.com/group/beagleboard/browse_thread/thread/197a8ef6b46cc828 8&nbsp;mW sleep for Beagle Board]
  
Without PM kernel, the Beagle [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm consumes ~1.5 watts idle, however it also uses the same amount under load] (see bottom of that page).
+
Without PM kernel, the Beagle [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm consumes ~1.5&nbsp;watts idle, however it also uses the same amount under load] (see bottom of that page).
  
 
==DLP Pico projector==
 
==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.
+
Texas Instruments is developing a Pico Video Projector Kit (PVPK) as a peripheral for the BeagleBoard. The stand-alone pico projector will support VGA resolution (640 x 480 pixels), RGB 888 input through a DVI interface. The physical connector on the projector will be HDMI. See [http://groups.google.com/group/beagleboard/msg/10e218972380ee48 mailing list] and [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector] for more details.
  
 
It is available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23836-ND DigiKey] for $349.
 
It is available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23836-ND DigiKey] for $349.
Line 265: Line 265:
 
==Interfacing to Raw LCD Panels==
 
==Interfacing to Raw LCD Panels==
  
Currently on Rev A / B boards there is no direct access to the LCD lines before they enter the DVI framer. The REV C2 provides access to these lines. Several projects to interface an LCD to the beagleboard exist:
+
Currently on Rev A / B boards there is no direct access to the LCD lines before they enter the DVI framer. The REV C2 provides access to these lines. Several projects to interface an LCD to the BeagleBoard exist:
  
 
* [[BeagleBoardRawLCD|interfacing to Raw LCD Panels]] article  
 
* [[BeagleBoardRawLCD|interfacing to Raw LCD Panels]] article  
* [http://digitalsurveyinstruments.com/beagleperiphials/hdmi2parallel/doc/index.htm hdmi to parallel] workaround method
+
* [http://digitalsurveyinstruments.com/beagleperiphials/hdmi2parallel/doc/index.htm HDMI-to-parallel] workaround method
* [http://www.harbaum.org/till/dvi2par/index.shtml dvi2par cheap diy HDMI to parallel converter]
+
* [http://www.harbaum.org/till/dvi2par/index.shtml dvi2par cheap DIY HDMI-to-parallel converter]
  
 
=Availability=
 
=Availability=
Line 293: Line 293:
 
Note: Some users report that they got some questions from DigiKey to be answered before board shipping is done.
 
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: While you get free shipping, most probably you have to pay tax, for example, ordering from Europe. Users report that they had to pay EUR ~34 - 44 VAT + importing taxes (depending on european country), resulting in EUR 137 - 147 ordering from Europe.
  
Note: For European users, [http://www.ebv.com/fileadmin/products/Press_Print/Campaigns/2009/Product_Campaigns/Texas_Beagle_Board_englisch.pdf EBV Elektronik] sells its own blue version of the board for 179 EUR, which includes all useful accessories (DVI cable, serial cable, USB 2.0 Ethernet, USB hub, 2 GB MMC, power supply, Linux BSP).
+
Note: For European users, [http://www.ebv.com/fileadmin/products/Press_Print/Campaigns/2009/Product_Campaigns/Texas_Beagle_Board_englisch.pdf EBV Elektronik] sells its own blue version of the board for 179 EUR, which includes all useful accessories (DVI cable, serial cable, USB 2.0 Ethernet, USB hub, 2&nbsp;GB MMC, power supply, Linux BSP).
  
 
Note: German (Europe) users can order through German shops, too. For higher price, though.  
 
Note: German (Europe) users can order through German shops, too. For higher price, though.  
Line 329: Line 329:
 
* Uses [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] OMAP power controller instead of TWL4030
 
* Uses [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] OMAP power controller instead of TWL4030
 
* Three additional PWM signals on the expansion connector added as pin mux options to existing pins ([http://groups.google.com/group/beagleboard/browse_thread/thread/d5872b7c6d74592c?hl=en# message])
 
* 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)
+
* Revision detection (to be able to identify C2 board from older boards by software, for example, for different pin mux)
* 256MB RAM ([http://groups.google.com/group/beagleboard/msg/3a38d0f21cefd6b1?hl=en message]) (and still 256MB NAND like rev B)
+
* 256&nbsp;MB RAM ([http://groups.google.com/group/beagleboard/msg/3a38d0f21cefd6b1?hl=en message]) (and still 256&nbsp;MB NAND like rev B)
  
 
Note: Revision C2 is the first production version, and all orders from Digi-Key are shipped as Rev C2.
 
Note: Revision C2 is the first production version, and all orders from Digi-Key are shipped as Rev C2.
Line 344: Line 344:
 
==Revision C4==
 
==Revision C4==
 
Revision C4 boards are the same as Revision C3 except:
 
Revision C4 boards are the same as Revision C3 except:
* Processor is 720MHz capable OMAP3
+
* Processor is 720&nbsp;MHz capable OMAP3
 
* Improved USB Host PHY power rails
 
* Improved USB Host PHY power rails
  
 
==Revision C5==
 
==Revision C5==
 
Revision C5 boards are the same as Revision C4 [http://circuitco.com/support/index.php?title=BeagleBoard#Image_Files except]:
 
Revision C5 boards are the same as Revision C4 [http://circuitco.com/support/index.php?title=BeagleBoard#Image_Files except]:
* The memory chip is upgraded to 512 MB NAND
+
* The memory chip is upgraded to 512&nbsp;MB NAND
  
 
==Clones==
 
==Clones==
 
===EBVBeagle===
 
===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/].
 
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.
+
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].
 
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===
[[Mini_Board|ICETEK-OMAP3530-Mini]] is a chinese BeagleBoard clone.
+
[[Mini_Board|ICETEK-OMAP3530-Mini]] is a Chinese BeagleBoard clone.
  
 
===DevKit8000===
 
===DevKit8000===
Line 370: Line 370:
  
 
===Tianyeit CIP312===
 
===Tianyeit CIP312===
[http://www.tianyeit.com CIP312 ] is from [http://www.tianyeit.com Tianyeit], China. It is has many functions ,such as WLAN/BT/ dual 10/100M Ethernet Contoller-LAN9221I/MCP2512  CAN BUS/ Touch Screen Controller/USB HUB/USB host/USB OTG Etc. Our module is base on DM3730/omap3530 all functions are packaged in 40x40x3.5mm Package ; For detail information please visit our website
+
[http://www.tianyeit.com CIP312 ] is from [http://www.tianyeit.com Tianyeit], China. It is has many functions ,such as WLAN/BT/ dual 10/100M Ethernet Contoller-LAN9221I/MCP2512  CAN BUS/ Touch Screen Controller/USB HUB/USB host/USB OTG Etc. Our module is base on DM3730/omap3530 all functions are packaged in 40x40x3.5&nbsp;mm package ; For detailed information, please visit our website
 
[[Image:http://www.tianyeit.com/download/cip312.jpg]]
 
[[Image:http://www.tianyeit.com/download/cip312.jpg]]
  
 
===IGEPv2===
 
===IGEPv2===
[http://www.igep-platform.com/ IGEPv2 Platform] is a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, wifi+bluetooth.
+
[http://www.igep-platform.com/ IGEPv2 Platform] is a Spanish BeagleBoard clone, slightly larger, with additional peripherals like, for example, Ethernet connector, Wi-Fi and Bluetooth.
* 720MHz OMAP3 Processor
+
* 720&nbsp;MHz OMAP3 Processor
* 512MB RAM / 512MB Flash
+
* 512&nbsp;MB RAM / 512&nbsp;MB Flash
 +
 
 
===SOM3530===
 
===SOM3530===
[[SOM3530]] is a chinese BeagleBoard clone [[System-on-Module]],Dimension 40x40x4mm, Maybe the smallest [http://wiki.davincidsp.com/index.php?title=OMAP3_Overview OMAP3530]-based modules in the world! Including 100M high perfomance ethernet I/F
+
[[SOM3530]] is a Chinese BeagleBoard clone [[System-on-Module]], dimensions 40x40x4&nbsp;mm, maybe the smallest [http://wiki.davincidsp.com/index.php?title=OMAP3_Overview OMAP3530]-based modules in the world! Including 100&nbsp;Mbit/s high perfomance Ethernet I/F.
  
 
==BeagleBoard-based products==
 
==BeagleBoard-based products==
Line 388: Line 389:
 
** [http://groups.google.com/group/beagleboard/browse_thread/thread/1c82316019633e51 SketchUp 3D model]
 
** [http://groups.google.com/group/beagleboard/browse_thread/thread/1c82316019633e51 SketchUp 3D model]
 
* [http://www.esawdust.com/product/encl-dh-r1/ eSawdust metal case]
 
* [http://www.esawdust.com/product/encl-dh-r1/ eSawdust metal case]
* [http://aspectrt.web.fc2.com/support/ Aspect metal case for Beagleboard-xM]
+
* [http://aspectrt.web.fc2.com/support/ Aspect metal case for BeagleBoard-xM]
  
 
=Adapters=
 
=Adapters=
Line 394: Line 395:
 
For quite detailed information about all BeagleBoard peripherals see [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)].
 
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.
+
See [[BeagleBoardPeripherals| BeagleBoard peripherals and adapters page]] for useful add ons for BeagleBoard.
  
 
==Expansion boards==
 
==Expansion boards==
 
See [[:Category:BeagleBoard_Expansion_Boards]] for more information about expansion boards
 
See [[:Category:BeagleBoard_Expansion_Boards]] for more information about expansion boards
  
[http://www.nxelec.com/products/hmi BeadaFrame] - A 7" TFT LCD Screen with resistive touch for BeagleBoard and BeagleBone. A plastic(ABS) frame is included also for ease of mounting.
+
[http://www.nxelec.com/products/hmi BeadaFrame] - A 7" TFT LCD Screen with resistive touch for BeagleBoard and BeagleBone. A plastic (ABS) frame is included also for ease of mounting.
  
[http://www.chalk-elec.com LVDS LCD] - small add-on board to connect any LVDS LCD panel (like those in notebooks) to BeagleBoard (-xM) and PandaBoard. Also, they offer plug-and-play bundle with 10" 1024x600 LCD with capacitance touchscreen and ambient light sensor for automatic brightness control. Board is open-source.
+
[http://www.chalk-elec.com LVDS LCD] - small add-on board to connect any LVDS LCD panel (like those in notebooks) to BeagleBoard (-xM) and PandaBoard. Also, they offer plug-and-play bundle with 10" 1024x600 LCD with capacitance touchscreen and ambient light sensor for automatic brightness control. The board is open-source.
  
[http://www.liquidware.com/shop/show/BB-BT/BeagleTouch BeagleTouch] - A modular "shield" that snaps on top of the Beagle Board and provides a touch-screen OLED interface
+
[http://www.liquidware.com/shop/show/BB-BT/BeagleTouch BeagleTouch] - A modular "shield" that snaps on top of the BeagleBoard and provides a touch-screen OLED interface
  
[http://www.liquidware.com/shop/show/BB-BJC/BeagleJuice BeagleJuice] - A lithium ion battery module that snaps on the back of the Beagle Board that powers the Beagle Board.
+
[http://www.liquidware.com/shop/show/BB-BJC/BeagleJuice BeagleJuice] - A lithium ion battery module that snaps on the back of the BeagleBoard that powers the BeagleBoard.
  
[http://www.picklejar.org/lox LOX] - A dual channel internet linking radio (Ham, GMRS, etc) interface that can run any combination of 2 repeaters, simplex nodes, or remote bases.
+
[http://www.picklejar.org/lox LOX] - A dual channel internet linking radio (Ham, GMRS, etc.) interface that can run any combination of two repeaters, simplex nodes, or remote bases.
  
 
==JTAG==
 
==JTAG==
Line 414: Line 415:
 
See [[BeagleBoardJTAG]] for more information.
 
See [[BeagleBoardJTAG]] for more information.
  
==RS232==
+
==RS-232==
  
The pinout on the beagle board is "AT/Everex" or "IDC10". You can buy [http://www.pccables.com/07120.htm IDC10 to DB9M adapters] in many places as they are commonly used for old PCs. Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available. You can also probably rip one of those cables out of any old desktop computer, where it's being used to support the serial port. Be careful, though -- some of those cables will have that tenth hole filled in so you'd have to snap off the extraneous pin on your BeagleBoard. Keep looking until you find a cable with all 10 holes open.
+
The pinout on the BeagleBoard is "AT/Everex" or "IDC10". You can buy [http://www.pccables.com/07120.htm IDC10 to DB9M adapters] in many places as they are commonly used for old PCs. Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available. You can also probably rip one of those cables out of any old desktop computer, where it's being used to support the serial port. Be careful, though -- some of those cables will have that tenth hole filled in so you'd have to snap off the extraneous pin on your BeagleBoard. Keep looking until you find a cable with all 10 holes open.
  
 
Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available.
 
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.
Line 422: Line 423:
 
==USB-to-Serial Converter==
 
==USB-to-Serial Converter==
  
Since many systems no longer come with an actual serial port, you might need to pick up a USB-to-serial converter at your local computer store to connect to your BeagleBoard. Be warned that some of them simply do not work. Many of them are based on the Prolific chip, and require the pl2303 module to be loaded. But even when two converters appear to have exactly the same characteristics as listed in /var/log/messages, if you simply can't get one to work, be ready to try a different one.
+
Since many systems no longer come with an actual serial port, you might need to pick up a USB-to-serial converter at your local computer store to connect to your BeagleBoard. Be warned that some of them simply do not work. Many of them are based on the Prolific chip, and require the pl2303 module to be loaded. But even when two converters appear to have exactly the same characteristics as listed in /var/log/messages, if you simply can't get one to work, be ready to try a different one.
  
 
==USB==
 
==USB==
Line 430: Line 431:
 
The HS ([http://en.wikipedia.org/wiki/USB#USB_signalling HighSpeed]) USB [http://en.wikipedia.org/wiki/EHCI ECHI] controller on OMAP3 on BeagleBoard supports high-speed only. This simplifies the logic on the device.  FS/LS (FullSpeed/LowSpeed) devices, such as keyboards and mice, require going through a high-speed USB 2.0 hub.
 
The HS ([http://en.wikipedia.org/wiki/USB#USB_signalling HighSpeed]) USB [http://en.wikipedia.org/wiki/EHCI ECHI] controller on OMAP3 on BeagleBoard supports high-speed only. This simplifies the logic on the device.  FS/LS (FullSpeed/LowSpeed) devices, such as keyboards and mice, require going through a high-speed USB 2.0 hub.
  
According to the BeagleBoard System Reference Manual Rev C2, the EHCI port can source 5V at 500mA which is enough to power a hub and several low-power devices. However, this is only true if the BeagleBoard is powered through its power jack from a well-regulated 5V external power supply. If the BeagleBoard is powered through the OTG port, the EHCI port sources an "extremely limited" ampount of power (probably 100mA or so) so you'll need a "self-powered" USB 2.0 hub with its own external power supply.  [Reference: Sections 5.6 and 7.2 of the BBSRM Rev C2.2.]
+
According to the BeagleBoard System Reference Manual Rev C2, the EHCI port can source 5&nbsp;V at 500&nbsp;mA which is enough to power a hub and several low-power devices. However, this is only true if the BeagleBoard is powered through its power jack from a well-regulated 5&nbsp;V external power supply. If the BeagleBoard is powered through the OTG port, the EHCI port sources an "extremely limited" ampount of power (probably 100&nbsp;mA or so) so you'll need a "self-powered" USB 2.0 hub with its own external power supply.  [Reference: Sections 5.6 and 7.2 of the BBSRM Rev C2.2.]
  
'''Hardware issue on rev C3''' - the EHCI port on some rev C3 boards is unstable and will disconnect hubs/devices. Symptoms are: devices are disconnected from the port and cannot be reconnected without a reboot. It appears the shared 1.8V rail between the OMAP3530 and the power chip was getting noisy. Suggested solution (works on many boards) is adding a 22 uF 0805 package SMT capacitor atop the existing cap on C97. If SMT parts are not available, some boards can be repaired by a 22 uF through-hole capacitor across GND and VIO_1V8 on the expansion connector. See [http://groups.google.com/group/beagleboard/browse_thread/thread/5b8385f0bb1f63da] for more information.
+
'''Hardware issue on rev C3''' - the EHCI port on some rev C3 boards is unstable and will disconnect hubs/devices. Symptoms are: devices are disconnected from the port and cannot be reconnected without a reboot. It appears the shared 1.8&nbsp;V rail between the OMAP3530 and the power chip was getting noisy. Suggested solution (works on many boards) is adding a 22&nbsp;µF 0805 package SMT capacitor atop the existing capacitor on C97. If SMT parts are not available, some boards can be repaired by a 22&nbsp;µF through-hole capacitor across GND and VIO_1V8 on the expansion connector. See [http://groups.google.com/group/beagleboard/browse_thread/thread/5b8385f0bb1f63da] for more information.
  
 
===OTG===
 
===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.
+
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.
+
When using the OTG port in host mode, you must power the BeagleBoard using the +5&nbsp;V power jack. If you connect a USB hub, you'll probably also need external power for the USB hub as well, because according to the Hardware Reference manual the BeagleBoard OTG port only sources 100&nbsp;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".
+
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.]
 
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.]
Line 460: Line 461:
 
BeagleBoard can be connected to a DVI monitor using an HDMI male to DVI male cable.
 
BeagleBoard can be connected to a DVI monitor using an HDMI male to DVI male cable.
  
The BeagleBoard does not connect the HDMI shell to ground or any other BeagleBoard signal. This is not a problem with high-quality HDMI to DVI cables that connect all the ground wires. However, there are lots of cheap HDMI to HDMI cables that do not connect the ground wires and only use the shell as a combined shield and ground. To use one of these you would need to connect the BeagleBoard's HDMI shell to ground.  The BeagleBoard-xM connects the HDMI shell to frame ground, which is in turn connected to system ground through R119.  For more information, see this thread: [http://groups.google.com/group/beagleboard/browse_thread/thread/861da101804da56b].
+
The BeagleBoard does not connect the HDMI shell to ground or any other BeagleBoard signal. This is not a problem with high-quality HDMI to DVI cables that connect all the ground wires. However, there are lots of cheap HDMI to HDMI cables that do not connect the ground wires and only use the shell as a combined shield and ground. To use one of these you would need to connect the BeagleBoard's HDMI shell to ground.  The BeagleBoard-xM connects the HDMI shell to frame ground, which is in turn connected to system ground through R119.  For more information, see this thread: [http://groups.google.com/group/beagleboard/browse_thread/thread/861da101804da56b].
  
 
== Arduino ==
 
== Arduino ==
  
* [[BeagleBoard_Trainer|Trainer Board]] from [http://www.tincantools.com TinCanTools] has an arduino compatible Atmel AVR on board
+
* [[BeagleBoard_Trainer|Trainer Board]] from [http://www.tincantools.com TinCanTools] has an Arduino compatible Atmel AVR on board
* Arduino [http://arduino.cc/en/Main/ArduinoBoardNano Nano] uses a FTDI FT-232 based interface which is supported by the ftdi_sio kernel driver- [[BeagleBoard_with_Arduino|How To Notes]]
+
* Arduino [http://arduino.cc/en/Main/ArduinoBoardNano Nano] uses an FTDI FT-232 based interface which is supported by the ftdi_sio kernel driver- [[BeagleBoard_with_Arduino|How To Notes]]
 
* Arduino [http://arduino.cc/en/Main/ArduinoBoardUno Uno] uses a Atmel ATmega8U2 based interface which is supported by the cdc_acm kernel driver - [[BeagleBoard_with_Arduino|How To Notes]]
 
* Arduino [http://arduino.cc/en/Main/ArduinoBoardUno Uno] uses a Atmel ATmega8U2 based interface which is supported by the cdc_acm kernel driver - [[BeagleBoard_with_Arduino|How To Notes]]
  
Line 483: Line 484:
 
==Serial and USB boot==
 
==Serial and USB boot==
  
Historically, using OMAP3's boot ROM for serial and USB boot, there are several tools around. The newest are Nishanth' ''OMAP U-Boot Utils'', while there are still some older tools for serial boot and USB boot. It is also possible to access the [[u-boot environment variables in linux|u-boot env from linux]].
+
Historically, using OMAP3's boot ROM for serial and USB boot, there are several tools around. The newest are Nishanth' ''OMAP U-Boot Utils'', while there are still some older tools for serial boot and USB boot. It is also possible to access the [[u-boot environment variables in linux|U-Boot environment from Linux]].
  
 
===OMAP U-Boot Utils===
 
===OMAP U-Boot Utils===
Line 506: Line 507:
 
===USB boot===
 
===USB boot===
  
There is a patch to x-loader to allow it to do a USB boot. It can boot all the way to a Linux login.
+
There is a patch to x-loader to allow it to do a USB boot. It can boot all the way to a Linux login.
It's is used with a new version of omap3_usbload
+
It's is used with a new version of omap3_usbload.
  
 
* [http://members.efn.org/~rick/pub/x-loader-usb.tar.bz2 x-loader-usb]
 
* [http://members.efn.org/~rick/pub/x-loader-usb.tar.bz2 x-loader-usb]
Line 517: Line 518:
 
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 [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.
+
See the [[BeagleBoardRecovery#USB_recovery|USB recovery section]] on how to use USB boot for board recovery.
  
 
==NAND boot==
 
==NAND boot==
Line 529: Line 530:
 
===MMC/SD formatting===
 
===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.
+
As described in above MMC/SD boot description, you have to ''create a bootable partition on MMC/SD Card''. This can be done using, for example, Windows or Linux tools.
  
 
'''Windows'''
 
'''Windows'''
Line 545: Line 546:
 
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.
 
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''):
+
To mount second ext2 partition as root file system (e.g. containing contents of [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode rd-ext2.bin]) use kernel boot arguments (for example, in U-Boot using ''setenv bootargs''):
  
 
  console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait
 
  console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait
Line 551: Line 552:
 
===U-Boot booting===
 
===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):
+
If your MMC/SD card formatting is correct and you put [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode MLO, u-boot.bin and uImage] on the card you should get a U-Boot prompt after booting the BeagleBoard. For example (output from terminal program with 115200 8N1):
  
 
  ...40T.........XH.H.U�..Instruments X-Loader 1.41
 
  ...40T.........XH.H.U�..Instruments X-Loader 1.41
Line 573: Line 574:
 
  OMAP3 beagleboard.org #
 
  OMAP3 beagleboard.org #
  
Using this u-boot prompt, you now can start kernel uImage stored on MMC card manually:
+
Using this U-Boot prompt, you now can start kernel uImage stored on MMC card manually:
  
 
  OMAP3 beagleboard.org # mmc init
 
  OMAP3 beagleboard.org # mmc init
Line 592: Line 593:
 
On barebox you will have to generate it two time.
 
On barebox you will have to generate it two time.
  
The First time as a x-loader via defconfig:  omap3530_beagle_xload_defconfig
+
The first time as a x-loader via defconfig:  omap3530_beagle_xload_defconfig
  
the Second time as the real boot loader omap3530_beagle_defconfig
+
The second time as the real boot loader omap3530_beagle_defconfig
  
 
=Code=
 
=Code=
Line 604: Line 605:
 
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.  
 
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:
+
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/u-boot.bin u-boot.bin]
Line 616: Line 617:
 
'''Update on April 23 - 2010''': Sources for the X-Loader and U-Boot that ship on the BeagleBoard can be found at [http://gitorious.org/beagleboard-validation/ http://gitorious.org/beagleboard-validation/]. The U-Boot version found in that repository supersedes the one found at [http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/ http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/].
 
'''Update on April 23 - 2010''': Sources for the X-Loader and U-Boot that ship on the BeagleBoard can be found at [http://gitorious.org/beagleboard-validation/ http://gitorious.org/beagleboard-validation/]. The U-Boot version found in that repository supersedes the one found at [http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/ http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/].
  
'''Update on March 3 - 2011''': Sources for the SD card shipped with revisions Ax and Bx of the BeagleBoard-xM are in the Angstrom Distribution.  The script used to build the sources is documented at http://code.google.com/p/beagleboard/wiki/BeagleBoardDiagnosticsNext. The sources at http://gitorious.org/beagleboard-validation are meant to mimic what was used in the OpenEmbedded-based build.
+
'''Update on March 3 - 2011''': Sources for the SD card shipped with revisions Ax and Bx of the BeagleBoard-xM are in the Angstrom Distribution.  The script used to build the sources is documented at http://code.google.com/p/beagleboard/wiki/BeagleBoardDiagnosticsNext. The sources at http://gitorious.org/beagleboard-validation are meant to mimic what was used in the OpenEmbedded-based build.
  
 
Besides above binary and source images (TI's and communities one), for various parts of Beagle software stack there are community supported [http://git.or.cz/ git] repositories available.  
 
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.  
Line 649: Line 650:
 
  make CROSS_COMPILE=arm-none-linux-gnueabi-  
 
  make CROSS_COMPILE=arm-none-linux-gnueabi-  
  
Result will be a ~160k sized ''u-boot.bin'' in main directory.
+
Result will be a ~160&nbsp;KB sized ''u-boot.bin'' in the 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].
+
Note: Due to (patch and binary) size, the BeagleBoard splash screen was removed from upstream version. If you want it back, use [http://groups.google.com/group/beagleboard/browse_thread/thread/3ad9b803a3418624 U-Boot v1 BeagleBoard splash screen patch].
  
 
Note: For experimental U-Boot patches not ready for mainline yet, Steve's [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=summary Beagle U-Boot git repository] is used to test them. Get it by:
 
Note: For experimental U-Boot patches not ready for mainline yet, Steve's [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=summary Beagle U-Boot git repository] is used to test them. Get it by:
Line 660: Line 661:
  
 
Note: For changing the screen resolution there is one option modifying the file in "include/configs/omap3_beagle.h" and adjusting the maximum resolution before compiling as describe in [http://gitorious.org/linux-omap-dss2/linux/blobs/master/Documentation/arm/OMAP/DSS ARM OMAP2/3 Display Subsystem]
 
Note: For changing the screen resolution there is one option modifying the file in "include/configs/omap3_beagle.h" and adjusting the maximum resolution before compiling as describe in [http://gitorious.org/linux-omap-dss2/linux/blobs/master/Documentation/arm/OMAP/DSS ARM OMAP2/3 Display Subsystem]
 
  
 
Note: For beagleboard revision C4, above sources will not work. USB EHCI does not get powered, hence devices are not detected...
 
Note: For beagleboard revision C4, above sources will not work. USB EHCI does not get powered, hence devices are not detected...
get a patched version of u-boot from http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/
+
Get a patched version of u-boot from http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/
 
('''Update on April 23 - 2010''': This repository has been superseded by the U-Boot version found at [http://gitorious.org/beagleboard-validation/ http://gitorious.org/beagleboard-validation/])
 
('''Update on April 23 - 2010''': This repository has been superseded by the U-Boot version found at [http://gitorious.org/beagleboard-validation/ http://gitorious.org/beagleboard-validation/])
  
 
+
Note: If you want to activate I²C from the expansion header, modify board/ti/beagle/beagle.h :
Note: If you want to activate I2C from the expansion header, modify board/ti/beagle/beagle.h :
+
  
 
  MUX_VAL(CP(I2C2_SCL), (IEN  | PTU | EN | M4)) /*GPIO_168*/
 
  MUX_VAL(CP(I2C2_SCL), (IEN  | PTU | EN | M4)) /*GPIO_168*/
Line 688: Line 687:
 
  make distclean
 
  make distclean
 
  make ARCH=arm omap2plus_defconfig
 
  make ARCH=arm omap2plus_defconfig
  make ARCH=arm menuconfig  # only needed if you want to change the default configuration
+
  make ARCH=arm menuconfig  # Only needed if you want to change the default configuration
 
  make ARCH=arm uImage
 
  make ARCH=arm uImage
  
Line 696: Line 695:
  
 
If you use the OE toolchain and want to build outside of the OE tree you should do
 
If you use the OE toolchain and want to build outside of the OE tree you should do
 +
 
  ARCH=arm
 
  ARCH=arm
 
  export ARCH
 
  export ARCH
Line 703: Line 703:
 
  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- menuconfig  # only needed if you want to change the default configuration
 
  make CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage
 
  make CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage
 +
 
Note: the staging dir in the path is for mkimage. If you've built a kernel before with oe, the program should be there
 
Note: the staging dir in the path is for mkimage. If you've built a kernel before with oe, the program should be there
  
Line 709: Line 710:
 
===Experimental kernel patches and hacks===
 
===Experimental kernel patches and hacks===
  
Some beagle developers maintain their own kernel experimental patches and hacks not ready for upstream:
+
Some BeagleBoard developers maintain their own kernel experimental patches and hacks not ready for upstream:
  
 
* [http://veter-project.blogspot.com/2012/03/comfortable-kernel-workflow-on.html Build Angstrom 2.6.38 Kernel] to compile kernel modules natively, see [https://groups.google.com/forum/?fromgroups#!searchin/beagleboard/sam/beagleboard/eg6zYMcdMMA/KA3y0CS6n5cJ Angstrom package to natively compile kernel modules post] for corrections to the how-to.
 
* [http://veter-project.blogspot.com/2012/03/comfortable-kernel-workflow-on.html Build Angstrom 2.6.38 Kernel] to compile kernel modules natively, see [https://groups.google.com/forum/?fromgroups#!searchin/beagleboard/sam/beagleboard/eg6zYMcdMMA/KA3y0CS6n5cJ Angstrom package to natively compile kernel modules post] for corrections to the how-to.
 
* [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap Koen's collection of kernels patches for OE] and the [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap_git.bb list of relevant patches] '''(Broken Link)'''
 
* [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap Koen's collection of kernels patches for OE] and the [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap_git.bb list of relevant patches] '''(Broken Link)'''
* [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=shortlog;h=refs/heads/test Steve's kernel tree], a clone of main OMAP git with additional patches, mainly beagle audio (ASOC) related. '''(Broken Link)'''
+
* [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=shortlog;h=refs/heads/test Steve's kernel tree], a clone of main OMAP git with additional patches, mainly beagle audio (ASOC) related. '''(broken link)'''
* [http://git.mansr.com/?p=linux-omap;a=summary Mans' kernel tree], a clone of main OMAP git with additional patches, mainly display & framebuffer related. '''(Link to Unknown Project)'''
+
* [http://git.mansr.com/?p=linux-omap;a=summary Mans' kernel tree], a clone of the main OMAP Git repository with additional patches, mainly display & framebuffer related. '''(Link to Unknown Project)'''
* [http://www.bat.org/~tomba/linux-omap.html Tomi's kernel tree], a clone of main OMAP git with display sub-system patches, replacing the entire display driver with one that is the likely direction moving forward.
+
* [http://www.bat.org/~tomba/linux-omap.html Tomi's kernel tree], a clone of the main OMAP Git repository with display sub-system patches, replacing the entire display driver with one that is the likely direction moving forward.
  
 
=Compiler=
 
=Compiler=
Line 723: Line 724:
 
==ARM==
 
==ARM==
  
There is broad compiler support including gcc - please see [http://www.elinux.org/ARMCompilers ARM Compilers]
+
There is broad compiler support, including GCC - please see [http://www.elinux.org/ARMCompilers ARM Compilers]
  
 
==C64x+ DSP==
 
==C64x+ DSP==
Line 731: Line 732:
 
Note: my.TI account required. You may create an account [https://my.ti.com here]
 
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.
+
Note: An pld c6000 Linux compiler is available on the [ftp://ftp.ti.com/pub/cs/linux_cgt500.tar.gz TI FTP site]. It does NOT support c64x+ core in OMAP3 devices. Not recommended.
  
You can also 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.
+
You can also use the [http://focus.ti.com/dsp/docs/dspsupportaut.tsp?familyId=44&sectionId=3&tabId=416&toolTypeId=30 full-CCS free evaluation tools for 120 days], but they currently require purchase to upgrade to service release 9 to support full JTAG debugging with supported JTAG hardware.
  
 
See [[BeagleBoard/DSP_Howto| BeagleBoard DSP howto]] for information about how to use the DSP.
 
See [[BeagleBoard/DSP_Howto| BeagleBoard DSP howto]] for information about how to use the DSP.
Line 739: Line 740:
 
=Cortex A8 ARM features =
 
=Cortex A8 ARM features =
  
ARM Cortex-A8 in OMAP3 is a high performance dual-issue applications processor which reaches a performance of 2.0 DMIPS/MHz (compared to ARM11 at 1.2 DMIPS/MHz). It is ARM v7 architecture, which is fully backwards compatible with application code for previous ARM processors.
+
ARM Cortex-A8 in OMAP3 is a high performance dual-issue applications processor which reaches a performance of 2.0 DMIPS/MHz (compared to ARM11 at 1.2 DMIPS/MHz). It is ARM v7 architecture, which is fully backwards compatible with application code for previous ARM processors.
  
 
It includes a floating point unit (ARM VFPv3 architecture) and the ARM NEON SIMD instruction set.
 
It includes a floating point unit (ARM VFPv3 architecture) and the ARM NEON SIMD instruction set.
  
See [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] article for an intro into VFP-lite and NEON.
+
See [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] article for an introduction into VFP-lite and NEON.
  
 
===ARM NEON===
 
===ARM NEON===
  
NEON is a 64/128-bit wide SIMD vector extension for ARM, which has been architected to be an efficient C compiler target as well as being used from assembly language. It has 32x 64-bit registers (with a dual view as 16x 128-bit registers) which can hold the following datatypes:
+
NEON is a 64/128-bit wide SIMD vector extension for ARM, which has been architected to be an efficient C compiler target as well as being used from assembly language. It has 32x 64-bit registers (with a dual view as 16x 128-bit registers) which can hold the following datatypes:
 
* 64-bit signed/unsigned
 
* 64-bit signed/unsigned
 
* 32-bit signed/unsigned
 
* 32-bit signed/unsigned
Line 754: Line 755:
 
* 8-bit signed/unsigned
 
* 8-bit signed/unsigned
  
The key advantage of NEON is very high performance vector math processing, whilst being easy to program. It is the same thread of control as the ARM (but different instructions), and is supported by the same tools, debuggers and operating systems.
+
The key advantage of NEON is very high performance vector math processing, whilst being easy to program. It is the same thread of control as the ARM (but different instructions), and is supported by the same tools, debuggers and operating systems.
  
 
The NEON instruction set is documented in ARM's [http://infocenter.arm.com/help/topic/com.arm.doc.dui0204i/DUI0204I_rvct_assembler_guide.pdf RealView Compilation Tools Assembler Guide].
 
The NEON instruction set is documented in ARM's [http://infocenter.arm.com/help/topic/com.arm.doc.dui0204i/DUI0204I_rvct_assembler_guide.pdf RealView Compilation Tools Assembler Guide].
  
For NEON optimized libraries see [http://www.us.design-reuse.com/news/18429/aac-mp3-mpeg-4-h-264-fft-openmax-cortex-a8-neon-arm11-processors.html ARM Releases AAC, MP3, MPEG-4, H.264 and FFT OpenMAX DL Libraries, Highly Optimized for Cortex-A8/NEON and ARM11 Processors]. Note: Read the [http://www.arm.com/products/esd/openmax_v7libraries.html EULA].
+
For NEON optimized libraries, see [http://www.us.design-reuse.com/news/18429/aac-mp3-mpeg-4-h-264-fft-openmax-cortex-a8-neon-arm11-processors.html ARM Releases AAC, MP3, MPEG-4, H.264 and FFT OpenMAX DL Libraries, Highly Optimized for Cortex-A8/NEON and ARM11 Processors]. Note: Read the [http://www.arm.com/products/esd/openmax_v7libraries.html EULA].
  
 
NEON is used by various opensource projects:
 
NEON is used by various opensource projects:
* [http://www.libav.org/ Libav] - libavcodec used by mplayer, omapfbplay, and many other linux applications
+
* [http://www.libav.org/ Libav] - libavcodec used by mplayer, omapfbplay, and many other Linux applications
 
* libpixman - used by X.org and Mozilla & Webkit browsers to render text and graphics
 
* libpixman - used by X.org and Mozilla & Webkit browsers to render text and graphics
 
* [http://www.bluez.org/ Bluez] - official Linux Bluetooth stack
 
* [http://www.bluez.org/ Bluez] - official Linux Bluetooth stack
* [http://eigen.tuxfamily.org/ Eigen2] - C++ template library for linear algebra (matrix math etc)
+
* [http://eigen.tuxfamily.org/ Eigen2] - C++ template library for linear algebra (matrix math, etc.)
 
* [http://www.webmproject.org/code/ Webm] - Google's new opensource video codec
 
* [http://www.webmproject.org/code/ Webm] - Google's new opensource video codec
  
 
Compilation tools support for NEON:
 
Compilation tools support for NEON:
 
* ARM RVDS
 
* ARM RVDS
* gcc
+
* GCC
 
* [http://blog.llvm.org/2010/04/arm-advanced-simd-neon-intrinsics-and.html LLVM]
 
* [http://blog.llvm.org/2010/04/arm-advanced-simd-neon-intrinsics-and.html LLVM]
  
Line 777: Line 778:
  
 
1) '''VFPv3'''  Floating point instruction set (used for single/double precision scalar operations).
 
1) '''VFPv3'''  Floating point instruction set (used for single/double precision scalar operations).
These is used by gcc for C floating point operations on 'float' and 'double' since ANSI C can only describe scalar floating point, where there is only one operation at a time.
+
These is used by GCC for C floating point operations on 'float' and 'double' since ANSI C can only describe scalar floating point, where there is only one operation at a time.
  
2) '''NEON'''  [http://www.arm.com/products/multimedia/neon/ NEON] vectorized single precision operations (2 values in a D-register, or 4 values in a Q-register)
+
2) '''NEON'''  [http://www.arm.com/products/multimedia/neon/ NEON] vectorized single precision operations (two values in a D-register, or four values in a Q-register)
These can be use by gcc when -ftree-vectorize is enabled and -mfpu=neon is specified, and the code can be vectorized. In other cases the VFPv3 scalar ops will be used.
+
These can be use by GCC when -ftree-vectorize is enabled and -mfpu=neon is specified, and the code can be vectorized. In other cases, the VFPv3 scalar ops will be used.
  
 
ARM Cortex-A processors have separate floating point pipelines that handle these different instructions.
 
ARM Cortex-A processors have separate floating point pipelines that handle these different instructions.
  
On Cortex-A8, the designers' focus was on the NEON unit performance which can sustain 1 cycle/instr throughput (processing 2 single-precision values at once) for consumer multimedia. The scalar VFPv3 FPU cannot achieve this level of performance (cycle timings are in the Cortex-A8 TRM download), but it is still a lot better than doing floating point using integer instructions.
+
On Cortex-A8, the designers' focus was on the NEON unit performance which can sustain one cycle/instruction throughput (processing two single-precision values at once) for consumer multimedia. The scalar VFPv3 FPU cannot achieve this level of performance (cycle timings are in the Cortex-A8 TRM download), but it is still a lot better than doing floating point using integer instructions.
  
 
If you need the highest performance floating point on Cortex-A8, you need to use single precision and ensure the code uses the NEON vectorized instructions:
 
If you need the highest performance floating point on Cortex-A8, you need to use single precision and ensure the code uses the NEON vectorized instructions:
* use gcc with -ftree-vectorize  (possibly modify source code to make it vector friendly)
+
* Use GCC with -ftree-vectorize  (possibly modify source code to make it vector friendly)
* use NEON instrinsics (#include <arm_neon.h>, float32x2_t datatype and vmul_f32() etc)
+
* Use NEON instrinsics (#include <arm_neon.h>, float32x2_t datatype and vmul_f32() etc)
* use NEON asm directly
+
* Use NEON assembly language directly
  
On Cortex-A9, there is a much higher performance floating point unit which can sustain 1 cycle/instr throughput, with low result latencies. OMAP4 uses dual-core Cortex-A9+NEON which gives excellent floating-point performance for both FPU and NEON instructions.
+
On Cortex-A9, there is a much higher performance floating point unit which can sustain one cycle/instruction throughput, with low result latencies. OMAP4 uses dual-core Cortex-A9+NEON which gives excellent floating-point performance for both FPU and NEON instructions.
  
 
=Board recovery=
 
=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. Do not panic and think you somehow 'bricked' the board unless you did apply 12V to it.
+
If you played, for example, with the contents of the [http://www.sakoman.net/omap3/flash%20procedure.txt NAND], it might happen that the BeagleBoard doesn't boot any more (without pressing user button) due to broken NAND content. See [[BeagleBoardRecovery|BeagleBoard recovery]] article how to fix this. Do not panic and think you somehow 'bricked' the board unless you did apply 12&nbsp;V to it.
  
 
=Development environments=
 
=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.
+
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==
 
==OpenEmbedded==
Line 811: Line 812:
 
===One very important note:===   
 
===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:
+
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.
+
* Make an SD card with the [http://www.angstrom-distribution.org/demo/beagleboard Angstrom Demo files]. See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat Beagleboard Wiki Page] for more information on making the SD card.
* Put the SD Card in the Beagle, and boot up to the U-Boot Prompt.
+
* Put the SD card in the BeagleBoard, and boot up to the U-Boot prompt.
 
* Do the first six instructions in the [http://code.google.com/p/beagleboard/wiki/BeagleNANDFlashing Flashing Commands with U-Boot] section.   
 
* 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.
+
* Reboot the BeagleBoard to see that the new X-Loader is properly loaded.
  
This will update the X-Loader to a newer version that will automatically load uImage from the SD Card when present -- rather than always using the uImage in the Beagleboard NAND.
+
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==
 
==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].
+
The Eclipse [http://www.eclipse.org/cdt/ C Development Tools Project] provides a fully functional C and C++ integrated development environment (IDE) for the Eclipse platform. The Eclipse [http://www.eclipse.org/dsdp/tm/ DSDP Target Managment Project] provides a "Remote System Explorer" (RSE) plugin that simplifies downloading files to the BeagleBoard and editing files on the BeagleBoard within the Eclipse IDE. A Linux Target Agent is available as part of the [http://wiki.eclipse.org/DSDP/TM/TCF_FAQ Target Communications Framework (TCF) component]. Information on how RSE is used for, for example, Gumstix development is described in [http://groups.google.com/group/beagleboard/browse_thread/thread/509831f7c24cb79f# this post].
  
See also [[BeagleBoardEclipse|Using Eclipse with Beagle]] (for JTAG debugging)
+
See also [[BeagleBoardEclipse|Using Eclipse with Beagle]] (for JTAG debugging).
  
 
==Android==
 
==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.
+
The [http://source.android.com Android] platform is a software stack for mobile devices including an operating system, middleware and key applications. Developers can create applications for the platform using the [http://code.google.com/android/ Android SDK]. Applications are written using the Java programming language and run on Dalvik, a custom virtual machine designed for embedded use which runs on top of a Linux kernel.
  
 
There are several resources for Android on OMAP (Beagle) available:
 
There are several resources for Android on OMAP (Beagle) available:
Line 837: Line 838:
 
[http://beagleboard.org/project/android Beagleboard.org's Android project page] [http://groups.google.com/group/beagleboard/browse_thread/thread/7b422f113ce489b5 announced], the successful porting of Android on Beagle board by [http://embinux.com EMBINUX&trade;] Team. The [http://labs.embinux.org/git/ source code] and [http://www.embinux.com/download_beagle.php binaries] are available for download and review.  
 
[http://beagleboard.org/project/android Beagleboard.org's Android project page] [http://groups.google.com/group/beagleboard/browse_thread/thread/7b422f113ce489b5 announced], the successful porting of Android on Beagle board by [http://embinux.com EMBINUX&trade;] Team. The [http://labs.embinux.org/git/ source code] and [http://www.embinux.com/download_beagle.php binaries] are available for download and review.  
  
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.
+
Detailed instructions, for porting Android on BeagleBoard, are available [http://labs.embinux.org/index.php/Main_Page here]. Current release supports input devices (keyboard/mouse), network and sound.
  
You can [http://in.youtube.com/watch?v=nADn_vNVEKw watch Android booting] on Beagle Board.
+
You can [http://in.youtube.com/watch?v=nADn_vNVEKw watch Android booting] on BeagleBoard.
  
 
'''Android on OMAP wiki'''
 
'''Android on OMAP wiki'''
  
Wiki page for Andorid on OMAP can be found [[Android on OMAP|here]]
+
Wiki page for Andorid on OMAP can be found [[Android on OMAP|here]].
  
 
'''0xdroid'''
 
'''0xdroid'''
  
[http://gitorious.org/0xdroid  0xdroid], the enhanced version of Android on Beagleboard by [http://0xlab.org  0xlab]. The [http://gitorious.org/0xdroid  source code], [http://downloads.0xlab.org/ pre-built binaries], and [http://code.google.com/p/0xdroid/issues/list issue tracker] are available for review and reference.
+
[http://gitorious.org/0xdroid  0xdroid], the enhanced version of Android on BeagleBoard by [http://0xlab.org  0xlab]. The [http://gitorious.org/0xdroid  source code], [http://downloads.0xlab.org/ pre-built binaries], and [http://code.google.com/p/0xdroid/issues/list issue tracker] are available for review and reference.
  
The latest development supports OMAP audio, OMAP video overlays, ARM Cortex A8 NEON/Thumb2 performance optimizations, mouse cursor, hot-pluggable USB keyboard & mouse, user-friendly installer for system image, and various Android tweaks. Detailed instructions for 0xdroid are available through [http://code.google.com/p/0xdroid/wiki/MainPage Google Code wiki].
+
The latest development supports OMAP audio, OMAP video overlays, ARM Cortex A8 NEON/Thumb2 performance optimizations, mouse cursor, hot-pluggable USB keyboard & mouse, user-friendly installer for system image, and various Android tweaks. Detailed instructions for 0xdroid are available through [http://code.google.com/p/0xdroid/wiki/MainPage Google Code wiki].
  
You can watch 0xdroid demo video on Beagle Board:
+
You can watch the 0xdroid demo video on the BeagleBoard:
 
  * [http://www.youtube.com/watch?v=v6wdTOHrwQw 0xdroid demo video (1)]
 
  * [http://www.youtube.com/watch?v=v6wdTOHrwQw 0xdroid demo video (1)]
 
  * [http://www.youtube.com/watch?v=ol9LWBKXXwQ 0xdroid demo video (2)]
 
  * [http://www.youtube.com/watch?v=ol9LWBKXXwQ 0xdroid demo video (2)]
Line 858: Line 859:
 
==Mamona==
 
==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.
+
[http://dev.openbossa.org/trac/mamona/wiki Mamona] is an embedded Linux distribution for ARM EABI. The main goal of the Mamona Project is to offer a completely open source alternative/experimental platform for [http://maemo.org/ Maemo] using only free and open source components. Mamona [http://rsalveti.wordpress.com/2008/09/12/mamona-02-is-out 0.2] [http://franciscoalecrim.com/blog/2008/07/29/mamona-working-with-beagleboard/ supports] [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12013&contentId=28741 OMAP3430 Software Development Platform (SDP)], so you can also use it at Beagle (OMAP3530), too. Work is being done to officially support BeagleBoard.
  
 
==Ubuntu==
 
==Ubuntu==
Line 878: Line 879:
 
==Scratchbox==
 
==Scratchbox==
  
[http://www.scratchbox.org/ Scratchbox] is a cross-compilation toolkit designed to make embedded Linux application development easier. It also provides a full set of tools to integrate and cross-compile an entire Linux distribution. See [http://felipec.wordpress.com/2009/06/07/installing-scratchbox-1-and-2-for-arm-cross-compilation/ Felipe's Scratbox 1 and 2 intro], too.
+
[http://www.scratchbox.org/ Scratchbox] is a cross-compilation toolkit designed to make embedded Linux application development easier. It also provides a full set of tools to integrate and cross-compile an entire Linux distribution. See [http://felipec.wordpress.com/2009/06/07/installing-scratchbox-1-and-2-for-arm-cross-compilation/ Felipe's Scratbox 1 and 2 introduction], too.
  
 
=Software hints=
 
=Software hints=
  
This section collects hints, tips & tricks for various software components running on beagle.
+
This section collects hints, tips & tricks for various software components running on BeagleBoard.
 
* [[RPM_jffs2_issue]]
 
* [[RPM_jffs2_issue]]
 +
 
==QEMU==
 
==QEMU==
  
Line 898: Line 900:
 
==lmbench==
 
==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.
+
Avik posted a detailed [http://groups.google.com/group/beagleboard/browse_thread/thread/c8b8f07ce61161a1 step-by-step procedure] to run [http://sourceforge.net/project/showfiles.php?group_id=14418 lmbench] on BeagleBoard.
  
 
==Mediaplayer (FFmpeg)==
 
==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.
+
There is a thread how to get a [http://groups.google.com/group/beagleboard/browse_thread/thread/9b8025fc15120fd9# mediaplayer] with NEON optimization (FFmpeg) to run on BeagleBoard. Includes compiler hints and patches.
  
 
==Java==
 
==Java==
Line 951: Line 953:
 
Oracle states in the [https://blogs.oracle.com/henrik/entry/oracle_releases_jdk_for_linux FAQ] that they are working on hard float support, as well as a JavaFX 2 port to Linux/ARM.
 
Oracle states in the [https://blogs.oracle.com/henrik/entry/oracle_releases_jdk_for_linux FAQ] that they are working on hard float support, as well as a JavaFX 2 port to Linux/ARM.
  
== Booting Android (TI_Android_DevKit) from USB stick ==
+
== Booting Android (TI_Android_DevKit) from a USB stick ==
 
'''Please note'''
 
'''Please note'''
* This procedure was tested on beagleboard-xm revision B(A3)
+
* This procedure was tested on BeagleBoard-xM revision B(A3)
* sdcard will be still needed to load kernel.
+
* An SD card will be still needed to load the kernel.
* sdcard will contain boot parameters for kernel to use usb stick as root filesystem
+
* An SD card  will contain boot parameters for the kernel to use a USB stick as the root filesystem
  
 
'''Procedure'''
 
'''Procedure'''
# Download Android Froyo for beagleboard-xm from [http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_00_00/index_FDS.html TI]
+
# Download Android Froyo for BeagleBoard-xM from [http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_00_00/index_FDS.html TI]
# Follow the installation procedure for sdcard card.
+
# Follow the installation procedure for an SD card card.
# Test if froyo is working with your beagleboard-xm with sdcard.
+
# Test if Froyo is working with your BeagleBoard-xM with an SD card.
# You will notice that android has slow performance. That is why we will install root filesystem on usb stick.
+
# You will notice that Android has a slow performance. That is why we will install root filesystem on a USB stick.
# Format your usb stick and create one ext3 partition.
+
# Format your USB stick and create one ext3 partition.
 
# Mount newly created ext3 partition and extract TI's root filesystem to it: sudo tar jxvf rootfs_am37x.tar.bz2 -C /media/ROOT
 
# Mount newly created ext3 partition and extract TI's root filesystem to it: sudo tar jxvf rootfs_am37x.tar.bz2 -C /media/ROOT
# Unmount flashdisk and insert it into beagleboard.
+
# Unmount flashdisk and insert it into the BeagleBoard.
# Mount your sdcard to your computer.
+
# Mount your SD card to your computer.
# Now we need to tell beagleboard to use root filesystem from /dev/sda1 partition instead of sdcard partition that is done by overwriting boot.scr on sdcard with [http://www.apksoft.eu/android/boot.scr this one]
+
# Now we need to tell the BeagleBoard to use the root filesystem from the /dev/sda1 partition instead of the SD card partition. That is done by overwriting boot.scr on the SD card with [http://www.apksoft.eu/android/boot.scr this one]
# Unmount sdcard insert it into beagleboard and test.
+
# Unmount the SD card and insert it into the BeagleBoard and test.
  
 
=Graphics accelerator=
 
=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.
+
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:
 
Tutorial:
Line 979: Line 981:
 
Some videos:
 
Some videos:
  
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle working with Linux 2.6.27]
+
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on BeagleBoard working with Linux 2.6.27]
 
* [http://www.youtube.com/watch?v=24TXpqa9jG0&feature=related OpenGL ES 2.0 shader effects on OMAP3]
 
* [http://www.youtube.com/watch?v=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=-UFUbqoNgs8&feature=related 3D User Interface on OMAP3 Platform]
Line 997: Line 999:
 
=Links=
 
=Links=
 
==Home page==
 
==Home page==
[http://beagleboard.org/ beagleboard.org] (beagle board home)
+
[http://beagleboard.org/ beagleboard.org] (BeagleBoard home)
 
* Using [http://www.google.de/ Google] you can search beagleboard.org (including [http://www.beagleboard.org/irclogs/ IRC logs]) using ''site:beagleboard.org <search term>''
 
* 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>''
  
Line 1,010: Line 1,012:
 
* [http://code.google.com/p/beagleboard/ Beagle at code.google.com]
 
* [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://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://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for BeagleBoard]
* [http://beagleboard.org/resources Beagleboard resources page with hw docs]
+
* [http://beagleboard.org/resources BeagleBoard resources page with hardware documentation]
 
* Some [http://www.rasterman.com/ performance comparison] of BeagleBoard Rev. B with some other ARM/PC systems.
 
* 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]
 
* OMAP3 pinmux [http://www.hy-research.com/omap3_pinmux.html setup]
Line 1,017: Line 1,019:
  
 
==Contact and communication==
 
==Contact and communication==
* [http://groups.google.com/group/beagleboard Beagle board discussion list]
+
* [http://groups.google.com/group/beagleboard BeagleBoard discussion list]
* [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker]
+
* [http://code.google.com/p/beagleboard/issues/list BeagleBoard open point list and issue tracker]
* [http://beagleboard.blogspot.com/ Beagle board blog]
+
* [http://beagleboard.blogspot.com/ BeagleBoard blog]
* [http://feeds.feedburner.com/BeagleBoard Beagle board RSS feed]
+
* [http://feeds.feedburner.com/BeagleBoard BeagleBoard RSS feed]
 
* Chat:
 
* Chat:
** [http://beagleboard.org/chat Beagle Board chat]
+
** [http://beagleboard.org/chat BeagleBoard chat]
 
** IRC: #beagle channel on irc.freenode.net
 
** IRC: #beagle channel on irc.freenode.net
 
** [http://www.beagleboard.org/irclogs/index.php IRC archive]
 
** [http://www.beagleboard.org/irclogs/index.php IRC archive]
 
* [http://www.beaglesride.org/ Beagles Ride], a site about building a community around the BeagleBoard focused on in vehicle applications
 
* [http://www.beaglesride.org/ Beagles Ride], a site about building a community around the BeagleBoard focused on in vehicle applications
* [http://www.beagleboard.de/ German Beagle Board Forum and Wiki]
+
* [http://www.beagleboard.de/ German BeagleBoard Forum and Wiki]
  
 
==TI resources==
 
==TI resources==
Line 1,037: Line 1,039:
 
* [http://del.icio.us/tag/beagleboard+peripheral+verified Verified peripherals for BeagleBoard]
 
* [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]
 
* [http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt OMAP3430 Linux Power Management presentation]
 +
 
==Articles==
 
==Articles==
* [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article about Beagle]
+
* [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article about BeagleBoard]
 
* [http://www.linuxdevices.com/news/NS8479495970.html LinuxDevices article about Digi-Key launch]
 
* [http://www.linuxdevices.com/news/NS8479495970.html LinuxDevices article about Digi-Key launch]
* [http://www.linuxdevices.com/news/NS5682470737.html LinuxDevices article about Beagle Rev C, Beagle MID from HY Research, Touch Book and Sponsored Projects Contest]
+
* [http://www.linuxdevices.com/news/NS5682470737.html LinuxDevices article about BeagleBoard Rev C, Beagle MID from HY Research, Touch Book and Sponsored Projects Contest]
 
* [http://www.linuxjournal.com/article/10607 Linuxjournal article on the BeagleBoard]
 
* [http://www.linuxjournal.com/article/10607 Linuxjournal article on the BeagleBoard]
  
Line 1,046: Line 1,049:
 
* [[OMAP_and_DaVinci_Software_for_Dummies|OMAP and DaVinci Software for Dummies]]
 
* [[OMAP_and_DaVinci_Software_for_Dummies|OMAP and DaVinci Software for Dummies]]
  
==Beagle based training materials==
+
==BeagleBoard based training materials==
 
* http://free-electrons.com/blog/beagle-labs/
 
* http://free-electrons.com/blog/beagle-labs/
  
==Past Beagle events==
+
==Past BeagleBoard events==
* TIDC, February 26-28, 2008: [http://www.beagleboard.org/uploads/tidc_opensource.pdf Slides from TI developer conference (TIDC) open source session], covering also beagle board
+
* TIDC, February 26-28, 2008: [http://www.beagleboard.org/uploads/tidc_opensource.pdf Slides from TI developer conference (TIDC) open source session], covering also BeagleBoard
 
* [http://www.lugradio.org/live/USA2008/ LUG RADIO Live USA 2008, April 12-13, 2008]: [http://www.beagleboard.org/uploads/lugradio_20080411.PPT TI/Beagle Presentation] and [http://forums.lugradio.org/viewtopic.php?f=4&t=4094&st=0&sk=t&sd=a&sid=d69cc807569ab41e33f93af698c536b8&start=15#p41549 video]
 
* [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]
 
* 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://lugradio.org/live/UK2008/travel LugRadio Live UK 2008], July 19 - July 20, 2008: [http://www.flickr.com/photos/koenkooi/tags/lugradiolive/ Koen's pictures] showing e.g. [http://www.bigbuckbunny.org/index.php/download/ Big Buck BUNNY] playing at BeagleBoard. [http://linuxoutlaws.com/podcast/48 Interview with Linux Outlaws (52:06)] and the [http://www.youtube.com/watch?v=m9xVbntl-DY video]
 
* [http://osscamp.in/index.php/OSScamp_Bengaluru_Mobile_2008 OSScamp Bengaluru Mobile 2008], July 19, 2008
 
* [http://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]
+
* [http://www.linuxworldexpo.com LinuxWorld Conference & Expo], August 4 - August 7, 2008: [http://www.flickr.com/photos/jadon/sets/72157606586084668/ pictures with living BeagleBoard] and from [http://www.flickr.com/photos/linuxjournal/2738316951/in/set-72157606634486338/ Linux Journal's photostream]
 
* BeagleBoard.org event at Jillian's during LinuxWorldExpo, August 5, 2008, 5:30-7:30 pm
 
* 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]
 
* [http://barcamp.pbwiki.com/BarCampHouston3 BarCamp Houston 3], August 9, 2008, 9:00 A.M.: [http://www.flickr.com/photos/jadon/sets/72157606656532041/ pictures]
Line 1,068: Line 1,071:
 
* [[BeagleBoard/contest|BeagleBoard contest]] #1: Create a cool BeagleBoard application and win a Rev C1! Closed, ran until January 9, 2009
 
* [[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]]
 
* [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!
+
* [[BeagleBoard/contest|BeagleBoard contest #2]], until February 27, 2009: Create a cool BeagleBoard application and win a Rev C2!
 
* [http://groups.google.com/group/beagleboard/browse_thread/thread/b15cf8a5797c73a2 Silica - Free TI - ARM OMAP Workshop], Brussels, Europe, March 31st 2009
 
* [http://groups.google.com/group/beagleboard/browse_thread/thread/b15cf8a5797c73a2 Silica - Free TI - ARM OMAP Workshop], Brussels, Europe, March 31st 2009
 
* SILICA's [http://www.silica.com/events/seminars/seminar-overview/ti-omap-piccolo-poing.html Texas Instruments 2-in-1 Seminar: OMAP & Piccolo], May 13th 2009: Poing (Munich) - Germany
 
* SILICA's [http://www.silica.com/events/seminars/seminar-overview/ti-omap-piccolo-poing.html Texas Instruments 2-in-1 Seminar: OMAP & Piccolo], May 13th 2009: Poing (Munich) - Germany
* 24th until 27th June 2009: [http://www.linuxtag.org/2009/en.html Linux Tag Germany] with [http://groups.google.com/group/beagleboard/msg/27fefef5f1d2ef73 TI booth] and [http://www.linuxtag.org/2009/en/program/freies-vortragsprogramm/all-events/details.html?talkid=183 Beagle presentation]
+
* 24th until 27th June 2009: [http://www.linuxtag.org/2009/en.html Linux Tag Germany] with [http://groups.google.com/group/beagleboard/msg/27fefef5f1d2ef73 TI booth] and [http://www.linuxtag.org/2009/en/program/freies-vortragsprogramm/all-events/details.html?talkid=183 BeagleBoard presentation]
 
* until 31st July 2009: [http://www.cranessoftware.com/services/training/beagledesigncontest.html BeagleBoard Design Contest INDIA Edition] ([http://beagleboard.blogspot.com/2009/04/beagleboard-design-contest-india.html blog entry])
 
* until 31st July 2009: [http://www.cranessoftware.com/services/training/beagledesigncontest.html BeagleBoard Design Contest INDIA Edition] ([http://beagleboard.blogspot.com/2009/04/beagleboard-design-contest-india.html blog entry])
 
* TI Technology Day Dallas, Tex. on June 16 will held a [http://www.linuxdevices.com/news/NS5682470737.html BeagleBoard users group meeting] (see section ''Availability'').
 
* TI Technology Day Dallas, Tex. on June 16 will held a [http://www.linuxdevices.com/news/NS5682470737.html BeagleBoard users group meeting] (see section ''Availability'').
Line 1,077: Line 1,080:
 
* 22.- 23.08.2009, Sankt Augustin, Germany: [http://www.froscon.de/en/ FrOSCon 2009] ([http://groups.google.com/group/beagleboard/browse_thread/thread/6aee27a7d121f4f4# call for papers])
 
* 22.- 23.08.2009, Sankt Augustin, Germany: [http://www.froscon.de/en/ FrOSCon 2009] ([http://groups.google.com/group/beagleboard/browse_thread/thread/6aee27a7d121f4f4# call for papers])
  
==Beagle wiki pages==
+
==BeagleBoard wiki pages==
 
* [[BeagleBoardJTAG|BeagleBoard JTAG]] and [[OMAP3530_ICEPICK|OMAP3530_ICEPICK]] about JTAG on BeagleBoard
 
* [[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
+
* [[BeagleBoardOpenOCD|BeagleBoard OpenOCD]] has information about status and usage of open source JTAG software OpenOCD with Beagle
 
* [[Mount_BeagleBoard_Root_Filesystem_over_NFS_via_USB|Mount BeagleBoard root file system over NFS via USB]]
 
* [[Mount_BeagleBoard_Root_Filesystem_over_NFS_via_USB|Mount BeagleBoard root file system over NFS via USB]]
 
* [[BeagleBoardSugar|Sugar on BeagleBoard]]
 
* [[BeagleBoardSugar|Sugar on BeagleBoard]]
Line 1,086: Line 1,089:
 
* [[BeagleBoardOpenCV|Using OpenCV computer vision library with BeagleBoard]]
 
* [[BeagleBoardOpenCV|Using OpenCV computer vision library with BeagleBoard]]
 
* [[U-boot_musb_gadget_support|U-boot musb gadget support]]
 
* [[U-boot_musb_gadget_support|U-boot musb gadget support]]
* [[BeagleBoard-JP|Japanese translation of this Beagle page]]
+
* [[BeagleBoard-JP|Japanese translation of this BeagleBoard page]]
 
* [[BeagleEPD|BeagleBoard E-Ink Platform Driver]]
 
* [[BeagleEPD|BeagleBoard E-Ink Platform Driver]]
 
* [[BeagleBoardFedora|Random hacking notes for getting Fedora 10 to kinda work with the BeagleBoard]]
 
* [[BeagleBoardFedora|Random hacking notes for getting Fedora 10 to kinda work with the BeagleBoard]]
 
* BeagleBoard specific [[BeagleBoard/GSoC|Google Summer of Code 2009]] page, [[BeagleBoard/Ideas-2009|GSoC project ideas]] and [[BeagleBoard/GSoC/Application|GSoc application]]
 
* BeagleBoard specific [[BeagleBoard/GSoC|Google Summer of Code 2009]] page, [[BeagleBoard/Ideas-2009|GSoC project ideas]] and [[BeagleBoard/GSoC/Application|GSoc application]]
 
* [[BeagleBoard/DSP_Clarification|Info about the various Linux DSP systems for OMAP chips]]
 
* [[BeagleBoard/DSP_Clarification|Info about the various Linux DSP systems for OMAP chips]]
* [http://www.hervanta.com/stuff/Beaglebot Beaglebot]: build an experimental robotics project with Beagle
+
* [http://www.hervanta.com/stuff/Beaglebot Beaglebot]: build an experimental robotics project with BeagleBoard
 
* [http://code.google.com/p/beagleboard/w/list code.google.com BeagleBoard wiki]
 
* [http://code.google.com/p/beagleboard/w/list code.google.com BeagleBoard wiki]
 
* '''[[BeagleBoard/contest|BeagleBoard contest]]'''
 
* '''[[BeagleBoard/contest|BeagleBoard contest]]'''
Line 1,100: Line 1,103:
 
* [http://wh1t3s.com/2009/05/11/beagleboard-as-usb-mass-storage-device-via-usb-otg/ BeagleBoard as USB Mass Storage Device via USB OTG]
 
* [http://wh1t3s.com/2009/05/11/beagleboard-as-usb-mass-storage-device-via-usb-otg/ BeagleBoard as USB Mass Storage Device via USB OTG]
 
* [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm BeagleBoard as solar powered computer]
 
* [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm BeagleBoard as solar powered computer]
* [http://blog.makezine.com/archive/2009/02/blinking_leds_with_the_beagle_board.html Blinking LEDs with the Beagle Board] from Make:Online
+
* [http://blog.makezine.com/archive/2009/02/blinking_leds_with_the_beagle_board.html Blinking LEDs with the BeagleBoard] from Make:Online
* [http://www.crashcourse.ca/wiki/index.php/BeagleBoard Robert's private Beagle wiki] (please don't add anything there, do it here. It will help to avoid scattering. Thanks!)
+
* [http://www.crashcourse.ca/wiki/index.php/BeagleBoard Robert's private BeagleBoard wiki] (please don't add anything there, do it here. It will help to avoid splittering. Thanks!)
 
* [http://felipec.wordpress.com/2009/03/26/omap3-public-dsp-binaries-now-work/ Felipe's blog] about D1 MPEG-4 decoding using less than 15% of CPU with help of DSP
 
* [http://felipec.wordpress.com/2009/03/26/omap3-public-dsp-binaries-now-work/ Felipe's blog] about D1 MPEG-4 decoding using less than 15% of CPU with help of DSP
 
* [http://www.syspire.de/node/3 Embedded Mediacenter] based on BeagleBoard (German)
 
* [http://www.syspire.de/node/3 Embedded Mediacenter] based on BeagleBoard (German)
* [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] with VFP-lite and NEON intro
+
* [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] with VFP-lite and NEON introduction
* [http://particolarmente-urgentissimo.blogspot.com/2009/09/beagleboard-setting-date-via-gps.html Beagleboard setting date via GPS]
+
* [http://particolarmente-urgentissimo.blogspot.com/2009/09/beagleboard-setting-date-via-gps.html BeagleBoard setting date via GPS]
 
* [http://free-electrons.com/blog/beagle-labs/ Complete embedded Linux training labs] on the BeageBoard
 
* [http://free-electrons.com/blog/beagle-labs/ Complete embedded Linux training labs] on the BeageBoard
 
* [[BeagleBoardPWM]] Details about PWM on the BeagleBoard.
 
* [[BeagleBoardPWM]] Details about PWM on the BeagleBoard.
 
* [[BeagleBrick]] software defined radio project
 
* [[BeagleBrick]] software defined radio project
  
==Beagle photos==
+
==BeagleBoard photos==
* [http://www.flickr.com/groups/beagleboard/pool/ Beagle board pictures at flickr]
+
* [http://www.flickr.com/groups/beagleboard/pool/ BeagleBoard pictures at flickr]
* [http://www.flickr.com/photos/32615155@N00/2439256116/ Beagle board and USRP]
+
* [http://www.flickr.com/photos/32615155@N00/2439256116/ BeagleBoard and USRP]
* [http://www.flickr.com/photos/nishanthmenon/2438406603/ Modify SDP3430 QUART cable for beagle]
+
* [http://www.flickr.com/photos/nishanthmenon/2438406603/ Modify SDP3430 QUART cable for BeagleBoard]
* [http://www.flickr.com/photos/koenkooi/2695061759/ MythTV on Beagle]
+
* [http://www.flickr.com/photos/koenkooi/2695061759/ MythTV on BeagleBoard]
==Beagle videos==
+
 
* [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings]
+
==BeagleBoard videos==
* [http://www.youtube.com/watch?v=cXr-D1wROfQ Beagleboard in the Living Room]
+
* [http://uk.youtube.com/watch?v=fL_XMieanSc BeagleBoard Beginnings]
* [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu]
+
* [http://www.youtube.com/watch?v=cXr-D1wROfQ BeagleBoard in the Living Room]
* [http://uk.youtube.com/watch?v=TUYOjRGYeYU testsprite with beagleboard]
+
* [http://uk.youtube.com/watch?v=FuVwh_VrIxk BeagleBoard 3D, Angstrom, and Ubuntu]
* [http://uk.youtube.com/watch?v=9Z4ZTovtFKk Beagleboard LED demo]
+
* [http://uk.youtube.com/watch?v=TUYOjRGYeYU testsprite with BeagleBoard]
* [http://uk.youtube.com/watch?v=R33dzREZGEk LCD2USB attached to a 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=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=-tUBXD-KRp4 BeagleBoard Running Angstrom (VGA) on DLP Pico Projector]
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle working with Linux 2.6.27]
+
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on BeagleBoard working with Linux 2.6.27]
 
* Not on Beagle OMAP3530: [http://youtube.com/watch?v=5i9cWOK1spw Ubuntu 7.04 on on OMAP3430 SDP]
 
* 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]
+
* [http://in.youtube.com/watch?v=nADn_vNVEKw BeagleBoard booting Android]
* [http://www.youtube.com/watch?v=UHQdUS0i-nw Beagleboard, SGX, and libfreespace demo]
+
* [http://www.youtube.com/watch?v=UHQdUS0i-nw BeagleBoard, SGX, and libfreespace demo]
 +
 
 +
==BeagleBoard manufacturing==
 +
* [http://www.youtube.com/watch?v=C-CwkjT9z_0&feature=related BeagleBoard Solder Paste Screening]
 +
* [http://www.youtube.com/watch?v=9LLjDovIG2M&feature=related BeagleBoard Assembly Inspection]
 +
* [http://www.youtube.com/watch?v=sbOZfBnoVnM&feature=related BeagleBoard Functional Test]
 +
* [http://www.youtube.com/watch?v=cvDtXmJJcEI&feature=related BeagleBoard Reflow]
 +
* [http://www.youtube.com/watch?v=W2o4NTASxN0&feature=related BeagleBoard Assembly at Circuitco]
  
==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]
 
 
=Other OMAP boards=
 
=Other OMAP boards=
* OMAP 4430 Based 40X40mm size   [http://www.tianyeit.com CIP410] Computer In Package  from [http://www.tianyeit.com Tianyeit]
+
* OMAP 4430 Based 40X40&nbsp;mm size [http://www.tianyeit.com CIP410] computer in package from [http://www.tianyeit.com Tianyeit]
* OMAP DM3730/OMAP3530 Based  40X40mm size  [http://www.tianyeit.com CIP312] Computer In Package from [http://www.tianyeit.com Tianyeit]
+
* OMAP DM3730/OMAP3530 Based  40X40mm size  [http://www.tianyeit.com CIP312] Computer In Package from [http://www.tianyeit.com Tianyeit]
 
* OMAP 4430 based [[PandaBoard]]
 
* OMAP 4430 based [[PandaBoard]]
 
* OMAP-L138 Based [[Hawkboard]]
 
* OMAP-L138 Based [[Hawkboard]]
 
* OMAP3530 based [http://www.armkits.com/Product/devkit8000.asp DevKit8000] development board from [http://www.armkits.com Embest]
 
* OMAP3530 based [http://www.armkits.com/Product/devkit8000.asp DevKit8000] development board from [http://www.armkits.com Embest]
* OMAP3530 based [http://www.armkits.com/Product/sbc8100.asp SBC8100] Single Board Computer from [http://www.armkits.com Embest]
+
* OMAP3530 based [http://www.armkits.com/Product/sbc8100.asp SBC8100] Single-board computer from [http://www.armkits.com Embest]
 
* OMAP1 OMAP5912 (ARM9 + C5x DSP) based [[OSK|OSK]] board.
 
* OMAP1 OMAP5912 (ARM9 + C5x DSP) based [[OSK|OSK]] board.
 
* OMAP3 OMAP3430 based [https://gforge.ti.com/gf/project/omapzoom/wiki/?pagename=HardwareInformation Zoom MDK], which has been superseded by the [http://www.logicpd.com/products/development-kits/texas-instruments-zoom%E2%84%A2-omap34x-ii-mdp Zoom II], and other [http://www.logicpd.com/products LogicPD kits].
 
* OMAP3 OMAP3430 based [https://gforge.ti.com/gf/project/omapzoom/wiki/?pagename=HardwareInformation Zoom MDK], which has been superseded by the [http://www.logicpd.com/products/development-kits/texas-instruments-zoom%E2%84%A2-omap34x-ii-mdp Zoom II], and other [http://www.logicpd.com/products LogicPD kits].
Line 1,159: Line 1,164:
 
* OMAP3 based [http://www.kwikbyte.com/KBOC.html KwikByte 35XX System Module]
 
* OMAP3 based [http://www.kwikbyte.com/KBOC.html KwikByte 35XX System Module]
 
* OMAP3530 based [[DevKit8000]], a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard)
 
* OMAP3530 based [[DevKit8000]], a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard)
* OMAP3530 based [http://www.igep-platform.com/ IGEPv2 Platform], a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, wifi+bluetooth.
+
* OMAP3530 based [http://www.igep-platform.com/ IGEPv2 Platform], a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, Wi-Fi and Bluetooth.
 
* OMAP35x based [http://www.ultratronik.de/mmi-rechnerplattformen.html MMI4 from Ultratronik]
 
* OMAP35x based [http://www.ultratronik.de/mmi-rechnerplattformen.html MMI4 from Ultratronik]
 
* OMAP35x based [http://www.technexion.com/index.php/tao-3530 TAO-3530 from TechNexion], also sold in North America through [http://www.robotcraft.ca/webshop/index.php?manufacturers_id=21 Robotcraft Systems]
 
* OMAP35x based [http://www.technexion.com/index.php/tao-3530 TAO-3530 from TechNexion], also sold in North America through [http://www.robotcraft.ca/webshop/index.php?manufacturers_id=21 Robotcraft Systems]
Line 1,165: Line 1,170:
 
* OMAP35x based [[EGS3530]],a Chinese BeagleBoard clone from [http://www.ema-tech.com EMA]
 
* OMAP35x based [[EGS3530]],a Chinese BeagleBoard clone from [http://www.ema-tech.com EMA]
 
* OMAP3 OMAP35x based [http://www.buglabs.net/products BUG] from Bug Labs, Inc.
 
* OMAP3 OMAP35x based [http://www.buglabs.net/products BUG] from Bug Labs, Inc.
* OMAP35x System-on-Module [[SOM3530]],The smallest(40x40x4mm) OMAP35XX-based System on Module in the world! (It is not-Gumstix Overo is smaller. at 17mm*58mm)
+
* OMAP35x System-on-Module [[SOM3530]], the smallest(40x40x4&nbsp;mm) OMAP35XX-based system on module in the world! (It is not-Gumstix Overo is smaller at 17&nbsp;mm*58&nbsp;mm)
 
* OMAP35x based [http://www.compulab.co.il/t3530/html/t3530-cm-datasheet.htm CM-T3530 from CompuLab]
 
* OMAP35x based [http://www.compulab.co.il/t3530/html/t3530-cm-datasheet.htm CM-T3530 from CompuLab]
  

Revision as of 20:29, 15 October 2012


This page collects information about BeagleBoard.org's open hardware embedded computer boards based on TI's ARM processors. Most of this material is applicable to the BeagleBoard and BeagleBoard-xM. See the BeagleBone page for information on that board.

NEWS:


Contents

Events

Event Location Date
Maker Faire New York New York Hall of Science, Queens, NY, USA Sep 29 - 30, 2012
T-Dose Eindhoven, The Netherlands Oct 27 - 28, 2012
ARM Techcon Santa Clara, CA, USA Oct 30 - Nov 1, 2012
Embedded Linux Conference Europe Barcelona, Spain Nov 5 - 7, 2012

Hardware

The BeagleBoard is a low-cost, fan-less single-board computer based on TI's OMAP3 device family, with all of the expandability of today's desktop machines, but without the bulk, expense, or noise (from beagleboard.org). It uses a TI OMAP3530 processor (ARM Cortex-A8 superscalar core ~600 MHz paired with a TMS320C64x+ DSP ~430MHz and an Imagination SGX 2D/3D graphics processor). See OMAP3530 features for more processor features. Price is USD 149. The design goal was to make it as simple and cheap as possible, e.g. not having a LCD added, but letting you connect all add-ons available as cheap external components. See What is Beagle? and LinuxDevices article for more details.

The videos Beagle Board Beginnings and Beagle Board 3D, Angstrom, and Ubuntu give you a good intro about what BeagleBoard is about and its capabilities.

Components

Top view of rev B: Top view of rev C:
Bb revb top numbered.jpg Bb revc top numbered.jpg
No. Name Comment
1 OMAP3530 processor + 256 MB NAND

+ 128 MB DDR (rev B)

+ 256 MB DDR (rev C)

PoP: Package-On-Package implementation for Memory Stacking

256 MB NAND/128 MB Mobile DDR SDRAM available from DigiKey

(512MB NAND/256MB Mobile DDR SDRAM available from DigiKey)

Micron's multi chip packages (MCPs) for Beagle Board

2 DVI chip (TFP410)
3 DVI-D Connection via HDMI connector
4 14-pin JTAG 1.8V only!
5 Expansion connector: I2C, I2S, SPI, MMC/SD User must solder desired header into place
6 User button Allows setting boot order.
7 Reset button
8 USB 2.0 EHCI HS Rev A and B: not working, unpopulated

Rev C: populated and working

9 SD/MMC+ SDHC cards are supported
10 RS-232 serial
11 Alternate power normally powered by USB (unmounted on REV Ax boards, see errata)
12 USB 2.0 HS OTG Mini-AB connector. Board can be powered from port.
13 Stereo In
14 Stereo Out
15 S-Video
16 TWL4030 (Rev A thru C2 inc.)

TPS65950 (Rev C3 onwards)

Audio CODEC, USB port, power-on reset and power management. The TWL4030 is pin-compatible with the TPS65950 chip and was used due to the very limited availability of the TPS65950 in early board revisions.
17 LCD only rev C
18 USB power
19 Host PHY
20 32 kHz
21 12 MHz
22 RS-232 XVCR
23 PWR SW
24 VBAT
  • Board size: 3" x 3" (about 76.2 x 76.2 mm)
  • Weight: ~37 g
  • Currently six-layer PCB; target: four layer PCB

Bottom of rev B:

Beagle bottom.jpg

See jadonk's photostream for some more detailed BeagleBoard pictures.

Manual

See BeagleBoard System Reference Manual (rev. C3.0).

Schematic

Schematic of BeagleBoard Rev. C3 is available as part of BeagleBoard System Reference Manual (rev. C3.0). Rev C3 and previous are also available from BeagleBoard.org design page including in PDF format. Please make sure that you read, understand and agree Jason's mail before using this.

Layout

Layout of BeagleBoard Rev. C3 is available as part of BeagleBoard System Reference Manual (rev. C3.0). Rev C3 and previous layouts are also available from the BeagleBoard.org design page. Please make sure that you read, understand and agree Jason's mail before using this.

Errata

  1. 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 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 power supply with switched connector (do not connect anything to the “?” terminal. USB power will be permanently disabled and the board can only be powered from the 5 V.) See Koen's Beagleboard powermod picture with short descriptions, too.
  2. 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.
  3. 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.
  4. Boards revision < A5 only: There is an issue where on some boards the 1.8 V has excessive noise on it. This is the result of two incorrect parts L1 and L3 being installed on the board. The inductors that were initially installed in the switchers are 100uH and need to be 1 uH. This change will require that the board be returned for update. To check for correct parts, have a look to bottom of BeagleBoard. L1 - L3 are the larger parts there. They all have to be labeled with "102" (== 1uH). If any of these three inductors are labeled with "104" (== 100 uH) they are wrong and have to be exchanged.
  5. Boards revision A and B: USB HOST (EHCI) failures. See issue 15 and USB host test reproduce. This is a hardware defect. Most probably Rev. B board does not have the EHCI USB connector mounted. Workaround: Use OTG port with something like mini A to USB A adapter instead.
  6. Boards revision A and < B4: Plugging in a USB OTG cable will prevent Beagle from booting (with Git kernel), see issue #19, too. This is due to missing filtering capacitor at USB OTG VBUS. When the kernel driver detects that a USB OTG cable is inserted it enables the charge pump to generate VBUS. With no filtering VBUS looks like any switching regulator output with no filtering -- a huge voltage spike when the switch is on, followed by a rapid decay to a low voltage until the next switch on period. The capacitor is there to store energy between the output switch ON and OFF time, the feedback loop in the regulator does sample the cap voltage. Fix is to piggy-back solder a 0603 2.2 µF ceramic capacitor to D3, see VBUS modification D3 picture. Revision B4 boards and newer have this fix applied. Thanks to Steve for debugging this!
  7. Boards revision A and < B5: There is some issue with a 32 kHz clock depending on system configuration used to clock some OMAP3 peripherals. From this e.g. GPIOs, GPTIMERs, and USB on BeagleBoard might be affected. See Issue 22. The symptom from this is that after booting the Linux kernel, the serial console hangs after some time and no serial input/output is possible any more. There is one software workaround and one hardware fix for this: (A) Software workaround: Don't use the 32 kHz timer to clock Linux, instead use the MPU timer. (B) Hardware workaround: Remove capacitor C70, which improves the 32 kHz clock quality and avoids hang-up. Note: Revision A boards have capacitor C70 at the same location as rev. B boards. Note: Board revision >= B5 removes capacitor C70.
  8. Random boards, quite rare, revision < B6: Some random boards and quite rare, show directly after purchasing broken serial communication from the host PC to BeagleBoard. Symptom is that you get a new board, get serial output from BeagleBoard in terminal program, but can't type anything at U-Boot prompt (Note: Don't mix this with errata #7. With errata #7 you are able to use U-Boot normally, but the Linux prompt input stops after some time). Most users don't have this issue, though. So, first double check your serial configuration (FAQ1, FAQ2 and FAQ3). Only if you are really, really sure that anything with your serial connection is fine, consider sending the board back doing a RMA request. This issue was resolved on revision B6 and later boards.

For additional (software) issues and enhancement requests see Beagle board open point list & issue tracker, too.

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

Clocking

Some notes about (ARM processor) clock rates at BeagleBoard:

  • ARM Cortex-A8 processor is currently clocked at 500 MHz
  • 500 MHz is the default used because it is a balance of performance and longevity
  • For OMAP35x 600 MHz is maximum recommended
  • An additional 720 MHz overdrive is supported only on high-speed grade OMAP3530/25 devices as fitted to the BeagleBoard C4
  • At 600 MHz or higher OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy
  • Higher than 600/720 MHz is out of specification and no guarantee it will work at all (or not damage itself)
  • Also keep in mind that if you go higher you probably want to increase the core voltage. Some of this is mentioned in tables 3-3, 4-15 and 4-16 of the OMAP3530 data sheet. Some numbers:
ARM DSP core voltage
720 MHz 520 MHz 1.35 V
600 MHz 430 MHz 1.35 V
550 MHz 400 MHz 1.27 V
500 MHz 360 MHz 1.2 V
  • For some OMAP3 clock, voltage and power management discussion see OMAP3 power management white paper, too.
  • The OMAP3 chip on the Beagle lacks the efuses needed for using the SmartReflex technology, see [1].
  • There is a thermal monitor in the core, you could use to scale frequency up and down

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

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

Power management

Without PM kernel, the Beagle consumes ~1.5 watts idle, however it also uses the same amount under load (see bottom of that page).

DLP Pico projector

Texas Instruments is developing a Pico Video Projector Kit (PVPK) as a peripheral for the BeagleBoard. The stand-alone pico projector will support VGA resolution (640 x 480 pixels), RGB 888 input through a DVI interface. The physical connector on the projector will be HDMI. See mailing list and Beagle Running Angstrom (VGA) on DLP Pico Projector for more details.

It is available from DigiKey for $349.

See article from Make, too.

DigiKey videos part 1, part 2 and part 3.

Interfacing to Raw LCD Panels

Currently on Rev A / B boards there is no direct access to the LCD lines before they enter the DVI framer. The REV C2 provides access to these lines. Several projects to interface an LCD to the BeagleBoard exist:

Availability

BeagleBoard Rev. C3 boards are available from

BeagleBoard Rev. C4 boards are available from:

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

  • Click the US flag on the top right corner of Digi-Key BeagleBoard page to come to the international page
  • Select Order Online for your country
  • Add quantity 1 and part number 296-23428-ND
  • Click Add to order

When ordering over 65 EUR / GBP 50 product (BeagleBoard is above), for Europe the price depends on the actual dollar to EUR/GBP rate. On nov 9, 2008 the price was EUR 124 with free shipping.

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

Note: While you get free shipping, most probably you have to pay tax, for example, ordering from Europe. Users report that they had to pay EUR ~34 - 44 VAT + importing taxes (depending on european country), resulting in EUR 137 - 147 ordering from Europe.

Note: For European users, EBV Elektronik sells its own blue version of the board for 179 EUR, which includes all useful accessories (DVI cable, serial cable, USB 2.0 Ethernet, USB hub, 2 GB MMC, power supply, Linux BSP).

Note: German (Europe) users can order through German shops, too. For higher price, though.

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 errata for limitations.

Revision B

Revision B is same as revision A, except

  • fix for shorted LEDs 0/1
  • fix for wrong power jack pinout
  • revision B6 uses different package for U9/U11

Still has USB HOST (EHCI) failures. USB HOST (EHCI) connector isn't mounted.

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

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

Revision C2

Revision C2 is same as revision B7 except:

  • USB HOST (EHCI) is operational on revision C2, with standard USB A female connector.
  • Add interface for raw LCDs (mockup)
  • It uses updated OMAP3 revision. BeagleBoard revisions B4+B5 uses OMAP3 ES 2.1 (engineering sample), while BeagleBoard revision C2 uses ES 3.0. OMAP3 ES 3.0 fixes minor issues:
    • updated ARM Cortex A8 silicon (r1p3) fixing a very rare NEON issue that has not been seen in real code
  • Power measurement feature
  • Uses TPS65950 OMAP power controller instead of TWL4030
  • Three additional PWM signals on the expansion connector added as pin mux options to existing pins (message)
  • Revision detection (to be able to identify C2 board from older boards by software, for example, for different pin mux)
  • 256 MB RAM (message) (and still 256 MB NAND like rev B)

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

Revision C3

As revision C2 boards are sold out, revision C3 will ship now.

Revision C3 is same as revision C2 except:

  • Optional RTC VL1220 series backup battery
  • Mounting holes conected to ground
  • Slightly improved S-Video

Revision C4

Revision C4 boards are the same as Revision C3 except:

  • Processor is 720 MHz capable OMAP3
  • Improved USB Host PHY power rails

Revision C5

Revision C5 boards are the same as Revision C4 except:

  • The memory chip is upgraded to 512 MB NAND

Clones

EBVBeagle

EBV build and sell their own BeagleBoard called EBVBeagle, see e.g. [2]. 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 official press release.

Mini Board

ICETEK-OMAP3530-Mini is a Chinese BeagleBoard clone.

DevKit8000

DevKit8000 is from Embest, China. It is a compact development board based on TI OMAP3530.

DevKit8500D

DevKit8500D is from Embest, China. It is a high-performance development board based on TI DM3730.

SBC8530

SBC8530 is from Embest, China. It is a compact single board computer based on TI DM3730 and features UART, 4 USB Host, USB OTG, Ethernet, Audio, TF, WiFi/Bluetooth, LCD/VGA, DVI-D and S-Video.

Tianyeit CIP312

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

IGEPv2

IGEPv2 Platform is a Spanish BeagleBoard clone, slightly larger, with additional peripherals like, for example, Ethernet connector, Wi-Fi and Bluetooth.

  • 720 MHz OMAP3 Processor
  • 512 MB RAM / 512 MB Flash

SOM3530

SOM3530 is a Chinese BeagleBoard clone System-on-Module, dimensions 40x40x4 mm, maybe the smallest OMAP3530-based modules in the world! Including 100 Mbit/s high perfomance Ethernet I/F.

BeagleBoard-based products

Beagle case

Adapters

For quite detailed information about all BeagleBoard peripherals see BeagleBoard HW Reference Manual (rev. B6).

See BeagleBoard peripherals and adapters page for useful add ons for BeagleBoard.

Expansion boards

See Category:BeagleBoard_Expansion_Boards for more information about expansion boards

BeadaFrame - A 7" TFT LCD Screen with resistive touch for BeagleBoard and BeagleBone. A plastic (ABS) frame is included also for ease of mounting.

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

BeagleTouch - A modular "shield" that snaps on top of the BeagleBoard and provides a touch-screen OLED interface

BeagleJuice - A lithium ion battery module that snaps on the back of the BeagleBoard that powers the BeagleBoard.

LOX - A dual channel internet linking radio (Ham, GMRS, etc.) interface that can run any combination of two repeaters, simplex nodes, or remote bases.

JTAG

Depending on your JTAG tool, you'd need a 14-pin to 20-pin adapter to use an ARM debugger. The 14-pin TI JTAG connector is used on BeagleBoard and is supported by a large number of JTAG emulation products. See BeagleBoardJTAG for more information.

RS-232

The pinout on the BeagleBoard is "AT/Everex" or "IDC10". You can buy IDC10 to DB9M adapters in many places as they are commonly used for old PCs. Depending on your local configuration, you may need a 9-Pin NullModem cable to connect BeagleBoard to serial port of your PC. From TinCanTools there is a RS-232 DB-9 adapter and adapter schematic available. You can also probably rip one of those cables out of any old desktop computer, where it's being used to support the serial port. Be careful, though -- some of those cables will have that tenth hole filled in so you'd have to snap off the extraneous pin on your BeagleBoard. Keep looking until you find a cable with all 10 holes open.

Depending on your local configuration, you may need a 9-Pin NullModem cable to connect BeagleBoard to serial port of your PC. From TinCanTools there is a RS-232 DB-9 adapter and adapter schematic available.

USB-to-Serial Converter

Since many systems no longer come with an actual serial port, you might need to pick up a USB-to-serial converter at your local computer store to connect to your BeagleBoard. Be warned that some of them simply do not work. Many of them are based on the Prolific chip, and require the pl2303 module to be loaded. But even when two converters appear to have exactly the same characteristics as listed in /var/log/messages, if you simply can't get one to work, be ready to try a different one.

USB

There are two USB ports on the BeagleBoard, one with an EHCI controller and another with an OTG controller. As of Rev B4, the usb EHCI has been removed because of a hardware defect. Rev C will include USB EHCI working properly.

EHCI

The HS (HighSpeed) USB ECHI controller on OMAP3 on BeagleBoard supports high-speed only. This simplifies the logic on the device. FS/LS (FullSpeed/LowSpeed) devices, such as keyboards and mice, require going through a high-speed USB 2.0 hub.

According to the BeagleBoard System Reference Manual Rev C2, the EHCI port can source 5 V at 500 mA which is enough to power a hub and several low-power devices. However, this is only true if the BeagleBoard is powered through its power jack from a well-regulated 5 V external power supply. If the BeagleBoard is powered through the OTG port, the EHCI port sources an "extremely limited" ampount of power (probably 100 mA or so) so you'll need a "self-powered" USB 2.0 hub with its own external power supply. [Reference: Sections 5.6 and 7.2 of the BBSRM Rev C2.2.]

Hardware issue on rev C3 - the EHCI port on some rev C3 boards is unstable and will disconnect hubs/devices. Symptoms are: devices are disconnected from the port and cannot be reconnected without a reboot. It appears the shared 1.8 V rail between the OMAP3530 and the power chip was getting noisy. Suggested solution (works on many boards) is adding a 22 µF 0805 package SMT capacitor atop the existing capacitor on C97. If SMT parts are not available, some boards can be repaired by a 22 µF through-hole capacitor across GND and VIO_1V8 on the expansion connector. See [4] for more information.

OTG

The HS USB OTG (OnTheGo) controller on OMAP3 on the BeagleBoard does have support for all the USB 2.0 speeds (LS/FS/HS) and can act as either a host or a gadget/device. The HS USB OTG port is used as the default power input for the BeagleBoard. It is possible to boot the BeagleBoard using this USB port.

When using the OTG port in host mode, you must power the BeagleBoard using the +5 V power jack. If you connect a USB hub, you'll probably also need external power for the USB hub as well, because according to the Hardware Reference manual the BeagleBoard OTG port only sources 100 mA. This is enough to drive a single low-power device, but probably won't work with multiple devices.

The Linux kernel needs to know you want to use the OTG port in host mode. I believe OTG ports are supposed to figure this out for themselves using the OTG Host Negotiation Protocol, but for now the Linux kernel may need some help. Specifically, Pin 4 (ID) of the OTG connector needs to be shorted to Pin 5 (GND) by using a 5-pin USB Mini-A plug which shorts these pins together in the plug. A 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 here.

Since the right cables might be hard to get, you simply can

  • short circuit the two pins encircled in red in the image to the right. You can do this by running a wire between the two pins. That at least allows easier undoing the change. Actually you could even have a small switch or so between 4 and 5.

or

  • use a "mini B" cable (easier to get) and try the soldering of the two pins at the cable's connector. Depending on the cable it should be possible to open the plastic covering of mini-B port with a sharp-edged knife, then solder the two pins together, close the covering again and use some tape. This leaves the BeagleBoard unmodified.
Usb otg.png

The Rev C BeagleBoard has a pair of pads labeled J6 on the back of the board under the OTG connector. Shorting these pads together with a wire or solder blob connects pins 4 and 5. See Figure 20 in the BeagleBoard System Reference Manual Rev C2.2.

DVI

DVI-D connection on BeagleBoard uses an HDMI connector:

HDMI is backward-compatible with the single-link Digital Visual Interface carrying digital video (DVI-D or DVI-I, but not DVI-A) used on modern computer monitors and graphics cards. This means that a DVI-D source can drive a HDMI monitor, or vice versa, by means of a suitable adapter or cable, but the audio and remote control features of HDMI will not be available.

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

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

Arduino

  • Trainer Board from TinCanTools has an Arduino compatible Atmel AVR on board
  • Arduino Nano uses an FTDI FT-232 based interface which is supported by the ftdi_sio kernel driver- How To Notes
  • Arduino Uno uses a Atmel ATmega8U2 based interface which is supported by the cdc_acm kernel driver - How To Notes

BootRom

OMAP3 on BeagleBoard contains a BootRom. With this, BeagleBoard can boot without any code in permanent storage (NAND) or from peripherals. This is useful for first board bring up or if your BeagleBoard is bricked. For more information about BootRom booting see the Initialization chapter of SPRUF98.

User button

With user button on BeagleBoard you can configure boot order. Depending on this button, the order used to scan boot devices is changed. The boot order is (the first is the default boot source):

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

Technically speaking, the user button configures pin SYS.BOOT[5]. See the Initialization chapter of SPRUF98 for more details.

Serial and USB boot

Historically, using OMAP3's boot ROM for serial and USB boot, there are several tools around. The newest are Nishanth' OMAP U-Boot Utils, while there are still some older tools for serial boot and USB boot. It is also possible to access the U-Boot environment from Linux.

OMAP U-Boot Utils

Nishanth' 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 Nishanth' blog and announce mail, too.

Serial boot

Besides Nishanth' OMAP U-Boot Utils, to boot from USB or UART, you need a PC tool which talks with OMAP BootRom and speaks the correct protocol to download ARM target code to BeagleBoard. Currently there is one tool for UART boot:

See USB and serial download target code for some example target code to be downloaded to OMAP3 on BeagleBoard.

USB boot

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

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

See USB and serial download target code for some example target code to be downloaded to OMAP3 on BeagleBoard.

See the USB recovery section on how to use USB boot for board recovery.

NAND boot

See NAND boot article.

MMC/SD boot

Currently, boot the BeagleBoard with MMC/SD is the only working way for first board bring up.

MMC/SD formatting

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

Windows

See HP USB Disk Storage Format Tool 2.0.6 description on boot the BeagleBoard with MMC/SD page.

You can download this tool from here. Make sure the version is 2.0.6; newer versions may not work.

Linux

Please see OMAP3 MMC Boot Format.

Dual partition card

You can 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 rd-ext2.bin) use kernel boot arguments (for example, in U-Boot using setenv bootargs):

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

U-Boot booting

If your MMC/SD card formatting is correct and you put MLO, u-boot.bin and uImage on the card you should get a U-Boot prompt after booting the BeagleBoard. For example (output from terminal program with 115200 8N1):

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

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

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

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

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

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

If you like to make that happen every boot:

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

Note: saveenv will not work on the xM. You will need to create a boot.scr file in the FAT partition for the xM. See set up u-boot
Note2: after a saveenv, u-boot will not read your boot.scr any more. To make it use boot.src again, type "nand erase" in the u-boot promt (works on C4, older versions may need a "nand unlock" too).

Barebox booting

You can also use barebox to boot.

On barebox you will have to generate it two time.

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

The second time as the real boot loader omap3530_beagle_defconfig

Code

Code and binaries for BeagleBoard are available at various places.

Binaries

BeagleBoard pre-built binaries and source code can be found at Beagle source code and 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, 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 www.angstrom-distribution.org/demo/beagleboard directory should contain all the files you need:

See the beagle wiki on how to setup your SD card to use all this goodness.

Source

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

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

Besides above binary and source images (TI's and communities one), for various parts of Beagle software stack there are community supported git repositories available.

X-Loader

Steve did some work to consolidate and update X-Loader from various sources and put it in a X-Loader git repository. Get it by

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

Build:

make distclean
make omap3530beagle_config
make

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

U-Boot

Mainline U-Boot has good support for BeagleBoard (except for revision C4; see note below). Get it by:

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

Build (assuming Code Sourcery GCC):

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

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

Note: Due to (patch and binary) size, the BeagleBoard splash screen was removed from upstream version. If you want it back, use U-Boot v1 BeagleBoard splash screen patch.

Note: For experimental U-Boot patches not ready for mainline yet, Steve's Beagle U-Boot git repository is used to test them. Get it by:

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

Note: For changing the screen resolution there is one option modifying the file in "include/configs/omap3_beagle.h" and adjusting the maximum resolution before compiling as describe in ARM OMAP2/3 Display Subsystem

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

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

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

to

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

Linux kernel

Git repository of OMAP Linux kernel contains Beagle support. Get it by:

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

Build:

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

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

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

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

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

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

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

Experimental kernel patches and hacks

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

Compiler

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

ARM

There is broad compiler support, including GCC - please see ARM Compilers

C64x+ DSP

A free C64x DSP compiler is available as 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 here

Note: An pld c6000 Linux compiler is available on the TI FTP site. It does NOT support c64x+ core in OMAP3 devices. Not recommended.

You can also use the 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 for information about how to use the DSP.

Cortex A8 ARM features

ARM Cortex-A8 in OMAP3 is a high performance dual-issue applications processor which reaches a performance of 2.0 DMIPS/MHz (compared to ARM11 at 1.2 DMIPS/MHz). It is ARM v7 architecture, which is fully backwards compatible with application code for previous ARM processors.

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

See Floating Point Optimization article for an introduction into VFP-lite and NEON.

ARM NEON

NEON is a 64/128-bit wide SIMD vector extension for ARM, which has been architected to be an efficient C compiler target as well as being used from assembly language. It has 32x 64-bit registers (with a dual view as 16x 128-bit registers) which can hold the following datatypes:

  • 64-bit signed/unsigned
  • 32-bit signed/unsigned
  • 32-bit single precision floating point
  • 16-bit signed/unsigned
  • 8-bit signed/unsigned

The key advantage of NEON is very high performance vector math processing, whilst being easy to program. It is the same thread of control as the ARM (but different instructions), and is supported by the same tools, debuggers and operating systems.

The NEON instruction set is documented in ARM's RealView Compilation Tools Assembler Guide.

For NEON optimized libraries, see 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 EULA.

NEON is used by various opensource projects:

  • Libav - libavcodec used by mplayer, omapfbplay, and many other Linux applications
  • libpixman - used by X.org and Mozilla & Webkit browsers to render text and graphics
  • Bluez - official Linux Bluetooth stack
  • Eigen2 - C++ template library for linear algebra (matrix math, etc.)
  • Webm - Google's new opensource video codec

Compilation tools support for NEON:

ARM Cortex-A8 Floating Point

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

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

2) NEON NEON vectorized single precision operations (two values in a D-register, or four values in a Q-register) These can be use by GCC when -ftree-vectorize is enabled and -mfpu=neon is specified, and the code can be vectorized. In other cases, the VFPv3 scalar ops will be used.

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

On Cortex-A8, the designers' focus was on the NEON unit performance which can sustain one cycle/instruction throughput (processing two single-precision values at once) for consumer multimedia. The scalar VFPv3 FPU cannot achieve this level of performance (cycle timings are in the Cortex-A8 TRM download), but it is still a lot better than doing floating point using integer instructions.

If you need the highest performance floating point on Cortex-A8, you need to use single precision and ensure the code uses the NEON vectorized instructions:

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

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

Board recovery

If you played, for example, with the contents of the NAND, it might happen that the BeagleBoard doesn't boot any more (without pressing user button) due to broken NAND content. See BeagleBoard recovery article how to fix this. Do not panic and think you somehow 'bricked' the board unless you did apply 12 V to it.

Development environments

Instead of just using compiler + editor, you can use complete image create "development tool chains" which integrate compiler, build system, packaging tools, etc. in one tool chain.

OpenEmbedded

For OpenEmbedded (OE), there are some hints how to start with OE for BeagleBoard. See BeagleBoard and OpenEmbedded Git,OpenEmbedded development and 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 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:

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 C Development Tools Project provides a fully functional C and C++ integrated development environment (IDE) for the Eclipse platform. The Eclipse 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 Target Communications Framework (TCF) component. Information on how RSE is used for, for example, Gumstix development is described in this post.

See also Using Eclipse with Beagle (for JTAG debugging).

Android

The 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 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 OMAPZoom.org's wiki page on Android.

EMBINUX

Beagleboard.org's Android project page announced, the successful porting of Android on Beagle board by EMBINUX™ Team. The source code and binaries are available for download and review.

Detailed instructions, for porting Android on BeagleBoard, are available here. Current release supports input devices (keyboard/mouse), network and sound.

You can watch Android booting on BeagleBoard.

Android on OMAP wiki

Wiki page for Andorid on OMAP can be found here.

0xdroid

0xdroid, the enhanced version of Android on BeagleBoard by 0xlab. The source code, pre-built binaries, and issue tracker are available for review and reference.

The latest development supports OMAP audio, OMAP video overlays, ARM Cortex A8 NEON/Thumb2 performance optimizations, mouse cursor, hot-pluggable USB keyboard & mouse, user-friendly installer for system image, and various Android tweaks. Detailed instructions for 0xdroid are available through Google Code wiki.

You can watch the 0xdroid demo video on the BeagleBoard:

* 0xdroid demo video (1)
* 0xdroid demo video (2)
* 0xdroid demo video (3)

Mamona

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 Maemo using only free and open source components. Mamona 0.2 supports OMAP3430 Software Development Platform (SDP), so you can also use it at Beagle (OMAP3530), too. Work is being done to officially support BeagleBoard.

Ubuntu

See Ubuntu (ARM) installation guide how to install Ubuntu (ARM) on BeagleBoard.

Debian ARM

See Debian (ARM) installation guide how to install Debian (ARM) on BeagleBoard.

GeeXboX ARM

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

Scratchbox

Scratchbox is a cross-compilation toolkit designed to make embedded Linux application development easier. It also provides a full set of tools to integrate and cross-compile an entire Linux distribution. See Felipe's Scratbox 1 and 2 introduction, too.

Software hints

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

QEMU

QEMU supports OMAP3 being able to boot a BeagleBoard Linux kernel.

Linux hints

See BeagleBoard Google wiki Linux hints page (for Linux WTBU (Wireless TI Business Unit) kernel 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 step-by-step procedure to run lmbench on BeagleBoard.

Mediaplayer (FFmpeg)

There is a thread how to get a mediaplayer with NEON optimization (FFmpeg) to run on BeagleBoard. Includes compiler hints and patches.

Java

Open source

When using the 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 (details) is provided voluntarily through Jalimo.

See a post at mailing list, too.

OpenEmbedded users can add the 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)

Edward Nevill from ARM Ltd. is working on interpreter optimization in Zero for ARM.

People interested in getting this stuff working better should contact people on:

You should also check out IcedTea's FAQ.

Oracle Java

As of August 2012, there is a binary version of Oracle JDK 7 available for Linux/ARM under a free (but not open source) license. More information:

Supported features:

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

Oracle states in the FAQ that they are working on hard float support, as well as a JavaFX 2 port to Linux/ARM.

Booting Android (TI_Android_DevKit) from a USB stick

Please note

  • This procedure was tested on BeagleBoard-xM revision B(A3)
  • An SD card will be still needed to load the kernel.
  • An SD card will contain boot parameters for the kernel to use a USB stick as the root filesystem

Procedure

  1. Download Android Froyo for BeagleBoard-xM from TI
  2. Follow the installation procedure for an SD card card.
  3. Test if Froyo is working with your BeagleBoard-xM with an SD card.
  4. You will notice that Android has a slow performance. That is why we will install root filesystem on a USB stick.
  5. Format your USB stick and create one ext3 partition.
  6. Mount newly created ext3 partition and extract TI's root filesystem to it: sudo tar jxvf rootfs_am37x.tar.bz2 -C /media/ROOT
  7. Unmount flashdisk and insert it into the BeagleBoard.
  8. Mount your SD card to your computer.
  9. Now we need to tell the BeagleBoard to use the root filesystem from the /dev/sda1 partition instead of the SD card partition. That is done by overwriting boot.scr on the SD card with this one
  10. Unmount the SD card and insert it into the BeagleBoard and test.

Graphics accelerator

OMAP3530 used on BeagleBoard contains a graphics accelerator (SGX) based on the SGX core from Imagination Technologies. 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 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:

Some videos:

Beginners guide

You just got your new BeagleBoard, and now? See beginners guides.

FAQ

For BeagleBoard frequently asked questions (FAQ) see community FAQ and "official" BeagleBoard.org FAQ.

Links

Home page

beagleboard.org (BeagleBoard home)

  • Using Google you can search beagleboard.org (including IRC logs) using site:beagleboard.org <search term>

Manuals and resources

Contact and communication

TI resources

Articles

Books

BeagleBoard based training materials

Past BeagleBoard events

BeagleBoard wiki pages

BeagleBoard photos

BeagleBoard videos

BeagleBoard manufacturing

Other OMAP boards

Subpages

<splist

parent=
showparent=no
sort=asc
sortby=title
liststyle=ordered
showpath=no
kidsonly=no
debug=0

/>