Difference between revisions of "BeagleBoardUbuntu"

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

Latest revision as of 08:47, 13 March 2020

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

Ubuntu (18.04.4)

Default username/password:

  • username: ubuntu
  • password: temppwd

Image Updated:

  • 2020-03-12
    • BeagleBoard xM: v5.4.24-armv7-x20 kernel
    • All BeagleBone Variants and PocketBeagle: v4.19.94-ti-r36 kernel
    • BeagleBoard-X15 (and BeagleBone AI): v4.19.94-ti-r36 kernel
  • 2019-04-10
    • BeagleBoard xM: v4.19.31-armv7-x31 kernel
    • All BeagleBone Variants and PocketBeagle: v4.14.108-ti-r104 kernel
    • BeagleBoard-X15: v4.14.108-ti-r104 kernel
  • 2018-12-10
    • BeagleBoard xM: v4.19.8-armv7-x11 kernel
    • All BeagleBone Variants and PocketBeagle: v4.14.79-ti-r84 kernel
    • BeagleBoard-X15: v4.14.79-ti-r84 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) (Windows/Linux) http://192.168.7.2, (Mac/Linux) http://192.168.6.2
SSH, Port 22: ssh ubuntu@arm.local (Bone: via usb) (Windows/Linux) ubuntu@192.168.7.2, (Mac/Linux) ubuntu@192.168.6.2
Getty, Serial Port

Default user: ubuntu pass: temppwd

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2020-03-12/elinux/ubuntu-18.04.4-console-armhf-2020-03-12.tar.xz

Verify Image with:

sha256sum ubuntu-18.04.4-console-armhf-2020-03-12.tar.xz
abe086f9132dfe8e8b9df8d14da225e0ce89a082abc92515de8a2ac63fc54ae2  ubuntu-18.04.4-console-armhf-2020-03-12.tar.xz

Unpack Image:

tar xf ubuntu-18.04.4-console-armhf-2020-03-12.tar.xz
cd ubuntu-18.04.4-console-armhf-2020-03-12

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 Variants - beaglebone
  • OMAP5432 uEVM - omap5-uevm
  • BeagleBoard-X15 (BeagleBone AI) - 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 v2020.03 -b tmp

Stable:

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

Flasher

eMMC: All BeagleBone Variants 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 boot-up 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:

  • 2020-03-12
    • All BeagleBone Variants with eMMC: v4.19.94-ti-r36 kernel
  • 2019-04-10
    • All BeagleBone Variants with eMMC: v4.14.108-ti-r104 kernel
  • 2018-12-10
    • All BeagleBone Variants with eMMC: v4.14.79-ti-r84 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2020-03-12/flasher/bone-eMMC-flasher-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz

Verify Image with:

sha256sum bone-eMMC-flasher-ubuntu-18.04.4-console-armhf-2020-03-12-2gb*
2bc7f92df84dbd89c1cdd790ec794926a5d6b0f0b891143085d77141170518e2  bone-eMMC-flasher-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz

Windows/Mac/Linux gui

http://etcher.io

Linux: (dd)

xzcat bone-eMMC-flasher-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz | sudo dd of=/dev/sdX

eMMC: BeagleBoard-X15 and BeagleBone AI

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 boot-up 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:

  • 2020-03-12
    • BeagleBoard-X15 (and BeagleBone AI): v4.19.94-ti-r36 kernel
  • 2019-04-10
    • BeagleBoard-X15 (and BeagleBone AI): v4.14.108-ti-r104 kernel
  • 2018-12-10
    • BeagleBoard-X15 (and BeagleBone AI): v4.14.79-ti-r84 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2020-03-12/flasher/am57xx-eMMC-flasher-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz

Verify Image with:

sha256sum am57xx-eMMC-flasher-ubuntu-18.04.4-console-armhf-2020-03-12-2gb*
0c359f2b5e9d27d167f55877d3abfea0af2fe721463136f354dfd5d72be8a541  am57xx-eMMC-flasher-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz

Windows/Mac/Linux gui

http://etcher.io

Linux: (dd)

xzcat am57xx-eMMC-flasher-ubuntu-18.04.4-console-armhf-2020-03-12-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:

  • 2020-03-12
    • BeagleBoard xM: v5.4.24-armv7-x20 kernel
  • 2019-04-10
    • BeagleBoard xM: v4.19.31-armv7-x31 kernel
  • 2018-12-10
    • BeagleBoard xM: v4.19.8-armv7-x11 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2020-03-12/microsd/bbxm-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz

Verify Image with:

sha256sum bbxm-ubuntu-18.04.4-console-armhf-2020-03-12-2gb*
a3d8780a69ceca6c5462c80c5a061dbba7df91d9111e08e718ecf55420302b91  bbxm-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz

Windows/Mac/Linux gui

http://etcher.io

Linux: (dd)

xzcat bbxm-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz | sudo dd of=/dev/sdX

All BeagleBone Variants and PocketBeagle

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:

  • 2020-03-12
    • All BeagleBone Variants and PocketBeagle: v4.19.94-ti-r36 kernel
  • 2019-04-10
    • All BeagleBone Variants and PocketBeagle: v4.14.108-ti-r104 kernel
  • 2018-12-10
    • All BeagleBone Variants and PocketBeagle: v4.14.79-ti-r84 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2020-03-12/microsd/bone-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz

Verify Image with:

sha256sum bone-ubuntu-18.04.4-console-armhf-2020-03-12-2gb*
4c41976f1f574a4786002482167fe6443d8c9f1bced86a174459ffeba1f5b780  bone-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz

Windows/Mac/Linux gui

http://etcher.io

Linux: (dd)

xzcat bone-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz | sudo dd of=/dev/sdX

BeagleBoard-X15 and BeagleBone AI

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:

  • 2020-03-12
    • BeagleBoard-X15 (and BeagleBone AI): v4.19.94-ti-r36 kernel
  • 2019-04-10
    • BeagleBoard-X15 (and BeagleBone AI): v4.14.108-ti-r104 kernel
  • 2018-12-10
    • BeagleBoard-X15 (and BeagleBone AI): v4.14.79-ti-r84 kernel

Get prebuilt image:

wget https://rcn-ee.com/rootfs/2020-03-12/microsd/am57xx-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz

Verify Image with:

sha256sum am57xx-ubuntu-18.04.4-console-armhf-2020-03-12-2gb*
cd253167b43186c14c02e9e85ede006cd51336d5f8beae5b96765f494c24bd91  am57xx-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz

Windows/Mac/Linux gui

http://etcher.io

Linux: (dd)

xzcat am57xx-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz | sudo dd of=/dev/sdX

Method 2: 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.9.x-ti

beagleboard.org patchset: https://github.com/beagleboard/linux/tree/4.9
Based on: http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-4.9.y
4.9.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15
--ti-channel --lts-4_9
4.9.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15 + RT
--ti-rt-channel --lts-4_9
4.9.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15 + Xenomai
--ti-xenomai-channel --lts-4_9

4.14.x-ti

beagleboard.org patchset: https://github.com/beagleboard/linux/tree/4.14
Based on: http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-4.14.y
4.14.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15
--ti-channel --lts-4_14
4.14.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15 + RT
--ti-rt-channel --lts-4_14

Mainline (4.9.x lts)

4.9.x BeagleBone/BeagleBone Black
--bone-kernel --lts-4_9
4.9.x BeagleBone/BeagleBone Black + RT
--bone-rt-kernel --lts-4_9

Mainline (4.14.x lts)

4.14.x BeagleBone/BeagleBone Black
--bone-kernel --lts-4_14
4.14.x BeagleBone/BeagleBone Black + RT
--bone-rt-kernel --lts-4_14

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 Bionic 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/melodic/Installation/Ubuntu

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.