23da43ae12
This is an example of a Device-Tree-enabled Raspberry Pi defconfig. We have to use a 3.18-based kernel for that, but there are a few limitations: - we can not use the minimalist RPi defconfig bundled with the kernel, namely bcmrpi_quick_defconfig, because it is not DT-enabled, and sets CONFIG_ARM_PATCH_PHYS_VIRT to 'n', which prompts a value for CONFIG_PHYS_OFFSET, as it as no default for the bcm familly; - most importantly, the rpi-3.18.y branch is constantly rebased, so there is no guarantee that the sha1 I use today will still be usable in the long term. Using the name of hte branch is not better either. So, we bundle our own DT-enabled linux defconfig that is based on bcmrpi_quick_defconfig, with just CONFIG_ARM_PATCH_PHYS_VIRT set and the Device TRee enabled. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> |
||
---|---|---|
.. | ||
linux-3.18-rpi-dt.defconfig | ||
readme.txt |
RaspberryPi Intro ===== To be able to use your RaspberryPi board with the images generated by Buildroot, you have to choose whether you will use: * Volatile rootfs in RAM (the rootfs is an initramfs) or * Persistent rootfs on the SDCard Also, a good source of information is http://elinux.org/R-Pi_Hub How to build it =============== Configure Buildroot ------------------- The raspberrypi_defconfig configuration is a minimal configuration with all that is required to bring the Raspberry Pi. You should base your work on this defconfig: $ make raspberrypi_defconfig If you want to use a persistent rootfs, skip to "Build the rootfs", below. For a volatile rootfs, you have to slightly adjust the configuration: $ make menuconfig * Select "Filesystem images" * Select "initial RAM filesystem linked into linux kernel" You may also deselect "tar the root filesystem". Build the rootfs ---------------- Note: you will need to have access to the network, since Buildroot will download the packages' sources. You may now build your rootfs with: $ make (This may take a while; consider getting yourself a coffee ;-) ) Result of the build ------------------- After building, you should obtain this tree: output/images/ +-- rootfs.tar +-- rpi-firmware | +-- bootcode.bin | +-- config.txt | +-- fixup.dat | `-- start.elf `-- zImage Note for Volatile: rootfs.tar will only be there if you kept "tar the root filesystem" option selected in "Filesystem images". Prepare you SDCard ================== For more information, visit http://elinux.org/RPi_Advanced_Setup#Advanced_SD_card_setup In summary, your SDCard must have first partition in fat32 and marked bootable. Create the required partitions: - for a persistent rootfs, 10MiB is enough memory for the boot fat32 partition, and a second partition is required for the root filesystem - for a volatile rootfs, 50MiB is required for the boot fat32 partition Note: You can create any number of partitions you desire, the only requirement is that the first partition must be using fat32 and be bootable. Mount the partitions (adjust 'sdX' to match your SDcard device): $ sudo mount /dev/sdX1 /mnt/mountpointboot $ sudo mount /dev/sdX2 /mnt/mountpointroot (only for persistent rootfs) Install the binaries to the SDCard ---------------------------------- At the root of the boot partition, the RaspberryPi must find the following files: * bootcode.bin * config.txt * fixup.dat * start.elf * zImage For example: $ cp output/images/rpi-firmware/* /mnt/mountpointboot $ cp output/images/zImage /mnt/mountpointboot Note: The kernel image file name is defined in config.txt like this: kernel=zImage If you use a volatile rootfs, Skip to "Finish", below. For a persistent rootfs, there are further steps to do. Extract (as root!) the contents of the rootfs.tar archive into the second partition you created above: $ sudo tar xf rootfs.tar -C /mnt/mountpointroot Finish ====== Unmount all the partitions: $ sudo umount /mnt/mountpointboot $ sudo umount /mnt/mountpointroot (only for persistent rootfs) And eject your SDcard from your computer SDcard reader. Insert the SDcard into your Raspberry Pi, and power it up. Your new system should come up, now.