aboutsummaryrefslogtreecommitdiffstats
path: root/classes/sdcard_image-rpi.bbclass
AgeCommit message (Collapse)Author
2024-02-22sdcard_image-rpi.bbclass: include ${IMAGE_NAME_SUFFIX} directly in both ↵Martin Jansa
${IMAGE_NAME} and ${IMAGE_LINK_NAME} * Adjust to https://git.openembedded.org/openembedded-core/commit/?id=26d97acc71379ab6702fa54a23b6542a3f51779c * ${IMAGE_NAME}${IMAGE_NAME_SUFFIX} is almost always used together already and when they aren't it's usually because of hardcoded '.rootfs' suffix * it's a bit strange, because ${IMAGE_NAME_SUFFIX} is applied after the version from ${IMAGE_VERSION_SUFFIX}, if we move it to ${IMAGE_LINK_NAME} then it will be applied before the version and ${IMAGE_LINK_NAME} will be just the version-less symlink to latest built version. * it's not added to INITRAMFS_IMAGE_NAME as it assumes that all images used as initramfs will set IMAGE_NAME_SUFFIX to empty. Many already do as shown bellow, but you might need to extend this list in your layer. * without this fix, build with: IMAGE_FSTYPES:rpi = "rpi-sdimg.gz" will fail due to duplicated .rootfs suffix as shown in: http://errors.yoctoproject.org/Errors/Details/754267/ 130023424 bytes (130 MB, 124 MiB) copied, 0.0706353 s, 1.8 GB/s gzip: skipping: core-image-minimal-raspberrypi4-64.rootfs-20240222111049.rpi-sdimg does not exist WARNING: TOPDIR/tmp-glibc/work/raspberrypi4_64-oe-linux/core-image-minimal/1.0/temp/run.do_image_rpi_sdimg.1238835:263 exit 1 from 'gzip -f -9 -n -c --rsyncable core-image-minimal-raspberrypi4-64.rootfs-20240222111049.rpi-sdimg > core-image-minimal-raspberrypi4-64.rootfs-20240222111049.rpi-sdimg.gz' OE raspberrypi4-64@ /OE/build/oe-core/tmp-glibc/work/raspberrypi4_64-oe-linux/core-image-minimal/1.0/deploy-core-image-minimal-image-complete $ ll total 305612 drwxr-xr-x 2 martin martin 4096 Feb 22 12:12 ./ drwxr-xr-x 17 martin martin 4096 Feb 22 12:12 ../ -rw-r--r-- 1 martin martin 130023424 Feb 22 12:12 core-image-minimal-raspberrypi4-64.rootfs-20240222111049.ext3 -rw-r--r-- 1 martin martin 3535 Feb 22 12:12 core-image-minimal-raspberrypi4-64.rootfs-20240222111049.manifest -rw-r--r-- 1 martin martin 184549376 Feb 22 12:12 core-image-minimal-raspberrypi4-64.rootfs-20240222111049.rootfs.rpi-sdimg -rw-r--r-- 1 martin martin 0 Feb 22 12:12 core-image-minimal-raspberrypi4-64.rootfs-20240222111049.rpi-sdimg.gz -rw-r--r-- 1 martin martin 361441 Feb 22 12:12 core-image-minimal-raspberrypi4-64.rootfs-20240222111049.spdx.tar.zst -rw-r--r-- 1 martin martin 271541 Feb 22 12:12 core-image-minimal-raspberrypi4-64.rootfs-20240222111049.testdata.json -rw-r--r-- 1 martin martin 50331648 Feb 22 12:12 core-image-minimal-raspberrypi4-64.rootfs-20240222111049.vfat lrwxrwxrwx 1 martin martin 61 Feb 22 12:12 core-image-minimal-raspberrypi4-64.rootfs.ext3 -> core-image-minimal-raspberrypi4-64.rootfs-20240222111049.ext3 lrwxrwxrwx 1 martin martin 65 Feb 22 12:12 core-image-minimal-raspberrypi4-64.rootfs.manifest -> core-image-minimal-raspberrypi4-64.rootfs-20240222111049.manifest lrwxrwxrwx 1 martin martin 69 Feb 22 12:12 core-image-minimal-raspberrypi4-64.rootfs.spdx.tar.zst -> core-image-minimal-raspberrypi4-64.rootfs-20240222111049.spdx.tar.zst lrwxrwxrwx 1 martin martin 70 Feb 22 12:12 core-image-minimal-raspberrypi4-64.rootfs.testdata.json -> core-image-minimal-raspberrypi4-64.rootfs-20240222111049.testdata.json lrwxrwxrwx 1 martin martin 61 Feb 22 12:12 core-image-minimal-raspberrypi4-64.rootfs.vfat -> core-image-minimal-raspberrypi4-64.rootfs-20240222111049.vfat Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
2022-09-14sdcard_image-rpi.bbclass: Move SDIMG_KERNELIMAGE definitions to their machinesAndrei Gherzan
This unifies the configuration of SDIMG_KERNELIMAGE across machines. Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
2022-02-25sdcard_image-rpi.bbclass: Use processed list of device treesAndrei Gherzan
make_dtb_boot_files already creates the list of device trees with their right destination. There is no need to redo a similar logic here. As a matter of fact, the sdimg functionality had a bug because it didn't treat overlay_map.dtb as an overlays file. Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
2022-02-20sdcard_image-rpi: fix DeprecationWarningMartin Jansa
* fixes: classes/sdcard_image-rpi.bbclass:87: DeprecationWarning: invalid escape sequence \S classes/sdcard_image-rpi.bbclass:88: DeprecationWarning: invalid escape sequence \S classes/sdcard_image-rpi.bbclass:90: DeprecationWarning: invalid escape sequence \S classes/sdcard_image-rpi.bbclass:91: DeprecationWarning: invalid escape sequence \S Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2021-08-09sdcard_image-rpi.bbclass: Fix IMAGE_TYPEDEP override to use new syntaxKhem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2021-08-04Manually fix conversionMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2021-08-04Convert to new override syntaxMartin Jansa
This is the result of automated script conversion: oe-core/scripts/contrib/convert-overrides.py . converting the metadata to use ":" as the override character instead of "_". Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2021-03-04sdcard_image-rpi.bbclass: shorten the default BOOTDD_VOLUME_IDMartin Jansa
* raspberrypi4-64 is 15 characters and with dosfstools-4.2 it breaks rootfs.rpi-sdimg with: mkfs.vfat: Label can be no longer than 11 characters mkfs.fat 4.2 (2021-01-31) * introduced in: https://github.com/dosfstools/dosfstools/commit/c598354 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2021-02-25sdcard_image-rpi.bbclass: increase default boot partition size from 40MiB to ↵Martin Jansa
48MiB * 5.10 kernel got a bit bigger especially for aarch64: 5.10: 22M deploy/images/raspberrypi4-64/Image-raspberrypi4-64.bin 5.10: 7.0M deploy/images/raspberrypi4/uImage-raspberrypi4.bin 5.4: 16M deploy/images/raspberrypi4-64/Image-raspberrypi4-64.bin 5.4: 6.2M deploy/images/raspberrypi4/uImage-raspberrypi4.bin * and the space in fat boot partition was already tight: Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p1 40M 38M 1.7M 96% / * increase the size to compensate for it, otherwise do_image_rpi_sdimg now fails with: Creating filesystem with Boot partition 40960 KiB and RootFS 1822720 KiB 0+0 records in 0+0 records out 0 bytes copied, 0.000100992 s, 0.0 kB/s Model: (file) Disk foo.rootfs.rpi-sdimg: 1913MB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 4194kB 46.1MB 41.9MB primary boot, lba 2 46.1MB 1913MB 1866MB primary mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows mkfs.fat 4.1 (2017-01-24) Copying bootcode.bin Copying cmdline.txt Copying config.txt Copying fixup.dat Copying fixup4.dat Copying fixup4cd.dat Copying fixup4db.dat Copying fixup4x.dat Copying fixup_cd.dat Copying fixup_db.dat Copying fixup_x.dat Copying rpi-bootfiles-20210205.stamp Copying start.elf Copying start4.elf Copying start4cd.elf Copying start4db.elf Copying start4x.elf Copying start_cd.elf Copying start_db.elf Copying start_x.elf Copying bcm2711-rpi-4-b.dtb Copying at86rf233.dtbo Copying disable-bt.dtbo Copying dwc2.dtbo Copying gpio-ir.dtbo Copying gpio-ir-tx.dtbo Copying gpio-key.dtbo Copying hifiberry-amp.dtbo Copying hifiberry-dac.dtbo Copying hifiberry-dacplus.dtbo Copying hifiberry-digi.dtbo Copying justboom-both.dtbo Copying justboom-dac.dtbo Copying justboom-digi.dtbo Copying i2c-rtc.dtbo Copying imx219.dtbo Copying iqaudio-dac.dtbo Copying iqaudio-dacplus.dtbo Copying mcp2515-can0.dtbo Copying mcp2515-can1.dtbo Copying miniuart-bt.dtbo Copying pitft22.dtbo Copying pitft28-capacitive.dtbo Copying pitft28-resistive.dtbo Copying pitft35-resistive.dtbo Copying pps-gpio.dtbo Copying rpi-ft5406.dtbo Copying rpi-poe.dtbo Copying vc4-fkms-v3d.dtbo Copying vc4-kms-v3d.dtbo Copying w1-gpio.dtbo Copying w1-gpio-pullup.dtbo Copying kernel8.img Copying boot.scr Copying Image Disk full ERROR: mcopy cannot copy /OE/build/luneos-hardknott/webos-ports/tmp-glibc/deploy/images/raspberrypi4-64/Image into boot.img WARNING: exit code 1 from a shell command. Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2020-11-27rpi-bootfiles: Rename recipe to avoid ambiguityPaul Barker
The name `bootfiles` is too generic, we should use `rpi-bootfiles` instead. Signed-off-by: Paul Barker <pbarker@konsulko.com>
2020-11-27sdcard_image-rpi: Drop redundant dependency on rpi-config:do_deployPaul Barker
The bootfiles:do_deploy task already depends on rpi-config:do_deploy so we do not explicitly need to list the dependency again in the sdcard_image-rpi class. Signed-off-by: Paul Barker <pbarker@konsulko.com>
2020-08-10sdcard_image-rpi.bbclass: Fix when RPI_SDIMG_EXTRA_DEPENDS not definedAndrei Gherzan
If the variable is not defined, bitbake will fail: [...] Task 'depends' should be specified in the form 'packagename:task' [...] This is because not expanding the variable leaves an invalid entry. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2020-08-06Generalize the naming of the bootfiles deploy directoryJeff Ithier
The raspberry pi 4 variant has a BCM2711 chip, however it still uses the same boot files as the BCM2835 used in previous generations. This change generalizes the naming of the directory generated in the $DEPLOY_DIR to avoid the implication that the files are only meant for the BCM2835. Signed-off-by: Jeff Ithier <ithijme@gmail.com>
2020-07-29sdcard_image-rpi.bbclass: enable extensible inclusion into bootChristopher Clark
Add DEPLOYPAYLOAD, similar to the existing FATPAYLOAD, to enable adding files to the boot partition from the image deploy directory. Files such as hypervisor binaries may not be present (and in fact unwanted) within the root filesystem, so FATPAYLOAD is not sufficient. DEPLOYPAYLOAD is implemented with support for file renaming from the source file in the image deploy directory to the filename written into the boot image. DEPLOYPAYLOAD is a space-separated list of entries for additions, each of which can optionally be colon-separated: <image deploy directory file>:<destination filename> If the colon separator is omitted, the source deploy directory filename is used as the destination filename. The support for specifying the destination filename is used for including Xen, which produces a machine-specific file in the image deploy directory, and is written to the image partition with its expected filename: xen. Files that are to be included from the image deploy directory will be produced by tasks that the do_image_rpi_sdimg[depends] must list, so enable adding entries to that via a new variable: RPI_SDIMG_EXTRA_DEPENDS. These changes enable retiring a Xen-specific Raspberry Pi SD card bbclass from meta-virtualization and have been tested on the Raspberry Pi 4. Signed-off-by: Christopher Clark <christopher.w.clark@gmail.com>
2020-04-03rpi-u-boot-scr: Set u-boot-default-script as providerFabio Berton
Add u-boot-default-script to the PROVIDES variable to make easier to replace boot script in another layer just by changing PREFERRED_PROVIDER_u-boot-default-script variable. Set rpi-u-boot-scr as the default provider for meta-raspberrypi. Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
2019-12-05sdcard_image-rpi.bbclass: Use IMAGE_NAME_SUFFIX variable in SDIMGFrancois Retief
Use the IMAGE_NAME_SUFFIX variable to build the SDIMG name. Some layers, notably meta-mender, change the IMAGE_NAME_SUFFIX variable to something other that ".rootfs", causing build failures. Signed-off-by: Francois Retief <fgretief@gmail.com>
2019-10-09sdcard_image-rpi.bbclass: make the dep on rpi-config:do_deploy explicitChris Laplante
Signed-off-by: Chris Laplante <mostthingsweb@gmail.com>
2019-08-06sdcard_image-rpi.bbclass: use -v for all mcopy calls and add bbfatal in case ↵Martin Jansa
mcopy fails * I have this in our layer for some time: RPI_KERNEL_DEVICETREE_OVERLAYS_append = " overlays/vc4-fkms-v3d.dtbo" because we're using vc4graphics also on raspberrypi3 and it was working fine until recently. * now the default rpi-base.inc in warrior and master branch includes the same since: https://github.com/agherzan/meta-raspberrypi/commit/37aa050d5a44eb797540ef50408c2ca8e3da6fa0 and do_image_rpi_sdimg started failing with a bit useless log: ... Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 4194kB 46.1MB 41.9MB primary boot, lba 2 46.1MB 1145MB 1099MB primary mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows mkfs.fat 4.1 (2017-01-24) WARNING: exit code 1 from a shell command. * after adding -v to mcopy calls I got slightly better log: ... Copying w1-gpio-pullup.dtbo Copying w1-gpio.dtbo WARNING: exit code 1 from a shell command. * the issue is that mcopy behavior in non-interactive shell is to fail when the target file already exists (sometimes it seems to cause mcopy to hang forever), but when you execute the run.do_image_rpi_sdimg script manually in interactive shell it will nicely show this prompt on stderr: $ dtb=vc4-fkms-v3d.dtbo recipe-sysroot-native/usr/bin/mcopy -i boot.img -s BUILD/deploy/images/raspberrypi3/$dtb ::overlays/$dtb Long file name "vc4-fkms-v3d.dtbo" already exists. a)utorename A)utorename-all r)ename R)ename-all o)verwrite O)verwrite-all s)kip S)kip-all q)uit (aArRoOsSq): o * with the bbfatal the log is finally a bit more useful: ... Copying w1-gpio-pullup.dtbo Copying w1-gpio.dtbo ERROR: mcopy cannot copy TOPDIR/BUILD/deploy/images/raspberrypi3/vc4-fkms-v3d.dtbo into boot.img WARNING: exit code 1 from a shell command. * the only exception is FATPAYLOAD where it was ignoring mcopy with || true before, I've added bbwarn, because even issues like mentioned there "vfat issues like not supporting .~lock files" are probably worth reporting as warning (why would people add .~lock to FATPAYLOAD if it cannot be copied into boot.img) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2019-07-19sdcard_image-rpi: Check for armstub based on machine featureAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-07-04sdcard_image-rpi.bbclass: Use armstub machine featureAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-07-04sdcard_image-rpi.bbclass: Fix typoAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-07-04sdcard_image-rpi.bbclass: Include in the SD card image the armstub fileAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-06-13sdcard_image-rpi : minor bug in use of FATPAYLOADmalus-brandywine
Double quotation marks were added around FATPAYLOAD to prevent parsing error when FATPAYLOAD contains list of file names Signed-off-by: Nataliya Korovkina <malus.brandywine@gmail.com>
2019-02-19sdcard_image-rpi: Format boot partition as FAT32Richard Osterloh
Closes: #382 Signed-off-by: Richard Osterloh <richard.osterloh@gmail.com>
2018-12-12sdcard_image-rpi.bbclass: Remove SDIMG_COMPRESSIONIurii Lunev
Using SDIMG_COMPRESSION variable to choose compression type for produced images is deprecated. IMAGE_FSTYPES should be used instead. This patch removes any response to SDIMG_COMPRESSION within sdcard_image-rpi.bbclass Signed-off-by: Iurii Lunev <koolkhel@mail.ru>
2018-09-07sdcard_image-rpi: fix kernel artifacts variablesLaurent Bonnans
${INITRAMFS_SYMLINK_NAME} has been changed to ${INITRAMFS_LINK_NAME} in poky's commit f09947586c5c2c05368651838fea970808ab161d
2018-07-16sdcard_image-rpi.bbclass: allow to easily deploy vfat partition even for non ↵Martin Jansa
u-boot case Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2018-07-16sdcard_image-rpi.bbclass: drop KERNEL_INITRAMFS variableMartin Jansa
* use INITRAMFS_SYMLINK_NAME from new kernel-artifact-names.bbclass instead of KERNEL_INITRAMFS * the documentation says that KERNEL_INITRAMFS should be used to define extension of initramfs, but in linux-raspberrypi.inc it's defined only to 1 or empty based on INITRAMFS_IMAGE_BUNDLE variable and I don't see any code in meta-raspberry or oe-core which would use KERNEL_INITRAMFS to actualy name the initramfs artifact to create: ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}${KERNEL_INITRAMFS}-${MACHINE}.bin used in classes/sdcard_image-rpi.bbclass * also fix the assumption that there is -${MACHINE} suffix in: ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}${KERNEL_INITRAMFS}-${MACHINE}.bin because that's defined as KERNEL_IMAGE_SYMLINK_NAME and some DISTROs might use different value * this depends on oe-core changes which were merged today: http://git.openembedded.org/openembedded-core/commit/?id=7d0ef0eaa1bfe97015a774c26f5791622e7e8b12 * this is the last piece of previous pull-request: https://github.com/agherzan/meta-raspberrypi/pull/159 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2018-07-07sdcard_image-rpi.bbclass: use 4 spaces for indentation instead of mix of ↵Martin Jansa
tabs and spaces Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2018-07-07sdcard_image-rpi: add dependency on rpi-u-boot-scrMartin Jansa
* there is runtime dependency on rpi-u-boot-scr from u-boot itself: recipes-bsp/u-boot/u-boot_%.bbappend:RDEPENDS_${PN}_append_rpi = " rpi-u-boot-scr" * but that's not enough to ensure that rpi-u-boot-scr:do_deploy is finished before do_image_rpi_sdimg and for ${DEPLOY_DIR_IMAGE}/boot.scr to exist in time Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2018-07-07sdcard_image-rpi.bbclass: copy the DTB files with canonical nameMartin Jansa
* instead of using ${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.dtb use the entries from KERNEL_DEVICETREE * basename is still needed because raspberrypi3-64 is using: broadcom/bcm2710-rpi-3-b.dtb and the ${DEPLOY_DIR_IMAGE} doesn't contain any directories for DTBs and we cannot remove broadcom/ prefix, because then "make bcm2710-rpi-3-b.dtb" from kernel-devicetree.bbclass will fail with: make[3]: *** No rule to make target 'arch/arm64/boot/dts/bcm2710-rpi-3-b.dtb'. Stop. Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2018-05-04sdcard_image-rpi.bbclass: Fix a typo in commentEduardo Abinader
Only a small typo on bbclass header. Signed-off-by: Eduardo Abinader <eduardoabinader@gmail.com>
2018-02-28Fix do_image_rpi_sdimg/do_image_wic dependenciesPaul Barker
The dependency resolution code in bitbake has recently been optimized and this seems to have slightly changed the behaviour of do_image_rpi_sdimg and do_image_wic. We ensure that the main build artifacts are present by depending on the relevant do_deploy and do_populate_sysroot tasks. However, we need to ensure that other build tasks for these dependencies have also been executed before we try to create our image. This can be achieved by adding a recursive dependency on do_build, so that the do_build tasks of all recipes in the dependency chain of do_image_rpi_sdimg/do_image_wic are executed before the image function itself is executed. The original issue seen here was that 'recipedata' files were not copied to 'tmp/deploy/licenses' as do_populate_lic for each dependency had not been ran before the image creation function. The write_deploy_manifest function from license.bbclass (listed in IMAGE_POSTPROCESS_COMMAND) therefore failed. Adding the recursive dependency on do_build fixes this issue, ensuring do_populate_lic runs before do_image_rpi_sdimg/do_image_wic. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
2017-09-24sdcard_image-rpi: Use un-timestamped link to rootfs partition imagePaul Barker
The timestamp in the rootfs partition image filename may not match the current timestamp if the do_image_rpi_sdimg step is repeated without repeating the previous do_image_ext3 (or similar) step. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
2017-09-24sdcard_image-rpi: Drop unnecessary sync commandsPaul Barker
These commands are unnecessary and seem to mask failures to find the rootfs.ext3 file when re-running the do_image_rpi_sdimg stage without re-running the preceeding do_image_ext3 stage. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
2017-09-24Support using u-boot with Image format for raspberrypi3-64Paul Barker
For raspberrypi3-64 we need to use the Image or Image.gz format with u-boot instead of the legacy uImage format. We also need to issue the 'booti' command to boot the kernel instead of 'bootm'. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
2017-09-24linux-raspberrypi-base.bbclass: DropPaul Barker
The only remaining function in linux-raspberrypi-base was split_overlays() which is used in the sdcard_image-rpi class. So we can move this function over and drop the now-empty linux-raspberrypi-base class. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
2017-09-24linux-raspberrypi: Drop unnecessary codePaul Barker
* The kerneltype variable is not used anywhere after being set. * The manipulation of KERNEL_DEVICETREE is effectively a no-op, we read the current value in get_dts() and store this back into the same variable. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
2017-08-29sdcard_image-rpi: fix absolute path in vfat symlinkAndrea Galbusera
Fix bitbake complaining with: ERROR: core-image-minimal-1.0-r0 do_image_complete: sstate found an absolute path symlink [...].vfat pointing at [...].vfat. Please replace this with a relative link. This patch redefines SDIMG_VFAT as a file name instead of a full absolute path, then fixing the symlink creation by pointing to a relative target. The cp command that deploys the artifact is changed accordingly to include the destination path. Signed-off-by: Andrea Galbusera <gizero@gmail.com>
2017-06-29sdcard_image-rpi: replace IMAGE_DEPENDS_rpi-sdimg by do_image_rpi-sdimg[depends]Andreas Müller
* oe-core removed IMAGE_DEPENDS -> parsing fails with hint how to fix * add required task for each recipe Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
2017-06-21sdcard_image-rpi.bbclass: deploy vfat partitionMatthew McClintock
This is useful to update the bootloader/vfat partition from u-boot when you don't want to update everything: U-Boot> tftpboot 0x1000000 tmp/0VXje Waiting for Ethernet connection... done. Using sms0 device TFTP from server 192.168.0.1; our IP address is 192.168.0.26 Filename 'image.vfat'. Load address: 0x1000000 Loading: ################################################## 40 MiB 2.1 MiB/s done Bytes transferred = 41943040 (2800000 hex) U-Boot> mmc part Partition Map for MMC device 0 -- Partition Type: DOS Part Start Sector Num Sectors UUID Type 1 8192 81920 a63a4fbc-01 0c Boot 2 90112 163840 a63a4fbc-02 83 U-Boot> mmc erase 0x2000 0x14000 MMC erase: dev # 0, block # 8192, count 81920 ... 81920 blocks erased: OK U-Boot> mmc write 0x1000000 0x2000 0x14000 MMC write: dev # 0, block # 8192, count 81920 ... 81920 blocks written: OK U-Boot> Signed-off-by: Matthew McClintock <msm-oss@mcclintock.net>
2017-03-11sdcard_image: fix sdcard image generationJanek Filus
Rely on shell environment when copying devicetree and devicetree overlays to target image. Signed-off-by: Janek Filus <janek.filus@bytesatwork.ch> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2017-02-16sdcard: Use kernel8.img for 64bit kernel image nameKhem Raj
This helps the firmware to identify the kernel as 64bit image Signed-off-by: Khem Raj <raj.khem@gmail.com>
2016-10-31sdcard_image-rpi.bbclass: Include boot script when using u-bootPaul Barker
Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
2016-10-13sdcard_image-rpi.bbclass: Remove redundant RPI_KERNEL_VERSIONJonathan Liu
The value of the RPI_KERNEL_VERSION can change between None and the kernel version which can result in taskhash mismatch errors while building images. The taskhash mismatch errors can be reproduced using: bitbake -c cleansstate virtual/kernel core-image-minimal && bitbake core-image-minimal The get_dts() and split_overlays() functions are modified so that the kernel version argument is optional. If the version is not supplied to these functions, they will fallback to the Python equivalent of the expression used for RPI_KERNEL_VERSION. Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2016-09-21sdcard_image-rpi.bbclass: avoid corrupted images with latest oe-coreAndreas Müller
oe-core's commit d54339d4b1a7e884de636f6325ca60409ebd95ff creates image in IMGDEPLOYDIR and copies through sstate to DEPLOY_DIR_IMAGE. That causes DEPLOY_DIR_IMAGE not valid when calling IMAGE_CMD. Therefore use IMGDEPLOYDIR for sdcard creation too. Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
2016-09-21sdcard_image-rpi.bbclass: support for .dtbo files for dtb overlaysHerve Jourdain
Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb. Add support for both extensions for overlays (".dtb" and ".dtbo") CAUTION: in IMAGE_CMD_rpi-sdimg, 'TMPDIR' is not set, causing 'STAGING_KERNEL_BUILDDIR' to not be expanded, causing get_dts() to not being able to get the kernel version! To avoid this problem, the kernel version is added in a new variable outside the scope of IMAGE_CMD_rpi-sdimg, and its value passed to get_dts() and split_overlays()! Signed-off-by: Herve Jourdain <herve.jourdain@neuf.fr>
2016-09-16sdcard_image-rpi.bbclass: remove redundant IMAGEDATESTAMPJonathan Liu
The IMAGE_NAME variable already contains the date and time so it is redundant to also include the date again with IMAGEDATESTAMP when writing to image-version-info in the boot partition. Signed-off-by: Jonathan Liu <net147@gmail.com>
2016-07-13sdcard_image-rpi.bbclass: Add the vardepexcludesKhem Raj
The problem reappears because we need to add to the variable and not assign Signed-off-by: Khem Raj <raj.khem@gmail.com>
2016-07-08sdcard_image-rpi.bbclass: Exclude DATETIME from task stampKhem Raj
This helps in fixing occasional error seen quite often ERROR: wpe-image-1.0-r0 do_image_rpi_sdimg: Taskhash mismatch 7ea6b505bb7a2cc5ca03552bcf3333fa verses 3be7cdad8c4532430d96368c5ca523d4 for /a/builder/home/kraj/work/oe/meta-metrological/recipes-core/images/wp e-image.bb.do_image_rpi_sdimg ERROR: Taskhash mismatch 7ea6b505bb7a2cc5ca03552bcf3333fa verses 3be7cdad8c4532430d96368c5ca523d4 for /a/builder/home/kraj/work/oe/meta-metrological/recipes-core/images/wpe-image.bb.do_image_rpi_sdimg Signed-off-by: Khem Raj <raj.khem@gmail.com>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-28 17:33:25 +0000