Difference between revisions of "BeagleBoardUbuntu"

From eLinux.org
Jump to: navigation, search
(Canonical Pre-Installed Images)
m (Method 1: Download a Complete Pre-Configured Image: 2017-01-23)
(305 intermediate revisions by 14 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 =  
  
X-loader/MLO (1.4.4ss) & U-Boot (2010.03) (Zippy1 & Zippy2 Support)
+
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 53: Line 54:
 
  exec /sbin/getty 115200 ttyO2
 
  exec /sbin/getty 115200 ttyO2
  
= Method 1: Download a Complete Pre-Configured Image from Canonical Ubuntu website =
+
= Method 1: Download a Complete Pre-Configured Image =
  
Support:
+
== Demo Image ==
* ''#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''': BeagleBoard 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.9.x -b tmp
 +
./build_kernel.sh
 +
* '''Advanced Users only''': BeagleBone/BeagleBone Black:  Kernel v4.4.x source, used in these demo images: https://github.com/RobertCNelson/ti-linux-kernel-dev/tree/ti-linux-4.4.y
 +
git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
 +
cd ti-linux-kernel-dev
 +
git checkout origin/ti-linux-4.4.y -b tmp
 +
./build_kernel.sh
  
Just follow: https://wiki.ubuntu.com/ARM/OMAP
+
=== Ubuntu (16.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:
 +
*2017-03-09
 +
** BeagleBoard xM: v4.9.13-armv7-x4 kernel
 +
** All BeagleBone Varients: v4.4.52-ti-r91 kernel
 +
** OMAP5432 uEVM: v4.4.52-ti-r91 kernel
 +
** BeagleBoard-X15: v4.4.52-ti-r91 kernel
 +
*2017-01-23
 +
** BeagleBoard xM: v4.9.5-armv7-x4 kernel
 +
** All BeagleBone Varients: v4.4.43-ti-r84 kernel
 +
** OMAP5432 uEVM: v4.4.43-ti-r84 kernel
 +
** BeagleBoard-X15: v4.4.43-ti-r84 kernel
 +
*2017-01-13
 +
** BeagleBoard xM: v4.9.3-armv7-x4 kernel
 +
** All BeagleBone Varients: v4.4.40-ti-r80 kernel
 +
** OMAP5432 uEVM: v4.4.40-ti-r80 kernel
 +
** BeagleBoard-X15: v4.4.40-ti-r80 kernel
  
=Demo Image=
+
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
  
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..  For example, what are some of the differences? Ubuntu does not support the xM with lucid, with the rcn-ee.net kernel that's possible and done with the lucid image below..
+
Default user: ubuntu pass: temppwd
 
 
If the script in these demo images fail: email "bugs@rcn-ee.com" I need: terminal command, terminal log, distribution name, arch...
 
 
 
== Natty 11.04 ==
 
 
 
Image Updated August 5th, new v3.0 kernel...
 
 
 
Default user: ubuntu pass: temppwd  
 
  
 
Get prebuilt image:
 
Get prebuilt image:
 +
wget https://rcn-ee.com/rootfs/2017-03-09/elinux/ubuntu-16.04.2-console-armhf-2017-03-09.tar.xz
  
wget http://rcn-ee.net/deb/rootfs/natty/ubuntu-11.04-r3-minimal-armel.tar.xz
+
Verify Image with:
mirrors (will take some time to update):
+
  sha256sum ubuntu-16.04.2-console-armhf-2017-03-09.tar.xz
wget http://ynezz.ibawizard.net/beagleboard/natty/ubuntu-11.04-r3-minimal-armel.tar.xz
+
  8d0088c4842d3cbcacb64bafc74851307d43f55f1d10d17e0a9d1afe7a921e84 ubuntu-16.04.2-console-armhf-2017-03-09.tar.xz
 
 
Verify Image with:  
 
  md5sum ubuntu-11.04-r3-minimal-armel.tar.xz
 
  78bcd93acb37d6b63c90f68ff0f62976 ubuntu-11.04-r3-minimal-armel.tar.xz
 
  
 
Unpack Image:
 
Unpack Image:
  tar xJf ubuntu-11.04-r3-minimal-armel.tar.xz
+
  tar xf ubuntu-16.04.2-console-armhf-2017-03-09.tar.xz
  cd ubuntu-11.04-r3-minimal-armel
+
  cd ubuntu-16.04.2-console-armhf-2017-03-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 --mmc /dev/'''idontknow'''
+
  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/sda5 on / type ext4 (rw,errors=remount-ro,commit=0) '''<- x86 Root Partition'''
+
  NAME  MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
  /dev/sda4 on /opt type ext4 (rw,commit=0)
+
sda      8:0    0 465.8G  0 disk
 
+
├─sda1  8:1    0 446.9G  0 part / '''<- 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...
+
  ├─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
  
Look for a line that starts with "/dev/sdXX" in it; generally it will be mounted to the "/media directory" (in Ubuntu).  Double check that the size of the sd-card is correct in order to make sure it is the right one. Carelessly repartitioning a drive (that is ''not'' an SD card) on your own system can completely ruin your computer's setup. ("/dev/sdb1" represents the first partition of the "/dev/sdb" drive).  The correct name to use for your SD card could be "sdb", "sdc", or it could possibly have another final letter.  
+
* 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
 
sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle
 
  
Quick Install script for Panda
+
board options:
sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot panda
+
*BeagleBoard Ax/Bx/Cx/Dx          - omap3-beagle
 +
*BeagleBoard xM                  - omap3-beagle-xm
 +
*All BeagleBone Varients          - beaglebone
 +
*OMAP5432 uEVM                    - omap5-uevm
 +
*BeagleBoard-X15                  - am57xx-beagle-x15
  
*Additional Options
+
So for the BeagleBoard xM:
** --rootfs <ext4 default>
+
  sudo ./setup_sdcard.sh --mmc /dev/sdX --dtb omap3-beagle-xm
** --swap_file <swap file size in MB's>
 
** --addon <pico>
 
 
 
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 xfce4 gdm xubuntu-gdm-theme xubuntu-artwork xserver-xorg-video-omap3 network-manager
 
  
 
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 v2017.03 -b tmp
  
Built with rootstock trunk (ARM native mode, run directly on beagleboard):
+
Stable:
sudo ./rootstock --fqdn omap --imagesize 2G --dist natty --serial ttyO2 \
 
--login ubuntu --password temppwd \
 
--seed btrfs-tools,devmem2,i2c-tools,nano,pastebinit,uboot-envtools,uboot-mkimage,usbutils,wget,wireless-tools,wpasupplicant \
 
--script fixup.sh --components "main universe multiverse" \
 
--kernel-image http://rcn-ee.net/deb/natty/v3.0.0-x2/linux-image-3.0.0-x2_1.0natty_armel.deb
 
  
== Oneiric 11.10 Alpha 3==
+
./RootStock-NG.sh -c rcn-ee_console_ubuntu_xenial_armhf
  
Image Updated August 5th, new v3.0 kernel...
+
== Flasher ==
  
Note: This is ubuntu's Alpha 3 so...
+
=== eMMC: All BeagleBone Varients with eMMC ===
  
Default user: ubuntu pass: temppwd
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on Windows/Mac/Linux: https://etcher.io  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.
  
Get prebuilt image:
+
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
  
wget http://rcn-ee.net/deb/rootfs/oneiric/ubuntu-oneiric-alpha3-minimal-armel.tar.xz
+
This script will only take about 5-6 Minutes after power on.
mirrors (will take some time to update):
 
wget http://ynezz.ibawizard.net/beagleboard/oneiric/ubuntu-oneiric-alpha3-minimal-armel.tar.xz
 
  
Verify Image with:  
+
Notes:
md5sum ubuntu-oneiric-alpha3-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.
5003ced46f5dab190b0f3173fa847da2 ubuntu-oneiric-alpha3-minimal-armel.tar.xz
+
* If the 4 LED's blink a constant pattern, the eMMC write has failed. First REMOVE ALL capes, then retry again.
  
Unpack Image:
+
User: ubuntu
tar xJf ubuntu-oneiric-alpha3-minimal-armel.tar.xz
+
pass: temppwd
cd ubuntu-oneiric-alpha3-minimal-armel
 
  
Install Image:
+
Image Updated:
 +
*2017-03-09
 +
** All BeagleBone Varients with eMMC: v4.4.52-ti-r91 kernel
 +
*2017-01-23
 +
** All BeagleBone Varients with eMMC: v4.4.43-ti-r84 kernel
 +
*2017-01-13
 +
** All BeagleBone Varients with eMMC: v4.4.40-ti-r80 kernel
  
Quick Install script for Beagle Bx
+
Get prebuilt image:
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle_bx
+
  wget https://rcn-ee.com/rootfs/2017-03-09/flasher/BBB-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz
  
Quick Install script for Beagle Cx, xM A/B/C
+
Verify Image with:
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle
+
  sha256sum BBB-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb*
 +
5774f6d9aca247dbf46505cde6a439aae56aeb9cd4fa1ac3f46ce2a299851b89  BBB-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz
  
Quick Install script for Panda
+
Windows/Mac/Linux gui
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot panda
+
  http://etcher.io
  
*Additional Options
+
Linux: (dd)
** --rootfs <ext4 default>
+
xzcat BBB-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz | sudo dd of=/dev/sdX
** --swap_file <swap file size in MB's>
 
** --addon <pico>
 
  
You should now be able to unmount the SD card from you PC, insert into your BeagleBoard, reboot and have Ubuntu Maverick loaded.
+
=== eMMC: BeagleBoard-X15 ===
  
For a full gui install run this on your beagle (make sure network is setup):
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on Windows/Mac/Linux: https://etcher.io  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 ONSimply remove power, remove the microSD card and Ubuntu will now boot directly from eMMC.
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:
+
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
  
fixup.sh: http://rcn-ee.homeip.net:81/dl/updates/omap-image-builder/tools/fixup.sh
+
This script will only take about 5-6 Minutes after power on.
  
Built with rootstock trunk (ARM native mode, run directly on beagleboard):
+
Notes:
sudo ./rootstock --fqdn omap --imagesize 2G --dist oneiric --serial ttyO2 \
+
* 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.
--login ubuntu --password temppwd \
+
* If the 4 LED's blink a constant pattern, the eMMC write has failed. First REMOVE ALL capes, then retry again.
--seed btrfs-tools,devmem2,i2c-tools,nano,pastebinit,uboot-envtools,uboot-mkimage,usbutils,wget,wireless-tools,wpasupplicant \
 
--script fixup.sh --components "main universe multiverse" \
 
--kernel-image http://rcn-ee.net/deb/oneiric/v3.0.0-x2/linux-image-3.0.0-x2_1.0oneiric_armel.deb
 
  
= NetInstall Method =
+
User: ubuntu
 +
pass: temppwd
  
You will need a 1GB/2GB SD card or greater.
+
Image Updated:
Standard System : ~700MB
+
*2017-03-09
 +
** BeagleBoard-X15: v4.4.52-ti-r91 kernel
 +
*2017-01-23
 +
** BeagleBoard-X15: v4.4.43-ti-r84 kernel
 +
*2017-01-13
 +
** BeagleBoard-X15: v4.4.40-ti-r80 kernel
  
== Ubuntu 11.04 (Natty) ==
+
Get prebuilt image:
 +
wget https://rcn-ee.com/rootfs/2017-03-09/flasher/bbx15-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz
  
  git clone git://github.com/RobertCNelson/netinstall.git
+
Verify Image with:
  cd netinstall
+
  sha256sum bbx15-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb*
 +
  40f705e93a73dcf44ad4dfd36a806bcbe682ef1303e7a4326ef5947462382582  bbx15-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz
  
Install script for Beagle Bx
+
Windows/Mac/Linux gui
  ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_bx --distro natty
+
  http://etcher.io
  
Install script for Beagle Cx, xM A/B/C
+
Linux: (dd)
  ./mk_mmc.sh --mmc /dev/sdX --uboot beagle --distro natty
+
  xzcat bbx15-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz | sudo dd of=/dev/sdX
  
Install script for Panda
+
== raw microSD img ==
./mk_mmc.sh --mmc /dev/sdX --uboot panda --distro natty
 
  
*Options:
+
=== BeagleBoard xM ===
**--uboot : beagle_bx, beagle, panda
 
**--distro : maverick
 
**--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.
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on Windows/Mac/Linux: https://etcher.io
 
NetInstall boot Settings:
 
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:
+
User: ubuntu
 +
pass: temppwd
  
Configure the network:
+
Auto partition resize:
  usb0: USB net <- (usually the OTG port, but could also be the smsc95xx adapter on the beagle and panda)
+
  cd /opt/scripts/tools
  usb1: USB net <- (usually the smsc95xx adapter on the beagle and panda, when usb0 exist)
+
  git pull
  eth0: Ethernet <- Your usb-ethernet device (or the smsc95xx adapter with 2.6.39+)
+
  ./grow_partition.sh
  wlan0: Wifi <- Your usb-wifi device..
+
  sudo reboot
  
Troubshooting: If boot fails..
+
Image Updated:
*Hold the user button down to force booting from MMC
+
*2017-03-09
*Upgrade X-loader and U-boot [http://elinux.org/BeagleBoardUbuntu#Upgrade_X-loader_and_U-boot Upgrade X-loader and U-Boot]
+
** BeagleBoard xM: v4.9.13-armv7-x4 kernel
*Clear U-boot's Environment Variables in nand:
+
*2017-01-23
nand erase 260000 20000
+
** BeagleBoard xM: v4.9.5-armv7-x4 kernel
 +
*2017-01-13
 +
** BeagleBoard xM: v4.9.3-armv7-x4 kernel
  
NetInstall assumptions:
+
Get prebuilt image:
  Continue with out Kernel Modules <yes>
+
  wget https://rcn-ee.com/rootfs/2017-03-09/microsd/bbxm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz
Partition <Guided - use the largest continuous free space>
 
  
= Build an Ubuntu root file system with RootStock=
+
Verify Image with:
 +
sha256sum bbxm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb*
 +
cc6c202610430af966db750161f0d57303162def4d169dc4e9c8dbe9d8f88e28  bbxm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz
  
== Install RootStock ==
+
Windows/Mac/Linux gui
 +
http://etcher.io
  
This is based off Ubuntu's RootStock Project; [https://launchpad.net/project-rootstock RootStock] script.
+
Linux: (dd)
 +
xzcat bbxm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz | sudo dd of=/dev/sdX
  
Maverick (10.10)
+
=== All BeagleBone Varients ===
sudo apt-get install rootstock
 
  
Lucid (10.04) (use rootstock trunk)
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on Windows/Mac/Linux: https://etcher.io
sudo apt-get install rootstock (to install rootstock's dependices)
 
bzr branch lp:project-rootstock
 
cd project-rootstock
 
  
== RootStock ==
+
User: ubuntu
 +
pass: temppwd
  
=== RootStock: Useful seed Packages ===
+
Auto partition resize:
 +
cd /opt/scripts/tools
 +
git pull
 +
./grow_partition.sh
 +
sudo reboot
  
Useful Packages:
+
Image Updated:
linux-firmware,wireless-tools :wifi adapters..
+
*2017-03-09
ntpdate :sync real time clock from network
+
** All BeagleBone Varients: v4.4.52-ti-r91 kernel
 +
*2017-01-23
 +
** All BeagleBone Varients: v4.4.43-ti-r84 kernel
 +
*2017-01-13
 +
** All BeagleBone Varients: v4.4.40-ti-r80 kernel
  
GUI's (broken bug: FIXME)
+
Get prebuilt image:
  xfce4: xfce4,gdm,xubuntu-gdm-theme,xubuntu-artwork
+
  wget https://rcn-ee.com/rootfs/2017-03-09/microsd/bone-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz
  
=== RootStock: Running ===
+
Verify Image with:
 +
sha256sum bone-ubuntu-16.04.2-console-armhf-2017-03-09-2gb*
 +
fe3d2521b8ebaeca79ac5f5885a58ce3e4d93b7cc5adf407870017deae74c813  bone-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz
  
Rootstock Command line:
+
Windows/Mac/Linux gui
  sudo ./rootstock --fqdn <hostname> --login <rootuser> --password <rootuserpasswd> --imagesize <qemu image size> \
+
  http://etcher.io
--seed <packages> --dist <lucid/maverick> --serial <ttySx>  --kernel-image <http>
 
  
Basic Natty (11.04) Beagleboard minimal image:
+
Linux: (dd)
  sudo ./rootstock --fqdn omap --login ubuntu --password temppwd --imagesize 2G \
+
  xzcat bone-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz | sudo dd of=/dev/sdX
--seed wget,nano,linux-firmware,wireless-tools,usbutils --dist natty --serial ttyO2 \
 
--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:
+
=== OMAP5432 uEVM ===
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
 
  
= Manually Setup SD Card =
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on Windows/Mac/Linux: https://etcher.io
  
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
+
*2017-03-09
Rest as ext2/ext3/ext4/btrfs
+
** OMAP5432 uEVM: v4.4.52-ti-r91 kernel
 +
*2017-01-23
 +
** OMAP5432 uEVM: v4.4.43-ti-r84 kernel
 +
*2017-01-13
 +
** OMAP5432 uEVM: v4.4.40-ti-r80 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/2017-03-09/microsd/omap5-uevm-ubuntu-16.04.2-console-armhf-2017-03-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
+
  sha256sum omap5-uevm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb*
 +
65a48656354929eb95f1323d8e57f333b15dfccafb0bc56fc5d400afb029f763  omap5-uevm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz
  
Then create the new boot partition:
+
Windows/Mac/Linux gui
  sudo fdisk /dev/sdX << MMC_END
+
  http://etcher.io
n
 
p
 
1
 
1
 
+64M
 
t
 
e
 
p
 
w
 
MMC_END
 
  
Notes:
+
Linux: (dd)
  GNU Fdisk doesn't and won't work...
+
  xzcat omap5-uevm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz | sudo dd of=/dev/sdX
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
+
=== BeagleBoard-X15 ===
sudo parted --script /dev/sdX set 1 boot on
 
  
And format it as vfat:
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on Windows/Mac/Linux: https://etcher.io
sudo mkfs.vfat -F 16 /dev/sdX1
 
  
The rootfs partition, doesn't need any special options, so just use fdisk, gparted, etc to create and format your rootfs partition..
+
User: ubuntu
 +
pass: temppwd
  
Gparted Example: http://nishanthmenon.blogspot.com/2008/08/how-to-boot-beagle.html
+
Auto partition resize:
 +
cd /opt/scripts/tools
 +
git pull
 +
./grow_partition.sh
 +
sudo reboot
  
For Reference:
+
Image Updated:
Disk /dev/sdd: 2038 MB, 2038431744 bytes
+
*2017-03-09
255 heads, 63 sectors/track, 247 cylinders
+
** BeagleBoard-X15: v4.4.52-ti-r91 kernel
Units = cylinders of 16065 * 512 = 8225280 bytes
+
*2017-01-23
Disk identifier: 0x0008e471
+
** BeagleBoard-X15: v4.4.43-ti-r84 kernel
+
*2017-01-13
    Device Boot      Start        End      Blocks  Id  System
+
** BeagleBoard-X15: v4.4.40-ti-r80 kernel
/dev/sdd1              1          6      48163+  6  FAT16
 
/dev/sdd2              7        247    1935832+  83  Linux
 
  
== Boot Partition ==
+
Get prebuilt image:
 +
wget https://rcn-ee.com/rootfs/2017-03-09/microsd/bbx15-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz
  
Requirements:
+
Verify Image with:
 +
sha256sum bbx15-ubuntu-16.04.2-console-armhf-2017-03-09-2gb*
 +
5ac531de42eee98a118ce496ac0728357300cdb9d7b85038a6ff3c7c5d07af80  bbx15-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz
  
sudo apt-get install uboot-mkimage
+
Windows/Mac/Linux gui
  Mount the fatfs partition of your SD card.
+
  http://etcher.io
  
Mount such as: (/dev/sdX1 is the fat Boot Partition)
+
Linux: (dd)
  mkdir -p ./tmp
+
  xzcat bbx15-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz | sudo dd of=/dev/sdX
sudo mount /dev/sdX1 ./tmp
 
  
=== MLO and U-Boot ===
+
= Method 2: Use the NetInstall method=
  
Download and copy MLO and U-Boot from here:
+
You will need a 1GB/2GB/4GB/8GB SD card or greater.
  http://www.angstrom-distribution.org/demo/beagleboard/
+
  Standard system : ~700&nbsp;MB
  
First copy "MLO-beagleboard-1.44+rX+gitX-rX" as MLO to the Boot Partition
+
Report Bugs/Issues to: https://github.com/RobertCNelson/netinstall/issues
Then copy "u-boot-beagleboard-20XX.XX+r62+gitX-rX.bin" as u-boot.bin to the Boot Partition
+
(anywhere else will be ignored..)
  
=== U-Boot uImage and uInitrd ===
+
Download the netinstall script:
 +
git clone https://github.com/RobertCNelson/netinstall.git
 +
cd netinstall
  
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.  
+
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)
  
  mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n "Linux" -d ./vmlinuz-* ./uImage
+
Device: <board> selection:
  Copy "uImage" to the Boot Partition
+
*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
  
Next create a uInird (this contains a script to fix the rtc on boot, otherwise fsck/reboot/fsck/reboot/repeat happens..)
+
Installation script for new <board> selection: (slowly migrating all devices to this method)
 +
sudo ./mk_mmc.sh --mmc /dev/sdX --dtb <board> --distro <distro>
  
  mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 -n initramfs -d ./initrd.img-* ./uInitrd
+
So for the xM: with quantal:
Copy "uInitrd" to the Boot Partition
+
  sudo ./mk_mmc.sh --mmc /dev/sdX --dtb omap3-beagle-xm --distro quantal
  
=== U-Boot Boot Scripts ===
+
*Other Options:
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'.
+
**--firmware : installs firmware
 +
**--serial-mode : debian-installer uses Serial Port
  
fixrtc: (only uInitrd) Resets RTC based on last mount
+
Place SD card into BeagleBoard and boot:
buddy=${buddy}: (both) Kernel Zippy1/2 Support
 
mpurate=${mpurate}: (recommended core clock)
 
  
==== boot.scr -> uEnv.txt ====
+
Configure the network:
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:
+
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..  
  
create a new file: uEnv.txt
+
See my notes for my testing procedure: https://github.com/RobertCNelson/netinstall/blob/master/test.Ubuntu
bootenv=boot.scr
 
loaduimage=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
 
mmcboot=echo Running boot.scr script from mmc ...; source ${loadaddr}
 
  
==== Beagle Bx/Cx & xM ====
+
Troubleshooting: If booting fails..
 +
*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
  
create a new file: boot.cmd
+
NetInstall assumptions:
setenv dvimode 1280x720MR-16@60
+
  Assume asll <default>'s... Thanks you preseed.conf!!!
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:
 
 
 
mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "Ubuntu" -d ./boot.cmd ./boot.scr
 
Copy "boot.scr" to the Boot Partition
 
For "igepv2" users, rename this to "boot.ini"
 
 
 
Umount the Boot Partition:
 
 
 
sudo umount ./tmp
 
 
 
== RootFS Partition ==
 
Root File System
 
 
 
Mount your SD card's larger root file system partition (assuming /dev/sdX2) and 'untar' the rootfs into it.
 
  
mkdir -p ./tmp
+
= 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 449: Line 450:
 
==Install Latest Kernel Image==
 
==Install Latest Kernel Image==
  
===Script File===
+
General apt syntax for searching and installing a specific kernel:
 
+
  sudo apt-get update
Latest Stable is : https://github.com/RobertCNelson/stable-kernel
+
  sudo apt-cache search linux-image | grep <branch>
 
+
  sudo apt-get install linux-image-<specific version>
  export DIST=natty  (options are lucid/maverick/natty/oneiric/squeeze/wheezy)
+
sudo reboot
  wget http://rcn-ee.net/deb/${DIST}/LATEST
 
wget $(cat ./LATEST | 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
+
Latest kernel script
 +
cd /opt/scripts/tools/
 +
git pull
 +
sudo ./update_kernel.sh <OPTIONS>
  
Requires MMC card..
+
== 3.8.x ==
 +
This is the first beagleboard.org long term kernel tree with capemanager support, it's been the default install for Debian Wheezy
 +
beagleboard.org patchset: https://github.com/beagleboard/linux/tree/3.8
  
  git clone git://github.com/RobertCNelson/flash-omap.git
+
  3.8.x BeagleBone/BeagleBone Black FULL Cape Support
  cd flash-omap
+
  --bone-channel --stable
./mk_mmc.sh --mmc /dev/sdX (i.e. use /dev/sdc - the entire device, not a partition)
 
  
  1: Place MMC card in Beagle
+
  3.8.x BeagleBone/BeagleBone Black FULL Cape Support + Xenomai
2: Push/Hold User Button Down
+
  --bone-xenomai-channel --stable
  3: Apply Power
 
4: After U-boot loads, Let Off User Button
 
5: Wait for Flashing to end
 
6: Power down, remove/edit boot.scr from MMC card
 
  
Example 4G card:
+
== 4.4.x-ti ==
 +
This is slated to replace the v3.8.x tree in Debian Jessie, cape manager support is enabled.
 +
beagleboard.org patchset: https://github.com/beagleboard/linux/tree/4.4
  
  sudo fdisk -l
+
  4.4.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15
 +
--ti-channel --lts-4_4
  
  Disk '''/dev/sde''': 3957 MB, 3957325824 bytes
+
  4.4.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15 + RT
  255 heads, 63 sectors/track, 481 cylinders
+
  --ti-rt-channel --lts-4_4
Units = cylinders of 16065 * 512 = 8225280 bytes
 
Sector size (logical/physical): 512 bytes / 512 bytes
 
I/O size (minimum/optimal): 512 bytes / 512 bytes
 
Disk identifier: 0x00080e99
 
 
    Device Boot      Start        End      Blocks  Id  System
 
'''/dev/sde'''1  *          1          9      72261    e  W95 FAT16 (LBA)
 
  
  ./mk_mmc.sh --mmc /dev/sde
+
  4.4.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15 + RT
 +
-ti-xenomai-channel --lts-4_4
  
Worst case, depending on what's actually in NAND, you might still have to stop and do this:
+
== Mainline (lts) ==
  
  nand erase 260000 20000
+
  4.4.x BeagleBone/BeagleBone Black + SGX
  reset
+
  --bone-kernel --lts-4_4
  
===Manual Run===
+
  4.4.x BeagleBone/BeagleBone Black + RT + SGX
  mmc init
+
  --bone-rt-kernel --lts-4_4
  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 ==
+
Reboot with your new Kernel Image.
  
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)
+
== Xorg Drivers ==
  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''
+
Script:
 +
cd /opt/scripts/tools/
 +
git pull
  
=== SDK unPackage Script ===
+
BeagleBoard/PandaBoard:
 +
cd /opt/scripts/tools/graphics/
 +
./ti-omapdrm.sh
  
Download the latest version of the "create_sgx_package.sh" script
+
BeagleBone/BeagleBone Black:
  2.6.37
+
  cd /opt/scripts/tools/graphics/
wget https://github.com/RobertCNelson/stable-kernel/raw/master/create_sgx_package_2.6.37.sh
+
  ./ti-tilcdc.sh
  2.6.38+
 
wget https://github.com/RobertCNelson/stable-kernel/raw/master/create_sgx_package.sh
 
  
Make script executable
+
== SGX Drivers ==
chmod a+x ./create_sgx_package.sh
 
  
Run script
+
=== SGX BeagleBone/BeagleBone Black ===
./create_sgx_package.sh
 
  
After Successfully running:
+
Note, these are FBDEV only, no xorg/x11/etc...
  
:~/temp$ ls
+
Install the "4.1.x" lts/bone kernel:
create_sgx_package.sh
+
http://elinux.org/BeagleBoardUbuntu#Mainline_.28lts.29
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 ===
+
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
  
tar xf GFX_4_00_00_01_libs.tar.gz  (extracts install-SGX.sh and run-SGX.sh)
+
Copy ./deploy/GFX_5.01.01.02.tar.gz to BeagleBone/BeagleBone Black and install
./install-SGX.sh (copies necessary SGX libs and startup script)
+
  sudo tar xfv GFX_5.01.01.02.tar.gz -C /
  ./run-SGX.sh (force run the new init script, or you can just reboot...)
+
  cd /opt/gfxinstall/
 
+
  sudo ./sgx-install.sh
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
  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:
+
== Xorg Drivers ==
./create_dsp_package.sh
 
  
Copy DSP_Install_libs.tar.gz to beagle
+
Script:
 +
cd /opt/scripts/tools/
 +
git pull
  
Setup network...
+
BeagleBoard/PandaBoard:
 +
cd /opt/scripts/tools/graphics/
 +
./ti-omapdrm.sh
  
Extract:
+
BeagleBone/BeagleBone Black:
  tar xf DSP_Install_libs.tar.gz
+
  cd /opt/scripts/tools/graphics/
 +
./ti-tilcdc.sh
  
Install
+
= Swapfile =
./install-DSP.sh
 
  
Build gst-dsp stuff..
+
== Using a File for Swap Instead of a Partition ==
./install-gst-dsp.sh
 
  
Playbin:
+
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).
sudo gst-launch playbin2 uri=file://(file)
 
  
== Xorg omapfb Drivers ==
+
Some images (such as those from Linaro.org) do not come with a swap partition or any swap space allocated.
  
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.
+
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.
  
cat /var/log/Xorg.0.log | grep FBDEV
+
=== Creating a 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..
+
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:
  
xvinfo -display :0.0
+
sudo mkdir -p /var/cache/swap/ 
  X-Video Extension version 2.2
+
sudo dd if=/dev/zero of=/var/cache/swap/swapfile bs=1M count=1024
  screen #0
+
  sudo chmod 0600 /var/cache/swap/swapfile
  no adaptors present
+
  sudo mkswap /var/cache/swap/swapfile
 +
sudo swapon /var/cache/swap/swapfile
  
=== Drivers ===
+
To tell the OS to load this swapfile on each start up, edit the /etc/fstab file to include the following additional line:
  
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)
+
/var/cache/swap/swapfile    none    swap    sw    0  0
  
Lucid:
+
To verify that the swapfile is accessilble as swap to the OS, run "top" or "htop" at a console.
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, and more tips in general, click [[BeagleBoardAngstrom#Configuring_uEnv.txt_to_set_s-video_as_the_default_display|here]])''.
 
 
 
S-video is tested to be working on 2.6.35-rc5-dl9. S-video output can be enabled using bootargs at uboot as mentioned below.
 
 
 
=== 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'
 
 
 
Note that the NTSC resolution is 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
 
 
 
However, not all of this will be visible on-screen, this is called [http://en.wikipedia.org/wiki/Overscan Overscan]. To make the whole framebuffer fit on the screen you need to adjust the overlay. (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
 
 
 
=== PAL ===
 
 
 
    omapfb.mode='''tv:pal'''
 
    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:pal omapdss.def_disp=tv fixrtc buddy=unknown'
 
 
 
Using these settings video output will display on the tv, however 5-10% of the left and right edges of display are off the screen (using Ubuntu 10.10 with xfce).
 
 
 
xrandr shows the display is set to the minimum of 720x574. Please update wiki if you can fix this.
 
 
 
== 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 770: Line 599:
 
  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 778: Line 607:
 
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 790: Line 618:
  
 
=== 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 808: Line 636:
 
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 12:20, 13 March 2017

(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.9.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.4.y -b tmp
./build_kernel.sh

Ubuntu (16.04.2)

Default username/password:

  • username: ubuntu
  • password: temppwd

Image Updated:

  • 2017-03-09
    • BeagleBoard xM: v4.9.13-armv7-x4 kernel
    • All BeagleBone Varients: v4.4.52-ti-r91 kernel
    • OMAP5432 uEVM: v4.4.52-ti-r91 kernel
    • BeagleBoard-X15: v4.4.52-ti-r91 kernel
  • 2017-01-23
    • BeagleBoard xM: v4.9.5-armv7-x4 kernel
    • All BeagleBone Varients: v4.4.43-ti-r84 kernel
    • OMAP5432 uEVM: v4.4.43-ti-r84 kernel
    • BeagleBoard-X15: v4.4.43-ti-r84 kernel
  • 2017-01-13
    • BeagleBoard xM: v4.9.3-armv7-x4 kernel
    • All BeagleBone Varients: v4.4.40-ti-r80 kernel
    • OMAP5432 uEVM: v4.4.40-ti-r80 kernel
    • BeagleBoard-X15: v4.4.40-ti-r80 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/2017-03-09/elinux/ubuntu-16.04.2-console-armhf-2017-03-09.tar.xz

Verify Image with:

sha256sum ubuntu-16.04.2-console-armhf-2017-03-09.tar.xz
8d0088c4842d3cbcacb64bafc74851307d43f55f1d10d17e0a9d1afe7a921e84  ubuntu-16.04.2-console-armhf-2017-03-09.tar.xz

Unpack Image:

tar xf ubuntu-16.04.2-console-armhf-2017-03-09.tar.xz
cd ubuntu-16.04.2-console-armhf-2017-03-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
  • All BeagleBone Varients - 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 v2017.03 -b tmp

Stable:

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

Flasher

eMMC: All BeagleBone Varients with eMMC

This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on Windows/Mac/Linux: https://etcher.io 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:

  • 2017-03-09
    • All BeagleBone Varients with eMMC: v4.4.52-ti-r91 kernel
  • 2017-01-23
    • All BeagleBone Varients with eMMC: v4.4.43-ti-r84 kernel
  • 2017-01-13
    • All BeagleBone Varients with eMMC: v4.4.40-ti-r80 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2017-03-09/flasher/BBB-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz

Verify Image with:

sha256sum BBB-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb*
5774f6d9aca247dbf46505cde6a439aae56aeb9cd4fa1ac3f46ce2a299851b89  BBB-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz

Windows/Mac/Linux gui

http://etcher.io

Linux: (dd)

xzcat BBB-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz | sudo dd 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/Mac/Linux: https://etcher.io 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:

  • 2017-03-09
    • BeagleBoard-X15: v4.4.52-ti-r91 kernel
  • 2017-01-23
    • BeagleBoard-X15: v4.4.43-ti-r84 kernel
  • 2017-01-13
    • BeagleBoard-X15: v4.4.40-ti-r80 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2017-03-09/flasher/bbx15-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz

Verify Image with:

sha256sum bbx15-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb*
40f705e93a73dcf44ad4dfd36a806bcbe682ef1303e7a4326ef5947462382582  bbx15-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz

Windows/Mac/Linux gui

http://etcher.io

Linux: (dd)

xzcat bbx15-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz | sudo dd of=/dev/sdX

raw microSD img

BeagleBoard xM

This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on Windows/Mac/Linux: https://etcher.io

User: ubuntu pass: temppwd

Auto partition resize:

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

Image Updated:

  • 2017-03-09
    • BeagleBoard xM: v4.9.13-armv7-x4 kernel
  • 2017-01-23
    • BeagleBoard xM: v4.9.5-armv7-x4 kernel
  • 2017-01-13
    • BeagleBoard xM: v4.9.3-armv7-x4 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2017-03-09/microsd/bbxm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz

Verify Image with:

sha256sum bbxm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb*
cc6c202610430af966db750161f0d57303162def4d169dc4e9c8dbe9d8f88e28  bbxm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz

Windows/Mac/Linux gui

http://etcher.io

Linux: (dd)

xzcat bbxm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz | sudo dd of=/dev/sdX

All BeagleBone Varients

This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on Windows/Mac/Linux: https://etcher.io

User: ubuntu pass: temppwd

Auto partition resize:

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

Image Updated:

  • 2017-03-09
    • All BeagleBone Varients: v4.4.52-ti-r91 kernel
  • 2017-01-23
    • All BeagleBone Varients: v4.4.43-ti-r84 kernel
  • 2017-01-13
    • All BeagleBone Varients: v4.4.40-ti-r80 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2017-03-09/microsd/bone-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz

Verify Image with:

sha256sum bone-ubuntu-16.04.2-console-armhf-2017-03-09-2gb*
fe3d2521b8ebaeca79ac5f5885a58ce3e4d93b7cc5adf407870017deae74c813  bone-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz

Windows/Mac/Linux gui

http://etcher.io

Linux: (dd)

xzcat bone-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz | sudo dd of=/dev/sdX

OMAP5432 uEVM

This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on Windows/Mac/Linux: https://etcher.io

User: ubuntu pass: temppwd

Auto partition resize:

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

Image Updated:

  • 2017-03-09
    • OMAP5432 uEVM: v4.4.52-ti-r91 kernel
  • 2017-01-23
    • OMAP5432 uEVM: v4.4.43-ti-r84 kernel
  • 2017-01-13
    • OMAP5432 uEVM: v4.4.40-ti-r80 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2017-03-09/microsd/omap5-uevm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz

Verify Image with:

sha256sum omap5-uevm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb*
65a48656354929eb95f1323d8e57f333b15dfccafb0bc56fc5d400afb029f763  omap5-uevm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz

Windows/Mac/Linux gui

http://etcher.io

Linux: (dd)

xzcat omap5-uevm-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz | sudo dd of=/dev/sdX

BeagleBoard-X15

This image can be written to a 2GB (or larger) microSD card, via 'dd' on linux or on Windows/Mac/Linux: https://etcher.io

User: ubuntu pass: temppwd

Auto partition resize:

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

Image Updated:

  • 2017-03-09
    • BeagleBoard-X15: v4.4.52-ti-r91 kernel
  • 2017-01-23
    • BeagleBoard-X15: v4.4.43-ti-r84 kernel
  • 2017-01-13
    • BeagleBoard-X15: v4.4.40-ti-r80 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2017-03-09/microsd/bbx15-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz

Verify Image with:

sha256sum bbx15-ubuntu-16.04.2-console-armhf-2017-03-09-2gb*
5ac531de42eee98a118ce496ac0728357300cdb9d7b85038a6ff3c7c5d07af80  bbx15-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz

Windows/Mac/Linux gui

http://etcher.io

Linux: (dd)

xzcat bbx15-ubuntu-16.04.2-console-armhf-2017-03-09-2gb.img.xz | sudo dd 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

General apt syntax for searching and installing a specific kernel:

sudo apt-get update
sudo apt-cache search linux-image | grep <branch>
sudo apt-get install linux-image-<specific version>
sudo reboot

Latest kernel script

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh <OPTIONS>

3.8.x

This is the first beagleboard.org long term kernel tree with capemanager support, it's been the default install for Debian Wheezy

beagleboard.org patchset: https://github.com/beagleboard/linux/tree/3.8
3.8.x BeagleBone/BeagleBone Black FULL Cape Support
--bone-channel --stable
3.8.x BeagleBone/BeagleBone Black FULL Cape Support + Xenomai
--bone-xenomai-channel --stable

4.4.x-ti

This is slated to replace the v3.8.x tree in Debian Jessie, cape manager support is enabled.

beagleboard.org patchset: https://github.com/beagleboard/linux/tree/4.4
4.4.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15
--ti-channel --lts-4_4
4.4.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15 + RT
--ti-rt-channel --lts-4_4
4.4.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15 + RT
-ti-xenomai-channel --lts-4_4

Mainline (lts)

4.4.x BeagleBone/BeagleBone Black + SGX
--bone-kernel --lts-4_4
4.4.x BeagleBone/BeagleBone Black + RT + SGX
--bone-rt-kernel --lts-4_4

Reboot with your new Kernel Image.

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

SGX Drivers

SGX BeagleBone/BeagleBone Black

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

Install the "4.1.x" lts/bone kernel: http://elinux.org/BeagleBoardUbuntu#Mainline_.28lts.29

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.