Difference between revisions of "BeagleBoardUbuntu"

From eLinux.org
Jump to: navigation, search
m (Quantal 12.10 armhf: ubuntu-12.10-console-armhf-2013-08-24.tar.xz)
m (BeagleBone/BeagleBone Black: Typo)
(33 intermediate revisions by 5 users not shown)
Line 4: Line 4:
 
[[Category: BeagleBoard]]
 
[[Category: BeagleBoard]]
 
''(For BeagleBoardAngstrom, click [[BeagleBoardAngstrom|here]].)''
 
''(For BeagleBoardAngstrom, click [[BeagleBoardAngstrom|here]].)''
 +
''(Should [[Beagleboard:Ubuntu On BeagleBone Black]] be merged into this page?)''
  
This page is about running a distribution (ARM [http://wiki.debian.org/ArmEabiPort EABI]) [http://www.ubuntu.com/ Ubuntu] at [[BeagleBoard]]. BeagleBoard will boot the (ARM EABI) Ubuntu distribution from the [[BeagleBoard#MMC.2FSD_boot|SD card]]. Since much of this page is generic, it has also be extended to help support devices such as the [[PandaBoard]] and [[BeagleBone]].
+
This page is about running a Linux distribution (ARM [http://wiki.debian.org/ArmEabiPort EABI]) [http://www.ubuntu.com/ Ubuntu] on the [[BeagleBoard]]. BeagleBoard will boot the (ARM EABI) Ubuntu distribution from the [[BeagleBoard#MMC.2FSD_boot|SD card]]. Since much of this page is generic, it has also been extended to help support devices such as the [[PandaBoard]] and [[BeagleBone]].
  
 
* For the best experience, make sure you have an LCD/HDMI monitor attached to the BeagleBoard's HDMI port, 2 GB/4 GB/8 GB SD card, and a known good USB 2.0 hub with mouse and keyboard.
 
* For the best experience, make sure you have an LCD/HDMI monitor attached to the BeagleBoard's HDMI port, 2 GB/4 GB/8 GB SD card, and a known good USB 2.0 hub with mouse and keyboard.
Line 16: Line 17:
 
** [http://groups.google.com/group/beagleboard Email Beagleboard user group] *Recommended method
 
** [http://groups.google.com/group/beagleboard Email Beagleboard user group] *Recommended method
 
** ''#beagle'': Beagle IRC on Freenode, accessible also by [http://beagleboard.org/discuss web interface] ([http://www.beagleboard.org/irclogs/index.php logs])
 
** ''#beagle'': Beagle IRC on Freenode, accessible also by [http://beagleboard.org/discuss web interface] ([http://www.beagleboard.org/irclogs/index.php logs])
** Kernel Tree's
+
** Kernel Trees
 
*** [https://github.com/RobertCNelson/stable-kernel/tree/v3.7.x Stable (3.7.x) branch]
 
*** [https://github.com/RobertCNelson/stable-kernel/tree/v3.7.x Stable (3.7.x) branch]
 
*** [https://github.com/RobertCNelson/linux-dev Development Kernel source code]
 
*** [https://github.com/RobertCNelson/linux-dev Development Kernel source code]
Line 23: Line 24:
 
** ''#ubuntu-arm'': Ubuntu's ARM IRC on Freenode ([http://irclogs.ubuntu.com/ logs] -> year -> month -> day -> #ubuntu-arm.html)
 
** ''#ubuntu-arm'': Ubuntu's ARM IRC on Freenode ([http://irclogs.ubuntu.com/ logs] -> year -> month -> day -> #ubuntu-arm.html)
  
*When asking for help, please provide some debugging information:
+
*When requesting help, please provide some debugging information:
 
** U-Boot Version installed on board
 
** U-Boot Version installed on board
 
** Kernel Version: uname -a
 
** Kernel Version: uname -a
Line 32: Line 33:
  
 
Mainline U-Boot:
 
Mainline U-Boot:
* All old BeagleBoard (classic) Ax, Bx, Cx and Dx boards are required to upgrade to at least these U-Boot versions.
+
* All older BeagleBoard (classic) Ax, Bx, Cx and Dx boards are required to upgrade to at least these U-Boot versions
 
* XM Boards have no NAND, so MLO/u-boot.img is always required on the first partition
 
* XM Boards have no NAND, so MLO/u-boot.img is always required on the first partition
 
* Directions: [http://elinux.org/BeagleBoardUbuntu#Upgrade_X-loader_and_U-boot Upgrade X-loader and U-Boot]
 
* Directions: [http://elinux.org/BeagleBoardUbuntu#Upgrade_X-loader_and_U-boot Upgrade X-loader and U-Boot]
Line 52: Line 53:
 
  respawn
 
  respawn
 
  exec /sbin/getty 115200 ttyO2
 
  exec /sbin/getty 115200 ttyO2
 +
  
 
= Method 1: Download a Complete Pre-Configured Image =
 
= Method 1: Download a Complete Pre-Configured Image =
Line 57: Line 59:
 
==Demo Image==
 
==Demo Image==
  
* These demonstration images contain a custom Mainline based kernel with experimental enhancements to the boards supported. They are usually updated about once a month, as new features/enhancements get added by the community. Currently, this image ships with two kernel's "x" which is for mainline omap3+ devices (BeagleBoard/PandaBoard) and the "psp" which is for specifically the BeagleBone, as much of the kernel support for this device is currently in a TI Git kernel tree on [http://arago-project.org arago-project]. The kernel is stress tested by a farm of Panda/Beagle's running 24/7 under a heavy load (building gcc trunk/mainline kernel).
+
* These demonstration images contain a custom Mainline based kernel with experimental enhancements to the boards supported. They are usually updated about once a month, as new features/enhancements get added by the community. Currently, this image ships with two kernels "armv7" which is for mainline omap3+ devices (BeagleBoard/PandaBoard) and the "bone" which is specifically for the BeagleBone. The kernel is stress-tested by a farm of Panda/Beagles running 24/7 under a heavy load (building gcc trunk/mainline kernel).
  
 
* '''Advanced Users only''': Beagle xM: Kernel source, used in these demo images: https://github.com/RobertCNelson/armv7-multiplatform
 
* '''Advanced Users only''': Beagle xM: Kernel source, used in these demo images: https://github.com/RobertCNelson/armv7-multiplatform
 
  git clone git://github.com/RobertCNelson/armv7-multiplatform.git
 
  git clone git://github.com/RobertCNelson/armv7-multiplatform.git
 
  cd armv7-multiplatform
 
  cd armv7-multiplatform
  git checkout origin/v3.11.x -b tmp
+
  git checkout origin/v3.13.x -b tmp
./build_kernel.sh
+
* '''Advanced Users only''': Beagle/Panda: Kernel source, used in these demo images: https://github.com/RobertCNelson/stable-kernel
+
git clone git://github.com/RobertCNelson/stable-kernel.git
+
cd stable-kernel
+
git checkout origin/v3.7.x -b tmp
+
 
  ./build_kernel.sh
 
  ./build_kernel.sh
 
* '''Advanced Users only''': BeagleBone/BeagleBone Black:  Kernel v3.8.x source, used in these demo images: https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.8
 
* '''Advanced Users only''': BeagleBone/BeagleBone Black:  Kernel v3.8.x source, used in these demo images: https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.8
Line 77: Line 74:
 
  https://github.com/RobertCNelson/omap-image-builder
 
  https://github.com/RobertCNelson/omap-image-builder
  
If the script in these demo images fail: email "bugs@rcn-ee.com" I need: terminal command, terminal log, distribution name, arch...
+
If the script in these demo images fail: email "bugs@rcn-ee.com" I will need details: terminal command, terminal log, distribution name, arch...
  
=== Raring 13.04 armhf ===
+
=== Saucy 13.10 ===
 
Image Updated:
 
Image Updated:
*2013-08-24
+
*2014-01-24
** Beagle xM (ONLY): v3.11.0-rc6-armv7-x10 kernel (--dtb dt-beagle-xm)
+
** Beagle/Beagle xM: v3.13.0-armv7-x9 kernel
*** 1Ghz operation, NO expansion boards, only DVI out (s-video disabled)
+
** BeagleBone/BeagleBone Black: v3.8.13-bone37 kernel
*** see: /boot/uboot/tools/pkgs/ti-omapdrm.sh (for xorg drivers)
+
*2013-12-17
** BeagleBone/BeagleBone Black: v3.8.13-bone26 kernel
+
** Beagle xM (ONLY): v3.12.5-armv7-x10 kernel (--dtb dt-beagle-xm)
*** Lots of hdmi fixes...
+
** BeagleBone/BeagleBone Black: v3.8.13-bone32 kernel
 
** Beagle/Panda/Panda ES: v3.7.10-x13 kernel
 
** Beagle/Panda/Panda ES: v3.7.10-x13 kernel
*2013-07-22
+
*2013-11-15
 +
** Beagle xM (ONLY): v3.12.0-armv7-x8 kernel (--dtb dt-beagle-xm)
 +
** BeagleBone/BeagleBone Black: v3.8.13-bone30 kernel
 +
*** audio/mmc fixes...
 
** Beagle/Panda/Panda ES: v3.7.10-x13 kernel
 
** Beagle/Panda/Panda ES: v3.7.10-x13 kernel
** BeagleBone/BeagleBone Black: v3.8.13-bone24 kernel
 
*2013-06-14
 
** shellinabox disabled...
 
** Beagle/Panda/Panda ES: v3.7.10-x12 kernel
 
*** Panda: WiFi works again...
 
** BeagleBone: v3.2.42-psp27 kernel
 
** BeagleBone/BeagleBone Black: v3.8.13-bone21 kernel (--uboot bone_dtb)
 
*** BBB: Now built with the patched 'dtc'...
 
  
 
Services Active:
 
Services Active:
  Note: Depending on your internal network these may work out the box
+
  Note: Depending on your internal network these may work out of the box
 
  Apache, Port 80: http://arm/ (Bone: via usb) http://192.168.7.2
 
  Apache, Port 80: http://arm/ (Bone: via usb) http://192.168.7.2
 
  SSH, Port 22: ssh ubuntu@arm (Bone: via usb) ubuntu@192.168.7.2
 
  SSH, Port 22: ssh ubuntu@arm (Bone: via usb) ubuntu@192.168.7.2
 
  Getty, Serial Port
 
  Getty, Serial Port
  
Active on Boot Script:
+
Default user: ubuntu pass: temppwd
*Disable by removing "run_boot-scripts" from small boot partition...*
+
/opt/boot-scripts/<board>.sh
+
 
+
Default user: ubuntu pass: temppwd  
+
  
 
Get prebuilt image:
 
Get prebuilt image:
 +
wget https://rcn-ee.net/deb/rootfs/saucy/ubuntu-13.10-console-armhf-2014-01-24.tar.xz
  
  wget https://rcn-ee.net/deb/rootfs/raring/ubuntu-13.04-console-armhf-2013-08-24.tar.xz
+
Verify Image with:
  mirrors (will take some time to update):
+
  md5sum ubuntu-13.10-console-armhf-2014-01-24.tar.xz
  wget http://ynezz.ibawizard.net/beagleboard/raring/ubuntu-13.04-console-armhf-2013-08-24.tar.xz
+
  e199c4c20091abcf1ed025ee54856055 ubuntu-13.10-console-armhf-2014-01-24.tar.xz
  
Verify image with:
+
Unpack Image:
md5sum ubuntu-13.04-console-armhf-2013-08-24.tar.xz
+
  tar xf ubuntu-13.10-console-armhf-2014-01-24.tar.xz
026d8809821c9b6438f1d8ec4991aa58  ubuntu-13.04-console-armhf-2013-08-24.tar.xz
+
  cd ubuntu-13.10-console-armhf-2014-01-24
 
+
Unpack image:
+
  tar xJf ubuntu-13.04-console-armhf-2013-08-24.tar.xz
+
  cd ubuntu-13.04-console-armhf-2013-08-24
+
  
 
If you don't know the location of your SD card:
 
If you don't know the location of your SD card:
 
  sudo ./setup_sdcard.sh --probe-mmc
 
  sudo ./setup_sdcard.sh --probe-mmc
  
You should see something like  
+
You should see something like:
  
 
  Are you sure? I don't see [/dev/idontknow], here is what I do see...
 
  Are you sure? I don't see [/dev/idontknow], here is what I do see...
Line 148: Line 133:
 
* In this example, we can see via mount, '''/dev/sda1''' is the x86 rootfs, therefore '''/dev/sdd''' is the other drive in the system, which is the MMC/SD card that was inserted and should be used by ./setup_sdcard.sh...
 
* In this example, we can see via mount, '''/dev/sda1''' is the x86 rootfs, therefore '''/dev/sdd''' is the other drive in the system, which is the MMC/SD card that was inserted and should be used by ./setup_sdcard.sh...
  
Install image:
+
Install Image:
  
Quick install script for "board"
+
Quick install script for [board]
 
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot board
 
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot board
  
"board" options:
+
[board] options:
*BeagleBoard Ax/Bx/Cx/Dx    - beagle
+
*BeagleBoard xM      - beagle_xm
+
 
*BeagleBone/Black    - bone
 
*BeagleBone/Black    - bone
*PandaBoard & ES      - panda
 
  
So for the BeagleBoard xM:
+
So for the BeagleBone:
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle_xm
+
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot bone
  
Quick install script for "board" (using new --dtb option)
+
Quick install script for [board] (using new --dtb option)
 
  sudo ./setup_sdcard.sh --mmc /dev/sdX --dtb board
 
  sudo ./setup_sdcard.sh --mmc /dev/sdX --dtb board
  
"board" options:
+
board options:
*BeagleBoard xM       - dt-beagle-xm
+
*BeagleBoard Ax/Bx/Cx/Dx    - omap3-beagle
 +
*BeagleBoard xM             - omap3-beagle-xm
  
 
So for the BeagleBoard xM:
 
So for the BeagleBoard xM:
  sudo ./setup_sdcard.sh --mmc /dev/sdX --dtb dt-beagle-xm
+
  sudo ./setup_sdcard.sh --mmc /dev/sdX --dtb omap3-beagle-xm
  
*Additional Options
+
You should now be able to unmount the SD card from your PC, insert into your Board, reboot and have the OS loaded.
** --rootfs <ext4 default>
+
** --swap_file <swap file size in MB's>
+
** --addon pico <ti pico projector>
+
** --svideo-ntsc <use ntsc over dvi for video)
+
** --svideo-pal <use pal over dvi for video)
+
 
+
You should now be able to unmount the SD card from you PC, insert into your Board, reboot and have the OS loaded.
+
  
 
For a basic '''framebuffer''' driven desktop environment: (make sure network is setup):
 
For a basic '''framebuffer''' driven desktop environment: (make sure network is setup):
  Ethernet: "sudo ifconfig -a" and "sudo dhclient usb1" or "sudo dhclient eth0"
+
  Ethernet: sudo ifconfig -a and sudo dhclient usb1 or sudo dhclient eth0
  Wireless: http://elinux.org/BeagleBoardUbuntu#Wifi_Networking_.28command_line.29
+
  Wireless: http://elinux.org/BeagleBoardUbuntu#Wi-Fi_Networking_.28command_line.29
  
 
Then run:
 
Then run:
 
  /bin/sh /boot/uboot/tools/ubuntu/small-lxde-desktop.sh
 
  /bin/sh /boot/uboot/tools/ubuntu/small-lxde-desktop.sh
 
Additional Expansion Options:
 
 
*Beagle xM with Leopard Imaging: li5m03
 
** http://shop.leopardimaging.com/product.sc?productId=17
 
Add "camera=li5m03" to uEnv.txt and run:
 
/boot/uboot/tools/pkgs/aptina-media-ctl-n-yavta.sh
 
/boot/uboot/tools/pkgs/aptina-test-capture.sh
 
 
*Beagle xM with LSR COM6L wifi adapter (first units are missing eeprom) see in uEnv.txt for overrides:
 
#LSR COM6L Adapter Board
 
#http://eewiki.net/display/linuxonarm/LSR+COM6L+Adapter+Board
 
#First production run has unprogramed eeprom:
 
#buddy=lsr-com6l-adpt
 
 
#LSR COM6L Adapter Board + TiWi5
 
#wl12xx_clk=wl12xx_26mhz
 
  
 
Advanced: Build Image:
 
Advanced: Build Image:
  
Built with a fork of project-rootstock (ARM native mode, run directly on BeagleBoard), using a script from omap-image-builder:
+
Built with a fork of project-rootstock (ARM native mode, runs directly on BeagleBoard), using a script from omap-image-builder:
  
 
  git clone git://github.com/RobertCNelson/omap-image-builder.git
 
  git clone git://github.com/RobertCNelson/omap-image-builder.git
 
  cd omap-image-builder
 
  cd omap-image-builder
  git checkout v2013.08 -b v2013.08
+
  git checkout v2014.01-1 -b tmp
 
  touch release
 
  touch release
  ./build_image.sh
+
  ./rcn-ee_image.sh
  
=== Quantal 12.10 armhf ===
+
=== Raring 13.04 ===
  
 
Image Updated:
 
Image Updated:
*2013-08-24
+
*2014-01-24
** Beagle xM (ONLY): v3.11.0-rc6-armv7-x10 kernel (--dtb dt-beagle-xm)
+
** Beagle/Beagle xM: v3.13.0-armv7-x9 kernel
*** 1Ghz operation, NO expansion boards, only DVI out (s-video disabled)
+
** BeagleBone/BeagleBone Black: v3.8.13-bone37 kernel
*** see: /boot/uboot/tools/pkgs/ti-omapdrm.sh (for xorg drivers)
+
*2013-12-17
** BeagleBone/BeagleBone Black: v3.8.13-bone26 kernel
+
** Beagle xM (ONLY): v3.12.5-armv7-x10 kernel (--dtb dt-beagle-xm)
*** Lots of hdmi fixes...
+
** BeagleBone/BeagleBone Black: v3.8.13-bone32 kernel
 
** Beagle/Panda/Panda ES: v3.7.10-x13 kernel
 
** Beagle/Panda/Panda ES: v3.7.10-x13 kernel
*2013-07-22
+
*2013-11-15
 +
** Beagle xM (ONLY): v3.12.0-armv7-x8 kernel (--dtb dt-beagle-xm)
 +
** BeagleBone/BeagleBone Black: v3.8.13-bone30 kernel
 +
*** audio/mmc fixes...
 
** Beagle/Panda/Panda ES: v3.7.10-x13 kernel
 
** Beagle/Panda/Panda ES: v3.7.10-x13 kernel
** BeagleBone/BeagleBone Black: v3.8.13-bone24 kernel
 
*2013-06-14
 
** shellinabox disabled...
 
** Beagle/Panda/Panda ES: v3.7.10-x12 kernel
 
*** Panda: WiFi works again...
 
** BeagleBone: v3.2.42-psp27 kernel
 
** BeagleBone/BeagleBone Black: v3.8.13-bone21 kernel (--uboot bone_dtb)
 
*** BBB: Now built with the patched 'dtc'...
 
  
 
Get prebuilt image:
 
Get prebuilt image:
  wget https://rcn-ee.net/deb/rootfs/quantal/ubuntu-12.10-console-armhf-2013-08-24.tar.xz
+
  wget https://rcn-ee.net/deb/rootfs/raring/ubuntu-13.04-console-armhf-2014-01-24.tar.xz
  
Verify image with:  
+
Verify Image with:
  md5sum ubuntu-12.10-console-armhf-2013-08-24.tar.xz
+
  md5sum ubuntu-13.04-console-armhf-2014-01-24.tar.xz
  1d8c4999592123fdd3a51864394ccb49 ubuntu-12.10-console-armhf-2013-08-24.tar.xz
+
  0443f6b38a6a082f5a75f72f8a5cfaf4  ubuntu-13.04-console-armhf-2014-01-24.tar.xz
  
 
Unpack image:
 
Unpack image:
  tar xJf ubuntu-12.10-console-armhf-2013-08-24.tar.xz
+
  tar xf ubuntu-13.04-console-armhf-2014-01-24.tar.xz
  cd ubuntu-12.10-console-armhf-2013-08-24
+
  cd ubuntu-13.04-console-armhf-2014-01-24
  
Then follow directions show above with the other images...
+
Then follow the directions shown above with the other images...
  
=== Saucy 13.10 (experimental) ===
+
=== Trusty 14.04 (experimental) ===
  
 
Image Updated:
 
Image Updated:
*2013-07-22
+
*2014-01-24
 +
** Beagle/Beagle xM: v3.13.0-armv7-x9 kernel
 +
** BeagleBone/BeagleBone Black: v3.8.13-bone37 kernel
 +
*2013-12-17
 +
** Beagle xM (ONLY): v3.12.5-armv7-x10 kernel (--dtb dt-beagle-xm)
 +
** BeagleBone/BeagleBone Black: v3.8.13-bone32 kernel
 +
** Beagle/Panda/Panda ES: v3.7.10-x13 kernel
 +
*2013-11-15
 +
** Beagle xM (ONLY): v3.12.0-armv7-x8 kernel (--dtb dt-beagle-xm)
 +
** BeagleBone/BeagleBone Black: v3.8.13-bone30 kernel
 +
*** audio/mmc fixes...
 
** Beagle/Panda/Panda ES: v3.7.10-x13 kernel
 
** Beagle/Panda/Panda ES: v3.7.10-x13 kernel
** BeagleBone/BeagleBone Black: v3.8.13-bone24 kernel
 
  
 
Get prebuilt image:
 
Get prebuilt image:
  wget http://rcn-ee.net/deb/rootfs/saucy/ubuntu-saucy-console-armhf-2013-07-22.tar.xz
+
  wget https://rcn-ee.net/deb/rootfs/trusty/ubuntu-trusty-console-armhf-2014-01-24.tar.xz
  
Verify image with:  
+
Verify Image with:
  md5sum ubuntu-saucy-console-armhf-2013-07-22.tar.xz
+
  md5sum ubuntu-trusty-console-armhf-2014-01-24.tar.xz
  c8baaaf03b0027019b98ca1b21ad5113 ubuntu-saucy-console-armhf-2013-07-22.tar.xz
+
  ae97d2b7d927685a2bcd15303a1b2766 ubuntu-trusty-console-armhf-2014-01-24.tar.xz
  
 
Unpack image:
 
Unpack image:
  tar xJf ubuntu-saucy-console-armhf-2013-07-22.tar.xz
+
  tar xf ubuntu-trusty-console-armhf-2014-01-24.tar.xz
  cd ubuntu-saucy-console-armhf-2013-07-22
+
  cd ubuntu-trusty-console-armhf-2014-01-24
  
Then follow directions show above with the other images...
+
Then follow the directions shown above with the other images...
  
= Flasher =
+
== Flasher ==
  
== eMMC: BeagleBone Black ==
+
=== eMMC: BeagleBone Black ===
  
This image can be written to a 1Gb (or greater) microSD card, via 'dd' in linux or the win32 image program linked to on CircuitCo's wiki page.  First hold down on the boot select button (next to microSD card) and apply  
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or the win32 image program linked to on CircuitCo's wiki page.  First press and hold the boot select button (next to the microSD card), then apply power (same procedure as the official CircuitCo images). The board should boot into Ubuntu and begin flashing the eMMC, once completed all 4 LED's should be full ON.  Simply remove power, remove the microSD card and Ubuntu will now boot directly from eMMC.
power (same procedure as the official CircuitCo images), it should boot into Ubuntu and begin flashing the eMMC, once completed all 4 LED's should be full ON...  Simply remove power, remove microSD card and Ubuntu will now boot from eMMC.
+
  
Script for Reference: (this is the script that writes to the eMMC)
+
Script for reference: (this is the script that writes to the eMMC)
 
  https://github.com/RobertCNelson/tools/blob/master/scripts/beaglebone-black-copy-microSD-to-eMMC.sh
 
  https://github.com/RobertCNelson/tools/blob/master/scripts/beaglebone-black-copy-microSD-to-eMMC.sh
  
BTW: we are only writing about 500Mb's to the eMMC so the script will only take about 5-6 Minutes after power on.
+
BTW: we are only writing about 500 megabytes to the eMMC, so the script will only take about 5-6 Minutes after power on.
  
 
Notes:
 
Notes:
If only two LED's stay lit and nothing happens, the board has crashed due to lack of power. Try with a 5Volt DC supply plugged in..
+
* If only two LED's stay lit and nothing happens, the board has crashed due to lack of power. Retry with a 5Volt DC power supply connected.
 +
* If the 4 LED's blink a constant pattern, the eMMC write has failed. First REMOVE ALL capes, then retry again.
 +
** (error -84: which may mean you've reached the max number of erase/write cycles...)
  
 
User: ubuntu
 
User: ubuntu
Line 287: Line 251:
  
 
Image Updated:
 
Image Updated:
*2013-07-22
+
*2014-01-24
** BeagleBone Black: v3.8.13-bone24 kernel
+
** BeagleBone Black: v3.8.13-bone37 kernel
*2013-06-14
+
*2013-12-17
** shellinabox disabled...
+
** BeagleBone Black: v3.8.13-bone32 kernel
** BeagleBone Black: v3.8.13-bone21 kernel (--uboot bone_dtb)
+
*2013-11-15
*** BBB: Now built with the patched 'dtc'...
+
** BeagleBone Black: v3.8.13-bone30 kernel
*2013-05-29
+
*** ssh host key fixes (auto generated on bootup...)
** BeagleBone Black: v3.8.13-bone20 kernel
+
*** BBB: USB hotplug now works...
+
  
 
Get prebuilt image:
 
Get prebuilt image:
  wget http://rcn-ee.net/deb/flasher/raring/BBB-eMMC-flasher-ubuntu-13.04-2013-07-22.img.xz
+
  wget https://rcn-ee.net/deb/flasher/saucy/BBB-eMMC-flasher-ubuntu-13.10-2014-01-24-2gb.img.xz
  
 
Verify Image with:
 
Verify Image with:
  md5sum BBB-eMMC-flasher-ubuntu-13.04-2013-07-22.img.xz
+
  md5sum BBB-eMMC-flasher-ubuntu-13.10-2014-01-24-2gb.img.xz
  be334e72fcdffbf46ca958d8e94fbd67 BBB-eMMC-flasher-ubuntu-13.04-2013-07-22.img.xz
+
  2cce18a56e1802657aad15dc700ec200 BBB-eMMC-flasher-ubuntu-13.10-2014-01-24-2gb.img.xz
  
 
Follow the "standard" update procedure.
 
Follow the "standard" update procedure.
 
  http://circuitco.com/support/index.php?title=Updating_The_Software
 
  http://circuitco.com/support/index.php?title=Updating_The_Software
 +
 +
Linux:
 +
unxz BBB-eMMC-flasher-ubuntu-13.10-2014-01-24-2gb.img.xz
 +
sudo dd if=./BBB-eMMC-flasher-ubuntu-13.10-2014-01-24-2gb.img of=/dev/sdX
 +
 +
== raw microSD img ==
 +
 +
=== BeagleBone/BeagleBone Black ===
 +
 +
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or the win32 image program linked to on CircuitCo's wiki page.  First press and hold the boot select button (next to microSD card), then apply power (same procedure as the official CircuitCo images).  The board should boot into Ubuntu.
 +
 +
User: ubuntu
 +
pass: temppwd
 +
 +
Auto partition resize:
 +
cd /opt/scripts/tools
 +
git pull
 +
./grow_partition.sh
 +
sudo reboot
 +
 +
Image Updated:
 +
*2014-01-24
 +
** BeagleBone/BeagleBone Black: v3.8.13-bone37 kernel
 +
*2013-12-17
 +
** BeagleBone/BeagleBone Black: v3.8.13-bone32 kernel
 +
*2013-11-15
 +
** BeagleBone/BeagleBone Black: v3.8.13-bone30 kernel
 +
 +
Get prebuilt image:
 +
wget https://rcn-ee.net/deb/microsd/saucy/bone-ubuntu-13.10-2014-01-24-2gb.img.xz
 +
 +
Verify Image with:
 +
md5sum bone-ubuntu-13.10-2014-01-24-2gb.img.xz
 +
c53ab3fb2f97951a1e1fb60c8719ae55  bone-ubuntu-13.10-2014-01-24-2gb.img.xz
 +
 +
Linux:
 +
unxz bone-ubuntu-13.10-2014-01-24-2gb.img.xz
 +
sudo dd if=./bone-ubuntu-13.10-2014-01-24-2gb.img of=/dev/sdX
  
 
= Method 2: Use the NetInstall method=
 
= Method 2: Use the NetInstall method=
  
You will need a 1GB/2GB SD card or greater.
+
You will need a 1GB/2GB/4GB/8GB SD card or greater.
 
  Standard system : ~700&nbsp;MB
 
  Standard system : ~700&nbsp;MB
  
Line 315: Line 315:
 
(anywhere else will be ignored..)
 
(anywhere else will be ignored..)
  
Download netinstall script:
+
Download the netinstall script:
 
  git clone git://github.com/RobertCNelson/netinstall.git
 
  git clone git://github.com/RobertCNelson/netinstall.git
 
  cd netinstall
 
  cd netinstall
  
Current Support Ubuntu distributions:
+
Currently supported Ubuntu distributions:
 
  --distro oneiric (11.10)
 
  --distro oneiric (11.10)
 
  --distro precise-armhf (12.04)
 
  --distro precise-armhf (12.04)
  --distro quantal-armhf (12.10)
+
  --distro quantal (12.10)
 
+
  --distro raring (13.04)
Old <board> selection:
+
  --distro saucy (13.10)
  *BeagleBoard Ax/Bx - beagle_bx
+
*BeagleBoard Cx    - beagle_cx
+
  *BeagleBoard xMA/B/C    - beagle_xm
+
*BeagleBone Ax    - bone
+
*PandaBoard Ax    - panda
+
*PandaBoard ES    - panda_es
+
 
+
Install script for <board>
+
sudo ./mk_mmc.sh --mmc /dev/sdX --uboot <board> --distro <distro>
+
  
New <board> selection:
+
Device: <board> selection:
  *BeagleBoard xMx - omap3-beagle-xm
+
  *BeagleBoard Ax/Bx/Cx  - omap3-beagle
 +
*BeagleBoard xMA/B/C  - omap3-beagle-xm
 +
*BeagleBone Ax        - am335x-bone-serial
 +
*BeagleBone (DVI cape) - am335x-bone-video
 +
*BeagleBone Black      - am335x-boneblack
 +
*PandaBoard Ax    - omap4-panda
 +
*PandaBoard A4+    - omap4-panda-a4
 +
*PandaBoard ES    - omap4-panda-es
  
Install script for new <board> selection: (slowly migrating all devices to this method)
+
Installation script for new <board> selection: (slowly migrating all devices to this method)
 
  sudo ./mk_mmc.sh --mmc /dev/sdX --dtb <board> --distro <distro>
 
  sudo ./mk_mmc.sh --mmc /dev/sdX --dtb <board> --distro <distro>
  
So for the xM: with quantal-armhf:
+
So for the xM: with quantal:
sudo ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_xm --distro quantal-armhf
+
  sudo ./mk_mmc.sh --mmc /dev/sdX --dtb omap3-beagle-xm --distro quantal
(or)
+
  sudo ./mk_mmc.sh --mmc /dev/sdX --dtb omap3-beagle-xm --distro quantal-armhf
+
  
 
*Other Options:
 
*Other Options:
Line 359: Line 355:
 
See my notes for my testing procedure: https://github.com/RobertCNelson/netinstall/blob/master/test.Ubuntu
 
See my notes for my testing procedure: https://github.com/RobertCNelson/netinstall/blob/master/test.Ubuntu
  
Troubleshooting: If boot fails..
+
Troubleshooting: If booting fails..
 
*Hold the user button down to force booting from MMC
 
*Hold the user button down to force booting from MMC
 
*Upgrade X-loader and U-boot [http://elinux.org/BeagleBoardUbuntu#Upgrade_X-loader_and_U-boot Upgrade X-loader and U-Boot]
 
*Upgrade X-loader and U-boot [http://elinux.org/BeagleBoardUbuntu#Upgrade_X-loader_and_U-boot Upgrade X-loader and U-Boot]
*Clear U-boot's Environment Variables in nand:  
+
*Clear U-boot's Environment Variables in NAND:  
 
  nand erase 260000 20000
 
  nand erase 260000 20000
  
Line 370: Line 366:
 
= Method 3: Manual Install (no automatic scripts)=
 
= Method 3: Manual Install (no automatic scripts)=
  
Note, this section use to have a lot of details, but maintenance of the two wiki's became a pain, so for now on we will just link to my other pages:
+
Note, this section used to have a lot of details, but maintenance of the two wiki's became a pain, so for now on we will just link to my other pages:
  
 
== Beagle/Beagle xM ==
 
== Beagle/Beagle xM ==
Line 385: Line 381:
 
==Install Latest Kernel Image==
 
==Install Latest Kernel Image==
  
===Script File===
+
Script:
 +
cd /opt/scripts/tools
 +
git pull
  
Latest Stable is: https://github.com/RobertCNelson/stable-kernel
+
Stable:
 +
./update_kernel.sh
  
export DIST=oneiric  (options are lucid/maverick/natty/oneiric/precise/squeeze/wheezy)
+
Testing:
  export ARCH=armel (options are armel/armhf (armhf only for precise))
+
  ./update_kernel.sh --beta-kernel
+
 
Beagle/Panda
+
Custom: (has to be on rcn-ee.net)
export BOARD=omap
+
  ./update_kernel.sh --kernel v3.8.13-bone37
+
BeagleBone
+
export BOARD=omap-psp
+
+
wget http://rcn-ee.net/deb/${DIST}-${ARCH}/LATEST-${BOARD}
+
  wget $(cat ./LATEST-${BOARD} | grep STABLE | awk '{print $3}')
+
/bin/bash install-me.sh
+
  
Reboot with your new uImage.
+
Reboot with your new Kernel Image.
  
 
== Upgrade X-loader and U-boot ==
 
== Upgrade X-loader and U-boot ==
Line 408: Line 400:
 
*Note: the functionality of the "X-Loader" project has been merged as u-boot spl.
 
*Note: the functionality of the "X-Loader" project has been merged as u-boot spl.
  
Compatible with old Ax, Bx, Cx, and Dx BeagleBoards
+
Compatibility with older Ax, Bx, Cx, and Dx BeagleBoards
  
Note: Sometimes on these older boards, you just have to clear out the stored U-Boot environment variables in nand to make this script work:
+
Note: Sometimes on these older boards, you just have to clear out the stored U-Boot environment variables in NAND to make this script work:
 
  nand erase 260000 20000
 
  nand erase 260000 20000
  
Or: To fully erase the NAND..
+
Or: To fully erase the entire NAND:
 
  nand erase.chip
 
  nand erase.chip
  
Requires MMC card..
+
Requires MMC card:
  
 
  git clone git://github.com/RobertCNelson/flasher.git
 
  git clone git://github.com/RobertCNelson/flasher.git
Line 427: Line 419:
 
  sudo ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_cx
 
  sudo ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_cx
  
  1: Plug Serial Cable in and Start Serial terminal program
+
  1: Plug-in a serial cable and start the serial terminal program
 
  2: Place MMC card in Beagle
 
  2: Place MMC card in Beagle
 
  3: Push and hold the user button
 
  3: Push and hold the user button
 
  4: Plug-in power
 
  4: Plug-in power
  5: Wait for U-Boot countdown to finish, and let off user button
+
  5: Wait for U-Boot countdown to finish, then release the user button
 
  6: Wait for flashing/script to end
 
  6: Wait for flashing/script to end
 
  7: Power down, remove and reformat MMC card to final OS
 
  7: Power down, remove and reformat MMC card to final OS
Line 438: Line 430:
 
  sudo ./mk_mmc.sh --probe-mmc
 
  sudo ./mk_mmc.sh --probe-mmc
  
You should see something like  
+
You should see something like:
  
 
  Are you sure? I don't see [/dev/idontknow], here is what I do see...
 
  Are you sure? I don't see [/dev/idontknow], here is what I do see...
Line 449: Line 441:
 
  /dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0) '''<- x86 Root Partition'''
 
  /dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0) '''<- x86 Root Partition'''
  
* In this example, we can see via mount, '''/dev/sda1''' is the x86 rootfs, therefore '''/dev/mmcblk0''' is the other drive in the system, which is the MMC/SD card that was inserted and should be used by ./mk_mmc.sh...
+
* In this example, we can see via mount, '''/dev/sda1''' is the x86 rootfs, therefore '''/dev/mmcblk0''' is the other drive in the system, which is the MMC/SD card that was inserted and should be used by the ./mk_mmc.sh script.
  
 
== SGX Video Acceleration ==
 
== SGX Video Acceleration ==
  
 
'''BeagleBone (BBW) & BeagleBone Black (BBB)'''
 
'''BeagleBone (BBW) & BeagleBone Black (BBB)'''
* '''NOTHING in this section currently applies to your device, as we are waiting for 3.8/kms/drm bits from TI.'''
 
  
=== SGX armel/armhf v3.4.x+ ===
+
SGX support will most likely be included with Kernel 3.12 (see TI [http://software-dl.ti.com/dsps/dsps_public_sw/gfxsdk/5_01_00_01/index_FDS.html Graphics SDK release 5.01.00.01]), which is being worked on now (January 2014).
* Note: This is a still a work in progress, but so far all the basic sgx demos seem to work on my Beagle xM C... Thanks to TI for the special armhf binaries!!! --[[User:RobertCNelson|RobertCNelson]] 19:48, 17 July 2012 (UTC)
+
  
* Test with: Precise/12.04 armhf demo image with v3.4.5-x1, desktop was lxde via: "sudo apt-get install lxde lxde-core lxde-icon-theme"
+
== Xorg Drivers ==
  
==== Re-Build Kernel and SGX Kernel Modules ====
+
Script:
  git clone git://github.com/RobertCNelson/stable-kernel.git
+
  cd /opt/scripts/tools/
cd stable-kernel
+
  git pull
  git checkout origin/v3.7.x -b tmp
+
./build_kernel.sh (and then follow the directions as the script runs...)
+
  
Build kernel
+
BeagleBoard/PandaBoard:
  ./build_kernel.sh
+
cd /opt/scripts/tools/graphics/
 +
  ./ti-omapdrm.sh
  
Build SGX modules
+
BeagleBone/BeagleBone Black:
  ./sgx_build_modules.sh
+
cd /opt/scripts/tools/graphics/
 +
  ./ti-tilcdc.sh
  
Insert SD card, make sure to modify MMC in system.sh
+
== Building the Kernel ==
./tools/install_image.sh
+
 
+
Place SD card into the device and boot...
+
cd /opt/sgx
+
sudo tar xf GFX_4.0*_libs.tar.gz
+
sudo ./install-sgx.sh
+
 
+
Reboot, check modules (lsmod):
+
Module                  Size  Used by
+
bufferclass_ti          5727  0
+
omaplfb                11512  0
+
pvrsrvkm              165208  2 bufferclass_ti,omaplfb
+
 
+
Blit Test:
+
ubuntu@omap:/usr/bin/armhf/es5.0$ ./sgx_blit_test
+
------------------ SGX 3D Blit test -----------------
+
----------------------- Start -----------------------
+
Call PVRSRVConnect with a valid argument:
+
  OK
+
Get number of devices from PVRSRVEnumerateDevices:
+
  OK
+
.... Reported 1 devices
+
.... Device Number  | Device Type
+
            0000    | PVRSRV_DEVICE_ID_SGX
+
Attempt to acquire device 0:
+
  OK
+
Getting SGX Client info
+
  OK
+
.... ui32ProcessID:1133
+
Display Class API: enumerate devices
+
  OK
+
PVRSRVEnumerateDeviceClass() returns 1 display device(s)
+
  OK
+
Display Class API: open device
+
  OK
+
Display Class API: Get display info
+
  OK
+
.... Name:PowerVR OMAP Linux Display Driver
+
.... MaxSwapChains:1
+
.... MaxSwapChainBuffers:1
+
.... MinSwapInterval:0
+
.... MaxSwapInterval:1
+
Display Class API: enumerate display formats
+
  OK
+
  OK
+
.... Display format 0 - Pixelformat:1
+
Display Class API: enumerate display dimensions
+
  OK
+
  OK
+
.... Display dimensions 0 - ByteStride:2560 Width:1280 Height:720
+
Attempt to create memory context for SGX:
+
  OK
+
.... Shared heap 0 - HeapID:0x7000000 DevVAddr:0x1000 Size:0x87fe000 Attr:0x2014200
+
.... Shared heap 1 - HeapID:0x7000001 DevVAddr:0xc800000 Size:0xfff000 Attr:0x2024200
+
.... Shared heap 2 - HeapID:0x7000002 DevVAddr:0xe400000 Size:0x7f000 Attr:0x2024200
+
.... Shared heap 3 - HeapID:0x7000003 DevVAddr:0xf000000 Size:0x3ff000 Attr:0x2024200
+
.... Shared heap 4 - HeapID:0x7000004 DevVAddr:0xf400000 Size:0x4ff000 Attr:0x2014200
+
.... Shared heap 5 - HeapID:0x7000005 DevVAddr:0xfc00000 Size:0x1ff000 Attr:0x2014200
+
.... Shared heap 6 - HeapID:0x7000006 DevVAddr:0xdc00000 Size:0x7ff000 Attr:0x2014200
+
.... Shared heap 7 - HeapID:0x7000007 DevVAddr:0xe800000 Size:0x7ff000 Attr:0x2014200
+
.... Shared heap 8 - HeapID:0x7000008 DevVAddr:0xd800000 Size:0x3ff000 Attr:0x2024200
+
.... Shared heap 9 - HeapID:0x7000009 DevVAddr:0x8800000 Size:0x0 Attr:0x2024200
+
.... Shared heap 10 - HeapID:0x700000a DevVAddr:0x8800000 Size:0x3fff000 Attr:0x2014200
+
Display Class API: get the system (primary) buffer
+
  OK
+
Display Class API: map display surface to SGX
+
  OK
+
Attempt to create transfer context for SGX:
+
  OK
+
Do a SRCCOPY blit to the bottom right quadrant of the display:
+
(bottom right quadrant should be red on blue background):
+
  OK
+
  OK
+
Do a SRCCOPY blit to the top left quadrant of the display:
+
(top left quadrant should be striped (r/g/b/w) on blue background):
+
  OK
+
  OK
+
Do a CUSTOMSHADER blit to the top right quadrant of the display:
+
(top right quadrant should be yellow):
+
0xb6acd000 (host) 0xf407000 (device): Device mem for custom shader program
+
0xb6acb000 (host) 0xf408000 (device): Device mem for texture
+
USE custom shader program: 0x28841001.c0000000 mov.end o0, sa0
+
  OK
+
Do a SRCCOPY blit with COLOUR DOWNSAMPLING from ARGB8888 to RGB565
+
and then present the RGB565 to the bottom right quadrant of the screen
+
(bottom right quadrant should be a red gradient):
+
  OK
+
  OK
+
  OK
+
  OK
+
Free the off screen surfaces:
+
  OK
+
  OK
+
  OK
+
  OK
+
Destroy the transfer context:
+
  OK
+
Display Class API: unmap display surface from SGX
+
  OK
+
Destroy Device Memory Context
+
Display Class API: close the device
+
  OK
+
Release SGX Client Info:
+
  OK
+
Disconnect from services:
+
  OK
+
------------------ SGX 3D Blit test -----------------
+
------------------------ End ------------------------
+
 
+
=== SGX Legacy armel only upto v3.2.x ===
+
NOTE: this only works on BeagleBoard hardware, BeagleBone stuff is in development..
+
 
+
Requirements: stable-kernel (the Demo Images hosted on rcn-ee.net meet this requirement)
+
  https://github.com/RobertCNelson/stable-kernel
+
 
+
Note: Due to a bug (seems to only effect older Beagle Bx/Cx boards, use v3.0.8-x3 based kernels)
+
https://github.com/RobertCNelson/stable-kernel/issues/8
+
oneiric:
+
wget http://rcn-ee.net/deb/oneiric/v3.0.8-x3/install-me.sh
+
/bin/bash install-me.sh
+
 
+
==== SDK unPackage Script ====
+
 
+
Download the latest version of the "create_sgx_package.sh" script
+
2.6.37
+
wget https://raw.github.com/RobertCNelson/tools/master/x86/ti_omap/create_sgx_package_2.6.37.sh
+
2.6.38->3.2.x
+
wget https://raw.github.com/RobertCNelson/tools/master/x86/ti_omap/create_sgx_package_3.2.x.sh
+
 
+
Make script executable
+
chmod a+x ./create_sgx_package_*.sh
+
 
+
Run script
+
./create_sgx_package_*.sh
+
 
+
After Successfully running:
+
 
+
:~/temp$ ls
+
create_sgx_package.sh
+
GFX_X_XX_XX_XX_libs.tar.gz                      : -> Copy to Beagle (System Libs)
+
GFX_Linux_SDK.tar.gz                            : -> Copy to Beagle (DEMO's)
+
Graphics_SDK_setuplinux_X_XX_XX_XX.bin
+
SDK
+
SDK_BIN
+
 
+
==== Beagle: GFX_*_libs.tar.gz ====
+
 
+
tar xf GFX_4_00_00_01_libs.tar.gz  (extracts install-SGX.sh and run-SGX.sh)
+
./install-SGX.sh (copies necessary SGX libs and startup script)
+
./run-SGX.sh (force run the new init script, or you can just reboot...)
+
 
+
On successful install:
+
Stopping PVR
+
Starting PVR
+
Starting SGX fixup for ES2.x (or ES3.x) (or ES5.x xM)
+
 
+
Reboot for good measure (Maverick's Alpha-1 needs this....)
+
sudo reboot
+
 
+
==== Beagle: GFX_Linux_SDK.tar.gz ====
+
 
+
tar xf GFX_Linux_SDK.tar.gz
+
cd GFX_Linux_SDK
+
tar xf OGLES.tar.gz
+
 
+
==== Test SGX with a DEMO ====
+
 
+
cd OGLES/SDKPackage/Binaries/CommonX11/Demos/EvilSkull
+
./OGLESEvilSkull
+
 
+
==== Trouble Shooting ====
+
 
+
sudo rm /etc/powervr-esrev
+
sudo depmod -a omaplfb
+
sudo /etc/init.d/pvr restart
+
 
+
== DSP ==
+
 
+
=== gst-dsp ===
+
 
+
The following Gstreamer elements will be installed:
+
 
+
  $ gst-inspect | grep dsp
+
  dvdspu:  dvdspu: Sub-picture Overlay
+
  dsp:  dspdummy: DSP dummy element
+
  dsp:  dspvdec: DSP video decoder
+
  dsp:  dspadec: DSP audio decoder
+
  dsp:  dsph263enc: DSP video encoder
+
  dsp:  dspmp4venc: DSP MPEG-4 video encoder
+
  dsp:  dspjpegenc: DSP video encoder
+
  dsp:  dsph264enc: DSP video encoder
+
  dsp:  dspvpp: DSP VPP filter
+
  dsp:  dspipp: DSP IPP
+
 
+
Please note that h264 encoder (dsph264enc) will not work because of missing h264venc_sn.dll64P DSP part. [http://groups.google.com/group/omapdiscuss/msg/76d928726656c5fe According to this message], it is not available due to a licensing restriction.
+
 
+
Requirements: Kernel built with: "CONFIG_TIDSPBRIDGE=m", for reference, here is what rcn-ee.net's image/deb's are configured for:
+
ubuntu@arm:~$ zcat /proc/config.gz | grep TIDSP
+
CONFIG_TIDSPBRIDGE=m
+
CONFIG_TIDSPBRIDGE_MEMPOOL_SIZE=0x600000
+
CONFIG_TIDSPBRIDGE_RECOVERY=y
+
# CONFIG_TIDSPBRIDGE_CACHE_LINE_CHECK is not set
+
# CONFIG_TIDSPBRIDGE_NTFY_PWRERR is not set
+
# CONFIG_TIDSPBRIDGE_BACKTRACE is not set
+
 
+
On the xM: if 3.2.x is too jerky, try 3.4.x and use the create_dsp_package.sh script, as the module changed..
+
 
+
Download the latest version of the "create_dsp_package.sh" script
+
wget https://raw.github.com/RobertCNelson/tools/master/x86/ti_omap/create_dsp_package.sh
+
 
+
Make script executable
+
chmod a+x ./create_dsp_package.sh
+
 
+
Package script:
+
./create_dsp_package.sh
+
 
+
Copy DSP_Install_libs.tar.gz to Beagle
+
 
+
Setup network...
+
 
+
Extract:
+
ubuntu@arm:~$ tar xf DSP_Install_libs.tar.gz
+
 
+
Install:
+
ubuntu@arm:~$ ./install-DSP.sh
+
 
+
What got installed:
+
ubuntu@arm:~$ ls -lh /lib/dsp/
+
total 7.1M
+
-rwxr-xr-x 1 root root 1.3M Dec  3 10:56 baseimage.dof
+
-rwxr-xr-x 1 root root  51K Dec  3 10:56 conversions.dll64P
+
-rwxr-xr-x 1 root root  13K Dec  3 10:56 dctn_dyn.dll64P
+
-rwxr-xr-x 1 root root 2.5M Dec  3 10:56 h264vdec_sn.dll64P
+
-rwxr-xr-x 1 root root 481K Dec  3 10:56 jpegdec_sn.dll64P
+
-rwxr-xr-x 1 root root 229K Dec  3 10:56 jpegenc_sn.dll64P
+
-rwxr-xr-x 1 root root 767K Dec  3 10:56 m4venc_sn.dll64P
+
-rwxr-xr-x 1 root root 890K Dec  3 10:56 mp4vdec_sn.dll64P
+
-rwxr-xr-x 1 root root 707K Dec  3 10:56 mpeg4aacdec_sn.dll64P
+
-rwxr-xr-x 1 root root  15K Dec  3 10:56 qosdyn_3430.dll64P
+
-rwxr-xr-x 1 root root  14K Dec  3 10:56 ringio.dll64P
+
-rwxr-xr-x 1 root root 9.1K Dec  3 10:56 TSPA_Object_Code_Software_License_Agreement.txt
+
-rwxr-xr-x 1 root root  53K Dec  3 10:56 usn.dll64P
+
-rwxr-xr-x 1 root root 245K Dec  3 10:56 vpp_sn.dll64P
+
 
+
Building gst-dsp stuff:
+
 
+
If you installed this image via the demo images or netinstall, the gst-dsp build script is installed:
+
 
+
Update arm tools directory to the latest:
+
ubuntu@arm:~$ cd /boot/uboot/tools/
+
ubuntu@arm:/boot/uboot/tools$ sudo ./update.sh
+
 
+
Otherwise, install via git:
+
git clone git://github.com/RobertCNelson/tools.git
+
 
+
Change to the pkgs directory
+
ubuntu@arm:~$ cd /boot/uboot/tools/pkgs
+
(or if just cloned)
+
ubuntu@arm:~$ cd ~/tools/pkgs
+
 
+
Build gst-dsp stuff..
+
./ti-tidspbridge.sh
+
 
+
Start dspbridge (or just reboot)
+
sudo /etc/init.d/dsp_init start
+
 
+
Test dspbridge
+
sudo dsp-test
+
 
+
Playbin:
+
sudo gst-launch playbin2 uri=file://(file)
+
 
+
Example: (using http://www.bigbuckbunny.org/index.php/download/ 854x480 mp4 )
+
Note: it seems broken in Ubuntu precise armhf...
+
 
+
sudo gst-launch playbin2 uri=file:///home/USER/big_buck_bunny_480p_surround-fix.avi
+
 
+
Screenshot: (on my xm it's a little jerky at the moment, investigating..)
+
http://rcn-ee.net/bugs/dsp/dsp_v3.2.1-x2-test.jpg
+
 
+
== Xorg omapfb Drivers ==
+
 
+
By default Ubuntu will try to use the FBDEV video driver, however for the BeagleBoard we can take advantage of a more software optimized driver (still not using the sgx video hardware) using the NEON extensions of the Cortex-A8 core.
+
 
+
cat /var/log/Xorg.0.log | grep FBDEV
+
(II) FBDEV: driver for framebuffer: fbdev
+
(II) FBDEV(0): using default device
+
(II) FBDEV(0): Creating default Display subsection in Screen section
+
(==) FBDEV(0): Depth 16, (==) framebuffer bpp 16
+
(==) FBDEV(0): RGB weight 565
+
 
+
Login into Ubuntu and open a new terminal, xorg has to be running..
+
 
+
xvinfo -display :0.0
+
X-Video Extension version 2.2
+
screen #0
+
  no adaptors present
+
 
+
=== Drivers ===
+
 
+
Note: These are built with neon optimizations: http://git.debian.org/?p=collab-maint/xf86-video-omapfb.git;a=blob;f=debian/rules;h=c2f0d5391c96c5abb60b1e691ad86bb27e0c17d8;hb=HEAD  (line 48/49)
+
 
+
Lucid:
+
sudo apt-get install xserver-xorg-video-omap3
+
 
+
To verify it was correctly installed, reboot and:
+
 
+
cat /var/log/Xorg.0.log | grep omapfb
+
(II) LoadModule: "omapfb"
+
(II) Loading /usr/lib/xorg/modules/drivers//omapfb_drv.so
+
(II) Module omapfb: vendor="X.Org Foundation"
+
(II) omapfb: Driver for OMAP framebuffer (omapfb) and external LCD controllers:
+
(WW) Error opening /sys/devices/platform/omapfb/ctrl/name: No such file or directory
+
(II) omapfb(0): VideoRAM: 1800KiB (SDRAM)
+
(II) omapfb(0): Creating default Display subsection in Screen section
+
(**) omapfb(0): Depth 16, (--) framebuffer bpp 16
+
(==) omapfb(0): RGB weight 565
+
(==) omapfb(0): Default visual is TrueColor
+
(--) omapfb(0): Virtual size is 1280x720 (pitch 1280)
+
(**) omapfb(0):  Built-in mode "current"
+
(==) omapfb(0): DPI set to (96, 96)
+
(II) omapfb(0): DPMS enabled
+
(II) omapfb(0): Video plane capabilities:
+
(II) omapfb(0): Video plane supports the following image formats:
+
(II) omapfb(0): XVideo extension initialized
+
 
+
Login into Ubuntu and open a new terminal, xorg has to be running..
+
 
+
xvinfo -display :0.0
+
X-Video Extension version 2.2
+
screen #0
+
  Adaptor #0: "OMAP XV adaptor"
+
    number of ports: 1
+
    port base: 56
+
    operations supported: PutImage
+
    supported visuals:
+
      depth 16, visualID 0x21
+
    number of attributes: 1
+
    etc..
+
 
+
== Changing DVI output resolution ==
+
 
+
Ubuntu 10.10 above defaults to a resolution of 1284x768@16. This is set in the boot.cmd file in the boot partition of the SD card. To change the resolution the DVI output, edit boot.cmd accordingly then recreate the boot.scr file by:
+
 
+
mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "Ubuntu 10.10" -d ./boot.cmd ./boot.scr
+
 
+
Then reboot the BeagleBoard.
+
 
+
== S-Video ==
+
''(For configuring S-Video on Angstrom, click [[BeagleBoardAngstrom#Configuring_uEnv.txt_to_set_s-video_as_the_default_display|here]])''.
+
 
+
===Process for setting up S-Video===
+
 
+
S-video is tested to be working on 2.6.35-rc5-dl9. BeagleBoard s-video output has traditionally been enabled by "using bootargs (boot arguments) at uboot". In newer versions of the BeagleBoard, the developers have made things easier by instructing U-Boot to look for a .scr file about a dozen lines long that is called cmd.boot.scr, and then follow said parameters. In Angstrom, no boot.scr file is needed, instead, an even easier system is used, where a simple editable .txt file called uEnv.txt containing these parameters suffices (Env is for "environment"). For some reason, in the Ubuntu download files, typically there a bit of convoluted process where uEnv.txt is called up, uEnv.txt says "Go read conf.boot.scr", and cmd.boot.scr sets up the s-video.
+
 
+
To make cmd.boot.scr, create a text file named cmd.boot, then convert it into a .scr file with mkimage by running the following commands on the terminal:
+
 
+
First, you will probably need to get mkimage with apt-get. Run
+
 
+
    sudo apt-get install mkimage
+
 
+
Next, convert your cmd.boot.scr
+
 
+
    mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n 'Execute uImage' -d boot.cmd boot.scr
+
 
+
===Bootargs: make this cmd.boot to set s-video===
+
 
+
* NTSC
+
 
+
    omapfb.mode='''tv:ntsc'''
+
    omapdss.def_disp='''tv'''
+
 
+
Bootargs that has been validated.
+
 
+
    setenv bootargs 'console=tty0 console=ttyO2,115200n8 root=/dev/mmcblk0p2 rootwait ro vram=12M omapfb.mode=tv:ntsc omapdss.def_disp=tv
+
    fixrtc buddy=unknown'
+
 
+
===Screen cutoff problem===
+
 
+
NTSC resolution is supposed to be 640x480. However the edge bands around the TV screen differ from TV to TV. Output of '''fbset''' shown below:
+
 
+
    mode "720x482-30"
+
        # D: 13.500 MHz, H: 15.734 kHz, V: 29.970 Hz
+
        geometry 720 482 720 482 32
+
        timings 74074 16 58 6 31 64 6
+
        rgba 8/16,8/8,8/0,0/0
+
    endmode
+
 
+
Depending on your TV device, and what desktop you are running a certain amount of screen cutoff is likely to occur. This is called [http://en.wikipedia.org/wiki/Overscan overscan]. Typically, around 5-10% of the left and right edges of display are off the screen (using Ubuntu with xfce). This seems to be due to the fact that there is only one display resolution that is set for NTSC: <!-- I don't know about PAL--> 720 X 482. It is not possible to change this setting in the xfce4 Settings Manager like one would normally be able to do, because other options are greyed out/do not exist. Normally, even if the Settings Manager did not allow for it, a different resolution setting could be obtained by editing the xorg.conf file in /etc/X11/xorg.conf-4, or some similar place. HOWEVER there is no xorg.conf file in the Beagle version of xfce. xrandr shows the display is set to the minimum of 720x574. Adding an xorg.conf does not fix the problem, because Beagle takes its (analog) display resolution settings directly from the display driver, where 720 X 480 (720 X 574 for PAL <!-- This I gather, but I really don't know--> ) is hard coded in. 
+
 
+
An inelegant but usable workaround for the xfce desktop environment is simply to create vertical and horizontal panels that fill up the space that is cut off on the screen. This is not a complete solution, but at least it will prevent maximized windows from going off into nowhere land.
+
 
+
Truly fixing this would involve going into the display driver and reprogramming it to include additional S-video settings besides just NTSC and PAL. Specifically, to make the whole framebuffer fit on the screen you would need to adjust the overlay in the display driver, the OMAP DSS2. (Didn't test this yet. Some pointers from the driver's documentation below)
+
 
+
    /sys/devices/platform/omapdss/overlay? directory:
+
    enabled 0=off, 1=on
+
    input_size width,height (ie. the framebuffer size)
+
    manager Destination overlay manager name
+
    name
+
    output_size width,height
+
    position x,y
+
    screen_width width
+
    global_alpha  global alpha 0-255 0=transparent 255=opaque
+
 
+
== Building Kernel ==
+
  
 
https://github.com/RobertCNelson/stable-kernel
 
https://github.com/RobertCNelson/stable-kernel
  
Download SRC
+
Download Source:
 
  git clone git://github.com/RobertCNelson/stable-kernel.git
 
  git clone git://github.com/RobertCNelson/stable-kernel.git
  
Build kernel
+
Build the kernel:
 
  ./build_kernel.sh
 
  ./build_kernel.sh
  
Optional building the deb file
+
Optionally building the *.deb file:
 
  ./build_deb.sh
 
  ./build_deb.sh
 
  
 
= Swapfile =
 
= Swapfile =
Line 896: Line 480:
 
== Using a File for Swap Instead of a Partition ==
 
== Using a File for Swap Instead of a Partition ==
  
On the Bealgeboard you should expect to need a swap file given the limitation of how much RAM they have (between 256&nbsp;MB and 512&nbsp;MB). Some system programs like apt-get will only run properly when some swap space is present (due to 256&nbsp;MB not being enough RAM).
+
On the Beagleboard you should expect to require a swap file given the limitation of how little RAM is available (between 256&nbsp;MB and 512&nbsp;MB). Some system programs like apt-get will only run properly when some swap space is present (due to 256&nbsp;MB not being enough RAM).
  
Some images such as those from Linaro.org do not come with a swap partition or any swap space allocated.
+
Some images (such as those from Linaro.org) do not come with a swap partition or any swap space allocated.
  
Under Linux swap space can be either a dedicated partition or a single file. Both can be mounted as swap which the OS can access.
+
Under Linux, swap space can be either a dedicated partition or a swap file. Both can be mounted as swap which the OS can access.
  
 
=== Creating a Swapfile ===
 
=== Creating a Swapfile ===
  
The following commands will create a 1 gigabyte file, lock access to only root, format it as swap and then advertise it to the OS.
+
The following commands will create a 1 GB file, limit access only to root, format it as swap and then make it available to the OS:
  
 
  sudo mkdir -p /var/cache/swap/   
 
  sudo mkdir -p /var/cache/swap/   
Line 912: Line 496:
 
  sudo swapon /var/cache/swap/swapfile  
 
  sudo swapon /var/cache/swap/swapfile  
  
To ask the OS to load this swapfile on each start up, edit the /etc/fstab file to include the following additional line:
+
To tell the OS to load this swapfile on each start up, edit the /etc/fstab file to include the following additional line:
  
 
  /var/cache/swap/swapfile    none    swap    sw    0  0
 
  /var/cache/swap/swapfile    none    swap    sw    0  0
  
To verify that the swapfile is accessilble as swap to the OS, run "top" of "htop" at a console.
+
To verify that the swapfile is accessilble as swap to the OS, run "top" or "htop" at a console.
  
 
= Ubuntu Software =
 
= Ubuntu Software =
Line 924: Line 508:
 
=== /etc/network/interfaces ===
 
=== /etc/network/interfaces ===
  
It is possible and relatively easy to configure a Wi-Fi card from the command line.
+
It is relatively easy to configure a Wi-Fi card from the command line.
  
 
You will need to edit the /etc/network/interfaces file. There are several guides available via Google.
 
You will need to edit the /etc/network/interfaces file. There are several guides available via Google.
Line 943: Line 527:
 
  wpa-group CCMP
 
  wpa-group CCMP
 
  wpa-key-mgmt WPA-PSK
 
  wpa-key-mgmt WPA-PSK
  wpa-psk < INSERT KEY XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX>
+
  wpa-psk <INSERT KEY XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX>
  
Your Wi-Fi card will automatically load these settings on start up and give network access.
+
Your Wi-Fi card will automatically load these settings upon startup and initialize wireless network access.
  
 
== Lightweight window managers ==
 
== Lightweight window managers ==
Line 951: Line 535:
 
If you intend to use Ubuntu on the BeagleBoard you can install JWM or IceWM to improve performance.
 
If you intend to use Ubuntu on the BeagleBoard you can install JWM or IceWM to improve performance.
  
JWM in particular uses little RAM. On a BeagleBoard with 256&nbsp;MB, using JWM will leave about 60&nbsp;MB free to run applications in.
+
JWM in particular uses little RAM. On a BeagleBoard with 256&nbsp;MB, using JWM will leave about 60&nbsp;MB free in which to run applications.
  
 
== Web Apps ==
 
== Web Apps ==
  
 
=== Midori ===
 
=== Midori ===
Given that the BeagleBoard has fewer resources than a desktop a light-weight browser is more responsive. Midori is a light-weight browser that still supports flash, etc. It is available from the standard repositories.
+
Given that the BeagleBoard has fewer resources than a desktop a lightweight browser is more responsive. Midori is a lightweight browser that still supports flash, etc. It is available from the standard repositories:
 
http://en.wikipedia.org/wiki/Midori_%28web_browser%29
 
http://en.wikipedia.org/wiki/Midori_%28web_browser%29
  
Line 964: Line 548:
 
If you have a video source (webcam, IP cam, etc.) which appears as /dev/video0, etc. then you can use the Linux surveillance software "motion" to monitor the video stream and record periods of activity.
 
If you have a video source (webcam, IP cam, etc.) which appears as /dev/video0, etc. then you can use the Linux surveillance software "motion" to monitor the video stream and record periods of activity.
  
Motion is also available from the standard repositories.
+
Motion is also available from the standard repositories:
 
http://www.debian-administration.org/article/An_Introduction_to_Video_Surveillance_with_%27Motion%27
 
http://www.debian-administration.org/article/An_Introduction_to_Video_Surveillance_with_%27Motion%27
 
Using a 960x720 resolution webcam with a 15&nbsp;fps rate under the UVC driver the Rev C BeagleBoard under Xubuntu reports ~60% CPU utilisation.
 
Using a 960x720 resolution webcam with a 15&nbsp;fps rate under the UVC driver the Rev C BeagleBoard under Xubuntu reports ~60% CPU utilisation.
  
To make the BeagleBoard automatically start recording on boot do the following:
+
To make the BeagleBoard automatically start recording on boot, do the following:
  
 
* Auto Login - run "gdmsetup" from a terminal and select a user to automatically login  
 
* Auto Login - run "gdmsetup" from a terminal and select a user to automatically login  
 
* Sessions - make sure you don't save any previous X Windows sessions so that it doesn't prompt you for which one you want
 
* Sessions - make sure you don't save any previous X Windows sessions so that it doesn't prompt you for which one you want
* motion.conf - amend /etc/motion/motion.conf to the settings you want (that is, video output directory, record only video, record in MPEG-4, set frame rate, etc). Do this with "sudo medit /etc/motion/motion.conf" at a prompt.
+
* motion.conf - edit /etc/motion/motion.conf to use the settings you want (that is, video output directory, record only video, record in MPEG-4, set frame rate, etc). Do this with "sudo medit /etc/motion/motion.conf" at a prompt.
* Boot script - create a new script in /etc/rc2.d called "S65motion_client" and set permissions appropriately ("sudo chmod 777 /etc/rc2.d/S65motion_client"). Then edit the file so it has the following text in it:
+
* Boot script - create a new script in /etc/rc2.d called "S65motion_client" and set permissions appropriately ("sudo chmod 777 /etc/rc2.d/S65motion_client"). Then edit the file so it contains the following lines:
  
 
  #! /bin/sh
 
  #! /bin/sh
Line 980: Line 564:
 
This will now launch the motion client as root when you boot up.
 
This will now launch the motion client as root when you boot up.
  
Also note that unless your BeagleBoard can remember the time (battery backed up clock installed) the timestamps will not be correct until you update the time. If your BeagleBoard has an Internet connection this can be achieved with the ntpdate application.
+
Also note that unless your BeagleBoard can remember the time (battery backed up clock installed), the timestamps will not be correct until you update the time. If your BeagleBoard has an Internet connection this can be achieved using the ntpdate application.
  
 
== Robotics ==
 
== Robotics ==
  
 
=== ROS ===
 
=== ROS ===
Willow Garage hosts the open source Robotic Operating System (ROS). Whilst it is natively supported in Ubuntu, the official packages are only for the x86 platform. ROS can be installed from source and is generally easy to do so (although slow).
+
Willow Garage hosts the open source Robotic Operating System (ROS). While it is natively supported in Ubuntu, the official packages are only for the x86 platform. ROS can be installed from source and is generally easy to do so (although slow).
  
 
Following the instructions from here will build and install ROS on your BeagleBoard:
 
Following the instructions from here will build and install ROS on your BeagleBoard:

Revision as of 14:56, 13 February 2014

(For BeagleBoardAngstrom, click here.) (Should Beagleboard:Ubuntu On BeagleBone Black be merged into this page?)

This page is about running a Linux distribution (ARM EABI) Ubuntu on the BeagleBoard. BeagleBoard will boot the (ARM EABI) Ubuntu distribution from the SD card. Since much of this page is generic, it has also been extended to help support devices such as the PandaBoard and BeagleBone.

  • For the best experience, make sure you have an LCD/HDMI monitor attached to the BeagleBoard's HDMI port, 2 GB/4 GB/8 GB SD card, and a known good USB 2.0 hub with mouse and keyboard.

Help

If you need any help:

  • Ubuntu related help:
    • #ubuntu-arm: Ubuntu's ARM IRC on Freenode (logs -> year -> month -> day -> #ubuntu-arm.html)
  • When requesting help, please provide some debugging information:
    • U-Boot Version installed on board
    • Kernel Version: uname -a
    • pastebin dmesg
      • Copy from serial port or use "dmesg | pastebinit" (sudo apt-get install pastebinit)

Required Beagle Software

Mainline U-Boot:

  • All older BeagleBoard (classic) Ax, Bx, Cx and Dx boards are required to upgrade to at least these U-Boot versions
  • XM Boards have no NAND, so MLO/u-boot.img is always required on the first partition
  • Directions: Upgrade X-loader and U-Boot

Omap Serial Changes

boot.scr/boot.cmd changes:

With 2.6.35:

console=ttyS2,115200n8

With 2.6.36/37+:

console=ttyO2,115200n8

Serial console login: /etc/init/ttyO2.conf

start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]

respawn
exec /sbin/getty 115200 ttyO2


Method 1: Download a Complete Pre-Configured Image

Demo Image

  • These demonstration images contain a custom Mainline based kernel with experimental enhancements to the boards supported. They are usually updated about once a month, as new features/enhancements get added by the community. Currently, this image ships with two kernels "armv7" which is for mainline omap3+ devices (BeagleBoard/PandaBoard) and the "bone" which is specifically for the BeagleBone. The kernel is stress-tested by a farm of Panda/Beagles running 24/7 under a heavy load (building gcc trunk/mainline kernel).
git clone git://github.com/RobertCNelson/armv7-multiplatform.git
cd armv7-multiplatform
git checkout origin/v3.13.x -b tmp
./build_kernel.sh
git clone git://github.com/RobertCNelson/linux-dev.git
cd linux-dev
git checkout origin/am33x-v3.8 -b tmp
./build_kernel.sh
  • Advanced Users only: Userspace, used in these demo images:
https://github.com/RobertCNelson/omap-image-builder

If the script in these demo images fail: email "bugs@rcn-ee.com" I will need details: terminal command, terminal log, distribution name, arch...

Saucy 13.10

Image Updated:

  • 2014-01-24
    • Beagle/Beagle xM: v3.13.0-armv7-x9 kernel
    • BeagleBone/BeagleBone Black: v3.8.13-bone37 kernel
  • 2013-12-17
    • Beagle xM (ONLY): v3.12.5-armv7-x10 kernel (--dtb dt-beagle-xm)
    • BeagleBone/BeagleBone Black: v3.8.13-bone32 kernel
    • Beagle/Panda/Panda ES: v3.7.10-x13 kernel
  • 2013-11-15
    • Beagle xM (ONLY): v3.12.0-armv7-x8 kernel (--dtb dt-beagle-xm)
    • BeagleBone/BeagleBone Black: v3.8.13-bone30 kernel
      • audio/mmc fixes...
    • Beagle/Panda/Panda ES: v3.7.10-x13 kernel

Services Active:

Note: Depending on your internal network these may work out of the box
Apache, Port 80: http://arm/ (Bone: via usb) http://192.168.7.2
SSH, Port 22: ssh ubuntu@arm (Bone: via usb) ubuntu@192.168.7.2
Getty, Serial Port

Default user: ubuntu pass: temppwd

Get prebuilt image:

wget https://rcn-ee.net/deb/rootfs/saucy/ubuntu-13.10-console-armhf-2014-01-24.tar.xz

Verify Image with:

md5sum ubuntu-13.10-console-armhf-2014-01-24.tar.xz
e199c4c20091abcf1ed025ee54856055  ubuntu-13.10-console-armhf-2014-01-24.tar.xz

Unpack Image:

tar xf ubuntu-13.10-console-armhf-2014-01-24.tar.xz
cd ubuntu-13.10-console-armhf-2014-01-24

If you don't know the location of your SD card:

sudo ./setup_sdcard.sh --probe-mmc

You should see something like:

Are you sure? I don't see [/dev/idontknow], here is what I do see...

fdisk -l:
Disk /dev/sda: 500.1 GB, 500107862016 bytes <- x86 Root Drive
Disk /dev/sdd: 3957 MB, 3957325824 bytes <- MMC/SD card

lsblk:
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 465.8G  0 disk 
├─sda1   8:1    0 446.9G  0 part /  <- x86 Root Partition
├─sda2   8:2    0     1K  0 part 
└─sda5   8:5    0  18.9G  0 part [SWAP]
sdd      8:48   1   3.7G  0 disk 
├─sdd1   8:49   1    64M  0 part 
└─sdd2   8:50   1   3.6G  0 part 
  • In this example, we can see via mount, /dev/sda1 is the x86 rootfs, therefore /dev/sdd is the other drive in the system, which is the MMC/SD card that was inserted and should be used by ./setup_sdcard.sh...

Install Image:

Quick install script for [board]

sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot board

[board] options:

  • BeagleBone/Black - bone

So for the BeagleBone:

sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot bone

Quick install script for [board] (using new --dtb option)

sudo ./setup_sdcard.sh --mmc /dev/sdX --dtb board

board options:

  • BeagleBoard Ax/Bx/Cx/Dx - omap3-beagle
  • BeagleBoard xM - omap3-beagle-xm

So for the BeagleBoard xM:

sudo ./setup_sdcard.sh --mmc /dev/sdX --dtb omap3-beagle-xm

You should now be able to unmount the SD card from your PC, insert into your Board, reboot and have the OS loaded.

For a basic framebuffer driven desktop environment: (make sure network is setup):

Ethernet: sudo ifconfig -a and sudo dhclient usb1 or sudo dhclient eth0
Wireless: http://elinux.org/BeagleBoardUbuntu#Wi-Fi_Networking_.28command_line.29

Then run:

/bin/sh /boot/uboot/tools/ubuntu/small-lxde-desktop.sh

Advanced: Build Image:

Built with a fork of project-rootstock (ARM native mode, runs directly on BeagleBoard), using a script from omap-image-builder:

git clone git://github.com/RobertCNelson/omap-image-builder.git
cd omap-image-builder
git checkout v2014.01-1 -b tmp
touch release
./rcn-ee_image.sh

Raring 13.04

Image Updated:

  • 2014-01-24
    • Beagle/Beagle xM: v3.13.0-armv7-x9 kernel
    • BeagleBone/BeagleBone Black: v3.8.13-bone37 kernel
  • 2013-12-17
    • Beagle xM (ONLY): v3.12.5-armv7-x10 kernel (--dtb dt-beagle-xm)
    • BeagleBone/BeagleBone Black: v3.8.13-bone32 kernel
    • Beagle/Panda/Panda ES: v3.7.10-x13 kernel
  • 2013-11-15
    • Beagle xM (ONLY): v3.12.0-armv7-x8 kernel (--dtb dt-beagle-xm)
    • BeagleBone/BeagleBone Black: v3.8.13-bone30 kernel
      • audio/mmc fixes...
    • Beagle/Panda/Panda ES: v3.7.10-x13 kernel

Get prebuilt image:

wget https://rcn-ee.net/deb/rootfs/raring/ubuntu-13.04-console-armhf-2014-01-24.tar.xz

Verify Image with:

md5sum ubuntu-13.04-console-armhf-2014-01-24.tar.xz
0443f6b38a6a082f5a75f72f8a5cfaf4  ubuntu-13.04-console-armhf-2014-01-24.tar.xz

Unpack image:

tar xf ubuntu-13.04-console-armhf-2014-01-24.tar.xz
cd ubuntu-13.04-console-armhf-2014-01-24

Then follow the directions shown above with the other images...

Trusty 14.04 (experimental)

Image Updated:

  • 2014-01-24
    • Beagle/Beagle xM: v3.13.0-armv7-x9 kernel
    • BeagleBone/BeagleBone Black: v3.8.13-bone37 kernel
  • 2013-12-17
    • Beagle xM (ONLY): v3.12.5-armv7-x10 kernel (--dtb dt-beagle-xm)
    • BeagleBone/BeagleBone Black: v3.8.13-bone32 kernel
    • Beagle/Panda/Panda ES: v3.7.10-x13 kernel
  • 2013-11-15
    • Beagle xM (ONLY): v3.12.0-armv7-x8 kernel (--dtb dt-beagle-xm)
    • BeagleBone/BeagleBone Black: v3.8.13-bone30 kernel
      • audio/mmc fixes...
    • Beagle/Panda/Panda ES: v3.7.10-x13 kernel

Get prebuilt image:

wget https://rcn-ee.net/deb/rootfs/trusty/ubuntu-trusty-console-armhf-2014-01-24.tar.xz

Verify Image with:

md5sum ubuntu-trusty-console-armhf-2014-01-24.tar.xz
ae97d2b7d927685a2bcd15303a1b2766  ubuntu-trusty-console-armhf-2014-01-24.tar.xz

Unpack image:

tar xf ubuntu-trusty-console-armhf-2014-01-24.tar.xz
cd ubuntu-trusty-console-armhf-2014-01-24

Then follow the directions shown above with the other images...

Flasher

eMMC: BeagleBone Black

This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or the win32 image program linked to on CircuitCo's wiki page. First press and hold the boot select button (next to the microSD card), then apply power (same procedure as the official CircuitCo images). The board should boot into Ubuntu and begin flashing the eMMC, once completed all 4 LED's should be full ON. Simply remove power, remove the microSD card and Ubuntu will now boot directly from eMMC.

Script for reference: (this is the script that writes to the eMMC)

https://github.com/RobertCNelson/tools/blob/master/scripts/beaglebone-black-copy-microSD-to-eMMC.sh

BTW: we are only writing about 500 megabytes to the eMMC, so the script will only take about 5-6 Minutes after power on.

Notes:

  • If only two LED's stay lit and nothing happens, the board has crashed due to lack of power. Retry with a 5Volt DC power supply connected.
  • If the 4 LED's blink a constant pattern, the eMMC write has failed. First REMOVE ALL capes, then retry again.
    • (error -84: which may mean you've reached the max number of erase/write cycles...)

User: ubuntu pass: temppwd

Image Updated:

  • 2014-01-24
    • BeagleBone Black: v3.8.13-bone37 kernel
  • 2013-12-17
    • BeagleBone Black: v3.8.13-bone32 kernel
  • 2013-11-15
    • BeagleBone Black: v3.8.13-bone30 kernel
      • ssh host key fixes (auto generated on bootup...)

Get prebuilt image:

wget https://rcn-ee.net/deb/flasher/saucy/BBB-eMMC-flasher-ubuntu-13.10-2014-01-24-2gb.img.xz

Verify Image with:

md5sum BBB-eMMC-flasher-ubuntu-13.10-2014-01-24-2gb.img.xz
2cce18a56e1802657aad15dc700ec200  BBB-eMMC-flasher-ubuntu-13.10-2014-01-24-2gb.img.xz

Follow the "standard" update procedure.

http://circuitco.com/support/index.php?title=Updating_The_Software

Linux:

unxz BBB-eMMC-flasher-ubuntu-13.10-2014-01-24-2gb.img.xz
sudo dd if=./BBB-eMMC-flasher-ubuntu-13.10-2014-01-24-2gb.img of=/dev/sdX

raw microSD img

BeagleBone/BeagleBone Black

This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or the win32 image program linked to on CircuitCo's wiki page. First press and hold the boot select button (next to microSD card), then apply power (same procedure as the official CircuitCo images). The board should boot into Ubuntu.

User: ubuntu pass: temppwd

Auto partition resize:

cd /opt/scripts/tools
git pull
./grow_partition.sh
sudo reboot

Image Updated:

  • 2014-01-24
    • BeagleBone/BeagleBone Black: v3.8.13-bone37 kernel
  • 2013-12-17
    • BeagleBone/BeagleBone Black: v3.8.13-bone32 kernel
  • 2013-11-15
    • BeagleBone/BeagleBone Black: v3.8.13-bone30 kernel

Get prebuilt image:

wget https://rcn-ee.net/deb/microsd/saucy/bone-ubuntu-13.10-2014-01-24-2gb.img.xz

Verify Image with:

md5sum bone-ubuntu-13.10-2014-01-24-2gb.img.xz
c53ab3fb2f97951a1e1fb60c8719ae55  bone-ubuntu-13.10-2014-01-24-2gb.img.xz

Linux:

unxz bone-ubuntu-13.10-2014-01-24-2gb.img.xz
sudo dd if=./bone-ubuntu-13.10-2014-01-24-2gb.img of=/dev/sdX

Method 2: Use the NetInstall method

You will need a 1GB/2GB/4GB/8GB SD card or greater.

Standard system : ~700 MB

Report Bugs/Issues to: https://github.com/RobertCNelson/netinstall/issues (anywhere else will be ignored..)

Download the netinstall script:

git clone git://github.com/RobertCNelson/netinstall.git
cd netinstall

Currently supported Ubuntu distributions:

--distro oneiric (11.10)
--distro precise-armhf (12.04)
--distro quantal (12.10)
--distro raring (13.04)
--distro saucy (13.10)

Device: <board> selection:

*BeagleBoard Ax/Bx/Cx  - omap3-beagle
*BeagleBoard xMA/B/C   - omap3-beagle-xm
*BeagleBone Ax         - am335x-bone-serial
*BeagleBone (DVI cape) - am335x-bone-video
*BeagleBone Black      - am335x-boneblack
*PandaBoard Ax     - omap4-panda
*PandaBoard A4+    - omap4-panda-a4
*PandaBoard ES     - omap4-panda-es

Installation script for new <board> selection: (slowly migrating all devices to this method)

sudo ./mk_mmc.sh --mmc /dev/sdX --dtb <board> --distro <distro>

So for the xM: with quantal:

sudo ./mk_mmc.sh --mmc /dev/sdX --dtb omap3-beagle-xm --distro quantal
  • Other Options:
    • --firmware : installs firmware
    • --serial-mode : debian-installer uses Serial Port

Place SD card into BeagleBoard and boot:

Configure the network:

usb0: USB net <- (usually the OTG port)
eth0: USB net <- (usually the smsc95xx adapter on the BeagleBoard and PandaBoard)
wlan0: Wifi <- Your USDB-Wi-Fi device.. 

See my notes for my testing procedure: https://github.com/RobertCNelson/netinstall/blob/master/test.Ubuntu

Troubleshooting: If booting fails..

  • Hold the user button down to force booting from MMC
  • Upgrade X-loader and U-boot Upgrade X-loader and U-Boot
  • Clear U-boot's Environment Variables in NAND:
nand erase 260000 20000

NetInstall assumptions:

Assume asll <default>'s... Thanks you preseed.conf!!!

Method 3: Manual Install (no automatic scripts)

Note, this section used to have a lot of details, but maintenance of the two wiki's became a pain, so for now on we will just link to my other pages:

Beagle/Beagle xM

http://eewiki.net/display/linuxonarm/BeagleBoard

BeagleBone

http://eewiki.net/display/linuxonarm/BeagleBone

Panda/Panda ES

http://eewiki.net/display/linuxonarm/PandaBoard

Advanced

Install Latest Kernel Image

Script:

cd /opt/scripts/tools
git pull

Stable:

./update_kernel.sh

Testing:

./update_kernel.sh --beta-kernel

Custom: (has to be on rcn-ee.net)

./update_kernel.sh --kernel v3.8.13-bone37

Reboot with your new Kernel Image.

Upgrade X-loader and U-boot

  • Note: the functionality of the "X-Loader" project has been merged as u-boot spl.

Compatibility with older Ax, Bx, Cx, and Dx BeagleBoards

Note: Sometimes on these older boards, you just have to clear out the stored U-Boot environment variables in NAND to make this script work:

nand erase 260000 20000

Or: To fully erase the entire NAND:

nand erase.chip

Requires MMC card:

git clone git://github.com/RobertCNelson/flasher.git
cd flasher

For the Beagle Ax/Bx

sudo ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_bx

For the Beagle Cx/Dx

sudo ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_cx
1: Plug-in a serial cable and start the serial terminal program
2: Place MMC card in Beagle
3: Push and hold the user button
4: Plug-in power
5: Wait for U-Boot countdown to finish, then release the user button
6: Wait for flashing/script to end
7: Power down, remove and reformat MMC card to final OS

If you don't know the location of your SD card:

sudo ./mk_mmc.sh --probe-mmc

You should see something like:

Are you sure? I don't see [/dev/idontknow], here is what I do see...

fdisk -l:
Disk /dev/sda: 500.1 GB, 500107862016 bytes <- x86 Root Drive
Disk /dev/mmcblk0: 3957 MB, 3957325824 bytes <- MMC/SD card

mount:
/dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0) <- x86 Root Partition
  • In this example, we can see via mount, /dev/sda1 is the x86 rootfs, therefore /dev/mmcblk0 is the other drive in the system, which is the MMC/SD card that was inserted and should be used by the ./mk_mmc.sh script.

SGX Video Acceleration

BeagleBone (BBW) & BeagleBone Black (BBB)

SGX support will most likely be included with Kernel 3.12 (see TI Graphics SDK release 5.01.00.01), which is being worked on now (January 2014).

Xorg Drivers

Script:

cd /opt/scripts/tools/
git pull

BeagleBoard/PandaBoard:

cd /opt/scripts/tools/graphics/
./ti-omapdrm.sh

BeagleBone/BeagleBone Black:

cd /opt/scripts/tools/graphics/
./ti-tilcdc.sh

Building the Kernel

https://github.com/RobertCNelson/stable-kernel

Download Source:

git clone git://github.com/RobertCNelson/stable-kernel.git

Build the kernel:

./build_kernel.sh

Optionally building the *.deb file:

./build_deb.sh

Swapfile

Using a File for Swap Instead of a Partition

On the Beagleboard you should expect to require a swap file given the limitation of how little RAM is available (between 256 MB and 512 MB). Some system programs like apt-get will only run properly when some swap space is present (due to 256 MB not being enough RAM).

Some images (such as those from Linaro.org) do not come with a swap partition or any swap space allocated.

Under Linux, swap space can be either a dedicated partition or a swap file. Both can be mounted as swap which the OS can access.

Creating a Swapfile

The following commands will create a 1 GB file, limit access only to root, format it as swap and then make it available to the OS:

sudo mkdir -p /var/cache/swap/   
sudo dd if=/dev/zero of=/var/cache/swap/swapfile bs=1M count=1024
sudo chmod 0600 /var/cache/swap/swapfile 
sudo mkswap /var/cache/swap/swapfile 
sudo swapon /var/cache/swap/swapfile 

To tell the OS to load this swapfile on each start up, edit the /etc/fstab file to include the following additional line:

/var/cache/swap/swapfile    none    swap    sw    0   0

To verify that the swapfile is accessilble as swap to the OS, run "top" or "htop" at a console.

Ubuntu Software

Wi-Fi Networking (command line)

/etc/network/interfaces

It is relatively easy to configure a Wi-Fi card from the command line.

You will need to edit the /etc/network/interfaces file. There are several guides available via Google.

This is a particularly useful guide http://ubuntuforums.org/showthread.php?t=202834

A sample /etc/network/interfaces file for a WPA2 encrypted access point is:

auto lo
iface lo inet loopback
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <NAME OF AP>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <INSERT KEY XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX>

Your Wi-Fi card will automatically load these settings upon startup and initialize wireless network access.

Lightweight window managers

If you intend to use Ubuntu on the BeagleBoard you can install JWM or IceWM to improve performance.

JWM in particular uses little RAM. On a BeagleBoard with 256 MB, using JWM will leave about 60 MB free in which to run applications.

Web Apps

Midori

Given that the BeagleBoard has fewer resources than a desktop a lightweight browser is more responsive. Midori is a lightweight browser that still supports flash, etc. It is available from the standard repositories: http://en.wikipedia.org/wiki/Midori_%28web_browser%29

Surveillance

Motion

If you have a video source (webcam, IP cam, etc.) which appears as /dev/video0, etc. then you can use the Linux surveillance software "motion" to monitor the video stream and record periods of activity.

Motion is also available from the standard repositories: http://www.debian-administration.org/article/An_Introduction_to_Video_Surveillance_with_%27Motion%27 Using a 960x720 resolution webcam with a 15 fps rate under the UVC driver the Rev C BeagleBoard under Xubuntu reports ~60% CPU utilisation.

To make the BeagleBoard automatically start recording on boot, do the following:

  • Auto Login - run "gdmsetup" from a terminal and select a user to automatically login
  • Sessions - make sure you don't save any previous X Windows sessions so that it doesn't prompt you for which one you want
  • motion.conf - edit /etc/motion/motion.conf to use the settings you want (that is, video output directory, record only video, record in MPEG-4, set frame rate, etc). Do this with "sudo medit /etc/motion/motion.conf" at a prompt.
  • Boot script - create a new script in /etc/rc2.d called "S65motion_client" and set permissions appropriately ("sudo chmod 777 /etc/rc2.d/S65motion_client"). Then edit the file so it contains the following lines:
#! /bin/sh
/usr/bin/motion -c /etc/motion/motion.conf

This will now launch the motion client as root when you boot up.

Also note that unless your BeagleBoard can remember the time (battery backed up clock installed), the timestamps will not be correct until you update the time. If your BeagleBoard has an Internet connection this can be achieved using the ntpdate application.

Robotics

ROS

Willow Garage hosts the open source Robotic Operating System (ROS). While it is natively supported in Ubuntu, the official packages are only for the x86 platform. ROS can be installed from source and is generally easy to do so (although slow).

Following the instructions from here will build and install ROS on your BeagleBoard:

http://www.ros.org/wiki/cturtle/Installation/Ubuntu/SVN

You will need an Internet connection for your BeagleBoard for these scripts to work.

For more information about ROS, see www.ros.org.