![]() U-boot-boundary PROVIDES virtual/bootloader but was skipped: incompatible with machine (not in COMPATIBLE_MACHINE) U-boot PROVIDES virtual/bootloader but was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in the machine configuration. U-boot-qoriq PROVIDES virtual/bootloader but was skipped: incompatible with machine (not in COMPATIBLE_MACHINE) U-boot-toradex PROVIDES virtual/bootloader but was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in the machine configuration. U-boot-variscite PROVIDES virtual/bootloader but was skipped: incompatible with machine (not in COMPATIBLE_MACHINE) conf: ERROR: Nothing PROVIDES 'virtual/bootloader' See the error below when I remove the fake U-Boot package and removing calling out that virtual/bootloader is provided by it in the machine. Specifically NXP/Freescale layers as this is an i.MX6 device. I may be running in to complications from other Yocto layers. Thanks for the info, I wish it was that easy. MENDER_FEATURES_ENABLE:append = " mender-growfs-data mender-image mender-image-sd mender-client-install mender-systemd mender-persist-systemd-machine-id" MENDER_FEATURES_DISABLE:append = " mender-bios mender-grub mender-image-bios imender-image-gpt mender-image-ubi mender-image-uefi mender-partuuid mender-ubi mender-uboot" ![]() PREFERRED_PROVIDER_virtual/bootloader = "u-boot-fake"Īnd I’m not sure if these are important to the equation or not, but, I did tune what specific features were enabled and disabled:Ĭat conf/nf # Trying to tune mender features to only what we need # PREFERRED_PROVIDER_u-boot = "u-boot-fake" # Tricking Mender to thinking U-Boot is being built Set this this package as providing virtual/bootloader and u-boot The current docs say it only needs to provide U-Boot, but, testing shows that virtual/bootloader may be more important here? RPROVIDES_$ += "u-boot virtual/bootloader" I think I have this resolved but would still love some feedback on the topic in case there is an easier route.Ĭreate a fake U-Boot package that does nothing other than exist.Ĭat recipes-bsp/u-boot-fake/u-boot-fake_mender.bb DESCRIPTION = "Fake U-Boot provider" Any pointers on how to either prevent Mender from trying to build U-Boot (or any bootloader) or create a dummy recipe that claims to provide U-Boot but that the meta-mender layer also doesn’t try to patch? The rest of the integration is manual and should only ever be done once. The U-Boot binary is booted from an embedded storage device, it is not a part of the final disk image.įor all of these reasons, we need to be able to build just mender-client via Yocto. The U-Boot version is ancient, so much so that using newer compilers results in inexplicable issues with RAM. Moving to Yocto and meta-mender, it seems building U-Boot is a requirement of Mender. The specific platform in question we already have a U-Boot integration for the necessary Mender variables, etc. Using “master-next” for a proof of concept, I wanted to make that clear just in case it is important to the issue at hand. We’re working with a customer to integrate Yocto Kirkstone with Mender on one of our platforms. TFTP from server 172.17.44.150 our IP address is 172.17.44.I apologize if this isn’t the right category, please feel free to move it if needed. Warning: (eth1) using random MAC address - 5a:51:06:58:75:ab VService: Connection is ok on MU Vendor ID, Product ID, Addr uuu -v -b emmc_all imx-boot-imx8qxpmek-sd.bin b2qt-automotive-qt5-image-imx8qxpmek.imgįinally Boot2Qt boots fine and I can see Neptune starting, but when I try to modify the U-Boot enviroment variables, somehow the boot partition gets corrupted. $ bitbake -k b2qt-automotive-qt5-image.bbĪfter a while the image is generated, then I use the NXP manufacturing tool to flash it to the eMMC that MEK board includes: sudo. ![]() b2qt-init-build-env init -device imx8qxpmek I am working with NXP i.MX 8QuadXPlus Multisensory Enablement Kit (MEK) and I'd like to use Boot2Qt so I created Boot2Qt distro using this guide, the steps I did are: $ git clone -b thud git://code.qt.io/yocto/meta-boot2qt.git
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |