#ADDING RASPBERRY PI CODECS TO OPENELEC HOW TO#

The tool that actually sets the RaspberryPi in this mode is called rpiboot.Īfter executing it, we deploy the zImage into the RaspberryPi /media/$/boot/config.txt to set the firmware directive kernel=zImage. Thanks to the USB mass storage mode of the Raspberry Pi it is quite straightforward to update the kernel as it allows to mount the board eMMC partitions on the host system, and update whichever files we want. $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-j4 zImage $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcm2709_defconfig So we start our work by grabbing the Linux kernel source code from a the rpi-5.4.y provided by the Raspberry Pi Linux kernel repository:Īfter installing an appropriate ARM 32-bit cross-compilation toolchain, we’re ready to configure and build the kernel:

While Bootlin normally has a preference for using the upstream Linux kernel, for this project, we decided to keep using the Linux kernel fork provided by Raspberry Pi on Github, which is used by Raspberry Pi OS Lite. However, for this project, we obviously need to customize the Linux kernel configuration, so we had to build our own kernel. Our customer is using the RaspberryPi OS Lite, which is a Debian-based system, coming with its pre-compiled Linux kernel image. Building and loading an upstream RPi Linux

#ADDING RASPBERRY PI CODECS TO OPENELEC HOW TO#

We take this opportunity to share some insights on how to introduce new hardware support on RaspberryPi platforms, by taking advantage of the Raspberry Pi specific Device Tree overlay mechanism.

We recently had the chance to work on a customer project that involved the RaspberryPi Compute Module 3, with custom peripherals attached: a Microchip WILC1000 WiFi chip connected on SDIO, and a SGTL5000 audio codec connected over I2S/I2C.

Adding raspberry pi codecs to openelec