RPi building and installing OpenELEC - Revision history

Ghans at 18:50, 18 June 2012

2012-06-18T18:50:26Z

Fabi280: fixed path of the bootloader files

2012-05-27T07:21:33Z

fixed path of the bootloader files

Luttermann: "sudo echo" does not do anything! Corrected the command to use "sudo tee"

2012-05-18T17:08:02Z

"sudo echo" does not do anything! Corrected the command to use "sudo tee"

Greg117: /* Building OpenELEC */

2012-05-11T06:37:44Z

‎Building OpenELEC

RoSha: /* Building OpenELEC */

2012-05-10T15:47:07Z

‎Building OpenELEC

RoSha: /* Installing OpenELEC to the SD Card */

2012-05-10T15:41:33Z

‎Installing OpenELEC to the SD Card

RoSha: /* Building OpenELEC */

2012-05-10T15:34:53Z

‎Building OpenELEC

Frying fish: /* Cross Compiling and Build Systems */

2012-05-07T14:45:11Z

‎Cross Compiling and Build Systems

Sraue: /* Installing OpenELEC to the SD Card */ update kernel command line parameters and cmdline.txt creation

2012-05-02T09:30:07Z

‎Installing OpenELEC to the SD Card: update kernel command line parameters and cmdline.txt creation

Sraue: /* Installing OpenELEC to the SD Card */ cosmetics

2012-05-01T05:56:59Z

‎Installing OpenELEC to the SD Card: cosmetics

← Older revision		Revision as of 18:50, 18 June 2012
Line 163:		Line 163:
	* Issues (bug) tracker: https://github.com/OpenELEC/OpenELEC.tv/issues		* Issues (bug) tracker: https://github.com/OpenELEC/OpenELEC.tv/issues
	* IRC chat support: http://openelec.tv/find-help/chat		* IRC chat support: http://openelec.tv/find-help/chat
		+
		+	[[Category:RaspberryPi]]

@@ Line 113: / Line 113: @@
 Next we install the bootloader from the “bcm2835-driver” package. This is located in the project build folder. If you have downloaded pre-built files from elsewere the bootloader files can also be downloaded from here: [https://github.com/raspberrypi/firmware/tree/master/boot https://github.com/raspberrypi/firmware/tree/master/boot]. The *start.elf file controls how Raspberry Pi’s allocates RAM between OS and Video. The arm128_start.elf file allocates 128MB to each. The commands below assume the “System” partition has mounted as /media/System but some distros mount removable devices to other locations, e.g. /mnt/System.
-   sudo cp build.OpenELEC-RPi.arm-devel/bcm2835-driver-*/boot/arm128_start.elf /media/System/start.elf
+   sudo cp build.OpenELEC-RPi.arm-devel/bcm2835-bootloader-*/arm128_start.elf /media/System/start.elf
-   sudo cp build.OpenELEC-RPi.arm-devel/bcm2835-driver-*/boot/bootcode.bin /media/System/
+   sudo cp build.OpenELEC-RPi.arm-devel/bcm2835-bootloader-*/bootcode.bin /media/System/
-   sudo cp build.OpenELEC-RPi.arm-devel/bcm2835-driver-*/boot/loader.bin /media/System/
+   sudo cp build.OpenELEC-RPi.arm-devel/bcm2835-bootloader-*/loader.bin /media/System/
 Next we install kernel and system files from ~/OpenELEC.tv/target to the SD card. The kernel and system files have long names that identify the build kind, date and rNumber. They need to be renamed as we copy them. The system file must be renamed to SYSTEM (all uppercase) and the kernel file must be renamed to kernel.img (all lowercase, and not KERNEL).

@@ Line 124: / Line 124: @@
 Next we create a “cmdline.txt” file that contains bootloader parameters:
-   sudo echo "boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 ssh quiet" > /media/System/cmdline.txt
+   echo "boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 ssh quiet" | sudo tee /media/System/cmdline.txt
 To explain the boot parameters:

@@ Line 45: / Line 45: @@
 To now create an OpenELEC image for Raspberry Pi we need to tell the build-system the project and architecture to build for. The Raspberry Pi project uses the "arm" architecture so the “make” command to start the build process with is:
-   PROJECT=RPi ARCH=arm make
+   PROJECT=RPi ARCH=arm make release
 That’s all that’s needed! ..but make sure you type the command EXACTLY as shown here as the make command is case-sensitive.

@@ Line 40: / Line 40: @@
    git pull origin master
-As this will update all references to the latest ones and prevent errors during complication.
+This will update all references to the latest ones and prevent errors during complication.
 This will also fix any '404' errors that occur due to outdated references to the Confluence Skin similar to:
 <pre>http://sources.openelec.tv/devel/xbmc-rpi-theme-Confluence-xxxxxxx.tar.xz</pre>

@@ Line 120: / Line 120: @@
    sudo cp target/OpenELEC-RPi.arm-devel-20120424035956-r10695.system /media/System/SYSTEM
    sudo cp target/OpenELEC-RPi.arm-devel-20120424035956-r10695.kernel /media/System/kernel.img
 Next we create a “cmdline.txt” file that contains bootloader parameters:

@@ Line 36: / Line 36: @@
 ==Building OpenELEC==
-To create an OpenELEC image for Raspberry Pi we need to tell the build-system the project and architecture to build for. The Raspberry Pi project uses the "arm" architecture so the “make” command to start the build process with is:
+Before you start building it is recommended to update all references, by typing:
    PROJECT=RPi ARCH=arm make

@@ Line 21: / Line 21: @@
 * There is no dependency on the particular versions of compiler, libc and Linux kernel headers installed on the build-host. We cross-compile our own versions to ensure we always produce consistent and properly built software packages.
 * It allows you to run any Linux distribution as your build system. No matter what your personal preference the resulting OpenELEC image will always be the same.
-* It allows us to use the full power of the build-host. Like most ARM devices the Raspberry Pi does not have super fast CPU’s or lots of memory and it uses low-cost but slow USB and flash-card memory for storage; making it unsuitable for native building of large and complex software. Other Linux distributions targetting Raspberry Pi plan to use emulator tools like QEMU that were designed to test and run small software projects to build a full Operating System and it scares us to think how slow and error prone this will be. Even a highly optimised “minimalist” OS like OpenELEC involves the creation of ~500,000 small files during compilation so it’s simple common sense to cross compile and leverage the significantly better resources of a fast local build-host.
+* It allows us to use the full power of the build-host. Like most ARM devices the Raspberry Pi does not have super fast CPUs or lots of memory and it uses low-cost but slow USB and flash-card memory for storage; making it unsuitable for native building of large and complex software. Other Linux distributions targetting Raspberry Pi plan to use emulator tools like QEMU that were designed to test and run small software projects to build a full Operating System and it scares us to think how slow and error prone this will be. Even a highly optimised “minimalist” OS like OpenELEC involves the creation of ~500,000 small files during compilation so it’s simple common sense to cross compile and leverage the significantly better resources of a fast local build-host.
-−
 ==How to get the OpenELEC sources?==

@@ Line 115: / Line 115: @@
 Next we create a “cmdline.txt” file that contains bootloader parameters:
-   sudo echo "dwc_otg.lpm_enable=0 root=/dev/ram0 rdinit=/init boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 ssh quiet" > /media/System/cmdline.txt
+   sudo echo "boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 ssh quiet" > /media/System/cmdline.txt
 To explain the boot parameters:
 * '''boot=/dev/mmcblk0p1''' tells OpenELEC the partition which contains the kernel.img and SYSTEM file. It is also possible to use partition labels (boot=LABEL=System) or UUID (boot=UUID=<insert_your_uuid>) or to boot over the network (PXE)
 * '''disk=/dev/mmcblk0p2''' tells OpenELEC the “Storage” partition. It can also use partition labels (disk=LABEL=Storage) or UUID (disk=UUID=<insert_your_uuid>) or boot over the network (PXE)
 * '''ssh''' tells the system to always start the embedded SSH server to enable remote console access. It is optional, but will be useful on a “development” system. The SSH username is “root” and the password is “openelec” i.e.
    ssh root@192.168.2.1
 * '''quiet''' hides kernel messages from the screen during boot, this should be used unless you need to see kernel output for debugging.
 * '''nosplash''' prevents the OpenELEC splash screen from loading, shaving a few ms from the boot process. This can be useful for debugging if you need to see some of the init script actions that are recorded via the splash during boot.

@@ Line 134: / Line 134: @@
    total 91626
    drwx------. 2 sraue sraue    16384 Apr 25 17:09 .
-   drwxr-xr-x. 4 root    root          80 Apr 25 16:58 ..
+   drwxr-xr-x. 4 root  root        80 Apr 25 16:58 ..
    -rw-r--r--. 1 sraue sraue 83316736 Apr 25 17:00 SYSTEM
    -rw-r--r--. 1 sraue sraue    16528 Apr 25 16:59 bootcode.bin