Difference between revisions of "BeagleBoardUbuntu"

From eLinux.org
Jump to: navigation, search
m (Quantal 12.10 armhf testing: ubuntu-quantal-beta2-minimal-armhf-2012-09-27.tar.xz)
m (Undo revision 342674 by Mickeyf (talk) NAK: it's /opt/scripts/ https://github.com/RobertCNelson/omap-image-builder/blob/master/scripts/chroot.sh#L679)
 
(120 intermediate revisions by 9 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 (ARM [http://wiki.debian.org/ArmEabiPort EABI]) [http://www.ubuntu.com/ Ubuntu] distribution at [[BeagleBoard]]. BeagleBoard will boot the (ARM EABI) Ubuntu distribution from [[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 [https://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, 2GB/4GB/8GB SD card, and a known good usb2.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.
  
 
= Help =
 
= Help =
Line 14: Line 15:
  
 
*Kernel related help:
 
*Kernel related help:
** [http://groups.google.com/group/beagleboard Email Beagleboard user group] *Recommended method
+
** [https://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 Stable Kernel 3.2.x src]
+
*** [https://github.com/RobertCNelson/stable-kernel/tree/v3.7.x Stable (3.7.x) branch]
*** [https://github.com/RobertCNelson/linux-dev Development Kernel src]
+
*** [https://github.com/RobertCNelson/linux-dev Development Kernel source code]
  
 
*Ubuntu related help:
 
*Ubuntu related help:
** ''#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 31: Line 32:
 
= Required Beagle Software =  
 
= Required Beagle Software =  
  
Angstrom's X-loader/MLO & U-Boot
+
Mainline U-Boot:
* All Old Ax, Bx, Cx Boards are required to upgrade to atleast these MLO and 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 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 54: Line 55:
  
 
= Method 1: Download a Complete Pre-Configured Image =
 
= Method 1: Download a Complete Pre-Configured Image =
 
== Canonical/Ubuntu Images ==
 
Support:
 
''#ubuntu-arm'': Ubuntu's arm irc on freenode ([http://irclogs.ubuntu.com/ logs] -> year -> month -> day -> #ubuntu-arm.html)
 
 
Canonical only supports certain boards with images, at this moment.
 
*BeagleBoard xM -> "omap"
 
*PandaBoard & PandaBoard ES -> "omap4"
 
https://wiki.ubuntu.com/ARM/OMAP
 
  
 
==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/Panda Kernel source, used in these demo images: https://github.com/RobertCNelson/stable-kernel
+
* '''Advanced Users only''': Beagle xM: Kernel source, used in these demo images: https://github.com/RobertCNelson/armv7-multiplatform
  git clone git://github.com/RobertCNelson/stable-kernel.git
+
  git clone https://github.com/RobertCNelson/armv7-multiplatform.git
  cd stable-kernel
+
  cd armv7-multiplatform
 +
git checkout origin/v3.15.x -b tmp
 
  ./build_kernel.sh
 
  ./build_kernel.sh
* '''Advanced Users only''': BeagleBone Kernel source, used in these demo images: https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.2
+
* '''Advanced Users only''': BeagleBone/BeagleBone Black:  Kernel v3.8.x source, used in these demo images: https://github.com/RobertCNelson/bb-kernel/tree/am33x-v3.8
  git clone git://github.com/RobertCNelson/linux-dev.git
+
  git clone https://github.com/RobertCNelson/bb-kernel.git
  cd linux-dev
+
  cd bb-kernel
  git checkout origin/am33x-v3.2 -b am33x-v3.2
+
  git checkout origin/am33x-v3.8 -b tmp
 
  ./build_kernel.sh
 
  ./build_kernel.sh
 
* '''Advanced Users only''': Userspace, used in these demo images:
 
* '''Advanced Users only''': Userspace, used in these demo images:
 
  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...
+
=== Trusty 14.04 ===
 
+
=== Precise 12.04 armhf ===
+
 
+
 
Image Updated:
 
Image Updated:
*September 27th
+
*2014-07-06
** Beagle/Panda: v3.2.30-x14 kernel
+
** repo now enabled (repos.rcn-ee.net/ubuntu)
** Bone: v3.2.30-psp23 kernel
+
** Beagle/Beagle xM: v3.15.3-armv7-x4 kernel
* September 10th: r16
+
** BeagleBone/BeagleBone Black: v3.8.13-bone59 kernel
** Beagle/Panda: v3.2.28-x14 kernel
+
** OMAP5432 uEVM: v3.15.3-armv7-lpae-x5 kernel
** Bone: v3.2.28-psp21 kernel (now with "backlight" support for CircuitCo LCD3)
+
*2014-06-05
*July 29th: r5
+
** Beagle/Beagle xM: v3.14.5-armv7-x8 kernel
** Beagle/Panda: v3.2.24-x14 kernel
+
** BeagleBone/BeagleBone Black: v3.8.13-bone56 kernel
** Bone: v3.2.23-psp18 kernel
+
** OMAP5432 uEVM: v3.15.0-rc8-armv7-lpae-x4 kernel
*July 16th: r4
+
*2014-05-06
** Beagle/Panda: v3.2.23-x14 kernel
+
** Beagle/Beagle xM: v3.14.2-armv7-x5 kernel
** Bone: v3.2.21-psp16 kernel
+
** BeagleBone/BeagleBone Black: v3.8.13-bone49 kernel
*June 12th: r3
+
** Beagle/Panda: v3.2.19-x13 kernel
+
** Bone: v3.2.18-psp14 kernel (now supports the BeagleBone LCD from CircuitCo)
+
  
 
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/
+
  Apache, Port 80: http://arm.local/ (Bone: via usb) http://192.168.7.2
  SSH, Port 22: ssh ubuntu@arm
+
  SSH, Port 22: ssh ubuntu@arm.local (Bone: via usb) ubuntu@192.168.7.2
 
  Getty, Serial Port
 
  Getty, Serial Port
  
Default user: ubuntu pass: temppwd  
+
Default user: ubuntu pass: temppwd
  
 
Get prebuilt image:
 
Get prebuilt image:
 +
wget https://rcn-ee.net/deb/rootfs/trusty/ubuntu-14.04-console-armhf-2014-07-06.tar.xz
  
wget http://rcn-ee.net/deb/rootfs/precise/ubuntu-12.04-r7-minimal-armhf-2012-09-27.tar.xz
+
Verify Image with:
mirrors (will take some time to update):
+
  md5sum ubuntu-14.04-console-armhf-2014-07-06.tar.xz
wget http://ynezz.ibawizard.net/beagleboard/precise/ubuntu-12.04-r7-minimal-armhf-2012-09-27.tar.xz
+
  17bb222d1f0f6c81bde902a7a8928a67 ubuntu-14.04-console-armhf-2014-07-06.tar.xz
 
+
Verify Image with:  
+
  md5sum ubuntu-12.04-r7-minimal-armhf-2012-09-27.tar.xz
+
  6742f2edfbd4bebacf532ed5966e7765 ubuntu-12.04-r7-minimal-armhf-2012-09-27.tar.xz
+
  
 
Unpack Image:
 
Unpack Image:
  tar xJf ubuntu-12.04-r7-minimal-armhf-2012-09-27.tar.xz
+
  tar xf ubuntu-14.04-console-armhf-2014-07-06.tar.xz
  cd ubuntu-12.04-r7-minimal-armhf-2012-09-27
+
  cd ubuntu-14.04-console-armhf-2014-07-06
  
 
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...
 
   
 
   
 
  fdisk -l:
 
  fdisk -l:
 
  Disk /dev/sda: 500.1 GB, 500107862016 bytes '''<- x86 Root Drive'''
 
  Disk /dev/sda: 500.1 GB, 500107862016 bytes '''<- x86 Root Drive'''
  Disk /dev/mmcblk0: 3957 MB, 3957325824 bytes '''<- MMC/SD card'''
+
  Disk /dev/sdd: 3957 MB, 3957325824 bytes '''<- MMC/SD card'''
 
   
 
   
  mount:
+
  lsblk:
  /dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0) '''<- x86 Root Partition'''
+
  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/mmcblk0''' 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 --dtb board
  
"board" Options:  
+
board options:
*BeagleBoard Ax/Bx - beagle_bx
+
*BeagleBoard Ax/Bx/Cx/Dx   - omap3-beagle
*BeagleBoard Cx    - beagle_cx
+
*BeagleBoard xM            - omap3-beagle-xm
*BeagleBoard xMA/B/C    - beagle_xm
+
*BeagleBone/Black          - beaglebone
*BeagleBone Ax    - bone
+
*OMAP5432 uEVM              - omap5-uevm
*PandaBoard Ax - panda
+
*PandaBoard ES - panda_es
+
  
So For the BeagleBoard xM:
+
So for the BeagleBoard xM:
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle_xm
+
  sudo ./setup_sdcard.sh --mmc /dev/sdX --dtb omap3-beagle-xm
  
*Additional Options
+
Advanced: Build Image:
** --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.
+
Built with a fork of project-rootstock (ARM native mode, runs directly on BeagleBoard), using a script from omap-image-builder:
  
For a basic '''framebuffer''' driven desktop environment: (make sure network is setup):
+
  git clone https://github.com/RobertCNelson/omap-image-builder.git
  Ethernet: "sudo ifconfig -a" and "sudo dhclient usb1" or "sudo dhclient eth0"
+
cd omap-image-builder
Wireless: http://elinux.org/BeagleBoardUbuntu#Wifi_Networking_.28command_line.29
+
git checkout v2014.07 -b tmp
  
Then run:
+
Stable:
/bin/bash /boot/uboot/tools/ubuntu/minimal_lxde_desktop.sh
+
  
Advanced: Build Image:
+
./RootStock-NG.sh -c rcn-ee_console_ubuntu_stable_armhf
  
Built with a fork of project-rootstock (ARM native mode, run directly on beagleboard), using a script from omap-image-builder:
+
Testing:
  
  git clone git://github.com/RobertCNelson/omap-image-builder.git
+
  ./RootStock-NG.sh -c rcn-ee_console_ubuntu_testing_armhf
cd omap-image-builder
+
git checkout v2012.9-2 -b v2012.9-2
+
touch release
+
./build_image.sh
+
  
=== Oneiric 11.10 ===
+
=== Utopic 14.10 (Testing) ===
  
 
Image Updated:
 
Image Updated:
*September 27th (note: probally going to be last update..)
+
*2014-07-06
** Beagle/Panda: v3.2.30-x14 kernel
+
** repo now enabled (repos.rcn-ee.net/ubuntu)
** Bone: v3.2.30-psp23 kernel
+
** Beagle/Beagle xM: v3.15.3-armv7-x4 kernel
*September 10th: r13
+
** BeagleBone/BeagleBone Black: v3.8.13-bone59 kernel
** Beagle/Panda: v3.2.28-x14 kernel
+
** OMAP5432 uEVM: v3.15.3-armv7-lpae-x5 kernel
** Bone: v3.2.28-psp21 kernel (now with "backlight" support for CircuitCo LCD3)
+
*2014-06-05
*July 29th: r12
+
** Beagle/Beagle xM: v3.14.5-armv7-x8 kernel
** Beagle/Panda: v3.2.24-x14 kernel
+
** BeagleBone/BeagleBone Black: v3.8.13-bone56 kernel
** Bone: v3.2.23-psp18 kernel
+
** OMAP5432 uEVM: v3.15.0-rc8-armv7-lpae-x4 kernel
*July 16th: r11
+
*2014-05-06
** Beagle/Panda: v3.2.23-x14 kernel
+
** Beagle/Beagle xM: v3.14.2-armv7-x5 kernel
** Bone: v3.2.21-psp16 kernel
+
** BeagleBone/BeagleBone Black: v3.8.13-bone49 kernel
*June 12th: r10
+
** Beagle/Panda: v3.2.19-x13 kernel
+
** Bone: v3.2.18-psp14 kernel (now supports the BeagleBone LCD from CircuitCo)
+
  
Services Active:
+
Get prebuilt image:
  Note: Depending on your internal network these may work out the box
+
  wget https://rcn-ee.net/deb/rootfs/utopic/ubuntu-utopic-console-armhf-2014-07-06.tar.xz
Apache, Port 80: http://arm/
+
SSH, Port 22: ssh ubuntu@arm
+
Getty, Serial Port
+
  
Default user: ubuntu pass: temppwd
+
Verify Image with:
 +
md5sum ubuntu-utopic-console-armhf-2014-07-06.tar.xz
 +
c115e200f4a88cc12c98b4fbd48c16d3  ubuntu-utopic-console-armhf-2014-07-06.tar.xz
  
Get prebuilt image:
+
Unpack image:
 +
tar xf ubuntu-utopic-console-armhf-2014-07-06.tar.xz
 +
cd ubuntu-utopic-console-armhf-2014-07-06
  
wget http://rcn-ee.net/deb/rootfs/oneiric/ubuntu-11.10-r14-minimal-armel-2012-09-27.tar.xz
+
Then follow the directions shown above with the other images...
mirrors (will take some time to update):
+
wget http://ynezz.ibawizard.net/beagleboard/oneiric/ubuntu-11.10-r14-minimal-armel-2012-09-27.tar.xz
+
  
Verify Image with:
+
== Flasher ==
md5sum ubuntu-11.10-r14-minimal-armel-2012-09-27.tar.xz
+
3c600a52751f71e0ae04adef1ba91cef  ubuntu-11.10-r14-minimal-armel-2012-09-27.tar.xz
+
  
Unpack Image:
+
=== eMMC: BeagleBone Black ===
tar xJf ubuntu-11.10-r14-minimal-armel-2012-09-27.tar.xz
+
cd ubuntu-11.10-r14-minimal-armel-2012-09-27
+
  
If you don't know the location of your SD card:
+
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.
  sudo ./setup_sdcard.sh --probe-mmc
+
  
You should see something like
+
Script for reference: (this is the script that writes to the eMMC)
 +
https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v2.sh
  
Are you sure? I Don't see [/dev/idontknow], here is what I do see...
+
BTW: we are only writing about 500 megabytes to the eMMC, so the script will only take about 5-6 Minutes after power on.
+
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 ./setup_sdcard.sh...
+
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...)
  
Install Image:
+
User: ubuntu
 +
pass: temppwd
  
Quick Install script for "board"
+
Image Updated:
sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot "board"
+
*2014-07-06
 +
** repo now enabled (repos.rcn-ee.net/ubuntu)
 +
** BeagleBone Black: v3.8.13-bone59 kernel
 +
** NOTE: You'll need to hold the BOOT button on powerup...
 +
*2014-06-05
 +
** BeagleBone Black: v3.8.13-bone56 kernel
 +
*2014-05-06
 +
** BeagleBone Black: v3.8.13-bone49 kernel
  
"board" Options:  
+
Get prebuilt image:
*BeagleBoard Ax/Bx - beagle_bx
+
wget https://rcn-ee.net/deb/flasher/trusty/BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
*BeagleBoard Cx    - beagle_cx
+
*BeagleBoard xMA/B/C    - beagle_xm
+
*BeagleBone Ax    - bone
+
*PandaBoard Ax - panda
+
*PandaBoard ES - panda_es
+
  
So For the BeagleBoard xM:
+
Verify Image with:
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle_xm
+
  md5sum BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
 +
5cbec6b418ee383505a3ae4e40ac231f  BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
  
*Additional Options
+
Follow the "standard" update procedure.
** --rootfs <ext4 default>
+
http://elinux.org/Beagleboard:Updating_The_Software
** --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 OS loaded.
+
Linux:
 +
unxz BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
 +
sudo dd if=./BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-07-06-2gb.img of=/dev/sdX
  
For a full lxde based gui run this on your beagle (make sure network is setup):
+
== raw microSD img ==
Ethernet: "sudo ifconfig -a" and "sudo dhclient usb1" or "sudo dhclient eth0"
+
Wireless: http://elinux.org/BeagleBoardUbuntu#Wifi_Networking_.28command_line.29
+
  
Then run:
+
=== BeagleBoard xM ===
/bin/bash /boot/uboot/tools/ubuntu/minimal_lxde_desktop.sh
+
  
Advanced: Build Image:
+
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.
  
Built with a fork of project-rootstock (ARM native mode, run directly on beagleboard), using a script from omap-image-builder:
+
User: ubuntu
 +
pass: temppwd
  
  git clone git://github.com/RobertCNelson/omap-image-builder.git
+
Auto partition resize:
cd omap-image-builder
+
  cd /opt/scripts/tools
  git checkout v2012.9-2 -b v2012.9-2
+
  git pull
touch release
+
  ./grow_partition.sh
  ./build_image.sh
+
sudo reboot
 
+
=== Quantal 12.10 armhf testing ===
+
  
 
Image Updated:
 
Image Updated:
* September 27th: beta2
+
*2014-07-06
** Beagle/Panda: v3.2.30-x14 kernel
+
** repo now enabled (repos.rcn-ee.net/ubuntu)
** Bone: v3.2.30-psp23 kernel
+
** Beagle/Beagle xM: v3.15.3-armv7-x4 kernel
* September 10th: beta1
+
*2014-06-05
** Beagle/Panda: v3.2.28-x14 kernel
+
** Beagle/Beagle xM: v3.14.5-armv7-x8 kernel
** Bone: v3.2.28-psp21 kernel (now with "backlight" support for CircuitCo LCD3)
+
*2014-05-06
*July 29th: alpha3
+
** Beagle/Beagle xM: v3.14.2-armv7-x5 kernel
** Beagle/Panda: v3.2.24-x14 kernel
+
** Bone: v3.2.23-psp18 kernel
+
*July 16th: alpha2
+
** Beagle/Panda: v3.2.23-x14 kernel
+
** Bone: v3.2.21-psp16 kernel
+
 
+
Services Active:
+
Note: Depending on your internal network these may work out the box
+
Apache, Port 80: http://arm/
+
SSH, Port 22: ssh ubuntu@arm
+
Getty, Serial Port
+
 
+
Default user: ubuntu pass: temppwd
+
  
 
Get prebuilt image:
 
Get prebuilt image:
 +
wget https://rcn-ee.net/deb/microsd/trusty/bbxm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
  
wget http://rcn-ee.net/deb/rootfs/quantal/ubuntu-quantal-beta2-minimal-armhf-2012-09-27.tar.xz
+
Verify Image with:
  mirrors (will take some time to update):
+
md5sum bbxm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
  wget http://ynezz.ibawizard.net/beagleboard/quantal/ubuntu-quantal-beta2-minimal-armhf-2012-09-27.tar.xz
+
  799dd3428f3acc22edcf6acafaabef03 bbxm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
  
Verify Image with:  
+
Linux:
  md5sum ubuntu-quantal-beta2-minimal-armhf-2012-09-27.tar.xz
+
  unxz bbxm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
  cb1a79156807c29475fff28c3f9af155  ubuntu-quantal-beta2-minimal-armhf-2012-09-27.tar.xz
+
  sudo dd if=./bbxm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img of=/dev/sdX
  
Unpack Image:
+
=== BeagleBone/BeagleBone Black ===
tar xJf ubuntu-quantal-beta2-minimal-armhf-2012-09-27.tar.xz
+
cd ubuntu-quantal-beta2-minimal-armhf-2012-09-27
+
  
If you don't know the location of your SD card:
+
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.
  sudo ./setup_sdcard.sh --probe-mmc
+
  
You should see something like
+
User: ubuntu
 +
pass: temppwd
  
Are you sure? I Don't see [/dev/idontknow], here is what I do see...
+
Auto partition resize:
+
  cd /opt/scripts/tools
fdisk -l:
+
  git pull
  Disk /dev/sda: 500.1 GB, 500107862016 bytes '''<- x86 Root Drive'''
+
  ./grow_partition.sh
Disk /dev/mmcblk0: 3957 MB, 3957325824 bytes '''<- MMC/SD card'''
+
  sudo reboot
   
+
  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 ./setup_sdcard.sh...
+
Image Updated:
 +
*2014-07-06
 +
** repo now enabled (repos.rcn-ee.net/ubuntu)
 +
** BeagleBone/BeagleBone Black: v3.8.13-bone59 kernel
 +
** Black: NOTE: You'll need to hold the BOOT button on powerup...
 +
*2014-06-05
 +
** BeagleBone/BeagleBone Black: v3.8.13-bone56 kernel
 +
*2014-05-06
 +
** BeagleBone/BeagleBone Black: v3.8.13-bone49 kernel
  
Install Image:
+
Get prebuilt image:
 +
wget https://rcn-ee.net/deb/microsd/trusty/bone-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
  
Quick Install script for "board"
+
Verify Image with:
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot "board"
+
  md5sum bone-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
 +
11a01c5e96be7bf0ae5ba6d93047757b  bone-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
  
"board" Options:  
+
Linux:
*BeagleBoard Ax/Bx - beagle_bx
+
unxz bone-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
*BeagleBoard Cx    - beagle_cx
+
sudo dd if=./bone-ubuntu-14.04-console-armhf-2014-07-06-2gb.img of=/dev/sdX
*BeagleBoard xMA/B/C    - beagle_xm
+
*BeagleBone Ax    - bone
+
*PandaBoard Ax - panda
+
*PandaBoard ES - panda_es
+
  
So For the BeagleBoard xM:
+
=== OMAP5432 uEVM ===
sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle_xm
+
  
*Additional Options
+
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.
** --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.
+
User: ubuntu
 +
pass: temppwd
  
For a basic '''framebuffer''' driven desktop environment: (make sure network is setup):
+
Auto partition resize:
  Ethernet: "sudo ifconfig -a" and "sudo dhclient usb1" or "sudo dhclient eth0"
+
  cd /opt/scripts/tools
  Wireless: http://elinux.org/BeagleBoardUbuntu#Wifi_Networking_.28command_line.29
+
git pull
 +
  ./grow_partition.sh
 +
sudo reboot
  
Then run:
+
Image Updated:
/bin/bash /boot/uboot/tools/ubuntu/minimal_lxde_desktop.sh
+
*2014-07-06
 +
** repo now enabled (repos.rcn-ee.net/ubuntu)
 +
** OMAP5432 uEVM: v3.15.3-armv7-lpae-x5 kernel
 +
*2014-06-05
 +
** OMAP5432 uEVM: v3.15.0-rc8-armv7-lpae-x4 kernel
  
Advanced: Build Image:
+
Get prebuilt image:
 +
wget https://rcn-ee.net/deb/microsd/trusty/omap5-uevm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
  
Built with a fork of project-rootstock (ARM native mode, run directly on beagleboard), using a script from omap-image-builder:
+
Verify Image with:
 +
md5sum omap5-uevm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
 +
1542cd3cf03863c5ec9fd0c51bdefd99  omap5-uevm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
  
git clone git://github.com/RobertCNelson/omap-image-builder.git
+
Linux:
cd omap-image-builder
+
unxz omap5-uevm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
  git checkout v2012.9-2 -b v2012.9-2
+
  sudo dd if=./omap5-uevm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img of=/dev/sdX
touch release
+
./build_image.sh
+
  
 
= 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 : ~700MB
+
  Standard system : ~700&nbsp;MB
  
== Ubuntu 12.04 (Precise) ==
+
Report Bugs/Issues to: https://github.com/RobertCNelson/netinstall/issues
 +
(anywhere else will be ignored..)
  
  git clone git://github.com/RobertCNelson/netinstall.git
+
Download the netinstall script:
 +
  git clone https://github.com/RobertCNelson/netinstall.git
 
  cd netinstall
 
  cd netinstall
  
Install script for "board"
+
Currently supported Ubuntu distributions:
  sudo ./mk_mmc.sh --mmc /dev/sdX --uboot "board" --distro precise-armhf
+
  --distro oneiric (11.10)
 +
--distro precise-armhf (12.04)
 +
--distro quantal (12.10)
 +
--distro raring (13.04)
 +
--distro saucy (13.10)
  
"board" Options:  
+
Device: <board> selection:
*BeagleBoard Ax/Bx - beagle_bx
+
*BeagleBoard Ax/Bx/Cx - omap3-beagle
*BeagleBoard Cx   - beagle_cx
+
*BeagleBoard xMA/B/C   - omap3-beagle-xm
*BeagleBoard xMA/B/C   - beagle_xm
+
*BeagleBone Ax         - am335x-bone-serial
*BeagleBone Ax   - bone
+
*BeagleBone (DVI cape) - am335x-bone-video
*PandaBoard Ax - panda
+
*BeagleBone Black      - am335x-boneblack
*PandaBoard ES - panda_es
+
*PandaBoard Ax     - omap4-panda
 +
*PandaBoard A4+    - omap4-panda-a4
 +
*PandaBoard ES     - omap4-panda-es
  
So For the BeagleBoard xM:
+
Installation script for new <board> selection: (slowly migrating all devices to this method)
  sudo ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_xm --distro precise-armhf
+
  sudo ./mk_mmc.sh --mmc /dev/sdX --dtb <board> --distro <distro>
  
*Options:
+
So for the xM: with quantal:
**--uboot : beagle_bx, beagle, panda
+
sudo ./mk_mmc.sh --mmc /dev/sdX --dtb omap3-beagle-xm --distro quantal
**--distro : maverick, oneiric
+
 
 +
*Other Options:
 
**--firmware : installs firmware
 
**--firmware : installs firmware
 
**--serial-mode : debian-installer uses Serial Port
 
**--serial-mode : debian-installer uses Serial Port
  
Place SD card into Beagle and boot:
+
Place SD card into BeagleBoard and boot:
  
 
Configure the network:
 
Configure the network:
 
  usb0: USB net <- (usually the OTG port)
 
  usb0: USB net <- (usually the OTG port)
  eth0: USB net <- (usually the smsc95xx adapter on the beagle and panda)
+
  eth0: USB net <- (usually the smsc95xx adapter on the BeagleBoard and PandaBoard)
  wlan0: Wifi <- Your usb-wifi device..  
+
  wlan0: Wifi <- Your USDB-Wi-Fi device..  
 +
 
 +
See my notes for my testing procedure: https://github.com/RobertCNelson/netinstall/blob/master/test.Ubuntu
  
Troubshooting: 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
  
 
NetInstall assumptions:
 
NetInstall assumptions:
  Continue with out Kernel Modules <yes>
+
  Assume asll <default>'s... Thanks you preseed.conf!!!
Partition <Guided - use the largest continuous free space>
+
  
 
= Method 3: Manual Install (no automatic scripts)=
 
= Method 3: Manual Install (no automatic scripts)=
  
For this section, you can use the files from above:
+
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:
Demo Images: http://elinux.org/BeagleBoardUbuntu#Demo_Image
+
Rootstock: http://elinux.org/BeagleBoardUbuntu#Build_an_Ubuntu_root_file_system_with_RootStock
+
  
BUT it assumes you have your own kernel uImage/modules from any of the many sources..
+
== Beagle/Beagle xM ==
 +
http://eewiki.net/display/linuxonarm/BeagleBoard
  
== Partition SD Card ==
+
== BeagleBone ==
You will need a 1GB SD card or greater.
+
  http://eewiki.net/display/linuxonarm/BeagleBone
  Standard Console System : ~286MB
+
+ Desktop environment (lxde,gdm) : ~479MB
+
  
Starting with an empty SD card and using gparted, create:
+
== BeagleBone Black ==
  50 MiB Primary Partition, fat16/fat32
+
  http://eewiki.net/display/linuxonarm/BeagleBone+Black
Rest as ext2/ext3/ext4/btrfs
+
  
First blank the MMC card's partition table with parted: (/dev/sdX as an example)
+
== Panda/Panda ES ==
sudo parted -s /dev/sdX mklabel msdos
+
  http://eewiki.net/display/linuxonarm/PandaBoard
 
+
With fdisk: (note: GNU Fdisk doesn't work..)
+
sudo fdisk /dev/sdX << __EOF__
+
n
+
p
+
1
+
+
+64M
+
t
+
e
+
p
+
w
+
__EOF__
+
 
+
Make sure to set the partition boot flag
+
sudo parted --script /dev/sdX set 1 boot on
+
 
+
And format it as vfat:
+
sudo mkfs.vfat -F 16 /dev/sdX1 -n boot
+
 
+
The rootfs partition, doesn't need any special options, so just use fdisk, gparted, etc to create and format your rootfs partition..
+
 
+
Gparted Example: http://nishanthmenon.blogspot.com/2008/08/how-to-boot-beagle.html
+
 
+
== Boot Partition ==
+
 
+
Requirements:
+
 
+
Mount the fatfs partition of your SD card.
+
 
+
Mount such as: (/dev/sdX1 is the fat Boot Partition)
+
mkdir -p ./tmp
+
sudo mount /dev/sdX1 ./tmp
+
 
+
=== MLO and U-Boot ===
+
 
+
==== Beagle/Beagle xM ====
+
Download and copy MLO and U-Boot from here:
+
 
+
First download "http://rcn-ee.net/deb/tools/beagleboard/MLO-beagleboard-v2012.07-r1" as MLO to the Boot Partition
+
Then download "http://rcn-ee.net/deb/tools/beagleboard/u-boot-beagleboard-v2012.07-r1.img" as u-boot.img to the Boot Partition
+
 
+
==== BeagleBone ====
+
Download and copy MLO and U-Boot from here:
+
 
+
First download "http://rcn-ee.net/deb/tools/beaglebone/MLO-beaglebone-v2012.07-490-ga6f0c4f-r0" as MLO to the Boot Partition
+
Then download "http://rcn-ee.net/deb/tools/beaglebone/u-boot-beaglebone-v2012.07-490-ga6f0c4f-r0.img" as u-boot.img to the Boot Partition
+
 
+
==== Panda/Panda ES ====
+
 
+
Download and copy MLO and U-Boot from here:
+
 
+
  First download "http://rcn-ee.net/deb/tools/pandaboard/MLO-pandaboard-v2012.04.01-r2" as MLO to the Boot Partition
+
Then download "http://rcn-ee.net/deb/tools/pandaboard/u-boot-pandaboard-v2012.04.01-r2.img" as u-boot.img to the Boot Partition
+
 
+
=== U-Boot Boot Scripts ===
+
The version of U-Boot installed or recommended to install uses boot scripts by default.  This allows users to easily switch between multiple SD cards with different OS's with different parameters installed.  Ubuntu/Debian requires a slight modification to the bootargs line vs. Angstrom, 'ro' vs 'rw'.
+
 
+
fixrtc: (only uInitrd) Resets RTC based on last mount
+
buddy=${buddy}: (both) Kernel Zippy1/2 Support
+
mpurate=${mpurate}: (recommended core clock)
+
 
+
==== boot.scr -> uEnv.txt ====
+
Newer version's of u-boot now look for a uEnv.txt file vs the older boot.scr, since most boards still use the older boot.scr here's an easy compatibility script:
+
 
+
create a new file: uEnv.txt
+
bootenv=boot.scr
+
loaduimage=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
+
mmcboot=echo Running boot.scr script from mmc ...; source ${loadaddr}
+
 
+
==== Beagle Bx/Cx ====
+
 
+
create a new file: uEnv.txt
+
console=ttyO2,115200n8
+
+
vram=12MB
+
defaultdisplay=dvi
+
dvimode=1280x720MR-16@60
+
+
optargs=console=tty0
+
+
mmcroot=/dev/mmcblk0p2 ro
+
mmcrootfstype=ext4 rootwait fixrtc
+
+
xyz_load_image=fatload mmc 0:1 0x80300000 zImage
+
xyz_load_initrd=fatload mmc 0:1 0x81600000 initrd.img; setenv initrd_size ${filesize}
+
xyz_load_dtb=fatload mmc 0:1 0x815f0000 /dtbs/${dtb_file}
+
+
video_args=setenv video vram=${vram} omapfb.mode=${defaultdisplay}:${dvimode} omapdss.def_disp=${defaultdisplay}
+
expansion_args=setenv expansion buddy=${buddy} buddy2=${buddy2} musb_hdrc.fifo_mode=5
+
mmcargs=setenv bootargs console=${console} ${optargs} ${video} root=${mmcroot} rootfstype=${mmcrootfstype} ${expansion}
+
+
device_args=run video_args; run expansion_args; run mmcargs
+
+
#zImage and initrd.gz:
+
xyz_mmcboot=run xyz_load_image; run xyz_load_initrd; echo Booting from mmc ...
+
loaduimage=run xyz_mmcboot; run device_args; bootz 0x80300000 0x81600000:${initrd_size}
+
+
#zImage only:
+
#xyz_mmcboot=run xyz_load_image; echo Booting from mmc ...
+
#loaduimage=run xyz_mmcboot; run device_args; bootz 0x80300000
+
 
+
==== Beagle xM ====
+
 
+
create a new file: uEnv.txt
+
console=ttyO2,115200n8
+
+
vram=12MB
+
defaultdisplay=dvi
+
dvimode=1280x720MR-16@60
+
+
optargs=console=tty0
+
+
mmcroot=/dev/mmcblk0p2 ro
+
mmcrootfstype=ext4 rootwait fixrtc
+
+
xyz_load_image=fatload mmc 0:1 0x80300000 zImage
+
xyz_load_initrd=fatload mmc 0:1 0x81600000 initrd.img; setenv initrd_size ${filesize}
+
xyz_load_dtb=fatload mmc 0:1 0x815f0000 /dtbs/${dtb_file}
+
+
video_args=setenv video vram=${vram} omapfb.mode=${defaultdisplay}:${dvimode} omapdss.def_disp=${defaultdisplay}
+
expansion_args=setenv expansion buddy=${buddy} buddy2=${buddy2} camera=${camera}
+
mmcargs=setenv bootargs console=${console} ${optargs} ${video} root=${mmcroot} rootfstype=${mmcrootfstype} ${expansion}
+
+
device_args=run video_args; run expansion_args; run mmcargs
+
+
#zImage and initrd.gz:
+
xyz_mmcboot=run xyz_load_image; run xyz_load_initrd; echo Booting from mmc ...
+
loaduimage=run xyz_mmcboot; run device_args; bootz 0x80300000 0x81600000:${initrd_size}
+
+
#zImage only:
+
#xyz_mmcboot=run xyz_load_image; echo Booting from mmc ...
+
#loaduimage=run xyz_mmcboot; run device_args; bootz 0x80300000
+
 
+
==== BeagleBone ====
+
 
+
create a new file: uEnv.txt
+
console=ttyO2,115200n8
+
+
mmcroot=/dev/mmcblk0p2 ro
+
mmcrootfstype=ext4 rootwait fixrtc
+
+
xyz_load_image=fatload mmc 0:1 0x80300000 zImage
+
xyz_load_initrd=fatload mmc 0:1 0x81600000 initrd.img; setenv initrd_size ${filesize}
+
xyz_load_dtb=fatload mmc 0:1 0x815f0000 /dtbs/${dtb_file}
+
+
mmcargs=setenv bootargs console=${console} ${optargs} root=${mmcroot} rootfstype=${mmcrootfstype}
+
+
#zImage and initrd.gz:
+
xyz_mmcboot=run xyz_load_image; run xyz_load_initrd; echo Booting from mmc ...
+
loaduimage=run xyz_mmcboot; run mmcargs; bootz 0x80300000 0x81600000:${initrd_size}
+
+
#zImage only:
+
#xyz_mmcboot=run xyz_load_image; echo Booting from mmc ...
+
#loaduimage=run xyz_mmcboot; run mmcargs; bootz 0x80300000
+
 
+
==== Panda/Panda ES ====
+
 
+
create a new file: uEnv.txt
+
console=ttyO2,115200n8
+
+
vram=16MB
+
defaultdisplay=dvi
+
dvimode=1280x720MR-16@60
+
+
optargs=console=tty0
+
+
mmcroot=/dev/mmcblk0p2 ro
+
mmcrootfstype=ext4 rootwait fixrtc
+
+
xyz_load_image=fatload mmc 0:1 0x80300000 zImage
+
xyz_load_initrd=fatload mmc 0:1 0x81600000 initrd.img; setenv initrd_size ${filesize}
+
xyz_load_dtb=fatload mmc 0:1 0x815f0000 /dtbs/${dtb_file}
+
+
video_args=setenv video vram=${vram} omapfb.mode=${defaultdisplay}:${dvimode} omapdss.def_disp=${defaultdisplay}
+
expansion_args=setenv expansion buddy=${buddy} buddy2=${buddy2}
+
mmcargs=setenv bootargs console=${console} ${optargs} ${video} root=${mmcroot} rootfstype=${mmcrootfstype} ${expansion}
+
+
device_args=run video_args; run expansion_args; run mmcargs
+
+
#zImage and initrd.gz:
+
xyz_mmcboot=run xyz_load_image; run xyz_load_initrd; echo Booting from mmc ...
+
loaduimage=run xyz_mmcboot; run device_args; bootz 0x80300000 0x81600000:${initrd_size}
+
+
#zImage only:
+
#xyz_mmcboot=run xyz_load_image; echo Booting from mmc ...
+
#loaduimage=run xyz_mmcboot; run device_args; bootz 0x80300000
+
+
Umount the Boot Partition:
+
 
+
sudo umount ./tmp
+
 
+
== RootFS Partition ==
+
Root File System
+
 
+
Mount your SD card's larger root file system partition (assuming /dev/sdX2) and 'untar' the rootfs into it.
+
 
+
mkdir -p ./tmp
+
sudo mount /dev/sdX2 ./tmp
+
sudo tar xfp armel-rootfs-*.tgz -C ./tmp
+
sudo umount ./tmp
+
 
+
== Ubuntu Bugs & Tweaks ==
+
 
+
===Enable Network Access===
+
 
+
Modify /etc/network/interfaces
+
auto eth0
+
iface eth0 inet dhcp
+
 
+
Manual: From the Command line
+
sudo ifconfig -a
+
sudo dhclient ethX (or wlanX/etc..)
+
 
+
Additional Network Setup Information can be found [[BeagleBoardUbuntuNetwork|HERE]]
+
  
 
= Advanced =
 
= Advanced =
Line 662: Line 409:
 
==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
+
export BOARD=omap
+
+
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
+
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 ==
 
== Upgrade X-loader and U-boot ==
  
Compatible with Old Ax,Bx,Cx BeagleBoards
+
*Note: the functionality of the "X-Loader" project has been merged as u-boot spl.
  
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:
+
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
 
  nand erase 260000 20000
  
Requires MMC card..
+
Or: To fully erase the entire NAND:
 +
nand erase.chip
 +
 
 +
Requires MMC card:
  
  git clone git://github.com/RobertCNelson/flasher.git
+
  git clone https://github.com/RobertCNelson/flasher.git
 
  cd flasher
 
  cd flasher
  
For the Beagle Bx
+
For the Beagle Ax/Bx
 
  sudo ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_bx
 
  sudo ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_bx
  
For the Beagle Cx
+
For the Beagle Cx/Dx
 
  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 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, 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 710: Line 458:
 
  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...
 
   
 
   
 
  fdisk -l:
 
  fdisk -l:
Line 721: Line 469:
 
  /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 Drivers ==
  
=== SGX armel/armhf v3.4.x+ ===
+
=== SGX BeagleBone/BeagleBone Black ===
* 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"
+
Note, these are FBDEV only, no xorg/x11/etc...
  
==== Re-Build Kernel and SGX Kernel Modules ====
+
Install "special" Kernel
  git clone git://github.com/RobertCNelson/stable-kernel.git
+
  cd /opt/scripts/tools
cd stable-kernel
+
  git pull
  git checkout origin/v3.4.x -b v3.4.x
+
  sudo ./update_kernel.sh --kernel v3.13.11-bone12
  ./build_kernel.sh (and then follow the directions as the script runs...)
+
  
Build SGX modules
+
Build SGX modules/userspace (must be done on an x86, due to the TI 5.01.01.01 blob extractor)
 +
git clone https://github.com/RobertCNelson/bb-kernel.git
 +
cd bb-kernel/
 +
git checkout origin/am33x-v3.13 -b tmp-sgx
 +
./build_kernel.sh
 
  ./sgx_build_modules.sh
 
  ./sgx_build_modules.sh
  
Insert SD card, make sure to modify MMC in system.sh
+
Copy ./deploy/GFX_5.01.01.01.tar.gz to BeagleBone/BeagleBone Black and install
./tools/install_image.sh
+
  sudo tar xfv GFX_5.01.01.01.tar.gz -C /
 
+
  cd /opt/gfxinstall/
Place SD card into Device and boot...
+
  sudo ./sgx-install.sh
cd /opt/sgx
+
sudo tar xf GFX_4.06.00.03_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://github.com/RobertCNelson/stable-kernel/raw/master/create_sgx_package_2.6.37.sh
+
  2.6.38+
+
wget https://github.com/RobertCNelson/stable-kernel/raw/master/create_sgx_package.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
 
  sudo reboot
  
==== Beagle: GFX_Linux_SDK.tar.gz ====
+
Verify omaplfb & pvrsrvkm loaded
 +
ubuntu@arm:~$ lsmod | grep omaplfb
 +
omaplfb                12065  0
 +
pvrsrvkm              178782  1 omaplfb
  
tar xf GFX_Linux_SDK.tar.gz
+
SGX Demos
  cd GFX_Linux_SDK
+
  cd /opt/gfxsdkdemos/ogles2/
  tar xf OGLES.tar.gz
+
  ./OGLES2ChameleonMan
  
==== Test SGX with a DEMO ====
+
== Xorg Drivers ==
  
cd OGLES/SDKPackage/Binaries/CommonX11/Demos/EvilSkull
+
Script:
./OGLESEvilSkull
+
  cd /opt/scripts/tools/
 
+
  git pull
==== 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:
+
  voodoo@beagle-xma-512mb:~$ zcat /proc/config.gz | grep TIDSP
+
CONFIG_TIDSPBRIDGE=m
+
CONFIG_TIDSPBRIDGE_MEMPOOL_SIZE=0x600000
+
# CONFIG_TIDSPBRIDGE_DEBUG is not set
+
CONFIG_TIDSPBRIDGE_RECOVERY=y
+
# CONFIG_TIDSPBRIDGE_CACHE_LINE_CHECK is not set
+
CONFIG_TIDSPBRIDGE_WDT3=y
+
CONFIG_TIDSPBRIDGE_WDT_TIMEOUT=5
+
# CONFIG_TIDSPBRIDGE_NTFY_PWRERR is not set
+
# CONFIG_TIDSPBRIDGE_BACKTRACE is not
+
 
+
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://github.com/RobertCNelson/stable-kernel/raw/master/create_dsp_package.sh
+
 
+
for 3.4.x+
+
wget https://raw.github.com/RobertCNelson/stable-kernel/v3.4.x/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:
+
tar xf DSP_Install_libs.tar.gz
+
 
+
Install
+
./install-DSP.sh
+
 
+
Build gst-dsp stuff..
+
./install-gst-dsp.sh
+
 
+
Start dspbridge (or just reboot)
+
sudo /etc/init.d/dsp 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: 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
+
 
+
Download SRC
+
git clone git://github.com/RobertCNelson/stable-kernel.git
+
 
+
Build Kernel
+
./build_kernel.sh
+
  
Optional Building Deb File
+
BeagleBoard/PandaBoard:
  ./build_deb.sh
+
cd /opt/scripts/tools/graphics/
 +
  ./ti-omapdrm.sh
  
 +
BeagleBone/BeagleBone Black:
 +
cd /opt/scripts/tools/graphics/
 +
./ti-tilcdc.sh
  
 
= Swapfile =
 
= Swapfile =
Line 1,136: Line 522:
 
== 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 256Mb and 512Mb). Some system programs like apt-get will only run properly when some swap space is present (due to 256Mb 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 1,152: Line 538:
 
  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 =
  
== Wifi Networking (command line) ==
+
== Wi-Fi Networking (command line) ==
  
 
=== /etc/network/interfaces ===
 
=== /etc/network/interfaces ===
  
It is possible and relatively easy to configure a wifi 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.
  
This is a particularly useful guide http://ubuntuforums.org/showthread.php?t=202834  
+
This is a particularly useful guide https://ubuntuforums.org/showthread.php?t=202834  
  
 
A sample /etc/network/interfaces file for a WPA2 encrypted access point is:
 
A sample /etc/network/interfaces file for a WPA2 encrypted access point is:
Line 1,183: Line 569:
 
  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 wifi 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 1,191: Line 577:
 
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 256MB, using JWM will leave about 60MB free to run apps 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
+
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:
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 1,203: Line 588:
  
 
=== Motion ===
 
=== 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.
+
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 15 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 xwindows 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 (ie video output directory, record only video, record in mpeg4, 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 1,221: Line 606:
 
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 app.
+
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:
  
 
http://www.ros.org/wiki/cturtle/Installation/Ubuntu/SVN
 
http://www.ros.org/wiki/cturtle/Installation/Ubuntu/SVN
  
You will need an Internet connection for your Beagleboard for these scripts to work.
+
You will need an Internet connection for your BeagleBoard for these scripts to work.
  
For more information about ROS see www.ros.org
+
For more information about ROS, see www.ros.org.

Latest revision as of 17:41, 28 July 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 https://github.com/RobertCNelson/armv7-multiplatform.git
cd armv7-multiplatform
git checkout origin/v3.15.x -b tmp
./build_kernel.sh
git clone https://github.com/RobertCNelson/bb-kernel.git
cd bb-kernel
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

Trusty 14.04

Image Updated:

  • 2014-07-06
    • repo now enabled (repos.rcn-ee.net/ubuntu)
    • Beagle/Beagle xM: v3.15.3-armv7-x4 kernel
    • BeagleBone/BeagleBone Black: v3.8.13-bone59 kernel
    • OMAP5432 uEVM: v3.15.3-armv7-lpae-x5 kernel
  • 2014-06-05
    • Beagle/Beagle xM: v3.14.5-armv7-x8 kernel
    • BeagleBone/BeagleBone Black: v3.8.13-bone56 kernel
    • OMAP5432 uEVM: v3.15.0-rc8-armv7-lpae-x4 kernel
  • 2014-05-06
    • Beagle/Beagle xM: v3.14.2-armv7-x5 kernel
    • BeagleBone/BeagleBone Black: v3.8.13-bone49 kernel

Services Active:

Note: Depending on your internal network these may work out of the box
Apache, Port 80: http://arm.local/ (Bone: via usb) http://192.168.7.2
SSH, Port 22: ssh ubuntu@arm.local (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/trusty/ubuntu-14.04-console-armhf-2014-07-06.tar.xz

Verify Image with:

md5sum ubuntu-14.04-console-armhf-2014-07-06.tar.xz
17bb222d1f0f6c81bde902a7a8928a67  ubuntu-14.04-console-armhf-2014-07-06.tar.xz

Unpack Image:

tar xf ubuntu-14.04-console-armhf-2014-07-06.tar.xz
cd ubuntu-14.04-console-armhf-2014-07-06

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 --dtb board

board options:

  • BeagleBoard Ax/Bx/Cx/Dx - omap3-beagle
  • BeagleBoard xM - omap3-beagle-xm
  • BeagleBone/Black - beaglebone
  • OMAP5432 uEVM - omap5-uevm

So for the BeagleBoard xM:

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

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 https://github.com/RobertCNelson/omap-image-builder.git
cd omap-image-builder
git checkout v2014.07 -b tmp

Stable:

./RootStock-NG.sh -c rcn-ee_console_ubuntu_stable_armhf

Testing:

./RootStock-NG.sh -c rcn-ee_console_ubuntu_testing_armhf

Utopic 14.10 (Testing)

Image Updated:

  • 2014-07-06
    • repo now enabled (repos.rcn-ee.net/ubuntu)
    • Beagle/Beagle xM: v3.15.3-armv7-x4 kernel
    • BeagleBone/BeagleBone Black: v3.8.13-bone59 kernel
    • OMAP5432 uEVM: v3.15.3-armv7-lpae-x5 kernel
  • 2014-06-05
    • Beagle/Beagle xM: v3.14.5-armv7-x8 kernel
    • BeagleBone/BeagleBone Black: v3.8.13-bone56 kernel
    • OMAP5432 uEVM: v3.15.0-rc8-armv7-lpae-x4 kernel
  • 2014-05-06
    • Beagle/Beagle xM: v3.14.2-armv7-x5 kernel
    • BeagleBone/BeagleBone Black: v3.8.13-bone49 kernel

Get prebuilt image:

wget https://rcn-ee.net/deb/rootfs/utopic/ubuntu-utopic-console-armhf-2014-07-06.tar.xz

Verify Image with:

md5sum ubuntu-utopic-console-armhf-2014-07-06.tar.xz
c115e200f4a88cc12c98b4fbd48c16d3  ubuntu-utopic-console-armhf-2014-07-06.tar.xz

Unpack image:

tar xf ubuntu-utopic-console-armhf-2014-07-06.tar.xz
cd ubuntu-utopic-console-armhf-2014-07-06

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/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v2.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-07-06
    • repo now enabled (repos.rcn-ee.net/ubuntu)
    • BeagleBone Black: v3.8.13-bone59 kernel
    • NOTE: You'll need to hold the BOOT button on powerup...
  • 2014-06-05
    • BeagleBone Black: v3.8.13-bone56 kernel
  • 2014-05-06
    • BeagleBone Black: v3.8.13-bone49 kernel

Get prebuilt image:

wget https://rcn-ee.net/deb/flasher/trusty/BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz

Verify Image with:

md5sum BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
5cbec6b418ee383505a3ae4e40ac231f  BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz

Follow the "standard" update procedure.

http://elinux.org/Beagleboard:Updating_The_Software

Linux:

unxz BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
sudo dd if=./BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-07-06-2gb.img of=/dev/sdX

raw microSD img

BeagleBoard xM

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-07-06
    • repo now enabled (repos.rcn-ee.net/ubuntu)
    • Beagle/Beagle xM: v3.15.3-armv7-x4 kernel
  • 2014-06-05
    • Beagle/Beagle xM: v3.14.5-armv7-x8 kernel
  • 2014-05-06
    • Beagle/Beagle xM: v3.14.2-armv7-x5 kernel

Get prebuilt image:

wget https://rcn-ee.net/deb/microsd/trusty/bbxm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz

Verify Image with:

md5sum bbxm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
799dd3428f3acc22edcf6acafaabef03  bbxm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz

Linux:

unxz bbxm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
sudo dd if=./bbxm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img of=/dev/sdX

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-07-06
    • repo now enabled (repos.rcn-ee.net/ubuntu)
    • BeagleBone/BeagleBone Black: v3.8.13-bone59 kernel
    • Black: NOTE: You'll need to hold the BOOT button on powerup...
  • 2014-06-05
    • BeagleBone/BeagleBone Black: v3.8.13-bone56 kernel
  • 2014-05-06
    • BeagleBone/BeagleBone Black: v3.8.13-bone49 kernel

Get prebuilt image:

wget https://rcn-ee.net/deb/microsd/trusty/bone-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz

Verify Image with:

md5sum bone-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
11a01c5e96be7bf0ae5ba6d93047757b  bone-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz

Linux:

unxz bone-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
sudo dd if=./bone-ubuntu-14.04-console-armhf-2014-07-06-2gb.img of=/dev/sdX

OMAP5432 uEVM

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-07-06
    • repo now enabled (repos.rcn-ee.net/ubuntu)
    • OMAP5432 uEVM: v3.15.3-armv7-lpae-x5 kernel
  • 2014-06-05
    • OMAP5432 uEVM: v3.15.0-rc8-armv7-lpae-x4 kernel

Get prebuilt image:

wget https://rcn-ee.net/deb/microsd/trusty/omap5-uevm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz

Verify Image with:

md5sum omap5-uevm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
1542cd3cf03863c5ec9fd0c51bdefd99  omap5-uevm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz

Linux:

unxz omap5-uevm-ubuntu-14.04-console-armhf-2014-07-06-2gb.img.xz
sudo dd if=./omap5-uevm-ubuntu-14.04-console-armhf-2014-07-06-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 https://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

BeagleBone Black

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

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 https://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 Drivers

SGX BeagleBone/BeagleBone Black

Note, these are FBDEV only, no xorg/x11/etc...

Install "special" Kernel

cd /opt/scripts/tools
git pull
sudo ./update_kernel.sh --kernel v3.13.11-bone12

Build SGX modules/userspace (must be done on an x86, due to the TI 5.01.01.01 blob extractor)

git clone https://github.com/RobertCNelson/bb-kernel.git
cd bb-kernel/
git checkout origin/am33x-v3.13 -b tmp-sgx
./build_kernel.sh
./sgx_build_modules.sh

Copy ./deploy/GFX_5.01.01.01.tar.gz to BeagleBone/BeagleBone Black and install

sudo tar xfv GFX_5.01.01.01.tar.gz -C /
cd /opt/gfxinstall/
sudo ./sgx-install.sh
sudo reboot

Verify omaplfb & pvrsrvkm loaded

ubuntu@arm:~$ lsmod | grep omaplfb
omaplfb                12065  0 
pvrsrvkm              178782  1 omaplfb

SGX Demos

cd /opt/gfxsdkdemos/ogles2/
./OGLES2ChameleonMan

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

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 https://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.