d0b055239e
The gpu_mem option is not using the proper option argument which causes sed to fail. + case "${arg}" in + gpu_mem=ome/gportay/output-rpi3-qtwe/images + sed -e '/^ome/gportay/output-rpi3-qtwe/images=/s,=.*,=ome/gportay/output-rpi3-qtwe/images,' -i /home/gportay/output-rpi3-qtwe/images/rpi-firmware/config.txt sed: -e expression #1, char 8: extra characters after command + case "${arg}" in + gpu_mem=ome/gportay/output-rpi3-qtwe/images + sed -e '/^ome/gportay/output-rpi3-qtwe/images=/s,=.*,=ome/gportay/output-rpi3-qtwe/images,' -i /home/gportay/output-rpi3-qtwe/images/rpi-firmware/config.txt sed: -e expression #1, char 8: extra characters after command The issue comes from the use of $1 instead of $arg to extract the gpu_mem value. $1 is the $(BINARIES_DIR) which leads to a sed expression error. Also, it adds the error flag to the shell script to prevent from such situation and terminate the build in error. Signed-off-by: Gaël PORTAY <gael.portay@savoirfairelinux.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> |
||
---|---|---|
.. | ||
genimage-raspberrypi0.cfg | ||
genimage-raspberrypi2.cfg | ||
genimage-raspberrypi3-64.cfg | ||
genimage-raspberrypi3.cfg | ||
genimage-raspberrypi.cfg | ||
post-build.sh | ||
post-image.sh | ||
readme.txt |
Raspberry Pi Intro ===== These instructions apply to all models of the Raspberry Pi: - the original models A and B, - the "enhanced" models A+ and B+, - the model B2 (aka Raspberry Pi 2) - the model B3 (aka Raspberry Pi 3). How to build it =============== Configure Buildroot ------------------- There are two RaspberryPi defconfig files in Buildroot, one for each major variant, which you should base your work on: For models A, B, A+ or B+: $ make raspberrypi_defconfig For model Zero (model A+ in smaller form factor): $ make raspberrypi0_defconfig For model 2 B: $ make raspberrypi2_defconfig For model 3 B: $ make raspberrypi3_defconfig 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/ +-- bcm2708-rpi-b.dtb [1] +-- bcm2708-rpi-b-plus.dtb [1] +-- bcm2709-rpi-2-b.dtb [1] +-- bcm2710-rpi-3-b.dtb [1] +-- boot.vfat +-- rootfs.ext4 +-- rpi-firmware/ | +-- bootcode.bin | +-- cmdline.txt | +-- config.txt | +-- fixup.dat | +-- start.elf | `-- overlays/ [2] +-- sdcard.img `-- zImage [1] Not all of them will be present, depending on the RaspberryPi model you are using. [2] Only for the Raspberry Pi 3 Model (overlay pi3-miniuart-bt is needed to enable the RPi3 serial console otherwise occupied by the bluetooth chip). Alternative would be to disable the serial console in cmdline.txt and /etc/inittab. How to write the SD card ======================== Once the build process is finished you will have an image called "sdcard.img" in the output/images/ directory. Copy the bootable "sdcard.img" onto an SD card with "dd": $ sudo dd if=output/images/sdcard.img of=/dev/sdX Insert the SDcard into your Raspberry Pi, and power it up. Your new system should come up now and start two consoles: one on the serial port on the P1 header, one on the HDMI output where you can login using a USB keyboard.