Difference between revisions of "BeagleBoardUbuntu"

From eLinux.org
Jump to: navigation, search
m (Oneiric 11.10: not beta anymore)
m (Method 1: Download a Complete Pre-Configured Image: 2015-04-09)
(247 intermediate revisions by 13 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 EABI) [http://www.ubuntu.com/ Ubuntu] distribution at [[BeagleBoard]]. BeagleBoard will boot the (ARM EABI) Ubuntu distribution from [[BeagleBoard#MMC.2FSD_boot|SD card]].
+
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]].
  
Note: for the best experience, make sure you have an LCD attached to the 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.0 src]
+
*** [https://github.com/RobertCNelson/armv7-multiplatform/ v3.17.x kernel 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 Bx, C2/3/4 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.bin 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 55: Line 56:
 
= Method 1: Download a Complete Pre-Configured Image =
 
= Method 1: Download a Complete Pre-Configured Image =
  
== Canonical/Ubuntu Images ==
+
== Demo Image ==
Support:
 
''#ubuntu-arm'': Ubuntu's arm irc on freenode ([http://irclogs.ubuntu.com/ logs] -> year -> month -> day -> #ubuntu-arm.html)
 
  
=== Natty 11.04 ===
+
* '''Advanced Users only''': Beagle xM: Kernel source, used in these demo images: https://github.com/RobertCNelson/armv7-multiplatform
 +
git clone https://github.com/RobertCNelson/armv7-multiplatform.git
 +
cd armv7-multiplatform
 +
git checkout origin/v4.0.x -b tmp
 +
./build_kernel.sh
 +
* '''Advanced Users only''': BeagleBone/BeagleBone Black:  Kernel v3.14.x source, used in these demo images: https://github.com/RobertCNelson/ti-linux-kernel-dev/tree/ti-linux-3.14.y
 +
git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
 +
cd ti-linux-kernel-dev
 +
git checkout origin/ti-linux-3.14.y -b tmp
 +
./build_kernel.sh
  
Just follow: https://wiki.ubuntu.com/ARM/OMAP
+
=== Ubuntu (14.04.2) ===
  
=== Maverick 10.10 ===
+
Default username/password:
 +
*username: ubuntu
 +
*password: temppwd
  
Just follow https://wiki.ubuntu.com/ARM/OMAPMaverickInstall and make sure you're using a SD card >= 4GB.
+
Image Updated:
 +
*2015-04-09
 +
** Beagle/Beagle xM: v4.0.0-rc7-armv7-x1 kernel
 +
** BeagleBone/BeagleBone Black: v3.14.37-ti-r57 kernel
 +
** OMAP5432 uEVM: v3.14.37-ti-r57 kernel
 +
** BeagleBoard-X15: v3.14.37-ti-r57 kernel
 +
*2015-02-19
 +
** Beagle/Beagle xM: v3.19.0-armv7-x3 kernel
 +
** BeagleBone/BeagleBone Black: v3.14.33-ti-r50 kernel
 +
** OMAP5432 uEVM: v3.14.33-ti-r50 kernel
 +
** BeagleBoard-X15: v3.14.33-ti-r50 kernel
 +
*2015-01-06
 +
** Beagle/Beagle xM: v3.18.1-armv7-x2 kernel
 +
** BeagleBone/BeagleBone Black: v3.14.26-ti-r43 kernel
 +
** OMAP5432 uEVM: v3.14.26-ti-r43 kernel
 +
** BeagleBoard-X15: v3.14.26-ti-r43 kernel
  
==Demo Image==
+
Services Active:
 
+
Note: Depending on your internal network these may work out of the box
Note, these Demo Images contain a custom kernel from rcn-ee.net. If you'd like to use ubuntu's 'kernel' edit "/etc/flash-kernel.conf" disable the rcn-ee kernel variable then install flash-kernel which should bring ubuntu's kernel with it. Once you do this, it's not trivial to reverse the process..
+
  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
If the script in these demo images fail: email "bugs@rcn-ee.com" I need: terminal command, terminal log, distribution name, arch...
+
Getty, Serial Port
 
 
=== Oneiric 11.10 ===
 
 
 
Image Updated Oct 13th, updated v3.0.6 kernel, now with better s-video support (setup_sdcard.sh option)...
 
  
 
Default user: ubuntu pass: temppwd
 
Default user: ubuntu pass: temppwd
  
 
Get prebuilt image:
 
Get prebuilt image:
 +
wget https://rcn-ee.com/rootfs/2015-04-09/ubuntu-14.04.2-console-armhf-2015-04-09.tar.xz
  
wget http://rcn-ee.net/deb/rootfs/oneiric/ubuntu-11.10-r0-minimal-armel.tar.xz
+
Verify Image with:
mirrors (will take some time to update):
+
  md5sum ubuntu-14.04.2-console-armhf-2015-04-09.tar.xz
wget http://ynezz.ibawizard.net/beagleboard/oneiric/ubuntu-11.10-r0-minimal-armel.tar.xz
+
  be1f3008aaa32d88c842897e324bcdf8 ubuntu-14.04.2-console-armhf-2015-04-09.tar.xz
 
 
Verify Image with:  
 
  md5sum ubuntu-11.10-r0-minimal-armel.tar.xz
 
  06f5559e9c3cbd1ddb3dd4735e0edb8d ubuntu-11.10-r0-minimal-armel.tar.xz
 
  
 
Unpack Image:
 
Unpack Image:
  tar xJf ubuntu-11.10-r0-minimal-armel.tar.xz
+
  tar xf ubuntu-14.04.2-console-armhf-2015-04-09.tar.xz
  cd ubuntu-11.10-r0-minimal-armel
+
  cd ubuntu-14.04.2-console-armhf-2015-04-09
  
 
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/sda5''' is the x68 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 Beagle Bx
+
Quick install script for [board]
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle_bx
+
  sudo ./setup_sdcard.sh --mmc /dev/sdX --dtb board
  
Quick Install script for Beagle Cx, xM A/B/C
+
board options:
sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle
+
*BeagleBoard Ax/Bx/Cx/Dx    - omap3-beagle
 +
*BeagleBoard xM             - omap3-beagle-xm
 +
*BeagleBone/Black          - beaglebone
 +
*OMAP5432 uEVM              - omap5-uevm
 +
*BeagleBoard-X15            - am57xx-beagle-x15
  
Quick Install script for Panda
+
So for the BeagleBoard xM:
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot panda
+
  sudo ./setup_sdcard.sh --mmc /dev/sdX --dtb omap3-beagle-xm
 
 
*Additional Options
 
** --rootfs <ext4 default>
 
** --swap_file <swap file size in MB's>
 
** --addon <pico>
 
** --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 BeagleBoard, reboot and have Ubuntu Maverick loaded.
 
 
 
For a full gui install run this on your beagle (make sure network is setup):
 
Ethernet: "sudo ifconfig -a" and "sudo dhclient usb1" or "sudo dhclient eth0"
 
Wireless: http://elinux.org/BeagleBoardUbuntu#Wifi_Networking_.28command_line.29
 
sudo apt-get update
 
sudo apt-get install xubuntu-desktop
 
  
 
Advanced: Build Image:
 
Advanced: Build Image:
  
fixup.sh: https://github.com/RobertCNelson/omap-image-builder/raw/master/tools/fixup.sh
+
git clone https://github.com/RobertCNelson/omap-image-builder.git
 +
cd omap-image-builder
 +
git checkout v2015.04 -b tmp
  
Built with rootstock trunk (ARM native mode, run directly on beagleboard):
+
Stable:
sudo ./rootstock --fqdn omap --imagesize 2G --dist oneiric --serial ttyO2 \
 
--login ubuntu --password temppwd \
 
--seed git-core,nano,pastebinit,usbutils,wget,i2c-tools,uboot-envtools,uboot-mkimage,btrfs-tools,openssh-server,usb-modeswitch,wireless-tools,wpasupplicant \
 
--script fixup.sh --components "main universe multiverse" \
 
--kernel-image http://rcn-ee.net/deb/oneiric/v3.0.6-x3/linux-image-3.0.6-x3_1.0oneiric_armel.deb
 
  
=== Natty 11.04 ===
+
./RootStock-NG.sh -c rcn-ee_console_ubuntu_stable_armhf
  
Image Updated Oct 13th, updated v3.0.6 kernel, now with better s-video support (setup_sdcard.sh option)...
+
== Flasher ==
  
Default user: ubuntu pass: temppwd
+
=== eMMC: BeagleBone Black ===
  
Get prebuilt image:
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on windows: https://wiki.ubuntu.com/Win32DiskImager  First press and hold the boot select button (next to the microSD card), then apply power. On bootup the board should indicate it has started the flashing procedure visually via a Cylon Sweep pattern shown on the 4 LED's next to the ethernet jack. Progress is reported on both the serial debug and hdmi connectors, 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.
  
  wget http://rcn-ee.net/deb/rootfs/natty/ubuntu-11.04-r5-minimal-armel.tar.xz
+
Script for reference: (this is the script that writes to the eMMC)
mirrors (will take some time to update):
+
  https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v3.sh
wget http://ynezz.ibawizard.net/beagleboard/natty/ubuntu-11.04-r5-minimal-armel.tar.xz
 
  
Verify Image with:
+
This script will only take about 5-6 Minutes after power on.
md5sum ubuntu-11.04-r5-minimal-armel.tar.xz
 
5b34f8078b0f62165203488eea740123  ubuntu-11.04-r5-minimal-armel.tar.xz
 
  
Unpack Image:
+
Notes:
tar xJf ubuntu-11.04-r5-minimal-armel.tar.xz
+
* 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.
cd ubuntu-11.04-r5-minimal-armel
+
* If the 4 LED's blink a constant pattern, the eMMC write has failed. First REMOVE ALL capes, then retry again.
  
If you don't know the location of your SD card:
+
User: ubuntu
sudo ./setup_sdcard.sh --probe-mmc
+
pass: temppwd
  
You should see something like
+
Image Updated:
 +
*2015-04-09
 +
** BeagleBone Black: v3.14.37-ti-r57 kernel
 +
*2015-02-19
 +
** BeagleBone Black: v3.14.33-ti-r50 kernel
 +
*2015-01-06
 +
** BeagleBone Black: v3.14.26-ti-r43 kernel
  
Are you sure? I Don't see [/dev/idontknow], here is what I do see...
+
Get prebuilt image:
   
+
  wget https://rcn-ee.com/rootfs/2015-04-09/flasher/BBB-eMMC-flasher-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
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/sda5''' is the x68 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...
+
Verify Image with:
 +
md5sum BBB-eMMC-flasher-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
 +
bd5ec650b1966b63651ff40f785aa532  BBB-eMMC-flasher-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
  
Install Image:
+
Follow the "standard" update procedure.
 +
http://elinux.org/Beagleboard:Updating_The_Software
  
Quick Install script for Beagle Bx
+
Linux:
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle_bx
+
unxz BBB-eMMC-flasher-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
 +
  sudo dd if=./BBB-eMMC-flasher-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img of=/dev/sdX
  
Quick Install script for Beagle Cx, xM A/B/C
+
== raw microSD img ==
sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle
 
  
Quick Install script for Panda
+
=== BeagleBoard (classic) ===
sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot panda
 
  
*Additional Options
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on windows: https://wiki.ubuntu.com/Win32DiskImager
** --rootfs <ext4 default>
 
** --swap_file <swap file size in MB's>
 
** --addon <pico>
 
** --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 BeagleBoard, reboot and have Ubuntu Maverick loaded.
+
User: ubuntu
 +
pass: temppwd
  
For a full gui install run this on your beagle (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
sudo apt-get update
+
  ./grow_partition.sh
  sudo apt-get install xfce4 gdm xubuntu-gdm-theme xubuntu-artwork xserver-xorg-video-omap3 network-manager
+
  sudo reboot
 
 
Advanced: Build Image:
 
  
fixup.sh: https://github.com/RobertCNelson/omap-image-builder/raw/master/tools/fixup.sh
+
Image Updated:
 +
*2015-04-09
 +
** Beagle: v4.0.0-rc7-armv7-x1 kernel
 +
*2015-02-19
 +
** Beagle: v3.19.0-armv7-x3 kernel
 +
*2015-01-06
 +
** Beagle: v3.18.1-armv7-x2 kernel
  
Built with rootstock trunk (ARM native mode, run directly on beagleboard):
+
Get prebuilt image:
 +
wget https://rcn-ee.com/rootfs/2015-04-09/microsd/bb-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
  
sudo ./rootstock --fqdn omap --imagesize 2G --dist natty --serial ttyO2 \
+
Verify Image with:
  --login ubuntu --password temppwd \
+
  md5sum bb-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
--seed git-core,nano,pastebinit,usbutils,wget,i2c-tools,uboot-envtools,uboot-mkimage,btrfs-tools,openssh-server,usb-modeswitch,wireless-tools,wpasupplicant \
+
  f1bea9c95ec950af62be5a41499c1854  bb-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
  --script fixup.sh --components "main universe multiverse" \
 
--kernel-image http://rcn-ee.net/deb/natty/v3.0.6-x3/linux-image-3.0.6-x3_1.0natty_armel.deb
 
  
= Method 2: Use the NetInstall method=
+
Linux:
 +
unxz bb-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
 +
sudo dd if=./bb-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img of=/dev/sdX
  
You will need a 1GB/2GB SD card or greater.
+
=== BeagleBoard xM ===
Standard System : ~700MB
 
  
== Ubuntu 11.04 (Natty) ==
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on windows: https://wiki.ubuntu.com/Win32DiskImager
  
git clone git://github.com/RobertCNelson/netinstall.git
+
User: ubuntu
cd netinstall
+
pass: temppwd
  
Install script for Beagle Bx
+
Auto partition resize:
  ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_bx --distro natty
+
cd /opt/scripts/tools
 +
git pull
 +
  ./grow_partition.sh
 +
sudo reboot
  
Install script for Beagle Cx, xM A/B/C
+
Image Updated:
./mk_mmc.sh --mmc /dev/sdX --uboot beagle --distro natty
+
*2015-04-09
 +
** Beagle xM: v4.0.0-rc7-armv7-x1 kernel
 +
*2015-02-19
 +
** Beagle xM: v3.19.0-armv7-x3 kernel
 +
*2015-01-06
 +
** Beagle xM: v3.18.1-armv7-x2 kernel
  
Install script for Panda
+
Get prebuilt image:
  ./mk_mmc.sh --mmc /dev/sdX --uboot panda --distro natty
+
  wget https://rcn-ee.com/rootfs/2015-04-09/microsd/bbxm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
  
*Options:
+
Verify Image with:
**--uboot : beagle_bx, beagle, panda
+
md5sum bbxm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
**--distro : maverick
+
842d75d306831461c103670498682be3  bbxm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
**--firmware : installs firmware
 
**--serial-mode : debian-installer uses Serial Port
 
**--usb-rootfs : (uImage on /dev/mmcblkp0 and rootfs on external usb drive /dev/sda1)
 
  
Note: The default options work for most people, but if you'd like to tweak boot settings, edit these before running the script.
+
Linux:
   
+
  unxz bbxm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
NetInstall boot Settings:
+
  sudo dd if=./bbxm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img of=/dev/sdX
gedit ./netinstall/scripts/boot.scr/dvi.cmd
 
gedit ./netinstall/scripts/boot.scr/serial.cmd
 
   
 
Normal Boot Settings:
 
gedit ./netinstall/scripts/boot.scr/dvi-normal-natty.cmd
 
gedit ./netinstall/scripts/boot.scr/serial-normal-natty.cmd
 
  
Place SD card into Beagle and boot:
+
=== BeagleBone/BeagleBone Black ===
  
Configure the network:
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on windows: https://wiki.ubuntu.com/Win32DiskImager
usb0: USB net <- (usually the OTG port, but could also be the smsc95xx adapter on the beagle and panda)
 
usb1: USB net <- (usually the smsc95xx adapter on the beagle and panda, when usb0 exist)
 
eth0: Ethernet <- Your usb-ethernet device (or the smsc95xx adapter with 2.6.39+)
 
wlan0: Wifi <- Your usb-wifi device..  
 
  
Troubshooting: If boot fails..
+
User: ubuntu
*Hold the user button down to force booting from MMC
+
pass: temppwd
*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:  
 
nand erase 260000 20000
 
  
NetInstall assumptions:
+
Auto partition resize:
  Continue with out Kernel Modules <yes>
+
  cd /opt/scripts/tools
  Partition <Guided - use the largest continuous free space>
+
  git pull
 +
./grow_partition.sh
 +
sudo reboot
  
= Method 3: Build an Ubuntu root file system with RootStock=
+
Image Updated:
 +
*2015-04-09
 +
** BeagleBone/BeagleBone Black: v3.14.37-ti-r57 kernel
 +
*2015-02-19
 +
** BeagleBone/BeagleBone Black: v3.14.33-ti-r50 kernel
 +
*2015-01-06
 +
** BeagleBone/BeagleBone Black: v3.14.26-ti-r43 kernel
  
== Install RootStock ==
+
Get prebuilt image:
 +
wget https://rcn-ee.com/rootfs/2015-04-09/microsd/bone-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
  
This is based off Ubuntu's RootStock Project; [https://launchpad.net/project-rootstock RootStock] script.
+
Verify Image with:
 +
md5sum bone-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
 +
9a29ba2c92ec1632fb097f2170027512  bone-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
  
Maverick (10.10)
+
Linux:
  sudo apt-get install rootstock
+
unxz bone-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
 +
  sudo dd if=./bone-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img of=/dev/sdX
  
Lucid (10.04) (use rootstock trunk)
+
=== OMAP5432 uEVM ===
sudo apt-get install rootstock (to install rootstock's dependices)
 
bzr branch lp:project-rootstock
 
cd project-rootstock
 
  
== RootStock ==
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on windows: https://wiki.ubuntu.com/Win32DiskImager
  
=== RootStock: Useful seed Packages ===
+
User: ubuntu
 +
pass: temppwd
  
Useful Packages:
+
Auto partition resize:
  linux-firmware,wireless-tools :wifi adapters..
+
  cd /opt/scripts/tools
  ntpdate :sync real time clock from network
+
git pull
 +
./grow_partition.sh
 +
  sudo reboot
  
GUI's (broken bug: FIXME)
+
Image Updated:
xfce4: xfce4,gdm,xubuntu-gdm-theme,xubuntu-artwork
+
*2015-04-09
 +
** OMAP5432 uEVM: v3.14.37-ti-r57 kernel
 +
*2015-02-19
 +
** OMAP5432 uEVM: v3.14.33-ti-r50 kernel
 +
*2015-01-06
 +
** OMAP5432 uEVM: v3.14.26-ti-r43 kernel
  
=== RootStock: Running ===
+
Get prebuilt image:
 +
wget https://rcn-ee.com/rootfs/2015-04-09/microsd/omap5-uevm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
  
Rootstock Command line:
+
Verify Image with:
  sudo ./rootstock --fqdn <hostname> --login <rootuser> --password <rootuserpasswd> --imagesize <qemu image size> \
+
  md5sum omap5-uevm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
  --seed <packages> --dist <lucid/maverick> --serial <ttySx>  --kernel-image <http>
+
  39bd21bdb09cd38ab0c2d7ed9668ac34  omap5-uevm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
  
Basic Natty (11.04) Beagleboard minimal image:
+
Linux:
  sudo ./rootstock --fqdn omap --login ubuntu --password temppwd --imagesize 2G \
+
  unxz omap5-uevm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
  --seed wget,nano,linux-firmware,wireless-tools,usbutils --dist natty --serial ttyO2 \
+
  sudo dd if=./omap5-uevm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img of=/dev/sdX
--components "main universe multiverse" \
 
--kernel-image http://rcn-ee.net/deb/natty/v2.6.39-x1/linux-image-2.6.39-x1_1.0natty_armel.deb
 
  
Upon Completion, you should have:
+
=== BeagleBoard-X15 ===
armel-rootfs-<date>.tgz  -> Root file System, dump to ext2/3 partition of SD card
 
vmlinuz-2.6.<version>    -> Boot Image, use mkimage to create uImage and dump to the first fat16 partition of SD card
 
initrd.img-2.6.<version> -> Boot initramfs, use mkimage to create uInitrd and dump to the first fat16 partition of SD card
 
  
= Method 4 (More advanced) Start by Manually Setting Up your SD Card(without an automatic SD card setup script)=
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on windows: https://wiki.ubuntu.com/Win32DiskImager
  
For this section, you can use the files from above:
+
User: ubuntu
Demo Images: http://elinux.org/BeagleBoardUbuntu#Demo_Image
+
pass: temppwd
Rootstock: http://elinux.org/BeagleBoardUbuntu#Build_an_Ubuntu_root_file_system_with_RootStock
 
  
== Partition SD Card ==
+
Auto partition resize:
You will need a 1GB SD card or greater.
+
cd /opt/scripts/tools
  Standard Console System : ~286MB
+
git pull
  + Desktop environment (lxde,gdm) : ~479MB
+
  ./grow_partition.sh
 +
  sudo reboot
  
Starting with an empty SD card and using gparted, create:
+
Image Updated:
50 MiB Primary Partition, fat16/fat32
+
*2015-04-09
Rest as ext2/ext3/ext4/btrfs
+
** BeagleBoard-X15: v3.14.37-ti-r57 kernel
 +
*2015-02-19
 +
** BeagleBoard-X15: v3.14.33-ti-r50 kernel
 +
*2015-01-06
 +
** BeagleBoard-X15: v3.14.26-ti-r43 kernel
  
Note: The boot partition can be hard to make bootable at times, here's a quick command line:
+
Get prebuilt image:
 +
wget https://rcn-ee.com/rootfs/2015-04-09/microsd/bbx15-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
  
First blank the MMC card's partition table with parted: (/dev/sdX as an example)
+
Verify Image with:
  sudo parted -s /dev/sdX mklabel msdos
+
  md5sum bbx15-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
 +
d5aa4a68283a7034e61f01dcc75832d6  bbx15-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
  
Then create the new boot partition:
+
Linux:
  sudo fdisk /dev/sdX << MMC_END
+
unxz bbx15-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
n
+
  sudo dd if=./bbx15-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img of=/dev/sdX
p
 
1
 
1
 
+64M
 
t
 
e
 
p
 
w
 
MMC_END
 
  
Notes:
+
= Method 2: Use the NetInstall method=
GNU Fdisk doesn't and won't work...
 
fdisk (util-linux-ng 2.18.x) (just Fedora) add: "-c=dos -u=cylinders" ... "sudo fdisk -c=dos -u=cylinders /dev/sdX"
 
  
Make sure to set the partition boot flag
+
You will need a 1GB/2GB/4GB/8GB SD card or greater.
  sudo parted --script /dev/sdX set 1 boot on
+
  Standard system : ~700&nbsp;MB
  
And format it as vfat:
+
Report Bugs/Issues to: https://github.com/RobertCNelson/netinstall/issues
sudo mkfs.vfat -F 16 /dev/sdX1
+
(anywhere else will be ignored..)
  
The rootfs partition, doesn't need any special options, so just use fdisk, gparted, etc to create and format your rootfs partition..
+
Download the netinstall script:
 +
git clone https://github.com/RobertCNelson/netinstall.git
 +
cd netinstall
  
Gparted Example: http://nishanthmenon.blogspot.com/2008/08/how-to-boot-beagle.html
+
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)
  
For Reference:
+
Device: <board> selection:
  Disk /dev/sdd: 2038 MB, 2038431744 bytes
+
  *BeagleBoard Ax/Bx/Cx  - omap3-beagle
  255 heads, 63 sectors/track, 247 cylinders
+
  *BeagleBoard xMA/B/C  - omap3-beagle-xm
  Units = cylinders of 16065 * 512 = 8225280 bytes
+
  *BeagleBone Ax        - am335x-bone-serial
  Disk identifier: 0x0008e471
+
  *BeagleBone (DVI cape) - am335x-bone-video
   
+
  *BeagleBone Black      - am335x-boneblack
     Device Boot      Start        End      Blocks  Id  System
+
*PandaBoard Ax     - omap4-panda
  /dev/sdd1              1          6      48163+   6  FAT16
+
  *PandaBoard A4+   - omap4-panda-a4
  /dev/sdd2              7        247     1935832+  83  Linux
+
  *PandaBoard ES     - omap4-panda-es
  
== Boot Partition ==
+
Installation script for new <board> selection: (slowly migrating all devices to this method)
 +
sudo ./mk_mmc.sh --mmc /dev/sdX --dtb <board> --distro <distro>
  
Requirements:
+
So for the xM: with quantal:
 +
sudo ./mk_mmc.sh --mmc /dev/sdX --dtb omap3-beagle-xm --distro quantal
  
sudo apt-get install uboot-mkimage
+
*Other Options:
Mount the fatfs partition of your SD card.
+
**--firmware : installs firmware
 +
**--serial-mode : debian-installer uses Serial Port
  
Mount such as: (/dev/sdX1 is the fat Boot Partition)
+
Place SD card into BeagleBoard and boot:
mkdir -p ./tmp
 
sudo mount /dev/sdX1 ./tmp
 
  
=== MLO and U-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..
  
Download and copy MLO and U-Boot from here:  
+
See my notes for my testing procedure: https://github.com/RobertCNelson/netinstall/blob/master/test.Ubuntu
http://www.angstrom-distribution.org/demo/beagleboard/
 
  
First copy "MLO-beagleboard-1.44+rX+gitX-rX" as MLO to the Boot Partition
+
Troubleshooting: If booting fails..
Then copy "u-boot-beagleboard-20XX.XX+r62+gitX-rX.bin" as u-boot.bin to the Boot Partition
+
*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]
 +
*Clear U-boot's Environment Variables in NAND:
 +
nand erase 260000 20000
  
=== U-Boot uImage and uInitrd ===
+
NetInstall assumptions:
 +
Assume asll <default>'s... Thanks you preseed.conf!!!
  
U-Boot needs a compatible kernel image to boot.  To do this, we are using mkimage from (uboot-mkimage) to create an image from the vmlinuz kernel file.
+
= Method 3: Manual Install (no automatic scripts)=
  
mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n "Linux" -d ./vmlinuz-* ./uImage
+
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:
Copy "uImage" to the Boot Partition
 
  
Next create a uInird (this contains a script to fix the rtc on boot, otherwise fsck/reboot/fsck/reboot/repeat happens..)
+
== Beagle/Beagle xM ==
 +
http://eewiki.net/display/linuxonarm/BeagleBoard
  
  mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 -n initramfs -d ./initrd.img-* ./uInitrd
+
== BeagleBone ==
Copy "uInitrd" to the Boot Partition
+
  http://eewiki.net/display/linuxonarm/BeagleBone
  
=== U-Boot Boot Scripts ===
+
== BeagleBone Black ==
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'.
+
  http://eewiki.net/display/linuxonarm/BeagleBone+Black
  
fixrtc: (only uInitrd) Resets RTC based on last mount
+
== Panda/Panda ES ==
buddy=${buddy}: (both) Kernel Zippy1/2 Support
+
  http://eewiki.net/display/linuxonarm/PandaBoard
  mpurate=${mpurate}: (recommended core clock)
 
  
==== boot.scr -> uEnv.txt ====
+
= Advanced =
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
+
==Install Latest Kernel Image==
bootenv=boot.scr
 
loaduimage=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
 
mmcboot=echo Running boot.scr script from mmc ...; source ${loadaddr}
 
  
==== Beagle Bx/Cx & xM ====
+
Script:
 +
cd /opt/scripts/tools
 +
git pull
  
create a new file: boot.cmd
+
Stable:
  setenv dvimode 1280x720MR-16@60
+
  ./update_kernel.sh
setenv vram 12MB
 
setenv bootcmd 'fatload mmc 0:1 0x80300000 uImage; fatload mmc 0:1 0x81600000 uInitrd; bootm 0x80300000 0x81600000'
 
setenv bootargs console=ttyO2,115200n8 console=tty0 root=/dev/mmcblk0p2 rootwait ro vram=${vram} omapfb.mode=dvi:${dvimode} fixrtc buddy=${buddy} mpurate=${mpurate}
 
boot
 
  
Use mkimage create to actual *.scr file for U-Boot:
+
Testing:
 +
./update_kernel.sh --beta-kernel
  
mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "Ubuntu" -d ./boot.cmd ./boot.scr
+
Custom: (has to be on rcn-ee.net)
Copy "boot.scr" to the Boot Partition
+
./update_kernel.sh --kernel v3.8.13-bone69
For "igepv2" users, rename this to "boot.ini"
 
  
Umount the Boot Partition:
+
Reboot with your new Kernel Image.
  
sudo umount ./tmp
+
== Upgrade X-loader and U-boot ==
  
== RootFS Partition ==
+
*Note: the functionality of the "X-Loader" project has been merged as u-boot spl.
Root File System
 
  
Mount your SD card's larger root file system partition (assuming /dev/sdX2) and 'untar' the rootfs into it.
+
Compatibility with older Ax, Bx, Cx, and Dx BeagleBoards
  
mkdir -p ./tmp
+
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:
sudo mount /dev/sdX2 ./tmp
+
  nand erase 260000 20000
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
+
Or: To fully erase the entire NAND:
sudo ifconfig -a
+
  nand erase.chip
  sudo dhclient ethX (or wlanX/etc..)
 
  
Additional Network Setup Information can be found [[BeagleBoardUbuntuNetwork|HERE]]
+
Requires MMC card:
  
= Advanced =
+
git clone https://github.com/RobertCNelson/flasher.git
 +
cd flasher
  
==Install Latest Kernel Image==
+
For the Beagle Ax/Bx
 
 
===Script File===
 
 
 
Latest Stable is : https://github.com/RobertCNelson/stable-kernel
 
 
 
export DIST=natty  (options are lucid/maverick/natty/oneiric/squeeze/wheezy)
 
wget http://rcn-ee.net/deb/${DIST}/LATEST-omap
 
wget $(cat ./LATEST-omap | grep STABLE | awk '{print $3}')
 
/bin/bash install-me.sh
 
 
 
Reboot with your new uImage
 
 
 
== Upgrade X-loader and U-boot ==
 
 
 
Compatible with Bx,C2/3/4
 
 
 
Requires MMC card..
 
 
 
git clone git://github.com/RobertCNelson/flash-omap.git
 
cd flash-omap
 
 
 
For the Beagle 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
+
  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
  
 
If you don't know the location of your SD card:
 
If you don't know the location of your SD card:
  ./mk_mmc.sh --mmc /dev/'''idontknow'''
+
  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 514: Line 498:
 
  /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/sda5''' is the x68 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.
  
Worst case, depending on what's actually in NAND, you might still have to stop and do this:
+
== SGX Drivers ==
  
nand erase 260000 20000
+
=== SGX BeagleBone/BeagleBone Black ===
reset
 
  
===Manual Run===
+
NNote, these are FBDEV only, no xorg/x11/etc...
mmc init
 
fatload mmc 0:1 0x80200000 MLO
 
nand unlock
 
nand ecc hw
 
nandecc hw
 
nand erase 0 80000
 
nand write 0x80200000 0 20000
 
nand write 0x80200000 20000 20000
 
nand write 0x80200000 40000 20000
 
nand write 0x80200000 60000 20000
 
 
fatload mmc 0:1 0x80300000 u-boot.bin
 
nand unlock
 
nand ecc sw
 
nandecc sw
 
nand erase 80000 160000
 
nand write 0x80300000 80000 160000
 
nand erase 260000 20000
 
reset
 
  
== SGX Video Acceleration ==
+
Install sgx modules (3.14.x ti kernel):
 +
sudo apt-get install ti-sgx-es8-modules-`uname -r`
 +
sudo depmod -a `uname -r`
 +
sudo update-initramfs -uk `uname -r`
  
Requirements: 2.6-stable from launchpad or 2.6.35.3-x1+ deb's from rcn-ee.net. (the Demo Images hosted on rcn-ee.net meet this requirement)
+
Build SGX userspace (must be done on an x86, due to the TI 5.01.01.01 blob extractor)
  https://github.com/RobertCNelson/stable-kernel
+
git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
 +
cd ti-linux-kernel-dev/
 +
git checkout origin/ti-linux-3.14.y -b tmp-sgx
 +
./sgx_create_package.sh
  
Note: ''An older version of these instructions was adapted for the IGEPv2 platform - if you are following this tutorial and have an IGEPv2, consider using http://wiki.jmaustin.org/wiki/IgepSGXUbuntu instead''
+
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 /
=== SDK unPackage Script ===
+
  cd /opt/gfxinstall/
 
+
  sudo ./sgx-install.sh
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
 +
debian@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
+
  sudo ./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 ===
+
BeagleBoard/PandaBoard:
 +
cd /opt/scripts/tools/graphics/
 +
./ti-omapdrm.sh
  
  sudo rm /etc/powervr-esrev
+
BeagleBone/BeagleBone Black:
  sudo depmod -a omaplfb
+
  cd /opt/scripts/tools/graphics/
sudo /etc/init.d/pvr restart
+
  ./ti-tilcdc.sh
  
== DSP ==
+
= Swapfile =
  
=== gst-dsp ===
+
== Using a File for Swap Instead of a Partition ==
  
Seems to work on all Beagle's, with atleast 2.6.38+ now...
+
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).
  
Requirements: 2.6-stable from launchpad or 2.6.38+ deb's from rcn-ee.net. (the Demo Images hosted on rcn-ee.net meet this requirement)
+
Some images (such as those from Linaro.org) do not come with a swap partition or any swap space allocated.
  https://github.com/RobertCNelson/stable-kernel
 
  
Download the latest version of the "create_dsp_package.sh" script
+
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.
wget https://github.com/RobertCNelson/stable-kernel/raw/master/create_dsp_package.sh
 
  
Make script executable
+
=== Creating a Swapfile ===
chmod a+x ./create_dsp_package.sh
 
  
Package script:
+
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:
./create_dsp_package.sh
 
  
Copy DSP_Install_libs.tar.gz to beagle
+
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
  
Setup network...
+
To tell the OS to load this swapfile on each start up, edit the /etc/fstab file to include the following additional line:
  
Extract:
+
  /var/cache/swap/swapfile    none    swap    sw    0  0
  tar xf DSP_Install_libs.tar.gz
 
  
Install
+
To verify that the swapfile is accessilble as swap to the OS, run "top" or "htop" at a console.
./install-DSP.sh
 
 
 
Build gst-dsp stuff..
 
./install-gst-dsp.sh
 
 
 
Playbin:
 
sudo gst-launch playbin2 uri=file://(file)
 
 
 
== 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
 
./build_deb.sh
 
  
 
= 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 802: Line 597:
 
  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 810: Line 605:
 
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 822: Line 616:
  
 
=== 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 840: Line 634:
 
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).
+
ROS (Robot Operating System) provides libraries and tools to help software developers create robot applications. It provides hardware abstraction, device drivers, libraries, visualizers, message-passing, package management, and more. ROS is licensed under an open source, BSD license.
  
Following the instructions from here will build and install ROS on your beagleboard:
+
There are currently builds of ROS for Ubuntu Trusty armhf. These builds include most but not all packages, and save a considerable amount of time compared to doing a full source-based installation:
  
http://www.ros.org/wiki/cturtle/Installation/Ubuntu/SVN
+
http://wiki.ros.org/indigo/Installation/UbuntuARM
  
You will need an Internet connection for your Beagleboard for these scripts to work.
+
Alternatively ROS can be installed from source and is generally easy to do so (although slow).
  
For more information about ROS see www.ros.org
+
For more information about ROS, see www.ros.org.

Revision as of 07:19, 10 April 2015

(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

git clone https://github.com/RobertCNelson/armv7-multiplatform.git
cd armv7-multiplatform
git checkout origin/v4.0.x -b tmp
./build_kernel.sh
git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
cd ti-linux-kernel-dev
git checkout origin/ti-linux-3.14.y -b tmp
./build_kernel.sh

Ubuntu (14.04.2)

Default username/password:

  • username: ubuntu
  • password: temppwd

Image Updated:

  • 2015-04-09
    • Beagle/Beagle xM: v4.0.0-rc7-armv7-x1 kernel
    • BeagleBone/BeagleBone Black: v3.14.37-ti-r57 kernel
    • OMAP5432 uEVM: v3.14.37-ti-r57 kernel
    • BeagleBoard-X15: v3.14.37-ti-r57 kernel
  • 2015-02-19
    • Beagle/Beagle xM: v3.19.0-armv7-x3 kernel
    • BeagleBone/BeagleBone Black: v3.14.33-ti-r50 kernel
    • OMAP5432 uEVM: v3.14.33-ti-r50 kernel
    • BeagleBoard-X15: v3.14.33-ti-r50 kernel
  • 2015-01-06
    • Beagle/Beagle xM: v3.18.1-armv7-x2 kernel
    • BeagleBone/BeagleBone Black: v3.14.26-ti-r43 kernel
    • OMAP5432 uEVM: v3.14.26-ti-r43 kernel
    • BeagleBoard-X15: v3.14.26-ti-r43 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.com/rootfs/2015-04-09/ubuntu-14.04.2-console-armhf-2015-04-09.tar.xz

Verify Image with:

md5sum ubuntu-14.04.2-console-armhf-2015-04-09.tar.xz
be1f3008aaa32d88c842897e324bcdf8  ubuntu-14.04.2-console-armhf-2015-04-09.tar.xz

Unpack Image:

tar xf ubuntu-14.04.2-console-armhf-2015-04-09.tar.xz
cd ubuntu-14.04.2-console-armhf-2015-04-09

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
  • BeagleBoard-X15 - am57xx-beagle-x15

So for the BeagleBoard xM:

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

Advanced: Build Image:

git clone https://github.com/RobertCNelson/omap-image-builder.git
cd omap-image-builder
git checkout v2015.04 -b tmp

Stable:

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

Flasher

eMMC: BeagleBone Black

This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on windows: https://wiki.ubuntu.com/Win32DiskImager First press and hold the boot select button (next to the microSD card), then apply power. On bootup the board should indicate it has started the flashing procedure visually via a Cylon Sweep pattern shown on the 4 LED's next to the ethernet jack. Progress is reported on both the serial debug and hdmi connectors, 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-v3.sh

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

User: ubuntu pass: temppwd

Image Updated:

  • 2015-04-09
    • BeagleBone Black: v3.14.37-ti-r57 kernel
  • 2015-02-19
    • BeagleBone Black: v3.14.33-ti-r50 kernel
  • 2015-01-06
    • BeagleBone Black: v3.14.26-ti-r43 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2015-04-09/flasher/BBB-eMMC-flasher-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz

Verify Image with:

md5sum BBB-eMMC-flasher-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
bd5ec650b1966b63651ff40f785aa532  BBB-eMMC-flasher-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz

Follow the "standard" update procedure.

http://elinux.org/Beagleboard:Updating_The_Software

Linux:

unxz BBB-eMMC-flasher-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
sudo dd if=./BBB-eMMC-flasher-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img of=/dev/sdX

raw microSD img

BeagleBoard (classic)

This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on windows: https://wiki.ubuntu.com/Win32DiskImager

User: ubuntu pass: temppwd

Auto partition resize:

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

Image Updated:

  • 2015-04-09
    • Beagle: v4.0.0-rc7-armv7-x1 kernel
  • 2015-02-19
    • Beagle: v3.19.0-armv7-x3 kernel
  • 2015-01-06
    • Beagle: v3.18.1-armv7-x2 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2015-04-09/microsd/bb-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz

Verify Image with:

md5sum bb-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
f1bea9c95ec950af62be5a41499c1854  bb-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz

Linux:

unxz bb-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
sudo dd if=./bb-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img of=/dev/sdX

BeagleBoard xM

This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on windows: https://wiki.ubuntu.com/Win32DiskImager

User: ubuntu pass: temppwd

Auto partition resize:

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

Image Updated:

  • 2015-04-09
    • Beagle xM: v4.0.0-rc7-armv7-x1 kernel
  • 2015-02-19
    • Beagle xM: v3.19.0-armv7-x3 kernel
  • 2015-01-06
    • Beagle xM: v3.18.1-armv7-x2 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2015-04-09/microsd/bbxm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz

Verify Image with:

md5sum bbxm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
842d75d306831461c103670498682be3  bbxm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz

Linux:

unxz bbxm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
sudo dd if=./bbxm-ubuntu-14.04.2-console-armhf-2015-04-09-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 on windows: https://wiki.ubuntu.com/Win32DiskImager

User: ubuntu pass: temppwd

Auto partition resize:

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

Image Updated:

  • 2015-04-09
    • BeagleBone/BeagleBone Black: v3.14.37-ti-r57 kernel
  • 2015-02-19
    • BeagleBone/BeagleBone Black: v3.14.33-ti-r50 kernel
  • 2015-01-06
    • BeagleBone/BeagleBone Black: v3.14.26-ti-r43 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2015-04-09/microsd/bone-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz

Verify Image with:

md5sum bone-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
9a29ba2c92ec1632fb097f2170027512  bone-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz

Linux:

unxz bone-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
sudo dd if=./bone-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img of=/dev/sdX

OMAP5432 uEVM

This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on windows: https://wiki.ubuntu.com/Win32DiskImager

User: ubuntu pass: temppwd

Auto partition resize:

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

Image Updated:

  • 2015-04-09
    • OMAP5432 uEVM: v3.14.37-ti-r57 kernel
  • 2015-02-19
    • OMAP5432 uEVM: v3.14.33-ti-r50 kernel
  • 2015-01-06
    • OMAP5432 uEVM: v3.14.26-ti-r43 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2015-04-09/microsd/omap5-uevm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz

Verify Image with:

md5sum omap5-uevm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
39bd21bdb09cd38ab0c2d7ed9668ac34  omap5-uevm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz

Linux:

unxz omap5-uevm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
sudo dd if=./omap5-uevm-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img of=/dev/sdX

BeagleBoard-X15

This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on windows: https://wiki.ubuntu.com/Win32DiskImager

User: ubuntu pass: temppwd

Auto partition resize:

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

Image Updated:

  • 2015-04-09
    • BeagleBoard-X15: v3.14.37-ti-r57 kernel
  • 2015-02-19
    • BeagleBoard-X15: v3.14.33-ti-r50 kernel
  • 2015-01-06
    • BeagleBoard-X15: v3.14.26-ti-r43 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2015-04-09/microsd/bbx15-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz

Verify Image with:

md5sum bbx15-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
d5aa4a68283a7034e61f01dcc75832d6  bbx15-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz

Linux:

unxz bbx15-ubuntu-14.04.2-console-armhf-2015-04-09-2gb.img.xz
sudo dd if=./bbx15-ubuntu-14.04.2-console-armhf-2015-04-09-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-bone69

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

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

Install sgx modules (3.14.x ti kernel):

sudo apt-get install ti-sgx-es8-modules-`uname -r`
sudo depmod -a `uname -r`
sudo update-initramfs -uk `uname -r`

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

git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
cd ti-linux-kernel-dev/
git checkout origin/ti-linux-3.14.y -b tmp-sgx
./sgx_create_package.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

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

SGX Demos

cd /opt/gfxsdkdemos/ogles2/
sudo ./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

ROS (Robot Operating System) provides libraries and tools to help software developers create robot applications. It provides hardware abstraction, device drivers, libraries, visualizers, message-passing, package management, and more. ROS is licensed under an open source, BSD license.

There are currently builds of ROS for Ubuntu Trusty armhf. These builds include most but not all packages, and save a considerable amount of time compared to doing a full source-based installation:

http://wiki.ros.org/indigo/Installation/UbuntuARM

Alternatively ROS can be installed from source and is generally easy to do so (although slow).

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