Difference between revisions of "BeagleBoardUbuntu"

From eLinux.org
Jump to: navigation, search
m (Oneiric 11.10: Add image for the bone)
m (Method 1: Download a Complete Pre-Configured Image: 2015-11-13)
(252 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.1.x 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)
 
  
Just follow: https://wiki.ubuntu.com/ARM/OMAP
+
* '''Advanced Users only''': BeagleBoard xM: Kernel source, used in these demo images: https://github.com/RobertCNelson/armv7-multiplatform
 
+
git clone https://github.com/RobertCNelson/armv7-multiplatform.git
==Demo Image==
+
cd armv7-multiplatform
 
+
git checkout origin/v4.3.x -b tmp
Note, these Demo Images contain a custom kernel from rcn-ee.netIf 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 itOnce you do this, it's not trivial to reverse the process..
+
./build_kernel.sh
 +
* '''Advanced Users only''': BeagleBone/BeagleBone Black:  Kernel v4.1.x source, used in these demo images: https://github.com/RobertCNelson/ti-linux-kernel-dev/tree/ti-linux-4.1.y
 +
  git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
 +
cd ti-linux-kernel-dev
 +
git checkout origin/ti-linux-4.1.y -b tmp
 +
  ./build_kernel.sh
  
If the script in these demo images fail: email "bugs@rcn-ee.com" I need: terminal command, terminal log, distribution name, arch...
+
=== Ubuntu (14.04.3) ===
  
=== Oneiric 11.10 ===
+
Default username/password:
 +
*username: ubuntu
 +
*password: temppwd
  
Image Updated Nov 30th, updated v3.1.4 kernel for the Beagle/Panda, 7inch CircuitCo ulcd now works (needs a little tweaking), 2nd ti-psp-3.1 based linux kernel now with BeagleBone support. (Note: Not as cool as the BeagleBone Angstrom Default Image)...
+
Image Updated:
 +
*2015-11-13
 +
** BeagleBoard xM: v4.3.0-armv7-x0 kernel
 +
** BeagleBone White/Black/Green: v4.1.12-ti-r29 kernel
 +
** OMAP5432 uEVM: v4.1.12-ti-r29 kernel
 +
** BeagleBoard-X15: v4.1.12-ti-r29 kernel
 +
*2015-10-09
 +
** BeagleBoard xM: v4.2.3-armv7-x2 kernel
 +
** BeagleBone White/Black/Green: v4.1.10-ti-r21 kernel
 +
** OMAP5432 uEVM: v4.1.10-ti-r21 kernel
 +
** BeagleBoard-X15: v4.1.10-ti-r21 kernel
 +
*2015-09-11
 +
** BeagleBoard xM: v4.2.0-armv7-x1 kernel
 +
** BeagleBone White/Black/Green: v4.1.6-ti-r15 kernel
 +
** OMAP5432 uEVM: v4.1.6-ti-r15 kernel
 +
** BeagleBoard-X15: v4.1.6-ti-r15 kernel
  
 
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://omap/
+
  Apache, Port 80: http://arm.local/ (Bone: via usb) http://192.168.7.2
  SSH, Port 22: ssh ubuntu@omap
+
  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.com/rootfs/2015-11-13/elinux/ubuntu-14.04.3-console-armhf-2015-11-13.tar.xz
  
wget http://rcn-ee.net/deb/rootfs/oneiric/ubuntu-11.10-r1-minimal-armel.tar.xz
+
Verify Image with:
mirrors (will take some time to update):
+
  md5sum ubuntu-14.04.3-console-armhf-2015-11-13.tar.xz
wget http://ynezz.ibawizard.net/beagleboard/oneiric/ubuntu-11.10-r1-minimal-armel.tar.xz
+
  4e5c82b71090e27115065113b44c196e ubuntu-14.04.3-console-armhf-2015-11-13.tar.xz
 
 
Verify Image with:  
 
  md5sum ubuntu-11.10-r1-minimal-armel.tar.xz
 
  54ccd8c489863cab65ea28c6aec50350 ubuntu-11.10-r1-minimal-armel.tar.xz
 
  
 
Unpack Image:
 
Unpack Image:
  tar xJf ubuntu-11.10-r1-minimal-armel.tar.xz
+
  tar xf ubuntu-14.04.3-console-armhf-2015-11-13.tar.xz
  cd ubuntu-11.10-r1-minimal-armel
+
  cd ubuntu-14.04.3-console-armhf-2015-11-13
  
 
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 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, Cx, xM A/B/C
+
Quick install script for [board]
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle
+
  sudo ./setup_sdcard.sh --mmc /dev/sdX --dtb board
  
Quick Install script for BeagleBone A2/A3
+
board options:
sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot bone
+
*BeagleBoard Ax/Bx/Cx/Dx          - omap3-beagle
 +
*BeagleBoard xM                  - omap3-beagle-xm
 +
*BeagleBone White/Black/Green    - 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
+
Advanced: Build Image:
** --rootfs <ext4 default>
 
** --swap_file <swap file size in MB's>
 
** --addon pico <ti pico projector>
 
** --addon ulcd <CircuitCo 7 inch lcd>
 
** --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.
+
git clone https://github.com/RobertCNelson/omap-image-builder.git
 +
cd omap-image-builder
 +
git checkout v2015.11 -b tmp
  
For a full gui install run this on your beagle (make sure network is setup):
+
Stable:
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 gdm xubuntu-desktop
 
  
Advanced: Build Image:
+
./RootStock-NG.sh -c rcn-ee_console_ubuntu_trusty_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_xenial_armhf
cd omap-image-builder
 
git checkout v2011.11 -b v2011.11
 
./build_image.sh
 
  
=== Natty 11.04 ===
+
=== Ubuntu Testing (xenial) ===
  
Image Updated Nov 30th, updated v3.1.4 kernel for the Beagle/Panda, 7inch CircuitCo ulcd now works (needs a little tweaking), 2nd ti-psp-3.1 based linux kernel now with BeagleBone support. (Note: Not as cool as the BeagleBone Angstrom Default Image)...
+
Image Updated:
 +
*2015-11-13
 +
** BeagleBoard xM: v4.3.0-armv7-x0 kernel
 +
** BeagleBone White/Black/Green: v4.1.12-ti-r29 kernel
 +
** OMAP5432 uEVM: v4.1.12-ti-r29 kernel
 +
** BeagleBoard-X15: v4.1.12-ti-r29 kernel
  
Services Active:
+
Get prebuilt image:
  Apache, Port 80
+
  wget https://rcn-ee.com/rootfs/2015-11-13/elinux/ubuntu-xenial-console-armhf-2015-11-13.tar.xz
SSH, Port 22
 
Getty, Serial Port
 
  
Default user: ubuntu pass: temppwd
+
Verify Image with:
 +
md5sum ubuntu-xenial-console-armhf-2015-11-13.tar.xz
 +
de1ca6da053680fa3d4ab337e7b5342c  ubuntu-xenial-console-armhf-2015-11-13.tar.xz
  
Get prebuilt image:
+
Unpack image:
 +
tar xf ubuntu-xenial-console-armhf-2015-11-13.tar.xz
 +
cd ubuntu-xenial-console-armhf-2015-11-13
  
wget http://rcn-ee.net/deb/rootfs/natty/ubuntu-11.04-r6-minimal-armel.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/natty/ubuntu-11.04-r6-minimal-armel.tar.xz
 
  
Verify Image with:
+
== Flasher ==
md5sum ubuntu-11.04-r6-minimal-armel.tar.xz
 
a4fdcaf02afb27e5acf6a6d4352927ef  ubuntu-11.04-r6-minimal-armel.tar.xz
 
  
Unpack Image:
+
=== eMMC: BeagleBone Black/Green ===
tar xJf ubuntu-11.04-r6-minimal-armel.tar.xz
 
cd ubuntu-11.04-r6-minimal-armel
 
  
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 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.
  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-v3.sh
  
Are you sure? I Don't see [/dev/idontknow], here is what I do see...
+
This 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/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...
+
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.
  
Install Image:
+
User: ubuntu
 +
pass: temppwd
  
Quick Install script for Beagle Bx, Cx, xM A/B/C
+
Image Updated:
sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle
+
*2015-11-13
 +
** BeagleBone Black/Green: v4.1.12-ti-r29 kernel
 +
*2015-10-09
 +
** BeagleBone Black/Green: v4.1.10-ti-r21 kernel
 +
*2015-09-11
 +
** BeagleBone Black/Green: v4.1.6-ti-r15 kernel
  
Quick Install script for BeagleBone A2/A3
+
Get prebuilt image:
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot bone
+
wget https://rcn-ee.com/rootfs/2015-11-13/flasher/BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
 +
  wget https://rcn-ee.com/rootfs/2015-11-13/flasher/BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
  
Quick Install script for Panda
+
Verify Image with:
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot panda
+
  md5sum BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb*
 +
1f33ecbe120668b4d2e554d08d7a5362  BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
 +
fb9f5062f010b6c7dd53630814280cdb  BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
  
*Additional Options
+
Linux: (bmaptool 3.2)
** --rootfs <ext4 default>
+
sudo bmaptool copy --bmap BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap \
** --swap_file <swap file size in MB's>
+
BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz /dev/sdX
** --addon pico <ti pico projector>
 
** --addon ulcd <CircuitCo 7 inch lcd>
 
** --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.
+
Linux: (dd)
 +
unxz BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
 +
sudo dd if=./BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img of=/dev/sdX
  
For a full gui install run this on your beagle (make sure network is setup):
+
=== eMMC: BeagleBoard-X15 ===
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 xfce4 gdm xubuntu-gdm-theme xubuntu-artwork xserver-xorg-video-omap3 network-manager
 
  
Advanced: Build 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.
  
Built with a fork of project-rootstock (ARM native mode, run directly on beagleboard), using a script from omap-image-builder:
+
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
  
git clone git://github.com/RobertCNelson/omap-image-builder.git
+
This script will only take about 5-6 Minutes after power on.
cd omap-image-builder
 
git checkout v2011.11 -b v2011.11
 
./build_image.sh
 
  
= Method 2: Use the NetInstall method=
+
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.
  
You will need a 1GB/2GB SD card or greater.
+
User: ubuntu
Standard System : ~700MB
+
pass: temppwd
  
== Ubuntu 11.10 (Oneiric) ==
+
Image Updated:
 +
*2015-11-13
 +
** BeagleBoard-X15: v4.1.12-ti-r29 kernel
 +
*2015-10-09
 +
** BeagleBoard-X15: v4.1.10-ti-r21 kernel
 +
*2015-09-11
 +
** BeagleBoard-X15: v4.1.6-ti-r15 kernel
  
  git clone git://github.com/RobertCNelson/netinstall.git
+
Get prebuilt image:
  cd netinstall
+
  wget https://rcn-ee.com/rootfs/2015-11-13/flasher/bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
 +
  wget https://rcn-ee.com/rootfs/2015-11-13/flasher/bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
  
Install script for Beagle Bx
+
Verify Image with:
  sudo ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_bx --distro oneiric
+
  md5sum bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb*
 +
64a994770fa9e92b9076aef3dabd4011  bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
 +
45608d54cf3d5b74f84a30119009f0ae  bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
  
Install script for Beagle Cx, xM A/B/C
+
Linux: (bmaptool 3.2)
  sudo ./mk_mmc.sh --mmc /dev/sdX --uboot beagle --distro oneiric
+
  sudo bmaptool copy --bmap bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap \
 +
bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz /dev/sdX
  
Install script for Panda
+
Linux: (dd)
  sudo ./mk_mmc.sh --mmc /dev/sdX --uboot panda --distro oneiric
+
unxz bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
 +
  sudo dd if=./bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img of=/dev/sdX
  
*Options:
+
== raw microSD img ==
**--uboot : beagle_bx, beagle, panda
 
**--distro : maverick, oneiric
 
**--firmware : installs firmware
 
**--serial-mode : debian-installer uses Serial Port
 
**--addon ulcd : (ulcd from: http://search.digikey.com/scripts/DkSearch/dksus.dll?vendor=0&keywords=ULCD7-ND)
 
  
Place SD card into Beagle and boot:
+
=== BeagleBone White/Black/Green ===
  
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)
 
eth0: USB net <- (usually the smsc95xx adapter on the beagle and panda)
 
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: Manual Install (no automatic scripts)=
+
Image Updated:
 +
*2015-11-13
 +
** BeagleBone White/Black/Green: v4.1.12-ti-r29 kernel
 +
*2015-10-09
 +
** BeagleBone White/Black/Green: v4.1.10-ti-r21 kernel
 +
*2015-09-11
 +
** BeagleBone White/Black/Green: v4.1.6-ti-r15 kernel
  
For this section, you can use the files from above:
+
Get prebuilt image:
  Demo Images: http://elinux.org/BeagleBoardUbuntu#Demo_Image
+
  wget https://rcn-ee.com/rootfs/2015-11-13/microsd/bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
  Rootstock: http://elinux.org/BeagleBoardUbuntu#Build_an_Ubuntu_root_file_system_with_RootStock
+
  wget https://rcn-ee.com/rootfs/2015-11-13/microsd/bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
  
== Partition SD Card ==
+
Verify Image with:
You will need a 1GB SD card or greater.
+
md5sum bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb*
  Standard Console System : ~286MB
+
  bbb1a4eb8d99de70629afb837972d28f  bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
  + Desktop environment (lxde,gdm) : ~479MB
+
  ea014cdd50e6043ef9e71ca314e747b9  bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
  
Starting with an empty SD card and using gparted, create:
+
Linux: (bmaptool 3.2)
  50 MiB Primary Partition, fat16/fat32
+
  sudo bmaptool copy --bmap bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap \
  Rest as ext2/ext3/ext4/btrfs
+
  bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz /dev/sdX
  
Note: The boot partition can be hard to make bootable at times, here's a quick command line:
+
Linux: (dd)
 +
unxz bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
 +
sudo dd if=./bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img of=/dev/sdX
  
First blank the MMC card's partition table with parted: (/dev/sdX as an example)
+
=== OMAP5432 uEVM ===
sudo parted -s /dev/sdX mklabel msdos
 
  
Then create the new boot partition:
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on windows: https://wiki.ubuntu.com/Win32DiskImager
sudo fdisk /dev/sdX << MMC_END
 
n
 
p
 
1
 
1
 
+64M
 
t
 
e
 
p
 
w
 
MMC_END
 
  
Notes:
+
User: ubuntu
GNU Fdisk doesn't and won't work...
+
pass: temppwd
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
+
Auto partition resize:
  sudo parted --script /dev/sdX set 1 boot on
+
  cd /opt/scripts/tools
 +
git pull
 +
./grow_partition.sh
 +
sudo reboot
  
And format it as vfat:
+
Image Updated:
sudo mkfs.vfat -F 16 /dev/sdX1
+
*2015-11-13
 +
** OMAP5432 uEVM: v4.1.12-ti-r29 kernel
 +
*2015-10-09
 +
** OMAP5432 uEVM: v4.1.10-ti-r21 kernel
 +
*2015-09-11
 +
** OMAP5432 uEVM: v4.1.6-ti-r15 kernel
  
The rootfs partition, doesn't need any special options, so just use fdisk, gparted, etc to create and format your rootfs partition..
+
Get prebuilt image:
 +
wget https://rcn-ee.com/rootfs/2015-11-13/microsd/omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
 +
wget https://rcn-ee.com/rootfs/2015-11-13/microsd/omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
  
Gparted Example: http://nishanthmenon.blogspot.com/2008/08/how-to-boot-beagle.html
+
Verify Image with:
 +
md5sum omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb*
 +
de9d84a19ed3bb29a8aa7bc2e51661ad  omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
 +
7916a044a7ce4f9f5bd92276b5d21175  omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
  
For Reference:
+
Linux: (bmaptool 3.2)
Disk /dev/sdd: 2038 MB, 2038431744 bytes
+
  sudo bmaptool copy --bmap omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap \
255 heads, 63 sectors/track, 247 cylinders
+
  omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz /dev/sdX
Units = cylinders of 16065 * 512 = 8225280 bytes
 
Disk identifier: 0x0008e471
 
 
    Device Boot      Start        End      Blocks  Id System
 
  /dev/sdd1              1          6      48163+  6  FAT16
 
/dev/sdd2              7        247    1935832+  83  Linux
 
  
== Boot Partition ==
+
Linux: (dd)
 +
unxz omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
 +
sudo dd if=./omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img of=/dev/sdX
  
Requirements:
+
=== BeagleBoard-X15 ===
  
sudo apt-get install uboot-mkimage
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on windows: https://wiki.ubuntu.com/Win32DiskImager
Mount the fatfs partition of your SD card.
 
  
Mount such as: (/dev/sdX1 is the fat Boot Partition)
+
User: ubuntu
mkdir -p ./tmp
+
pass: temppwd
sudo mount /dev/sdX1 ./tmp
 
  
=== MLO and U-Boot ===
+
Auto partition resize:
 +
cd /opt/scripts/tools
 +
git pull
 +
./grow_partition.sh
 +
sudo reboot
  
Download and copy MLO and U-Boot from here:  
+
Image Updated:
http://www.angstrom-distribution.org/demo/beagleboard/
+
*2015-11-13
 +
** BeagleBoard-X15: v4.1.12-ti-r29 kernel
 +
*2015-10-09
 +
** BeagleBoard-X15: v4.1.10-ti-r21 kernel
 +
*2015-09-11
 +
** BeagleBoard-X15: v4.1.6-ti-r15 kernel
  
  First copy "MLO-beagleboard-1.44+rX+gitX-rX" as MLO to the Boot Partition
+
Get prebuilt image:
  Then copy "u-boot-beagleboard-20XX.XX+r62+gitX-rX.bin" as u-boot.bin to the Boot Partition
+
  wget https://rcn-ee.com/rootfs/2015-11-13/microsd/bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
 +
  wget https://rcn-ee.com/rootfs/2015-11-13/microsd/bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
  
=== U-Boot uImage and uInitrd ===
+
Verify Image with:
 +
md5sum bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb*
 +
43ebc464c665e411eb5fa4f97c6cd19a  bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
 +
ef95702b0590a22cd7d75cce0f61aff8  bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
  
U-Boot needs a compatible kernel image to bootTo do this, we are using mkimage from (uboot-mkimage) to create an image from the vmlinuz kernel file.  
+
Linux: (bmaptool 3.2)
 +
sudo bmaptool copy --bmap bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap \
 +
  bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz /dev/sdX
  
  mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n "Linux" -d ./vmlinuz-* ./uImage
+
Linux: (dd)
Copy "uImage" to the Boot Partition
+
  unxz bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
 +
sudo dd if=./bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img of=/dev/sdX
  
Next create a uInird (this contains a script to fix the rtc on boot, otherwise fsck/reboot/fsck/reboot/repeat happens..)
+
= Method 2: Use the NetInstall method=
  
mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 -n initramfs -d ./initrd.img-* ./uInitrd
+
You will need a 1GB/2GB/4GB/8GB SD card or greater.
  Copy "uInitrd" to the Boot Partition
+
  Standard system : ~700&nbsp;MB
  
=== U-Boot Boot Scripts ===
+
Report Bugs/Issues to: https://github.com/RobertCNelson/netinstall/issues
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'.
+
(anywhere else will be ignored..)
  
fixrtc: (only uInitrd) Resets RTC based on last mount
+
Download the netinstall script:
  buddy=${buddy}: (both) Kernel Zippy1/2 Support
+
  git clone https://github.com/RobertCNelson/netinstall.git
  mpurate=${mpurate}: (recommended core clock)
+
  cd netinstall
  
==== boot.scr -> uEnv.txt ====
+
Currently supported Ubuntu distributions:
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:
+
--distro oneiric (11.10)
 +
--distro precise-armhf (12.04)
 +
--distro quantal (12.10)
 +
--distro raring (13.04)
 +
--distro saucy (13.10)
  
create a new file: uEnv.txt
+
Device: <board> selection:
  bootenv=boot.scr
+
*BeagleBoard Ax/Bx/Cx  - omap3-beagle
  loaduimage=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
+
*BeagleBoard xMA/B/C  - omap3-beagle-xm
  mmcboot=echo Running boot.scr script from mmc ...; source ${loadaddr}
+
*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
  
==== Beagle Bx/Cx & xM ====
+
Installation script for new <board> selection: (slowly migrating all devices to this method)
 +
sudo ./mk_mmc.sh --mmc /dev/sdX --dtb <board> --distro <distro>
  
create a new file: boot.cmd
+
So for the xM: with quantal:
  setenv dvimode 1280x720MR-16@60
+
  sudo ./mk_mmc.sh --mmc /dev/sdX --dtb omap3-beagle-xm --distro quantal
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:
+
*Other Options:
 +
**--firmware : installs firmware
 +
**--serial-mode : debian-installer uses Serial Port
  
mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "Ubuntu" -d ./boot.cmd ./boot.scr
+
Place SD card into BeagleBoard and boot:
Copy "boot.scr" to the Boot Partition
 
For "igepv2" users, rename this to "boot.ini"
 
  
Umount the Boot Partition:
+
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..
  
sudo umount ./tmp
+
See my notes for my testing procedure: https://github.com/RobertCNelson/netinstall/blob/master/test.Ubuntu
  
== RootFS Partition ==
+
Troubleshooting: If booting fails..
Root File System
+
*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
  
Mount your SD card's larger root file system partition (assuming /dev/sdX2) and 'untar' the rootfs into it.
+
NetInstall assumptions:
 +
Assume asll <default>'s... Thanks you preseed.conf!!!
  
mkdir -p ./tmp
+
= Method 3: Manual Install (no automatic scripts)=
sudo mount /dev/sdX2 ./tmp
 
sudo tar xfp armel-rootfs-*.tgz -C ./tmp
 
sudo umount ./tmp
 
  
== Ubuntu Bugs & Tweaks ==
+
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:
  
===Enable Network Access===
+
== Beagle/Beagle xM ==
 +
http://eewiki.net/display/linuxonarm/BeagleBoard
  
Modify /etc/network/interfaces
+
== BeagleBone ==
auto eth0
+
http://eewiki.net/display/linuxonarm/BeagleBone
iface eth0 inet dhcp
 
  
Manual: From the Command line
+
== BeagleBone Black ==
  sudo ifconfig -a
+
  http://eewiki.net/display/linuxonarm/BeagleBone+Black
sudo dhclient ethX (or wlanX/etc..)
 
  
Additional Network Setup Information can be found [[BeagleBoardUbuntuNetwork|HERE]]
+
== Panda/Panda ES ==
 +
http://eewiki.net/display/linuxonarm/PandaBoard
  
 
= Advanced =
 
= Advanced =
Line 415: Line 462:
 
==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=natty  (options are lucid/maverick/natty/oneiric/squeeze/wheezy)
+
Testing:
  wget http://rcn-ee.net/deb/${DIST}/LATEST-omap
+
  ./update_kernel.sh --beta-kernel
wget $(cat ./LATEST-omap | 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-bone69
 +
 
 +
Reboot with your new Kernel Image.
  
 
== Upgrade X-loader and U-boot ==
 
== Upgrade X-loader and U-boot ==
  
Compatible with Bx,C2/3/4
+
*Note: the functionality of the "X-Loader" project has been merged as u-boot spl.
  
Requires MMC card..
+
Compatibility with older Ax, Bx, Cx, and Dx BeagleBoards
  
  git clone git://github.com/RobertCNelson/flash-omap.git
+
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:
  cd flash-omap
+
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 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
+
  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 463: Line 522:
 
  /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:
 
 
 
nand erase 260000 20000
 
reset
 
 
 
===Manual Run===
 
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 ==
 
 
 
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)
 
  https://github.com/RobertCNelson/stable-kernel
 
 
 
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''
 
 
 
=== 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
+
== SGX Drivers ==
./create_sgx_package.sh
 
  
After Successfully running:
+
=== SGX BeagleBone/BeagleBone Black ===
  
:~/temp$ ls
+
Note, these are FBDEV only, no xorg/x11/etc...
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 ===
+
Install sgx modules (3.14.x-ti or 4.1.x kernel):
 +
sudo apt-get install ti-sgx-es8-modules-`uname -r`
 +
sudo depmod -a `uname -r`
 +
sudo update-initramfs -uk `uname -r`
  
tar xf GFX_4_00_00_01_libs.tar.gz  (extracts install-SGX.sh and run-SGX.sh)
+
Build SGX userspace for 3.14.x-ti (must be done on an x86, due to the TI 5.01.01.02 blob extractor)
  ./install-SGX.sh (copies necessary SGX libs and startup script)
+
  git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
  ./run-SGX.sh (force run the new init script, or you can just reboot...)
+
cd ti-linux-kernel-dev/
 +
  git checkout origin/ti-linux-3.14.y -b tmp-sgx
 +
./sgx_create_package.sh
  
On Successful install:
+
Build SGX userspace for 4.1.x (must be done on an x86, due to the TI 5.01.01.02 blob extractor)
  Stopping PVR
+
git clone https://github.com/RobertCNelson/bb-kernel.git
  Starting PVR
+
  cd bb-kernel/
  Starting SGX fixup for ES2.x (or ES3.x) (or ES5.x xM)
+
  git checkout origin/am33x-v4.1 -b tmp-sgx
 +
  ./sgx_create_package.sh
  
Reboot for good measure (Maverick's Alpha-1 needs this....)
+
Copy ./deploy/GFX_5.01.01.02.tar.gz to BeagleBone/BeagleBone Black and install
 +
sudo tar xfv GFX_5.01.01.02.tar.gz -C /
 +
cd /opt/gfxinstall/
 +
sudo ./sgx-install.sh
 
  sudo reboot
 
  sudo reboot
  
=== Beagle: GFX_Linux_SDK.tar.gz ===
+
Verify omaplfb & pvrsrvkm loaded
 
+
  debian@arm:~$ lsmod | grep omaplfb
tar xf GFX_Linux_SDK.tar.gz
+
  omaplfb                12065 0
cd GFX_Linux_SDK
+
  pvrsrvkm              178782 1 omaplfb
tar xf OGLES.tar.gz
 
 
 
=== Test SGX with a DEMO ===
 
 
 
cd OGLES/SDKPackage/Binaries/CommonX11/Demos/EvilSkull
 
./OGLESEvilSkull
 
 
 
=== Trouble Shooting ===
 
 
 
sudo rm /etc/powervr-esrev
 
sudo depmod -a omaplfb
 
  sudo /etc/init.d/pvr restart
 
 
 
== DSP ==
 
 
 
=== gst-dsp ===
 
 
 
Seems to work on all Beagle's, with atleast 2.6.38+ now...
 
 
 
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)
 
  https://github.com/RobertCNelson/stable-kernel
 
 
 
Download the latest version of the "create_dsp_package.sh" script
 
wget https://github.com/RobertCNelson/stable-kernel/raw/master/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..
+
== Xorg Drivers ==
./install-gst-dsp.sh
 
  
Playbin:
+
Script:
  sudo gst-launch playbin2 uri=file://(file)
+
  cd /opt/scripts/tools/
 +
git pull
  
== Xorg omapfb Drivers ==
+
BeagleBoard/PandaBoard:
 +
cd /opt/scripts/tools/graphics/
 +
./ti-omapdrm.sh
  
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.
+
BeagleBone/BeagleBone Black:
 +
cd /opt/scripts/tools/graphics/
 +
./ti-tilcdc.sh
  
cat /var/log/Xorg.0.log | grep FBDEV
+
= Swapfile =
(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..
+
== Using a File for Swap Instead of a Partition ==
  
xvinfo -display :0.0
+
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).
X-Video Extension version 2.2
 
screen #0
 
  no adaptors present
 
  
=== Drivers ===
+
Some images (such as those from Linaro.org) do not come with a swap partition or any swap space allocated.
  
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)
+
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.
  
Lucid:
+
=== Creating a Swapfile ===
sudo apt-get install xserver-xorg-video-omap3
 
  
To verify it was correctly installed, reboot and:
+
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:
  
cat /var/log/Xorg.0.log | grep omapfb
+
sudo mkdir -p /var/cache/swap/  
  (II) LoadModule: "omapfb"
+
  sudo dd if=/dev/zero of=/var/cache/swap/swapfile bs=1M count=1024
(II) Loading /usr/lib/xorg/modules/drivers//omapfb_drv.so
+
  sudo chmod 0600 /var/cache/swap/swapfile
(II) Module omapfb: vendor="X.Org Foundation"
+
  sudo mkswap /var/cache/swap/swapfile
  (II) omapfb: Driver for OMAP framebuffer (omapfb) and external LCD controllers:
+
sudo swapon /var/cache/swap/swapfile
  (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..
+
To tell the OS to load this swapfile on each start up, edit the /etc/fstab file to include the following additional line:
  
xvinfo -display :0.0
+
  /var/cache/swap/swapfile    none    swap    sw    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 ==
+
To verify that the swapfile is accessilble as swap to the OS, run "top" or "htop" at a console.
 
 
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 751: Line 623:
 
  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 759: Line 631:
 
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 771: Line 642:
  
 
=== 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 789: Line 660:
 
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 09:27, 16 November 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.3.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-4.1.y -b tmp
./build_kernel.sh

Ubuntu (14.04.3)

Default username/password:

  • username: ubuntu
  • password: temppwd

Image Updated:

  • 2015-11-13
    • BeagleBoard xM: v4.3.0-armv7-x0 kernel
    • BeagleBone White/Black/Green: v4.1.12-ti-r29 kernel
    • OMAP5432 uEVM: v4.1.12-ti-r29 kernel
    • BeagleBoard-X15: v4.1.12-ti-r29 kernel
  • 2015-10-09
    • BeagleBoard xM: v4.2.3-armv7-x2 kernel
    • BeagleBone White/Black/Green: v4.1.10-ti-r21 kernel
    • OMAP5432 uEVM: v4.1.10-ti-r21 kernel
    • BeagleBoard-X15: v4.1.10-ti-r21 kernel
  • 2015-09-11
    • BeagleBoard xM: v4.2.0-armv7-x1 kernel
    • BeagleBone White/Black/Green: v4.1.6-ti-r15 kernel
    • OMAP5432 uEVM: v4.1.6-ti-r15 kernel
    • BeagleBoard-X15: v4.1.6-ti-r15 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-11-13/elinux/ubuntu-14.04.3-console-armhf-2015-11-13.tar.xz

Verify Image with:

md5sum ubuntu-14.04.3-console-armhf-2015-11-13.tar.xz
4e5c82b71090e27115065113b44c196e  ubuntu-14.04.3-console-armhf-2015-11-13.tar.xz

Unpack Image:

tar xf ubuntu-14.04.3-console-armhf-2015-11-13.tar.xz
cd ubuntu-14.04.3-console-armhf-2015-11-13

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 White/Black/Green - 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.11 -b tmp

Stable:

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

Testing:

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

Ubuntu Testing (xenial)

Image Updated:

  • 2015-11-13
    • BeagleBoard xM: v4.3.0-armv7-x0 kernel
    • BeagleBone White/Black/Green: v4.1.12-ti-r29 kernel
    • OMAP5432 uEVM: v4.1.12-ti-r29 kernel
    • BeagleBoard-X15: v4.1.12-ti-r29 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2015-11-13/elinux/ubuntu-xenial-console-armhf-2015-11-13.tar.xz

Verify Image with:

md5sum ubuntu-xenial-console-armhf-2015-11-13.tar.xz
de1ca6da053680fa3d4ab337e7b5342c  ubuntu-xenial-console-armhf-2015-11-13.tar.xz

Unpack image:

tar xf ubuntu-xenial-console-armhf-2015-11-13.tar.xz
cd ubuntu-xenial-console-armhf-2015-11-13

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

Flasher

eMMC: BeagleBone Black/Green

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-11-13
    • BeagleBone Black/Green: v4.1.12-ti-r29 kernel
  • 2015-10-09
    • BeagleBone Black/Green: v4.1.10-ti-r21 kernel
  • 2015-09-11
    • BeagleBone Black/Green: v4.1.6-ti-r15 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2015-11-13/flasher/BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
wget https://rcn-ee.com/rootfs/2015-11-13/flasher/BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap

Verify Image with:

md5sum BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb*
1f33ecbe120668b4d2e554d08d7a5362  BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
fb9f5062f010b6c7dd53630814280cdb  BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz

Linux: (bmaptool 3.2)

sudo bmaptool copy --bmap BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap \
BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz /dev/sdX

Linux: (dd)

unxz BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
sudo dd if=./BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img of=/dev/sdX

eMMC: 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 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-11-13
    • BeagleBoard-X15: v4.1.12-ti-r29 kernel
  • 2015-10-09
    • BeagleBoard-X15: v4.1.10-ti-r21 kernel
  • 2015-09-11
    • BeagleBoard-X15: v4.1.6-ti-r15 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2015-11-13/flasher/bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
wget https://rcn-ee.com/rootfs/2015-11-13/flasher/bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap

Verify Image with:

md5sum bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb*
64a994770fa9e92b9076aef3dabd4011  bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
45608d54cf3d5b74f84a30119009f0ae  bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz

Linux: (bmaptool 3.2)

sudo bmaptool copy --bmap bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap \
bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz /dev/sdX

Linux: (dd)

unxz bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
sudo dd if=./bbx15-eMMC-flasher-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img of=/dev/sdX

raw microSD img

BeagleBone White/Black/Green

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-11-13
    • BeagleBone White/Black/Green: v4.1.12-ti-r29 kernel
  • 2015-10-09
    • BeagleBone White/Black/Green: v4.1.10-ti-r21 kernel
  • 2015-09-11
    • BeagleBone White/Black/Green: v4.1.6-ti-r15 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2015-11-13/microsd/bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
wget https://rcn-ee.com/rootfs/2015-11-13/microsd/bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap

Verify Image with:

md5sum bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb*
bbb1a4eb8d99de70629afb837972d28f  bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
ea014cdd50e6043ef9e71ca314e747b9  bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz

Linux: (bmaptool 3.2)

sudo bmaptool copy --bmap bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap \
bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz /dev/sdX

Linux: (dd)

unxz bone-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
sudo dd if=./bone-ubuntu-14.04.3-console-armhf-2015-11-13-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-11-13
    • OMAP5432 uEVM: v4.1.12-ti-r29 kernel
  • 2015-10-09
    • OMAP5432 uEVM: v4.1.10-ti-r21 kernel
  • 2015-09-11
    • OMAP5432 uEVM: v4.1.6-ti-r15 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2015-11-13/microsd/omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
wget https://rcn-ee.com/rootfs/2015-11-13/microsd/omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap

Verify Image with:

md5sum omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb*
de9d84a19ed3bb29a8aa7bc2e51661ad  omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
7916a044a7ce4f9f5bd92276b5d21175  omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz

Linux: (bmaptool 3.2)

sudo bmaptool copy --bmap omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap \
omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz /dev/sdX

Linux: (dd)

unxz omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
sudo dd if=./omap5-uevm-ubuntu-14.04.3-console-armhf-2015-11-13-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-11-13
    • BeagleBoard-X15: v4.1.12-ti-r29 kernel
  • 2015-10-09
    • BeagleBoard-X15: v4.1.10-ti-r21 kernel
  • 2015-09-11
    • BeagleBoard-X15: v4.1.6-ti-r15 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2015-11-13/microsd/bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
wget https://rcn-ee.com/rootfs/2015-11-13/microsd/bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap

Verify Image with:

md5sum bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb*
43ebc464c665e411eb5fa4f97c6cd19a  bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap
ef95702b0590a22cd7d75cce0f61aff8  bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz

Linux: (bmaptool 3.2)

sudo bmaptool copy --bmap bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.bmap \
bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz /dev/sdX

Linux: (dd)

unxz bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-2gb.img.xz
sudo dd if=./bbx15-ubuntu-14.04.3-console-armhf-2015-11-13-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

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

Install sgx modules (3.14.x-ti or 4.1.x 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 for 3.14.x-ti (must be done on an x86, due to the TI 5.01.01.02 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

Build SGX userspace for 4.1.x (must be done on an x86, due to the TI 5.01.01.02 blob extractor)

git clone https://github.com/RobertCNelson/bb-kernel.git
cd bb-kernel/
git checkout origin/am33x-v4.1 -b tmp-sgx
./sgx_create_package.sh

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

sudo tar xfv GFX_5.01.01.02.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

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.