Difference between revisions of "BeagleBoardUbuntu"

From eLinux.org
Jump to: navigation, search
(Added section on adding a swapfile to the system)
(Method 3: Manual Install (no automatic scripts))
 
(225 intermediate revisions by 10 users not shown)
Line 4: Line 4:
 
[[Category: BeagleBoard]]
 
[[Category: BeagleBoard]]
 
''(For BeagleBoardAngstrom, click [[BeagleBoardAngstrom|here]].)''
 
''(For BeagleBoardAngstrom, click [[BeagleBoardAngstrom|here]].)''
 +
''(Should [[Beagleboard:Ubuntu On BeagleBone Black]] be merged into this page?)''
  
This page is about running a (ARM [http://wiki.debian.org/ArmEabiPort EABI]) [http://www.ubuntu.com/ Ubuntu] distribution at [[BeagleBoard]]. BeagleBoard will boot the (ARM EABI) Ubuntu distribution from [[BeagleBoard#MMC.2FSD_boot|SD card]]. Since much of this page is generic, it has also be extended to help support devices such as the [[PandaBoard]] and [[BeagleBone]].
+
This page is about running a Linux distribution (ARM [https://wiki.debian.org/ArmEabiPort EABI]) [http://www.ubuntu.com/ Ubuntu] on the [[BeagleBoard]]. BeagleBoard will boot the (ARM EABI) Ubuntu distribution from the [[BeagleBoard#MMC.2FSD_boot|SD card]]. Since much of this page is generic, it has also been extended to help support devices such as the [[PandaBoard]] and [[BeagleBone]].
  
* For the best experience, make sure you have an LCD/HDMI monitor attached to the BeagleBoard's HDMI port, 2GB/4GB/8GB SD card, and a known good usb2.0 hub with mouse and keyboard.
+
* For the best experience, make sure you have an LCD/HDMI monitor attached to the BeagleBoard's HDMI port, 2 GB/4 GB/8 GB SD card, and a known good USB 2.0 hub with mouse and keyboard.
  
 
= Help =
 
= Help =
Line 14: Line 15:
  
 
*Kernel related help:
 
*Kernel related help:
** [http://groups.google.com/group/beagleboard Email Beagleboard user group] *Recommended method
+
** [https://groups.google.com/group/beagleboard Email Beagleboard user group] *Recommended method
** ''#beagle'': Beagle irc on freenode, accessible also by [http://beagleboard.org/discuss web interface] ([http://www.beagleboard.org/irclogs/index.php logs])
+
** ''#beagle'': Beagle IRC on Freenode, accessible also by [http://beagleboard.org/discuss web interface] ([http://www.beagleboard.org/irclogs/index.php logs])
** Kernel Tree's
+
** Kernel Trees
*** [https://github.com/RobertCNelson/stable-kernel Stable Kernel 3.2.x src]
+
*** [https://github.com/RobertCNelson/armv7-multiplatform/ v4.17.x kernel branch]
*** [https://github.com/RobertCNelson/linux-dev Development Kernel src]
+
*** [https://github.com/RobertCNelson/linux-dev Development Kernel source code]
  
 
*Ubuntu related help:
 
*Ubuntu related help:
** ''#ubuntu-arm'': Ubuntu's arm irc on freenode ([http://irclogs.ubuntu.com/ logs] -> year -> month -> day -> #ubuntu-arm.html)
+
** ''#ubuntu-arm'': Ubuntu's ARM IRC on Freenode ([http://irclogs.ubuntu.com/ logs] -> year -> month -> day -> #ubuntu-arm.html)
  
*When asking for help, please provide some debugging information:
+
*When requesting help, please provide some debugging information:
 
** U-Boot Version installed on board
 
** U-Boot Version installed on board
 
** Kernel Version: uname -a
 
** Kernel Version: uname -a
Line 31: Line 32:
 
= Required Beagle Software =  
 
= Required Beagle Software =  
  
Angstrom's X-loader/MLO & U-Boot
+
Mainline U-Boot:
* All Old Ax, Bx, Cx Boards are required to upgrade to atleast these MLO and U-Boot versions.
+
* All older BeagleBoard (classic) Ax, Bx, Cx and Dx boards are required to upgrade to at least these U-Boot versions
* XM Boards have no NAND, so u-boot.img is always required on the first partition
+
* XM Boards have no NAND, so MLO/u-boot.img is always required on the first partition
 
* Directions: [http://elinux.org/BeagleBoardUbuntu#Upgrade_X-loader_and_U-boot Upgrade X-loader and U-Boot]
 
* Directions: [http://elinux.org/BeagleBoardUbuntu#Upgrade_X-loader_and_U-boot Upgrade X-loader and U-Boot]
  
Line 55: Line 56:
 
= Method 1: Download a Complete Pre-Configured Image =
 
= Method 1: Download a Complete Pre-Configured Image =
  
== Canonical/Ubuntu Images ==
+
== Demo Image ==
Support:
 
''#ubuntu-arm'': Ubuntu's arm irc on freenode ([http://irclogs.ubuntu.com/ logs] -> year -> month -> day -> #ubuntu-arm.html)
 
  
Canonical only supports certain boards with images, at this moment.
+
* '''Advanced Users only''': BeagleBoard xM: Kernel source, used in these demo images: https://github.com/RobertCNelson/armv7-multiplatform
*BeagleBoard xM -> "omap"
+
  git clone https://github.com/RobertCNelson/armv7-multiplatform.git
*PandaBoard & PandaBoard ES -> "omap4"
+
  cd armv7-multiplatform
https://wiki.ubuntu.com/ARM/OMAP
+
git checkout origin/v5.4.x -b tmp
 
 
==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''': Beagle/Panda Kernel source, used in these demo images: https://github.com/RobertCNelson/stable-kernel
 
  git clone git://github.com/RobertCNelson/stable-kernel.git
 
  cd stable-kernel
 
 
  ./build_kernel.sh
 
  ./build_kernel.sh
* '''Advanced Users only''': BeagleBone Kernel source, used in these demo images: https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.2
+
* '''Advanced Users only''': BeagleBone/BeagleBone Black/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/linux-dev.git
+
  git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
  cd linux-dev
+
  cd ti-linux-kernel-dev
  git checkout origin/am33x-v3.2 -b am33x-v3.2
+
  git checkout origin/ti-linux-4.19.y -b tmp
 
  ./build_kernel.sh
 
  ./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...
 
  
=== Precise 12.04 armhf ===
+
=== Ubuntu (18.04.4) ===
  
Notes: this 'armhf' hf= hard float, should be faster then 'armel', sgx/dsp bits probally won't work, as they are built for softfp..
+
Default username/password:
 
+
*username: ubuntu
Note: Errors in the way BeagleBoards A1 to C4 implemented the thumb instruction set mean that armhf should not be used with these boards.  Random segfaults will be the outcome if you do.
+
*password: temppwd
  
 
Image Updated:
 
Image Updated:
*May 1st: -r1
+
*2020-03-12
** Beagle/Panda: v3.2.16-x11 kernel (Panda: Audio Backported from v3.4-rc, Beagle: CircuitCo ulcd fixes, bbtoys-wifi fixes)
+
** BeagleBoard xM: v5.4.24-armv7-x20 kernel
** Bone: v3.2.0-psp7 kernel (more usb fixes)
+
** All BeagleBone Variants and PocketBeagle: v4.19.94-ti-r36 kernel
*March 29th: -beta2
+
** BeagleBoard-X15 (and BeagleBone AI): v4.19.94-ti-r36 kernel
** Beagle/Panda: v3.2.13-x7 kernel (panda bluetooth now works "sudo apt-get install bluetooth" to get all the userspace programs)
+
*2019-04-10
** Bone: v3.2.0-psp6 kernel (for users with usb problems, still no good solution yet..)
+
** BeagleBoard xM: v4.19.31-armv7-x31 kernel
*March 1st: -beta1
+
** All BeagleBone Variants and PocketBeagle: v4.14.108-ti-r104 kernel
** Beagle/Panda: v3.2.7 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:
 
Services Active:
  Note: Depending on your internal network these may work out the box
+
  Note: Depending on your internal network these may work out of the box
  Apache, Port 80: http://omap/
+
  Apache, Port 80: http://arm.local/ (Bone: via usb) (Windows/Linux) http://192.168.7.2, (Mac/Linux) http://192.168.6.2
  SSH, Port 22: ssh ubuntu@omap
+
  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
  
Default user: ubuntu pass: temppwd  
+
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 http://rcn-ee.net/deb/rootfs/precise/ubuntu-12.04-r1-minimal-armhf.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/precise/ubuntu-12.04-r1-minimal-armhf.tar.xz
+
  abe086f9132dfe8e8b9df8d14da225e0ce89a082abc92515de8a2ac63fc54ae2  ubuntu-18.04.4-console-armhf-2020-03-12.tar.xz
 
 
Verify Image with:
 
  md5sum ubuntu-12.04-r1-minimal-armhf.tar.xz
 
28a2e3969f3d6dd434d2481fd443e634  ubuntu-12.04-r1-minimal-armhf.tar.xz
 
  
 
Unpack Image:
 
Unpack Image:
  tar xJf ubuntu-12.04-r1-minimal-armhf.tar.xz
+
  tar xf ubuntu-18.04.4-console-armhf-2020-03-12.tar.xz
  cd ubuntu-12.04-r1-minimal-armhf
+
  cd ubuntu-18.04.4-console-armhf-2020-03-12
  
 
If you don't know the location of your SD card:
 
If you don't know the location of your SD card:
 
  sudo ./setup_sdcard.sh --probe-mmc
 
  sudo ./setup_sdcard.sh --probe-mmc
  
You should see something like  
+
You should see something like:
  
  Are you sure? I Don't see [/dev/idontknow], here is what I do see...
+
  Are you sure? I don't see [/dev/idontknow], here is what I do see...
 
   
 
   
 
  fdisk -l:
 
  fdisk -l:
 
  Disk /dev/sda: 500.1 GB, 500107862016 bytes '''<- x86 Root Drive'''
 
  Disk /dev/sda: 500.1 GB, 500107862016 bytes '''<- x86 Root Drive'''
  Disk /dev/mmcblk0: 3957 MB, 3957325824 bytes '''<- MMC/SD card'''
+
  Disk /dev/sdd: 3957 MB, 3957325824 bytes '''<- MMC/SD card'''
 
   
 
   
  mount:
+
  lsblk:
  /dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0) '''<- x86 Root Partition'''
+
  NAME  MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
 +
sda      8:0    0 465.8G  0 disk
 +
├─sda1  8:1    0 446.9G  0 part / '''<- x86 Root Partition'''
 +
├─sda2  8:2    0    1K  0 part
 +
└─sda5  8:5    0  18.9G  0 part [SWAP]
 +
sdd      8:48  1  3.7G  0 disk
 +
├─sdd1  8:49  1    64M  0 part
 +
└─sdd2  8:50  1  3.6G  0 part
  
* In this example, we can see via mount, '''/dev/sda1''' is the x86 rootfs, therefore '''/dev/mmcblk0''' is the other drive in the system, which is the MMC/SD card that was inserted and should be used by ./setup_sdcard.sh...
+
* In this example, we can see via mount, '''/dev/sda1''' is the x86 rootfs, therefore '''/dev/sdd''' is the other drive in the system, which is the MMC/SD card that was inserted and should be used by ./setup_sdcard.sh...
  
 
Install Image:
 
Install Image:
  
Quick Install script for "board"
+
Quick install script for [board]
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot "board"
+
  sudo ./setup_sdcard.sh --mmc /dev/sdX --dtb board
 
 
"board" Options:
 
*BeagleBoard Ax/Bx - beagle_bx
 
*BeagleBoard Cx    - beagle_cx
 
*BeagleBoard xMA/B/C    - beagle_xm
 
*BeagleBone Ax    - bone
 
*PandaBoard Ax - panda
 
*PandaBoard ES - panda_es
 
 
 
So For the BeagleBoard xM:
 
sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle_xm
 
 
 
*Additional Options
 
** --rootfs <ext4 default>
 
** --swap_file <swap file size in MB's>
 
** --addon pico <ti pico projector>
 
** --addon ulcd <CircuitCo 7 inch lcd>
 
** --svideo-ntsc <use ntsc over dvi for video)
 
** --svideo-pal <use pal over dvi for video)
 
 
 
You should now be able to unmount the SD card from you PC, insert into your Board, reboot and have the OS loaded.
 
  
For a full gui install run this on your beagle (make sure network is setup):
+
board options:
Ethernet: "sudo ifconfig -a" and "sudo dhclient usb1" or "sudo dhclient eth0"
+
*BeagleBoard Ax/Bx/Cx/Dx          - omap3-beagle
Wireless: http://elinux.org/BeagleBoardUbuntu#Wifi_Networking_.28command_line.29
+
*BeagleBoard xM                  - omap3-beagle-xm
sudo apt-get update
+
*All BeagleBone Variants          - beaglebone
  sudo apt-get install gdm xubuntu-desktop
+
*OMAP5432 uEVM                    - omap5-uevm
 +
*BeagleBoard-X15 (BeagleBone AI) - am57xx-beagle-x15
  
Note that the above will install Xserver but it will not update the SGX or other graphics libraries. NB that the SGX binary blobs will not work with a armhf pvr driver if they are build against armel. This means installing armhf 12.04 and running the above commands is unlikely to allow a GUI unless you also tweak the drivers.
+
So for the BeagleBoard xM:
 +
  sudo ./setup_sdcard.sh --mmc /dev/sdX --dtb omap3-beagle-xm
  
 
Advanced: Build Image:
 
Advanced: Build Image:
  
Built with a fork of project-rootstock (ARM native mode, run directly on beagleboard), using a script from omap-image-builder:
+
  git clone https://github.com/RobertCNelson/omap-image-builder.git
 
 
  git clone git://github.com/RobertCNelson/omap-image-builder.git
 
 
  cd omap-image-builder
 
  cd omap-image-builder
  git checkout v2012.4-1 -b v2012.4-1
+
  git checkout v2020.03 -b tmp
./build_image.sh
 
  
=== Oneiric 11.10 ===
+
Stable:
  
Image Updated:
+
./RootStock-NG.sh -c rcn-ee_console_ubuntu_bionic_armhf
*May 1st: -r8
 
** Beagle/Panda: v3.2.16-x11 kernel (Panda: Audio Backported from v3.4-rc, Beagle: CircuitCo ulcd fixes, bbtoys-wifi fixes)
 
** Bone: v3.2.0-psp7 kernel (more usb fixes)
 
*March 29th: -r7
 
** Beagle/Panda: v3.2.13-x7 kernel (panda bluetooth now works "sudo apt-get install bluetooth" to get all the userspace programs)
 
** Bone: v3.2.0-psp6 kernel (for users with usb problems, still no good solution yet..)
 
*March 1st: -r6
 
** Beagle/Panda: v3.2.7 kernel
 
  
Services Active:
+
== Flasher ==
Note: Depending on your internal network these may work out the box
 
Apache, Port 80: http://omap/
 
SSH, Port 22: ssh ubuntu@omap
 
Getty, Serial Port
 
  
Default user: ubuntu pass: temppwd
+
=== eMMC: All BeagleBone Variants with eMMC ===
  
Get prebuilt image:
+
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.
  
  wget http://rcn-ee.net/deb/rootfs/oneiric/ubuntu-11.10-r8-minimal-armel.tar.xz
+
Script for reference: (this is the script that writes to the eMMC)
mirrors (will take some time to update):
+
  https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v3.sh
wget http://ynezz.ibawizard.net/beagleboard/oneiric/ubuntu-11.10-r8-minimal-armel.tar.xz
 
  
Verify Image with:
+
This script will only take about 5-6 Minutes after power on.
md5sum ubuntu-11.10-r8-minimal-armel.tar.xz
 
979b3c6f68df6c51673200bcca511c0c  ubuntu-11.10-r8-minimal-armel.tar.xz
 
  
Unpack Image:
+
Notes:
tar xJf ubuntu-11.10-r8-minimal-armel.tar.xz
+
* If only two LED's stay lit and nothing happens, the board has crashed due to lack of power. Retry with a 5Volt DC power supply connected.
cd ubuntu-11.10-r8-minimal-armel
+
* If the 4 LED's blink a constant pattern, the eMMC write has failed. First REMOVE ALL capes, then retry again.
  
If you don't know the location of your SD card:
+
User: ubuntu
sudo ./setup_sdcard.sh --probe-mmc
+
pass: temppwd
  
You should see something like
+
Image Updated:
 +
*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
  
Are you sure? I Don't see [/dev/idontknow], here is what I do see...
+
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
fdisk -l:
 
Disk /dev/sda: 500.1 GB, 500107862016 bytes '''<- x86 Root Drive'''
 
Disk /dev/mmcblk0: 3957 MB, 3957325824 bytes '''<- MMC/SD card'''
 
 
mount:
 
/dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0) '''<- x86 Root Partition'''
 
  
* In this example, we can see via mount, '''/dev/sda1''' is the x86 rootfs, therefore '''/dev/mmcblk0''' is the other drive in the system, which is the MMC/SD card that was inserted and should be used by ./setup_sdcard.sh...
+
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
  
Install Image:
+
Windows/Mac/Linux gui
 +
http://etcher.io
  
Quick Install script for "board"
+
Linux: (dd)
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot "board"
+
  xzcat bone-eMMC-flasher-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz | sudo dd of=/dev/sdX
  
"board" Options:  
+
=== eMMC: BeagleBoard-X15 and BeagleBone AI ===
*BeagleBoard Ax/Bx - beagle_bx
 
*BeagleBoard Cx    - beagle_cx
 
*BeagleBoard xMA/B/C    - beagle_xm
 
*BeagleBone Ax    - bone
 
*PandaBoard Ax - panda
 
*PandaBoard ES - panda_es
 
  
So For the BeagleBoard xM:
+
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.
  sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot beagle_xm
 
  
*Additional Options
+
Script for reference: (this is the script that writes to the eMMC)
** --rootfs <ext4 default>
+
https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v3.sh
** --swap_file <swap file size in MB's>
 
** --addon pico <ti pico projector>
 
** --addon ulcd <CircuitCo 7 inch lcd>
 
** --svideo-ntsc <use ntsc over dvi for video)
 
** --svideo-pal <use pal over dvi for video)
 
  
You should now be able to unmount the SD card from you PC, insert into your Board, reboot and have OS loaded.
+
This script will only take about 5-6 Minutes after power on.
  
For a full gui install run this on your beagle (make sure network is setup):
+
Notes:
Ethernet: "sudo ifconfig -a" and "sudo dhclient usb1" or "sudo dhclient eth0"
+
* 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.
Wireless: http://elinux.org/BeagleBoardUbuntu#Wifi_Networking_.28command_line.29
+
* If the 4 LED's blink a constant pattern, the eMMC write has failed. First REMOVE ALL capes, then retry again.
sudo apt-get update
 
sudo apt-get install gdm xubuntu-desktop
 
  
Advanced: Build Image:
+
User: ubuntu
 +
pass: temppwd
  
Built with a fork of project-rootstock (ARM native mode, run directly on beagleboard), using a script from omap-image-builder:
+
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
  
  git clone git://github.com/RobertCNelson/omap-image-builder.git
+
Get prebuilt image:
cd omap-image-builder
+
  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
git checkout v2012.4-1 -b v2012.4-1
 
./build_image.sh
 
  
= Method 2: Use the NetInstall method=
+
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
  
You will need a 1GB/2GB SD card or greater.
+
Windows/Mac/Linux gui
  Standard System : ~700MB
+
  http://etcher.io
  
== Ubuntu 12.04 (Precise) ==
+
Linux: (dd)
 +
xzcat am57xx-eMMC-flasher-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz | sudo dd of=/dev/sdX
  
git clone git://github.com/RobertCNelson/netinstall.git
+
== raw microSD img ==
cd netinstall
 
  
Install script for "board"
+
=== BeagleBoard xM ===
sudo ./mk_mmc.sh --mmc /dev/sdX --uboot "board" --distro precise-armhf
 
  
"board" Options:  
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on Linux or on Windows/Mac/Linux: https://etcher.io
*BeagleBoard Ax/Bx - beagle_bx
 
*BeagleBoard Cx    - beagle_cx
 
*BeagleBoard xMA/B/C    - beagle_xm
 
*BeagleBone Ax    - bone
 
*PandaBoard Ax - panda
 
*PandaBoard ES - panda_es
 
  
So For the BeagleBoard xM:
+
User: ubuntu
sudo ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_xm --distro precise-armhf
+
pass: temppwd
  
*Options:
+
Auto partition resize:
**--uboot : beagle_bx, beagle, panda
+
cd /opt/scripts/tools
**--distro : maverick, oneiric
+
git pull
**--firmware : installs firmware
+
./grow_partition.sh
**--serial-mode : debian-installer uses Serial Port
+
sudo reboot
**--addon ulcd : (ulcd from: http://search.digikey.com/scripts/DkSearch/dksus.dll?vendor=0&keywords=ULCD7-ND)
 
  
Place SD card into Beagle and boot:
+
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
  
Configure the network:
+
Get prebuilt image:
  usb0: USB net <- (usually the OTG port)
+
  wget https://rcn-ee.com/rootfs/2020-03-12/microsd/bbxm-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz
eth0: USB net <- (usually the smsc95xx adapter on the beagle and panda)
 
wlan0: Wifi <- Your usb-wifi device..  
 
  
Troubshooting: If boot fails..
+
Verify Image with:
*Hold the user button down to force booting from MMC
+
sha256sum bbxm-ubuntu-18.04.4-console-armhf-2020-03-12-2gb*
*Upgrade X-loader and U-boot [http://elinux.org/BeagleBoardUbuntu#Upgrade_X-loader_and_U-boot Upgrade X-loader and U-Boot]
+
a3d8780a69ceca6c5462c80c5a061dbba7df91d9111e08e718ecf55420302b91  bbxm-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz
*Clear U-boot's Environment Variables in nand:
 
nand erase 260000 20000
 
  
NetInstall assumptions:
+
Windows/Mac/Linux gui
  Continue with out Kernel Modules <yes>
+
  http://etcher.io
Partition <Guided - use the largest continuous free space>
 
  
= Method 3: Manual Install (no automatic scripts)=
+
Linux: (dd)
 +
xzcat bbxm-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz | sudo dd of=/dev/sdX
  
For this section, you can use the files from above:
+
=== All BeagleBone Variants and PocketBeagle===
Demo Images: http://elinux.org/BeagleBoardUbuntu#Demo_Image
 
Rootstock: http://elinux.org/BeagleBoardUbuntu#Build_an_Ubuntu_root_file_system_with_RootStock
 
  
BUT it assumes you have your own kernel uImage/modules from any of the many sources..
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on Linux or on Windows/Mac/Linux: https://etcher.io
  
== Partition SD Card ==
+
User: ubuntu
You will need a 1GB SD card or greater.
+
pass: temppwd
Standard Console System : ~286MB
 
+ Desktop environment (lxde,gdm) : ~479MB
 
  
Starting with an empty SD card and using gparted, create:
+
Auto partition resize:
  50 MiB Primary Partition, fat16/fat32
+
  cd /opt/scripts/tools
  Rest as ext2/ext3/ext4/btrfs
+
git pull
 +
  ./grow_partition.sh
 +
sudo reboot
  
First blank the MMC card's partition table with parted: (/dev/sdX as an example)
+
Image Updated:
sudo parted -s /dev/sdX mklabel msdos
+
*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
  
With fdisk: (note: GNU Fdisk doesn't work..)
+
Get prebuilt image:
sudo fdisk /dev/sdX << __EOF__
+
wget https://rcn-ee.com/rootfs/2020-03-12/microsd/bone-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz
n
 
p
 
1
 
 
+64M
 
t
 
e
 
p
 
w
 
__EOF__
 
  
Make sure to set the partition boot flag
+
Verify Image with:
  sudo parted --script /dev/sdX set 1 boot on
+
  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
  
And format it as vfat:
+
Windows/Mac/Linux gui
  sudo mkfs.vfat -F 16 /dev/sdX1 -n boot
+
  http://etcher.io
  
The rootfs partition, doesn't need any special options, so just use fdisk, gparted, etc to create and format your rootfs partition..
+
Linux: (dd)
 +
xzcat bone-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz | sudo dd of=/dev/sdX
  
Gparted Example: http://nishanthmenon.blogspot.com/2008/08/how-to-boot-beagle.html
+
=== BeagleBoard-X15 and BeagleBone AI===
  
== Boot Partition ==
+
This image can be written to a 2GB (or larger) microSD card, via 'dd' on Linux or on Windows/Mac/Linux: https://etcher.io
  
Requirements:
+
User: ubuntu
 +
pass: temppwd
  
  sudo apt-get install uboot-mkimage
+
Auto partition resize:
  Mount the fatfs partition of your SD card.
+
  cd /opt/scripts/tools
 +
git pull
 +
  ./grow_partition.sh
 +
sudo reboot
  
Mount such as: (/dev/sdX1 is the fat Boot Partition)
+
Image Updated:
mkdir -p ./tmp
+
*2020-03-12
sudo mount /dev/sdX1 ./tmp
+
** 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
  
=== MLO and U-Boot ===
+
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
==== Beagle ====
 
Download and copy MLO and U-Boot from here:
 
 
 
  First download "http://rcn-ee.net/deb/tools/beagleboard/MLO-beagleboard-v2012.04.01-r1" as MLO to the Boot Partition
 
Then download "http://rcn-ee.net/deb/tools/beagleboard/u-boot-beagleboard-v2012.04.01-r1.img" as u-boot.img to the Boot Partition
 
 
 
==== BeagleBone ====
 
Download and copy MLO and U-Boot from here:
 
http://www.angstrom-distribution.org/demo/beaglebone/
 
 
 
First copy "MLO" as MLO to the Boot Partition
 
Then copy "u-boot.img" as u-boot.img to the Boot Partition
 
 
 
==== Panda/Panda ES ====
 
 
 
Download and copy MLO and U-Boot from here:
 
 
 
First download "http://rcn-ee.net/deb/tools/pandaboard/MLO-pandaboard-v2011.12-r1" as MLO to the Boot Partition
 
Then download "http://rcn-ee.net/deb/tools/pandaboard/u-boot-pandaboard-v2011.12-r1.img" as u-boot.img to the Boot Partition
 
 
 
=== U-Boot uImage and uInitrd ===
 
 
 
U-Boot needs a compatible kernel image to boot.  To do this, we are using mkimage from (uboot-mkimage) to create an image from the vmlinuz kernel file.  
 
 
 
mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n "Linux" -d ./vmlinuz-* ./uImage
 
Copy "uImage" to the Boot Partition
 
 
 
Next create a uInird (this contains a script to fix the rtc on boot, otherwise fsck/reboot/fsck/reboot/repeat happens..)
 
 
 
mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 -n initramfs -d ./initrd.img-* ./uInitrd
 
Copy "uInitrd" to the Boot Partition
 
 
 
=== U-Boot Boot Scripts ===
 
The version of U-Boot installed or recommended to install uses boot scripts by default.  This allows users to easily switch between multiple SD cards with different OS's with different parameters installed.  Ubuntu/Debian requires a slight modification to the bootargs line vs. Angstrom, 'ro' vs 'rw'.
 
 
 
fixrtc: (only uInitrd) Resets RTC based on last mount
 
buddy=${buddy}: (both) Kernel Zippy1/2 Support
 
mpurate=${mpurate}: (recommended core clock)
 
 
 
==== boot.scr -> uEnv.txt ====
 
Newer version's of u-boot now look for a uEnv.txt file vs the older boot.scr, since most boards still use the older boot.scr here's an easy compatibility script:
 
 
 
create a new file: uEnv.txt
 
bootenv=boot.scr
 
loaduimage=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
 
mmcboot=echo Running boot.scr script from mmc ...; source ${loadaddr}
 
 
 
==== Beagle Bx/Cx ====
 
 
 
create a new file: uEnv.txt
 
bootfile=uImage
 
bootinitrd=uInitrd
 
address_uimage=0x80300000
 
address_uinitrd=0x81600000
 
 
vram=12MB
 
 
console=ttyO2,115200n8
 
 
defaultdisplay=dvi
 
dvimode=1280x720MR-16@60
 
 
mmcroot=/dev/mmcblk0p2 ro
 
mmcrootfstype=ext4 rootwait fixrtc
 
optargs=console=tty0
 
 
mmc_load_uimage=fatload mmc 0:1 ${address_uimage} ${bootfile}
 
mmc_load_uinitrd=fatload mmc 0:1 ${address_uinitrd} ${bootinitrd}
 
 
expansion=buddy=${buddy} buddy2=${buddy2} camera=${camera}
 
video=vram=${vram} omapfb.mode=${defaultdisplay}:${dvimode} omapdss.def_disp=${defaultdisplay}
 
 
mmcargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate} ${expansion} ${video} root=${mmcroot} rootfstype=${mmcrootfstype} musb_hdrc.fifo_mode=5
 
 
loaduimage=run mmc_load_uimage; run mmc_load_uinitrd; echo Booting from mmc ...; run mmcargs; bootm ${address_uimage} ${address_uinitrd}
 
 
 
==== Beagle xM ====
 
 
 
create a new file: uEnv.txt
 
bootfile=uImage
 
bootinitrd=uInitrd
 
address_uimage=0x80300000
 
address_uinitrd=0x81600000
 
 
vram=12MB
 
 
console=ttyO2,115200n8
 
 
defaultdisplay=dvi
 
dvimode=1280x720MR-16@60
 
 
mmcroot=/dev/mmcblk0p2 ro
 
mmcrootfstype=ext4 rootwait fixrtc
 
optargs=console=tty0
 
 
mmc_load_uimage=fatload mmc 0:1 ${address_uimage} ${bootfile}
 
mmc_load_uinitrd=fatload mmc 0:1 ${address_uinitrd} ${bootinitrd}
 
 
expansion=buddy=${buddy} buddy2=${buddy2} camera=${camera}
 
video=vram=${vram} omapfb.mode=${defaultdisplay}:${dvimode} omapdss.def_disp=${defaultdisplay}
 
 
mmcargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate} ${expansion} ${video} root=${mmcroot} rootfstype=${mmcrootfstype}
 
 
loaduimage=run mmc_load_uimage; run mmc_load_uinitrd; echo Booting from mmc ...; run mmcargs; bootm ${address_uimage} ${address_uinitrd}
 
 
 
==== BeagleBone ====
 
 
 
create a new file: uEnv.txt
 
bootfile=uImage
 
bootinitrd=uInitrd
 
address_uimage=0x80300000
 
address_uinitrd=0x81600000
 
 
vram=12MB
 
 
console=ttyO0,115200n8
 
 
defaultdisplay=
 
dvimode=
 
 
mmcroot=/dev/mmcblk0p2 ro
 
mmcrootfstype=ext4 rootwait fixrtc
 
 
rcn_mmcloaduimage=fatload mmc 0:1 ${address_uimage} ${bootfile}
 
mmc_load_uinitrd=fatload mmc 0:1 ${address_uinitrd} ${bootinitrd}
 
 
mmc_args=run bootargs_defaults;setenv bootargs ${bootargs} root=${mmcroot} rootfstype=${mmcrootfstype} ip=${ip_method}
 
 
mmc_load_uimage=run rcn_mmcloaduimage; run mmc_load_uinitrd; echo Booting from mmc ...; run mmc_args; bootm ${address_uimage} ${address_uinitrd}
 
 
 
==== Panda/Panda ES ====
 
 
 
create a new file: uEnv.txt
 
bootfile=uImage
 
bootinitrd=uInitrd
 
address_uimage=0x80300000
 
address_uinitrd=0x81600000
 
 
vram=16MB
 
 
console=ttyO2,115200n8
 
 
defaultdisplay=dvi
 
dvimode=1280x720MR-16@60
 
 
mmcroot=/dev/mmcblk0p2 ro
 
mmcrootfstype=ext4 rootwait fixrtc
 
optargs=console=tty0
 
 
mmc_load_uimage=fatload mmc 0:1 ${address_uimage} ${bootfile}
 
mmc_load_uinitrd=fatload mmc 0:1 ${address_uinitrd} ${bootinitrd}
 
 
video=vram=${vram} omapfb.mode=${defaultdisplay}:${dvimode} omapdss.def_disp=${defaultdisplay}
 
 
mmcargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate} ${video} root=${mmcroot} rootfstype=${mmcrootfstype}
 
 
loaduimage=run mmc_load_uimage; run mmc_load_uinitrd; echo Booting from mmc ...; run mmcargs; bootm ${address_uimage} ${address_uinitrd}
 
 
Umount the Boot Partition:
 
  
  sudo umount ./tmp
+
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
  
== RootFS Partition ==
+
Windows/Mac/Linux gui
Root File System
+
http://etcher.io
  
Mount your SD card's larger root file system partition (assuming /dev/sdX2) and 'untar' the rootfs into it.
+
Linux: (dd)
 +
xzcat am57xx-ubuntu-18.04.4-console-armhf-2020-03-12-2gb.img.xz | sudo dd of=/dev/sdX
  
mkdir -p ./tmp
+
= Method 2: 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 564: 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
 +
sudo apt-cache search linux-image | grep <branch>
 +
sudo apt-get install linux-image-<specific version>
 +
sudo reboot
  
Latest Stable is : https://github.com/RobertCNelson/stable-kernel
+
Latest kernel script
 +
cd /opt/scripts/tools/
 +
git pull
 +
sudo ./update_kernel.sh <OPTIONS>
  
export DIST=oneiric  (options are lucid/maverick/natty/oneiric/precise/squeeze/wheezy)
+
== 3.8.x ==
export ARCH=armel (options are armel/armhf (armhf only for precise))
+
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
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
+
3.8.x BeagleBone/BeagleBone Black FULL Cape Support
 +
--bone-channel --stable
  
== Upgrade X-loader and U-boot ==
+
3.8.x BeagleBone/BeagleBone Black FULL Cape Support + Xenomai
 +
--bone-xenomai-channel --stable
  
Compatible with Old Ax,Bx,Cx BeagleBoards
+
== 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
  
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:
+
4.9.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15
  nand erase 260000 20000
+
  --ti-channel --lts-4_9
  
Requires MMC card..
+
4.9.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15 + RT
 +
--ti-rt-channel --lts-4_9
  
  git clone git://github.com/RobertCNelson/flash-omap.git
+
  4.9.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15 + Xenomai
  cd flash-omap
+
  --ti-xenomai-channel --lts-4_9
  
For the Beagle Bx
+
== 4.14.x-ti ==
  sudo ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_bx
+
  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
  
For the Beagle Cx
+
  4.14.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15
  sudo ./mk_mmc.sh --mmc /dev/sdX --uboot beagle_cx
+
--ti-channel --lts-4_14
  
1: Plug Serial Cable in and Start Serial terminal program
+
  4.14.x-ti BeagleBone/BeagleBone Black/BeagleBoard-X15 + RT
2: Place MMC card in Beagle
+
  --ti-rt-channel --lts-4_14
3: Push and Hold User Button
 
  4: Plug-in Power
 
  5: Wait for U-boot countdown to finish, 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:
+
== Mainline (4.9.x lts) ==
sudo ./mk_mmc.sh --probe-mmc
 
  
You should see something like
+
4.9.x BeagleBone/BeagleBone Black
 +
--bone-kernel --lts-4_9
  
  Are you sure? I Don't see [/dev/idontknow], here is what I do see...
+
  4.9.x BeagleBone/BeagleBone Black + RT
   
+
  --bone-rt-kernel --lts-4_9
fdisk -l:
 
Disk /dev/sda: 500.1 GB, 500107862016 bytes '''<- x86 Root Drive'''
 
Disk /dev/mmcblk0: 3957 MB, 3957325824 bytes '''<- MMC/SD card'''
 
 
mount:
 
/dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0) '''<- x86 Root Partition'''
 
  
* In this example, we can see via mount, '''/dev/sda1''' is the x86 rootfs, therefore '''/dev/mmcblk0''' is the other drive in the system, which is the MMC/SD card that was inserted and should be used by ./mk_mmc.sh...
+
== Mainline (4.14.x lts) ==
  
== SGX Video Acceleration ==
+
4.14.x BeagleBone/BeagleBone Black
 +
--bone-kernel --lts-4_14
  
NOTE: this only works on BeagleBoard hardware, BeagleBone stuff is in development..
+
4.14.x BeagleBone/BeagleBone Black + RT
 +
--bone-rt-kernel --lts-4_14
  
Requirements: stable-kernel (the Demo Images hosted on rcn-ee.net meet this requirement)
+
Reboot with your new Kernel Image.
  https://github.com/RobertCNelson/stable-kernel
 
  
Note: Due to a bug (seems to only effect older Beagle Bx/Cx boards, use v3.0.8-x3 based kernels)
+
== Xorg Drivers ==
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 ===
+
Script:
 +
cd /opt/scripts/tools/
 +
git pull
  
Download the latest version of the "create_sgx_package.sh" script
+
BeagleBoard/PandaBoard:
  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-omapdrm.sh
  2.6.38+
 
wget https://github.com/RobertCNelson/stable-kernel/raw/master/create_sgx_package.sh
 
  
Make script executable
+
BeagleBone/BeagleBone Black:
  chmod a+x ./create_sgx_package.sh
+
cd /opt/scripts/tools/graphics/
 +
  ./ti-tilcdc.sh
  
Run script
+
== SGX Drivers ==
./create_sgx_package.sh
 
  
After Successfully running:
+
=== SGX BeagleBone/BeagleBone Black ===
  
:~/temp$ ls
+
Note, these are FBDEV only, no xorg/x11/etc...
create_sgx_package.sh
 
GFX_X_XX_XX_XX_libs.tar.gz                      : -> Copy to Beagle (System Libs)
 
GFX_Linux_SDK.tar.gz                            : -> Copy to Beagle (DEMO's)
 
Graphics_SDK_setuplinux_X_XX_XX_XX.bin
 
SDK
 
SDK_BIN
 
  
=== Beagle: GFX_*_libs.tar.gz ===
+
Install the "4.1.x" lts/bone kernel:
 +
http://elinux.org/BeagleBoardUbuntu#Mainline_.28lts.29
  
tar xf GFX_4_00_00_01_libs.tar.gz  (extracts install-SGX.sh and run-SGX.sh)
+
Build SGX userspace for 4.1.x (must be done on an x86, due to the TI 5.01.01.02 blob extractor)
  ./install-SGX.sh (copies necessary SGX libs and startup script)
+
  git clone https://github.com/RobertCNelson/bb-kernel.git
  ./run-SGX.sh (force run the new init script, or you can just reboot...)
+
cd bb-kernel/
 +
  git checkout origin/am33x-v4.1 -b tmp-sgx
 +
./sgx_create_package.sh
  
On Successful install:
+
Copy ./deploy/GFX_5.01.01.02.tar.gz to BeagleBone/BeagleBone Black and install
  Stopping PVR
+
  sudo tar xfv GFX_5.01.01.02.tar.gz -C /
  Starting PVR
+
  cd /opt/gfxinstall/
  Starting SGX fixup for ES2.x (or ES3.x) (or ES5.x xM)
+
  sudo ./sgx-install.sh
 
 
Reboot for good measure (Maverick's Alpha-1 needs this....)
 
 
  sudo reboot
 
  sudo reboot
  
=== Beagle: GFX_Linux_SDK.tar.gz ===
+
Verify omaplfb & pvrsrvkm loaded
 +
debian@arm:~$ lsmod | grep omaplfb
 +
omaplfb                12065  0
 +
pvrsrvkm              178782  1 omaplfb
  
tar xf GFX_Linux_SDK.tar.gz
+
== Xorg Drivers ==
cd GFX_Linux_SDK
 
tar xf OGLES.tar.gz
 
  
=== Test SGX with a DEMO ===
+
Script:
 +
cd /opt/scripts/tools/
 +
git pull
  
cd OGLES/SDKPackage/Binaries/CommonX11/Demos/EvilSkull
+
BeagleBoard/PandaBoard:
./OGLESEvilSkull
+
  cd /opt/scripts/tools/graphics/
 
+
  ./ti-omapdrm.sh
=== Trouble Shooting ===
 
 
 
sudo rm /etc/powervr-esrev
 
sudo depmod -a omaplfb
 
sudo /etc/init.d/pvr restart
 
 
 
== DSP ==
 
 
 
=== gst-dsp ===
 
 
 
The following Gstreamer elements will be installed:
 
 
 
  $ gst-inspect | grep dsp
 
  dvdspu:  dvdspu: Sub-picture Overlay
 
  dsp:  dspdummy: DSP dummy element
 
  dsp:  dspvdec: DSP video decoder
 
  dsp:  dspadec: DSP audio decoder
 
  dsp:  dsph263enc: DSP video encoder
 
  dsp:  dspmp4venc: DSP MPEG-4 video encoder
 
  dsp:  dspjpegenc: DSP video encoder
 
  dsp:  dsph264enc: DSP video encoder
 
  dsp:  dspvpp: DSP VPP filter
 
  dsp:  dspipp: DSP IPP
 
 
 
Please note that h264 encoder (dsph264enc) will not work because of missing h264venc_sn.dll64P DSP part. [http://groups.google.com/group/omapdiscuss/msg/76d928726656c5fe According to this message], it is not available due to a licensing restriction.
 
 
 
Requirements: Kernel built with: "CONFIG_TIDSPBRIDGE=m", for reference, here is what rcn-ee.net's image/deb's are configured for:
 
voodoo@beagle-xma-512mb:~$ zcat /proc/config.gz | grep TIDSP
 
CONFIG_TIDSPBRIDGE=m
 
CONFIG_TIDSPBRIDGE_MEMPOOL_SIZE=0x600000
 
# CONFIG_TIDSPBRIDGE_DEBUG is not set
 
CONFIG_TIDSPBRIDGE_RECOVERY=y
 
# CONFIG_TIDSPBRIDGE_CACHE_LINE_CHECK is not set
 
CONFIG_TIDSPBRIDGE_WDT3=y
 
CONFIG_TIDSPBRIDGE_WDT_TIMEOUT=5
 
# CONFIG_TIDSPBRIDGE_NTFY_PWRERR is not set
 
# CONFIG_TIDSPBRIDGE_BACKTRACE is not
 
 
 
Download the latest version of the "create_dsp_package.sh" script
 
wget https://github.com/RobertCNelson/stable-kernel/raw/master/create_dsp_package.sh
 
 
 
Make script executable
 
chmod a+x ./create_dsp_package.sh
 
 
 
Package script:
 
./create_dsp_package.sh
 
 
 
Copy DSP_Install_libs.tar.gz to beagle
 
 
 
Setup network...
 
 
 
Extract:
 
tar xf DSP_Install_libs.tar.gz
 
 
 
Install
 
./install-DSP.sh
 
 
 
Build gst-dsp stuff..
 
./install-gst-dsp.sh
 
 
 
Start dspbridge (or just reboot)
 
sudo /etc/init.d/dsp start
 
 
 
Test dspbridge
 
sudo dsp-test
 
 
 
Playbin:
 
sudo gst-launch playbin2 uri=file://(file)
 
 
 
Example: (using http://www.bigbuckbunny.org/index.php/download/ 854x480 mp4 )
 
Note: seems broken in ubuntu precise armhf...
 
 
 
sudo gst-launch playbin2 uri=file:///home/USER/big_buck_bunny_480p_surround-fix.avi
 
 
 
Screenshot: (on my xm it's a little jerky at the moment, investigating..)
 
http://rcn-ee.net/bugs/dsp/dsp_v3.2.1-x2-test.jpg
 
 
 
== Xorg omapfb Drivers ==
 
 
 
By default Ubuntu will try to use the FBDEV video driver, however for the beagleboard we can take advantage of a more software optimized driver (still not using the sgx video hardware) using the NEON extensions of the Cortex-A8 core.
 
 
 
cat /var/log/Xorg.0.log | grep FBDEV
 
(II) FBDEV: driver for framebuffer: fbdev
 
(II) FBDEV(0): using default device
 
(II) FBDEV(0): Creating default Display subsection in Screen section
 
(==) FBDEV(0): Depth 16, (==) framebuffer bpp 16
 
(==) FBDEV(0): RGB weight 565
 
 
 
Login into Ubuntu and open a new terminal, xorg has to be running..
 
 
 
xvinfo -display :0.0
 
X-Video Extension version 2.2
 
screen #0
 
  no adaptors present
 
 
 
=== Drivers ===
 
 
 
Note: These are built with neon optimizations: http://git.debian.org/?p=collab-maint/xf86-video-omapfb.git;a=blob;f=debian/rules;h=c2f0d5391c96c5abb60b1e691ad86bb27e0c17d8;hb=HEAD  (line 48/49)
 
 
 
Lucid:
 
sudo apt-get install xserver-xorg-video-omap3
 
 
 
To verify it was correctly installed, reboot and:
 
 
 
cat /var/log/Xorg.0.log | grep omapfb
 
(II) LoadModule: "omapfb"
 
(II) Loading /usr/lib/xorg/modules/drivers//omapfb_drv.so
 
(II) Module omapfb: vendor="X.Org Foundation"
 
(II) omapfb: Driver for OMAP framebuffer (omapfb) and external LCD controllers:
 
(WW) Error opening /sys/devices/platform/omapfb/ctrl/name: No such file or directory
 
(II) omapfb(0): VideoRAM: 1800KiB (SDRAM)
 
(II) omapfb(0): Creating default Display subsection in Screen section
 
(**) omapfb(0): Depth 16, (--) framebuffer bpp 16
 
(==) omapfb(0): RGB weight 565
 
(==) omapfb(0): Default visual is TrueColor
 
(--) omapfb(0): Virtual size is 1280x720 (pitch 1280)
 
(**) omapfb(0):  Built-in mode "current"
 
(==) omapfb(0): DPI set to (96, 96)
 
(II) omapfb(0): DPMS enabled
 
(II) omapfb(0): Video plane capabilities:
 
(II) omapfb(0): Video plane supports the following image formats:
 
(II) omapfb(0): XVideo extension initialized
 
 
 
Login into Ubuntu and open a new terminal, xorg has to be running..
 
 
 
xvinfo -display :0.0
 
X-Video Extension version 2.2
 
screen #0
 
  Adaptor #0: "OMAP XV adaptor"
 
    number of ports: 1
 
    port base: 56
 
    operations supported: PutImage
 
    supported visuals:
 
      depth 16, visualID 0x21
 
    number of attributes: 1
 
    etc..
 
 
 
== Changing DVI output resolution ==
 
 
 
Ubuntu 10.10 above defaults to a resolution of 1284x768@16.  This is set in the boot.cmd file in the boot partition of the SD card.  To change the resolution the DVI output, edit boot.cmd accordingly then recreate the boot.scr file by:
 
 
 
mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "Ubuntu 10.10" -d ./boot.cmd ./boot.scr
 
 
 
Then reboot the BeagleBoard
 
 
 
== S-Video ==
 
''(For configuring S-Video on Angstrom, click [[BeagleBoardAngstrom#Configuring_uEnv.txt_to_set_s-video_as_the_default_display|here]])''.
 
 
 
===Process for setting up S-Video===
 
 
 
S-video is tested to be working on 2.6.35-rc5-dl9. BeagleBoard s-video output has traditionally been enabled by "using bootargs (boot arguments) at uboot". In newer versions of the BeagleBoard, the developers have made things easier by instructing u-boot to look for a .scr file about a dozen lines long that is called cmd.boot.scr, and then follow said parameters. In Angstrom, no boot.scr file is needed, instead, an even easier system is used, where a simple editable .txt file called uEnv.txt containing these parameters suffices (Env is for "environment"). For some reason, in the Ubuntu download files, typically there a bit of convoluted process where uEnv.txt is called up, uEnv.txt says "Go read conf.boot.scr", and cmd.boot.scr sets up the s-video.
 
 
 
To make cmd.boot.scr, create a text file named cmd.boot, then convert it into a .scr file with mkimage by running the following commands on the terminal:
 
 
 
First, you will probably need to get mkimage with apt-get. Run
 
 
 
    sudo apt-get install mkimage
 
 
 
Next, convert your cmd.boot.scr
 
 
 
    mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n 'Execute uImage' -d boot.cmd boot.scr
 
 
 
===Bootargs: make this cmd.boot to set s-video===
 
 
 
* NTSC
 
 
 
    omapfb.mode='''tv:ntsc'''
 
    omapdss.def_disp='''tv'''
 
 
 
Bootargs that has been validated.
 
 
 
    setenv bootargs 'console=tty0 console=ttyO2,115200n8 root=/dev/mmcblk0p2 rootwait ro vram=12M omapfb.mode=tv:ntsc omapdss.def_disp=tv
 
    fixrtc buddy=unknown'
 
 
 
===Screen cutoff problem===
 
 
 
 
 
NTSC resolution is supposed to be 640x480. However the edge bands around the TV screen differ from TV to TV. Output of '''fbset''' shown below:
 
 
 
    mode "720x482-30"
 
        # D: 13.500 MHz, H: 15.734 kHz, V: 29.970 Hz
 
        geometry 720 482 720 482 32
 
        timings 74074 16 58 6 31 64 6
 
        rgba 8/16,8/8,8/0,0/0
 
    endmode
 
 
 
Depending on your TV device, and what desktop you are running a certain amount of screen cutoff is likely to occur. This is called [http://en.wikipedia.org/wiki/Overscan Overscan]. Typically, around 5-10% of the left and right edges of display are off the screen (using Ubuntu with xfce). This seems to be due to the fact that there is only one display resolution that is set for NTSC: <!-- I don't know about PAL--> 720 X 482. It is not possible to change this setting in the xfce4 Settings Manager like one would normally be able to do, because other options are greyed out/do not exist. Normally, even if the Settings Manager did not allow for it, a different resolution setting could be obtained by editing the xorg.conf file in /etc/X11/xorg.conf-4, or some similar place. HOWEVER there is no xorg.conf file in the Beagle version of xfce. xrandr shows the display is set to the minimum of 720x574. Adding an xorg.conf does not fix the problem, because Beagle takes its (analog) display resolution settings directly from the display driver, where 720 X 480 (720 X 574 for PAL <!-- This I gather, but I really don't know--> ) is hard coded in.  
 
 
 
An inelegant but usable workaround for the xfce desktop environment is simply to create vertical and horizontal panels that fill up the space that is cut off on the screen. This is not a complete solution, but at least it will prevent maximized windows from going off into nowhere land.
 
 
 
 
 
Truly fixing this would involve going into the display driver and reprogramming it to include additional S-video settings besides just NTSC and PAL. Specifically, to make the whole framebuffer fit on the screen you would need to adjust the overlay in the display driver, the OMAP DSS2. (Didn't test this yet. Some pointers from the driver's documentation below)
 
 
 
    /sys/devices/platform/omapdss/overlay? directory:
 
    enabled 0=off, 1=on
 
    input_size width,height (ie. the framebuffer size)
 
    manager Destination overlay manager name
 
    name
 
    output_size width,height
 
    position x,y
 
    screen_width width
 
    global_alpha  global alpha 0-255 0=transparent 255=opaque
 
 
 
== Building Kernel ==
 
 
 
https://github.com/RobertCNelson/stable-kernel
 
 
 
Download SRC
 
  git clone git://github.com/RobertCNelson/stable-kernel.git
 
 
 
Build Kernel
 
./build_kernel.sh
 
 
 
Optional Building Deb File
 
./build_deb.sh
 
  
 +
BeagleBone/BeagleBone Black:
 +
cd /opt/scripts/tools/graphics/
 +
./ti-tilcdc.sh
  
 
= Swapfile =
 
= Swapfile =
Line 908: 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 256Mb and 512Mb). Some system programs like apt-get will only run properly when some swap space is present (due to 256Mb not being enough RAM).
+
On the Beagleboard you should expect to require a swap file given the limitation of how little RAM is available (between 256&nbsp;MB and 512&nbsp;MB). Some system programs like apt-get will only run properly when some swap space is present (due to 256&nbsp;MB not being enough RAM).
  
Some images such as those from Linaro.org do not come with a swap partition or any swap space allocated.
+
Some images (such as those from Linaro.org) do not come with a swap partition or any swap space allocated.
  
Under Linux swap space can be either a dedicated partition or a single file. Both can be mounted as swap which the OS can access.
+
Under Linux, swap space can be either a dedicated partition or a swap file. Both can be mounted as swap which the OS can access.
  
 
=== Creating a Swapfile ===
 
=== Creating a Swapfile ===
  
The following commands will create a 1 gigabyte file, lock access to only root, format it as swap and then advertise it to the OS.
+
The following commands will create a 1 GB file, limit access only to root, format it as swap and then make it available to the OS:
  
 
  sudo mkdir -p /var/cache/swap/   
 
  sudo mkdir -p /var/cache/swap/   
Line 924: 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 =
  
== 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 955: 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 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 963: 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 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 975: Line 542:
  
 
=== 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 993: 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 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 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.