Skip to content


Subversion checkout URL

You can clone with
Download ZIP
BeagleBone Getting Started Guide
branch: master

This branch is 527 commits behind jadonk:master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.


<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
<html xmlns="" lang="en"> 
 <title>BeagleBone Getting Started Guide</title> 
 <style type="text/css" media="screen">@import "Docs/common.css";</style>
 <link rel="icon" href="Docs/beagle.ico" type="image/x-icon" />
 <link rel="shortcut icon" href="Docs/beagle.ico" type="image/x-icon" />
 <div id="wrapper">

 <div id="contentarea2" class="line">
 <div id="contentbuffer">
 <div id="page">

 <a href="">
  <img id="head-logo" title="beagleboard logo" alt="beagleboard logo"
   src="Docs/beagle.png" height="80px" />
  <img id="head-icon" src="Docs/url.png" alt="beagleboard url" />
 <img id="in-hand" src="Docs/in-hand.png"
  alt="beaglebone in hand" align="right" height="200px" />

 <h1>Getting started with your new BeagleBone</h1>
 <p>This is the quick-start guide.  Before looking for any additional help, 
  please read (at least skim) <b>each</b> of:
   System Reference Manual</a></li>
   <a href="">BeagleBoard101
   <a href="">Frequently Asked Questions
  This document is supplied with the revision A5 BeagleBone, but the software
  is compatible with all previous revisions. It is highly recommended to view
  the on-line version of this document with updates available at <a
  href=""></a> and download the
  latest software if there is a newer version.

 <h2 id="before"><u>Before you begin, consider updating to a newer demo image</u></h2>
 <p>The latest pre-built version of this Angstrom Cloud9 IDE demo image is available from:
 <ul class="arrow">
   <a href="">Angstrom
    Distribution BeagleBone demo page</a></li>
   <a href=""> Angstrom
 <p>Please visit there now to download
  the latest version.  The <a href="">
  BeagleBoard101 presentation</a> will provide you with some guidance on
  writing the demo image to a microSD card if you aren't already a Linux
  user.  You can also find help on the <a href="">
  IRC live chat</a>.
 <p>Some version and debug information is stored in a dynamically produced file
  on this partition called <a href="info.txt">info.txt</a>, which if you are familiar
  with <a href="">building 
  Angstrom</a>, will let you know when this image was built and with what source.

 <p>If you are planning on using a different microSD card image, please look
  for support from the supplier of that image.  Some distributions available at the
  time of this release include (not supported by
 <ul class="arrow">
  <li>Texas Instruments releases<ul class="subitem">
   <li><a href="">
    Android Dev Kit (TI supported Android)</a></li>
   <li><a href="">
    Sitara SDK 5.03 (TI supported Linux)</a></li>
   <li><a href="">
    AM335x StarterWare (No operating system or your own RTOS)</a></li>
  <li>Linux<ul class="subitem">
   <li><a href="">Ubuntu</a></li>
   <li><a href="">Debian</a></li>
   <li><a href="">ArchLinux</a></li>
   <li><a href="">Gentoo</a></li>
   <li><a href="">
   <li><a href="">Buildroot</a></li>
   <li><a href="">Erlang/OTP using Buildroot</a></li>
  <li><a href="">QNX</a></li>

 <h2><u>Table of contents</u></h2>
 <ul class="arrow">
  <li><a href="#software">Software introduction</a>
   <ul class="subitem">
    <li><a href="#decision">Network connectivity</a></li>
    <li><a href="#drivers">Host USB drivers setup</a></li>
    <li><a href="#serial">Serial console</a></li>
    <li><a href="#g_ether">USB-to-Ethernet interface</a></li>
    <li><a href="#navigate">Navigating to web applications</a></li>
  <li><a href="#hardware">Hardware design</a>
   <ul class="subitem"><li><a href="#revisions">Hardware revisions</a></li></ul>
  <li><a href="#updates">Software history</a>
   <ul class="subitem">
    <li><a href="#todo">Known issues and future updates</a></li>
    <li><a href="#acknowledgments">Acknowledgements</a></li>

 <h2 id="software"><u>Software introduction</u></h2>
 <p>The Angstrom Distribution image provided with your BeagleBone includes a
  large amount of software already running as you are reading this document.
  It is also possible to install many more pre-built packages from the on-line
  repository feed using the 'opkg' tool.
 <p>Some of the running programs include web servers and other Internet servers
  that give you access to the board, even if you don't have a display, mouse
  and keyboard connected to it.

 <h3 id="decision"><u>Network connectivity</u></h3>
 <p>For many people, connecting your BeagleBone to your LAN and powering it via
  a <a href="">recommended 5V power
  adapter</a> is sufficient to get started using the BeagleBone.  The BeagleBone
  will fetch an IP address using DHCP and will broadcast it services using <a
  href="">Avahi</a>, so it is
  likely you'll simply see <a
  href="http://beaglebone.local">beaglebone.local</a> on your network.  If the
  DHCP address was provided ahead of you connecting up your USB cable, you
  might also find the IP address in <a href="info.txt">info.txt</a>.  Another
  option is to use your router's DHCP log to discover the IP address of your
 <p><small><b>Note:</b> The clock speed of the BeagleBone is determined by if
  the power source is USB or the 5V adapter at initial boot.  It will be 500MHz
  if the power source is USB and 720MHz if the power source is an

 <h3 id="drivers"><u>Getting your host machine USB drivers setup</u></h3>
 <p>This BeagleBone demo image exposes multiple USB device types to
  your host machine:
  <ul class="arrow">
   <li>FTDI USB-to-JTAG interface</li>
   <li>FTDI USB-to-serial interface</li>
   <li>Linux mass storage class interface <b>(<i>on startup</i>)</b><br/></li>
   <li>Linux USB-to-Ethernet interface <b>(<i>following &ltEJECT&gt</i>)</b></li>
 <p><small><b>Note:</b> On revision A3/A4 boards, the VID/PID were chosen to
  match the TI XDS100v2 (0x0403/0xA6D0).  On A5 and newer revisions when we've
  given the authors of CCS the chance to update their software, the generic
  FTDI VID/PID (0x0403/0x6010) will be used to simplify installation of drivers
  for systems already having those drivers.</small>
 <p><small><b>Note:</b> OpenOCD is an application that provides JTAG-based
  debugging on all three operating systems, but support for the BeagleBone
  USB-to-JTAG interface is still a work in progress.  Please visit the <a
  href="">OpenOCD Homepage</a> to learn more
  about the project, join the mailing list and help us to add support for the
 <p>Otherwise, support varies across Windows, Mac OSX or Linux.

 <ul class="arrow">
  <li>Code Composer Studio v5 (CCSv5) is a TI provided Eclipse-based integrated
   development environment that enables you to debug and develop C/C++ applications
   for your BeagleBone.  CCSv5 provides both a USB-to-serial driver as well as
   support for the USB-to-JTAG interface.  See the
   <a href="">
   CCSv5 wiki</a> page for download and installation information and
   <a href="Docs/ccs-jtag-simple.htm">instructions on getting started</a>.
  <li>Save and execute <a href="Drivers/Windows/BONE_DRV.exe">
   BONE_DRV.exe</a> for the USB-to-serial and USB-to-Ethernet drivers (or
   <a href="Drivers/Windows/BONE_D64.exe">BONE_D64.exe</a> for 64-bit Windows).
   For additional information, visit
   <a href="">FTDI's Virtual COM Port Drivers</a>
   page and the Ethernet over USB section of the <a href="">
   Linux-USB Gadget API Framework</a> page.

 <h4>Mac OS X</h4>
 <ul class="arrow">
  <li>Save and open
   <a href="Drivers/MacOSX/FTDI/FTDI_Ser.dmg">FTDI_Ser.dmg</a>,
   choose the correct .mpkg file and install the USB-to-serial drivers.
   For additional information, visit
   <a href="">FTDI's Virtual COM Port Drivers</a>
 <p><small><b>Note:</b> For the USB-to-Ethernet interface, the drivers are
  likely <i>already built into your system</i>, so no additional work is
  required.  For older OS X systems, you can look at the driver the folks over
  at Bug Labs have produced for their excellent modular development platform
  that you might use: <a
  Start_Guide_Mac_OS_X_10.5 </a> </small>
 <p>If you are on-line, here is a user's video showing the whole process:</p>
 <object width="560" height="315"><param name="movie"
  name="allowFullScreen" value="true"></param><param name="allowscriptaccess"
  type="application/x-shockwave-flash" width="560" height="315"
  allowscriptaccess="always" allowfullscreen="true"></embed></object>
 <p><small><b>Note:</b> The above uses an older software revision, but the
  differences are minimal.</small>

 <p>For A5 boards, no drivers should need to be installed.  For older boards,
  you'll need invoke the driver by specifying the vendor and product ID:
sudo modprobe ftdi_sio vendor=0x0403 product=0xa6d0
 <p>To make a pre-A5 BeagleBone show up upon every reboot, add a udev rule.
  Here is an example /etc/udev/rules.d/73-beaglebone.rules:
ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_interface", \
        ATTRS{idVendor}=="0403", ATTRS{idProduct}=="a6d0", \
        DRIVER=="", RUN+="/sbin/modprobe -b ftdi_sio"

ACTION=="add", SUBSYSTEM=="drivers", \
        ENV{DEVPATH}=="/bus/usb-serial/drivers/ftdi_sio", \
        ATTR{new_id}="0403 a6d0"

ACTION=="add", KERNEL=="ttyUSB*", \
	ATTRS{interface}=="BeagleBone", \
        ATTRS{bInterfaceNumber}=="00", \

ACTION=="add", KERNEL=="ttyUSB*", \
	ATTRS{interface}=="BeagleBone", \
        ATTRS{bInterfaceNumber}=="01", \
  Run the following to load the new udev rules:
sudo udevadm control --reload-rules
 <p><small><b>Note:</b> Code Composer Studio v5 (CCSv5) is a TI provided
  Eclipse-based integrated development environment that enables you to debug
  and develop C/C++ applications for your BeagleBone.  CCSv5 provides debug
  support in Linux over the USB-to-JTAG interface.  See the <a
  CCSv5 wiki</a> page for download and installation information.</small>

 <h3 id="serial"><u>Connect to your BeagleBone's serial console</u></h3>
 <p>Connecing to the serial port will give you access to the bootloader shell,
  kernel boot logs, a login prompt and the Linux shell.  The username is 'root'
  and the password is not set.  If the board is already booted, a quick press
  of &lt;Enter&gt; should bring up a new login prompt.

 <ul class="arrow">
  <li>Launch HyperTerminal (Start -> All Programs -> Accessories -> Communications
   -> HyperTerminal)</li>
  <li>Give the name 'BeagleBone' and press &lt;Enter&gt;</li>
  <li>Select the last (newest) COM port and press &lt;Enter&gt;</li>
  <li>Choose '115200' Bits per second, '8' Data bits, 'None' Parity, '1' Stop
   Bits, 'None' Flow control and press &lt;Enter&gt;

 <h4>Mac OS X or Linux</h4>
 <p>To open the serial terminal from a shell prompt, use the following command:
screen `ls /dev/{tty.usb*B,beaglebone-serial}` 115200
  Type CTRL-a k to exit screen.

 <h3 id="g_ether"><u>Launch USB-to-Ethernet interface</u></h3>
 <p><b>Eject the "BEAGLE_BONE" drive to enable the USB-to-Ethernet interface.</b></p>
 <p>At boot-up, the processor on your BeagleBone is running a USB storage "gadget" driver
  that served you up this file.  For this software build, you need to swap the storage gadget
  for a USB-to-Ethernet gadget when you are ready to establish an IP connection over your
  USB cable.
 <ul class="arrow">
  <li>From your PC, eject the BEAGLE_BONE USB drive.  The USB Ethernet gadget will automatically start.<br />
   <br /><small><b>Note #1:</b> It has been observed in Windows that it may actually take a
   couple of minutes for the driver to load on occasion.</small><br />
   <br /><small><b>Note #2:</b> It has been observed in Windows that you may be prompted
   to locate the 'linux.inf' file.  If you installed the driver properly, you should be able to
   find it under c:\windows\system32\drvstore\linux_...</small><br />
   <br />
  <li>Configure the adapter that appears for DHCP.</li>
  <li>The adapter should be given the IP address<li>

 <h3 id="navigate"><u>Navigate to your BeagleBone's web interface</u></h3>
 <p>At this point, you should have an IP connection either over Ethernet or over your
  USB cable.  The links below assume you are using your USB cable, which should be
  providing fixed IP addresses.</p>
 <p>The Linux distribution running on your BeagleBone is configured to start a handful
  of web servers upon boot.  This is the easiest way to get explore and program your
  BeagleBone if you are not already experienced with Linux.
 <p><small><b>Note:</b> Please note that many of the tools do not support Internet
  Explorer.  It is recommended you use recent versions of Chrome or Firefox.
 <p><small><b>Note #2:</b> Some VPNs may interfere with your local network connection to
    your BeagleBone.  Please consult your VPN guide.</small>
 <ul class="arrow">
  <li><b>BeagleBone 101 presentation</b> - <a href=""></a><br /><br />
   This application is largely self explanatory.  The source can be edited using
   the Cloud9 IDE.  The application is 'bone101.js'.<br /><br />
  <li><b>Cloud9 IDE</b> - <a href=""></a><br /><br />
   This development environment supports direct execution of
   JavaScript via Node.JS.  Visit <a href=""></a> for information
   on programming in Node.JS.<br /><br />
   The IDE is pre-populated with the source and demos of the
   <a href="">BoneScript project</a>.<br /><br />
   <small><b>Notes:</b> BoneScript is in an early alpha phase and is expected to be at
   a point suitable for building applications by Summer 2012.  There is currently no
   autorun features for the applications loaded into Cloud9 IDE, but that is one feature
   planned to be enabled.</small>
   <br /><br />
  <li><b>GateOne</b> - <a href=""></a><br /><br />
   For documentation, please visit the on-line
   <a href="">GateOne Documentation</a>.<br /><br />
   <small><b>Note:</b> This installation might be a bit slow, but we are actively working
   on improving this with the author.</small>
   <br /><br />

 <h2 id="hardware"><u>Hardware design materials</u></h2>
 <p>The latest hardware docs are <a href="">
  on-line</a>, but a local copy at the time of image creation is provided here for your
   <a href="Docs/Hardware/BONE_SRM.pdf">System Reference Manual</a>
   <a href="Docs/Hardware/BONE_SCH.pdf">Schematics (PDF)</a>
   <a href="Docs/Hardware/">Schematics (Orcad)</a>
   <a href="Docs/Hardware/BONE_BOM.xls">Bill of materials</a>
   <a href="Docs/Hardware/">PCB design files</a>

 <h3 id="revisions"><u>History of the hardware revisions</u></h3>
 <h4>A3</h4> <p>This is the original version of the board. Main issue was
 issues with the reset switch where the reset line was being pulled low which
 could cause random dropping of the Ethernet port. This issue has not be seen
 <h4>A4</h4> <p>This version of the board was mainly to provide a new SD
 connector due to supply issues. Also added was R219 in an attempt to make the
 Yellow LED on the RJ45 turn on when at 100M operation. This caused the
 Ethernet not to work on power up but did work after a board reboot.</p>
 <h4>A5</h4> <p>This version of the board returns the functionality of the
 board to that of the Rev A3 via the removal of R219. There have been no PCB
 changes for this revision. It uses the same PCB revision as the A4. It also
 ships with an updated version of the Angstrom image providing out of the box
 support for the DVI-D and 7” LCD Capes.</p>
 <p>There will be three possible versions of the Rev A5. One will be the new
 production version that is built from the ground up as an A5. The second
 version will be a reworked Revision A4 that has R219 removed at the factory
 and retested. The third version will be a revision A3, that just has the
 updated SW added. All reworked versions will have the reset switches double
 checked as well. All reworked boards will be retested using the full
 production test process.</p>
 <p>You will be able to identify these versions via the serial number. They
 all will be labeled as revision A5. The two digits after the BB in the serial
 number, S/N: 5111BB<font color="red">00</font>0023, will indicate the board.
 A fresh revision A5, will be 00, A4 reworked will be 01, and a recertified A3
 will be 02. There is no functional or operational difference between any of
 these boards. They are all revision A5 and will ship with the same SW.</p>
 <p>For those with Revision A3 and A4, you will be able to download the latest
 shipping image from <a
 BeagleBone page</a> and have all the features of the Revision A5. For A4
 users, you will need to remove R219 and instructions are provided also at <a
 BeagleBone page</a>.</p>

 <h2 id="updates"><u>Software updates</u></h2>
 <ul class="arrow">
   <ul class="subitem">
    <li>Added ADC support (still needs framework updates)</li>
    <li>Basic support for some LCD and DVI-D capes</li>

 <h3 id="todo"><u>Known issues and to-do list</u></h3>
 <ul class="arrow">
   <ul class="subitem">
    <li>Mount time for USB-to-Ethernet may take a couple of minutes under Windows</li>
   <ul class="subitem">
    <li>Need completed CAN drivers</li>
    <li>Need improved PWM support</li>
    <li>Need device tree support and run-time configuration with daughterboards</li>
    <li>Need improved USB and USB DMA support</li>
    <li>Need improved SD performance</li>
  <li>SD card image
   <ul class="subitem">
    <li>Add Java</li>
    <li>Need simplified IP discovery</li>
    <li>Need improved GateOne performance and resolve 'redirect loop' issue</li>
    <li>Need to consider ConnMan tethering for USB-based IP</li>
    <li>'top' refresh rate can sometimes be crazy fast</li>
    <li>Restore automounting of hotplugged media</li>
    <li>Restore Matrix and add application entries for GateOne and Cloud9 IDE</li>
   <ul class="subitem">
    <li>Need daughterboard building guide</li>
    <li>Add graphics and/or videos where appropriate</li>
    <li>Need full description of /sys entries</li>
    <li>Basic information on apps for each major interface type, ie. I2C, SPI, etc.</li>
    <li>Need to highlight daughterboard ("cape") EEPROM spec</li>
  <li>Cloud9 IDE and BoneScript
   <ul class="subitem">
    <li>Update the git data to match the checked out repository</li>
    <li>Update version of Bone101 included to one that runs</li>
    <li>Inclusion of node-fibers such that delays don't hog the CPU</li>
    <li>Arduino-like automatic execution of installed apps</li>
    <li>Dynamic web conent example with board status and streaming data</li>
    <li>Optimal utilization of the PRU and performance improvements</li>
    <li>Extensive improvements to the BoneScript API</li>
    <li>Need examples on programming in C and Python through the Cloud9 IDE interface</li>
    <li>Include npm and several node modules</li>

 <h3 id="acknowledgments"><u>Acknowledgements</u></h3>
 <p>Much thanks is required to the Linux, Angstrom, hardware and many software
  project contributors, but here are a few contributions of note providing
  feedback directly on the BeagleBone experience.  Providing these here also
  serves the purpose of giving some history on some of these updates.
 <ul class="arrow">
  <li><a href="!topic/beagleboard/gKQtFpdpB6k"></a></li>

 <div id="footer">
 <div id="cc"><a href="" target="_blank"><img src="" alt="Creative Commons - Conditions - Attribution and Share Alike" border="0" /></a></div>
  Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 3.0 license.<br/>
  Please see <a href="LICENSE.txt">LICENSE.txt</a> for more information.  Document version: 1.5


Something went wrong with that request. Please try again.