Re: [yocto] [Meta-Qt5] "Unknown Module: declarative" Error While Creating Toolchain
Maybe this: https://www.technexion.com/support/knowledgebase/resolving-dependencies-issues-in-yocto/ Zoran ___ On Tue, Jul 9, 2019 at 7:59 AM Onur Eser wrote: > > Hello All, > > I have talked to my BSP provider and they have solved the conflict files > issue with an update. Now I am able to create and boot a Yocto Image with > Meta-Qt5 recipes and 'dev_pkgs' in it. But still cannot create a toolchain. > Nor with I guess it is trying to compile something before qtdeclarative, but > these 'something' depends on qtdeclarative. > > My image is core image is Weston. I added the line 'inherit populate_sdk_qt5' > to my core-image-weston.bb file. And tried both commands 'bitbake > meta-toolchain-qt5' and 'bitbake -c populate_sdk core-image-weston'. The > result is the same. > > I cut just the error part of my output: > > | cd qdeclarativefolderlistmodel/ && ( test -e Makefile || > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/recipe-sysroot-native/usr/bin/qt5/qmake > -o Makefile > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/git/tests/auto/declarative/qdeclarativefolderlistmodel/qdeclarativefolderlistmodel.pro > ) && make -f Makefile > | Project ERROR: Unknown module(s) in QT: declarative widgets > | Makefile:88: recipe for target 'sub-qdeclarativecomponent-make_first' failed > | make[2]: *** [sub-qdeclarativecomponent-make_first] Error 3 > | make[2]: *** Waiting for unfinished jobs > | Project ERROR: Unknown module(s) in QT: declarative > | Project ERROR: Unknown module(s) in QT: declarative > | Makefile:113: recipe for target 'sub-qdeclarativecontext-make_first' failed > | make[2]: *** [sub-qdeclarativecontext-make_first] Error 3 > | Project ERROR: Unknown module(s) in QT: declarative > | Makefile:138: recipe for target 'sub-qdeclarativeengine-make_first' failed > | make[2]: *** [sub-qdeclarativeengine-make_first] Error 3 > | Makefile:63: recipe for target 'sub-parserstress-make_first' failed > | make[2]: *** [sub-parserstress-make_first] Error 3 > | make[2]: Entering directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual/declarative' > | make[2]: Nothing to be done for 'first'. > | make[2]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual/declarative' > | make[1]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual' > | Project ERROR: Unknown module(s) in QT: declarative > | Makefile:163: recipe for target 'sub-qdeclarativeerror-make_first' failed > | make[2]: *** [sub-qdeclarativeerror-make_first] Error 3 > | Project ERROR: Unknown module(s) in QT: declarative > | Makefile:188: recipe for target > 'sub-qdeclarativefolderlistmodel-make_first' failed > | make[2]: *** [sub-qdeclarativefolderlistmodel-make_first] Error 3 > | make[2]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/auto/declarative' > | Makefile:45: recipe for target 'sub-declarative-make_first' failed > | make[1]: *** [sub-declarative-make_first] Error 2 > | make[1]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/auto' > | Makefile:45: recipe for target 'sub-auto-make_first' failed > | make: *** [sub-auto-make_first] Error 2 > | ERROR: oe_runmake failed > | WARNING: exit code 1 from a shell command. > | ERROR: Function failed: do_compile_ptest_base (log file is located at > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/temp/log.do_compile_ptest_base.29566) > ERROR: Task > (/home/closx/poky/meta-qt5/recipes-qt/qt5/qtquick1_git.bb:do_compile_ptest_base) > failed with exit code '1' > > What do you guys think the reason of this issue may be? Any solution offers? > > My full output: > https://paste.ee/p/PupWr#Epvqnw9FoasgQEBhIXqQ8hH7veMcRybX > > Another source issue again? > Have a lovely day! > Onur > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Meta-Qt5] "Unknown Module: declarative" Error While Creating Toolchain
Hello Zoran! Thank you for your answer, but that page is about the missing packages in your configuration. There is no a missing dependency in my configuration. The recipe "qtdeclarative" is already added. Note: Sending again because sent as PM accidentally. Thanks anyway! Onur Zoran Stojsavljevic , 9 Tem 2019 Sal, 10:59 tarihinde şunu yazdı: > Maybe this: > > https://www.technexion.com/support/knowledgebase/resolving-dependencies-issues-in-yocto/ > > Zoran > ___ > > On Tue, Jul 9, 2019 at 7:59 AM Onur Eser wrote: > > > > Hello All, > > > > I have talked to my BSP provider and they have solved the conflict files > issue with an update. Now I am able to create and boot a Yocto Image with > Meta-Qt5 recipes and 'dev_pkgs' in it. But still cannot create a toolchain. > Nor with I guess it is trying to compile something before qtdeclarative, > but these 'something' depends on qtdeclarative. > > > > My image is core image is Weston. I added the line 'inherit > populate_sdk_qt5' to my core-image-weston.bb file. And tried both > commands 'bitbake meta-toolchain-qt5' and 'bitbake -c populate_sdk > core-image-weston'. The result is the same. > > > > I cut just the error part of my output: > > > > | cd qdeclarativefolderlistmodel/ && ( test -e Makefile || > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/recipe-sysroot-native/usr/bin/qt5/qmake > -o Makefile > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/git/tests/auto/declarative/qdeclarativefolderlistmodel/ > qdeclarativefolderlistmodel.pro ) && make -f Makefile > > | Project ERROR: Unknown module(s) in QT: declarative widgets > > | Makefile:88: recipe for target 'sub-qdeclarativecomponent-make_first' > failed > > | make[2]: *** [sub-qdeclarativecomponent-make_first] Error 3 > > | make[2]: *** Waiting for unfinished jobs > > | Project ERROR: Unknown module(s) in QT: declarative > > | Project ERROR: Unknown module(s) in QT: declarative > > | Makefile:113: recipe for target 'sub-qdeclarativecontext-make_first' > failed > > | make[2]: *** [sub-qdeclarativecontext-make_first] Error 3 > > | Project ERROR: Unknown module(s) in QT: declarative > > | Makefile:138: recipe for target 'sub-qdeclarativeengine-make_first' > failed > > | make[2]: *** [sub-qdeclarativeengine-make_first] Error 3 > > | Makefile:63: recipe for target 'sub-parserstress-make_first' failed > > | make[2]: *** [sub-parserstress-make_first] Error 3 > > | make[2]: Entering directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual/declarative' > > | make[2]: Nothing to be done for 'first'. > > | make[2]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual/declarative' > > | make[1]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual' > > | Project ERROR: Unknown module(s) in QT: declarative > > | Makefile:163: recipe for target 'sub-qdeclarativeerror-make_first' > failed > > | make[2]: *** [sub-qdeclarativeerror-make_first] Error 3 > > | Project ERROR: Unknown module(s) in QT: declarative > > | Makefile:188: recipe for target > 'sub-qdeclarativefolderlistmodel-make_first' failed > > | make[2]: *** [sub-qdeclarativefolderlistmodel-make_first] Error 3 > > | make[2]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/auto/declarative' > > | Makefile:45: recipe for target 'sub-declarative-make_first' failed > > | make[1]: *** [sub-declarative-make_first] Error 2 > > | make[1]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/auto' > > | Makefile:45: recipe for target 'sub-auto-make_first' failed > > | make: *** [sub-auto-make_first] Error 2 > > | ERROR: oe_runmake failed > > | WARNING: exit code 1 from a shell command. > > | ERROR: Function failed: do_compile_ptest_base (log file is located at > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/temp/log.do_compile_ptest_base.29566) > > ERROR: Task > > (/home/closx/poky/meta-qt5/recipes-qt/qt5/qtquick1_git.bb:do_compile_ptest_base) > failed with exit code '1' > > > > What do you guys think the reason of this issue may be? Any solution > offers? > > > > My full output: > > https://paste.ee/p/PupWr#Epvqnw9FoasgQEBhIXqQ8hH7veMcRybX > > > > Another source issue again? > > Have a lovely day! > > Onur > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list y
Re: [yocto] [Meta-Qt5] "Unknown Module: declarative" Error While Creating Toolchain
Onur, I am not subject matter expert in Qt layers... Here is what I found while searching for an answer to the problem... Here is the .bb causing to you problems: https://github.com/meta-qt5/meta-qt5/blob/sumo/recipes-qt/qt5/qtquick1_git.bb It is sumo branch. I noted that thud branch does NOT have this .bb (it is rearranged, and this .bb removed). meta-qt5 has there for thud: qtquickcontrols_git.bb and qtquickcontrols2_git.bb (for 5.11.3 version). Kludge: maybe you can try to build the whole thing using thud branch?! Hope this hepls, Zoran ___ On Tue, Jul 9, 2019 at 10:38 AM Onur Eser wrote: > > Hello Zoran! > Thank you for your answer, but that page is about the missing packages in > your configuration. There is no a missing dependency in my configuration. The > recipe "qtdeclarative" is already added. > > Note: Sending again because sent as PM accidentally. > Thanks anyway! > Onur > > Zoran Stojsavljevic , 9 Tem 2019 Sal, 10:59 > tarihinde şunu yazdı: >> >> Maybe this: >> https://www.technexion.com/support/knowledgebase/resolving-dependencies-issues-in-yocto/ >> >> Zoran >> ___ >> >> On Tue, Jul 9, 2019 at 7:59 AM Onur Eser wrote: >> > >> > Hello All, >> > >> > I have talked to my BSP provider and they have solved the conflict files >> > issue with an update. Now I am able to create and boot a Yocto Image with >> > Meta-Qt5 recipes and 'dev_pkgs' in it. But still cannot create a >> > toolchain. Nor with I guess it is trying to compile something before >> > qtdeclarative, but these 'something' depends on qtdeclarative. >> > >> > My image is core image is Weston. I added the line 'inherit >> > populate_sdk_qt5' to my core-image-weston.bb file. And tried both commands >> > 'bitbake meta-toolchain-qt5' and 'bitbake -c populate_sdk >> > core-image-weston'. The result is the same. >> > >> > I cut just the error part of my output: >> > >> > | cd qdeclarativefolderlistmodel/ && ( test -e Makefile || >> > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/recipe-sysroot-native/usr/bin/qt5/qmake >> > -o Makefile >> > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/git/tests/auto/declarative/qdeclarativefolderlistmodel/qdeclarativefolderlistmodel.pro >> > ) && make -f Makefile >> > | Project ERROR: Unknown module(s) in QT: declarative widgets >> > | Makefile:88: recipe for target 'sub-qdeclarativecomponent-make_first' >> > failed >> > | make[2]: *** [sub-qdeclarativecomponent-make_first] Error 3 >> > | make[2]: *** Waiting for unfinished jobs >> > | Project ERROR: Unknown module(s) in QT: declarative >> > | Project ERROR: Unknown module(s) in QT: declarative >> > | Makefile:113: recipe for target 'sub-qdeclarativecontext-make_first' >> > failed >> > | make[2]: *** [sub-qdeclarativecontext-make_first] Error 3 >> > | Project ERROR: Unknown module(s) in QT: declarative >> > | Makefile:138: recipe for target 'sub-qdeclarativeengine-make_first' >> > failed >> > | make[2]: *** [sub-qdeclarativeengine-make_first] Error 3 >> > | Makefile:63: recipe for target 'sub-parserstress-make_first' failed >> > | make[2]: *** [sub-parserstress-make_first] Error 3 >> > | make[2]: Entering directory >> > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual/declarative' >> > | make[2]: Nothing to be done for 'first'. >> > | make[2]: Leaving directory >> > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual/declarative' >> > | make[1]: Leaving directory >> > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual' >> > | Project ERROR: Unknown module(s) in QT: declarative >> > | Makefile:163: recipe for target 'sub-qdeclarativeerror-make_first' failed >> > | make[2]: *** [sub-qdeclarativeerror-make_first] Error 3 >> > | Project ERROR: Unknown module(s) in QT: declarative >> > | Makefile:188: recipe for target >> > 'sub-qdeclarativefolderlistmodel-make_first' failed >> > | make[2]: *** [sub-qdeclarativefolderlistmodel-make_first] Error 3 >> > | make[2]: Leaving directory >> > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/auto/declarative' >> > | Makefile:45: recipe for target 'sub-declarative-make_first' failed >> > | make[1]: *** [sub-declarative-make_first] Error 2 >> > | make[1]: Leaving directory >> > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/auto' >> > | Makefile:45: recipe for target 'sub-auto-make_first' failed >> > | make: *** [sub-auto-make_first] Error 2 >> > | ERROR: oe_runmake failed >> > | WARNING: exit code 1 from a shell command. >> > | ERROR: Function failed: do_compile_ptest_base (log file is l
Re: [yocto] [Meta-Qt5] "Unknown Module: declarative" Error While Creating Toolchain
Zoran, I know you are not a Qt Layers expert. I am trying to describe my problem to experts via common mails, so they will not missunderstand my issue. Oh lord, whole new building... I am not a time traveller, but I can say that I will wait for 10 hours or something for that to build, and it will fail because of something else. The worst part is, it gives the error on the FINAL STEP. After hours and hours and hours. Anyway, I will try thud branch. Wish me luck. Others can still offer solutions, I will keep this build too. Onur -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Meta-Qt5] "Unknown Module: declarative" Error While Creating Toolchain
One thing on my prio list is to buy very powerful 16 or 32 INTEL core 6950 or + server. Maybe AMD Ryzen 32 or 64 core (most likely). This almost eliminates this build problem... But in the current situation I am presently, I could not even buy extra bubble gum. ;-) I have only my HP Elite Book 840 G1 which has 4 HW threads (2C + 2HYP), and I have the same problem for YOCTO. To build any YOCTO build goes forever (the extras is that I have 500GB SSD there, which makes it much faster). But, nevertheless, the newer, the better... Hopefully! Toradex YOCTO gurus may hop to this thread, and help... Zoran ___ On Tue, Jul 9, 2019 at 11:12 AM Onur Eser wrote: > > Zoran, > > I know you are not a Qt Layers expert. I am trying to describe my problem to > experts via common mails, so they will not missunderstand my issue. > Oh lord, whole new building... I am not a time traveller, but I can say that > I will wait for 10 hours or something for that to build, and it will fail > because of something else. > The worst part is, it gives the error on the FINAL STEP. After hours and > hours and hours. > Anyway, I will try thud branch. Wish me luck. > > Others can still offer solutions, I will keep this build too. > Onur -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Stuck to build zImage-initramfs
Please, read the following thread: https://lists.yoctoproject.org/pipermail/yocto/2018-July/041680.html Zoran ___ On Mon, Jul 8, 2019 at 11:43 PM JH wrote: > > Hi, > > I have been stuck to build zImage-initramfs for weeks. I've read Yocto > latest document, but still failed to generate the initarmfs to run on > RAM. I added following statements in local.conf: > > UBOOT_CONFIG = "ram" > INITRAMFS_IMAGE_BUNDLE = "1" > DISTRO_FEATURES_append = " ram" > IMAGE_FSTYPES_append = " cpio.xz" > > It built to following images: > > dev-image.rootfs.cpio.xz > u-boot.imx-ram > zImage.bin > > If I extract the dev-image.rootfs.cpio.xz, it contains zImage at boot > directory. > > What I need is the zImage-initramfs to contain the rootfs in initramfs format. > > I see there is document ramfs-rootfs-initramfs.txt, but it did not > mention how to generate zImage-initramfs. > > There is core-image-minimal-initramfs.bb, but it cannot be run: > > $ MACHINE="imx6evk" DISTRO="imx6evk" bitbake core-image-minimal-initramfs > ERROR: Nothing PROVIDES 'core-image-minimal-initramfs' > core-image-minimal-initramfs was skipped: incompatible with host > arm-oe-linux-gnueabi (not in COMPATIBLE_HOST) > > Could any one help what I am missing here and how to build the > zImage-initramfs? > > Thank you. > > Kind regards, > > - jh > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bitbak command: No recipe available for
On Mon, 8 Jul 2019 at 12:29, danwe wrote: > > Hi, > > while using the command: > daniel@daniel-VirtualBox:~/bbb$ MACHINE=beaglebone bitbake core-immage-full > cmdline > I get the following ouput: > > Loading cache: 100% || Time: > 0:00:03 > Loaded 1358 entries from dependency cache. > Parsing recipes: 100% |##| Time: > 0:00:12 > Parsing of 832 .bb files complete (829 cached, 3 parsed). 1361 targets, 65 > skipped, 0 masked, 0 errors. > ERROR: No recipes available for: > /home/daniel/meta-bbb/recipes-connectivity/openssh/openssh_7.%.bbappend > /home/daniel/meta-bbb/recipes-qt/qt5/qtbase_git.bbappend > /home/daniel/meta-bbb/recipes-support/ntp/ntp_4.2.%.bbappend Ross answered this already: Your meta-bbb version seems incompatible with your poky version. If you are using git, make sure the branch names of all your layers match and that the branches are up to date. HTH, Jussi -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Stuck to build zImage-initramfs
Thanks Zoran, I did see that link and your post to run mkimage. Did you get zImage-initramfs? I have to admit, I lost in that long email discussion with different approaches, I tried all set up, but there is no zImage-initramfs to be generated, files built in deploy/images just could not be used to run uuu on imx6 RAM. There is post for add KERNEL_INITRAMFS = "-initramfs", it looks like very close to generate zImage-initramfs, but I could still not get it :-(. Thank you very much. On 7/9/19, Zoran Stojsavljevic wrote: > Please, read the following thread: > https://lists.yoctoproject.org/pipermail/yocto/2018-July/041680.html > > Zoran > ___ > > On Mon, Jul 8, 2019 at 11:43 PM JH wrote: >> >> Hi, >> >> I have been stuck to build zImage-initramfs for weeks. I've read Yocto >> latest document, but still failed to generate the initarmfs to run on >> RAM. I added following statements in local.conf: >> >> UBOOT_CONFIG = "ram" >> INITRAMFS_IMAGE_BUNDLE = "1" >> DISTRO_FEATURES_append = " ram" >> IMAGE_FSTYPES_append = " cpio.xz" >> >> It built to following images: >> >> dev-image.rootfs.cpio.xz >> u-boot.imx-ram >> zImage.bin >> >> If I extract the dev-image.rootfs.cpio.xz, it contains zImage at boot >> directory. >> >> What I need is the zImage-initramfs to contain the rootfs in initramfs >> format. >> >> I see there is document ramfs-rootfs-initramfs.txt, but it did not >> mention how to generate zImage-initramfs. >> >> There is core-image-minimal-initramfs.bb, but it cannot be run: >> >> $ MACHINE="imx6evk" DISTRO="imx6evk" bitbake core-image-minimal-initramfs >> ERROR: Nothing PROVIDES 'core-image-minimal-initramfs' >> core-image-minimal-initramfs was skipped: incompatible with host >> arm-oe-linux-gnueabi (not in COMPATIBLE_HOST) >> >> Could any one help what I am missing here and how to build the >> zImage-initramfs? >> >> Thank you. >> >> Kind regards, >> >> - jh >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Stuck to build zImage-initramfs
Jupiter, I never read carefully the whole mechanism how to bundle kernel with initramfs in YOCTO. I have there a description how to organize kernel image WITHOUT initramfs (only kernel image by itself) and separately initramfs as final stage, so I can do the tests with Lava, but I developed another meanings with such a configuration: some another way of testing various proofs of concepts. What you are asking is a classical approach: kernel bundled with initramfs, which is called Dracut phase, before mounting HDD/SSD permanent rootfs... It is non-trivial process, controlled by various kernel scripts. I also need to analyse this @ thread regarding what you have asked for... Maybe this is good time do to such a analysis! If? Zoran ___ On Tue, Jul 9, 2019 at 1:47 PM JH wrote: > > Thanks Zoran, I did see that link and your post to run mkimage. Did > you get zImage-initramfs? I have to admit, I lost in that long email > discussion with different approaches, I tried all set up, but there is > no zImage-initramfs to be generated, files built in deploy/images just > could not be used to run uuu on imx6 RAM. > > There is post for add KERNEL_INITRAMFS = "-initramfs", it looks like > very close to generate zImage-initramfs, but I could still not get it > :-(. > > Thank you very much. > > On 7/9/19, Zoran Stojsavljevic wrote: > > Please, read the following thread: > > https://lists.yoctoproject.org/pipermail/yocto/2018-July/041680.html > > > > Zoran > > ___ > > > > On Mon, Jul 8, 2019 at 11:43 PM JH wrote: > >> > >> Hi, > >> > >> I have been stuck to build zImage-initramfs for weeks. I've read Yocto > >> latest document, but still failed to generate the initarmfs to run on > >> RAM. I added following statements in local.conf: > >> > >> UBOOT_CONFIG = "ram" > >> INITRAMFS_IMAGE_BUNDLE = "1" > >> DISTRO_FEATURES_append = " ram" > >> IMAGE_FSTYPES_append = " cpio.xz" > >> > >> It built to following images: > >> > >> dev-image.rootfs.cpio.xz > >> u-boot.imx-ram > >> zImage.bin > >> > >> If I extract the dev-image.rootfs.cpio.xz, it contains zImage at boot > >> directory. > >> > >> What I need is the zImage-initramfs to contain the rootfs in initramfs > >> format. > >> > >> I see there is document ramfs-rootfs-initramfs.txt, but it did not > >> mention how to generate zImage-initramfs. > >> > >> There is core-image-minimal-initramfs.bb, but it cannot be run: > >> > >> $ MACHINE="imx6evk" DISTRO="imx6evk" bitbake core-image-minimal-initramfs > >> ERROR: Nothing PROVIDES 'core-image-minimal-initramfs' > >> core-image-minimal-initramfs was skipped: incompatible with host > >> arm-oe-linux-gnueabi (not in COMPATIBLE_HOST) > >> > >> Could any one help what I am missing here and how to build the > >> zImage-initramfs? > >> > >> Thank you. > >> > >> Kind regards, > >> > >> - jh > >> -- > >> ___ > >> yocto mailing list > >> yocto@yoctoproject.org > >> https://lists.yoctoproject.org/listinfo/yocto > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project Engineering Sync, 7/09/2019
Minutes: Yocto Project Engineering Sync When: Tuesday, July 09, 2019 8:00 AM-9:00 AM 1. Attending: Richard, Armin, Michael, David, Trevor, Tim, Vineela, Bruce * Richard: General notes - Status report was sent last night: https://lists.yoctoproject.org/pipermail/yocto/2019-July/045968.html - Richard got work done on the runqueue changes (to run setscene and normal tasks in parallel) - Autobuilder still has NFS issues - 2.7.1 is now out of QA and waiting for TSC to approve for release, pending review of a ptest issue. * Vineela: Ok to publish test report? Richard: yes. - Nathan posted a patch of test suites for the toolchain components (binutils/gcc/glibc). Good mailing list discussion. * Richard: question to David about effect on Toaster for setscene events in parallel and thus somewhat out of order (e.g. effect on progress bar). David: probably no problem since Toaster just gathers the events (and progress is progress), will review the update. * Michael: updated firewall, installed Debian Time (sp?). * Tim: email transition? Michael: need to update list and resubmit, will get update on timeframe. * Armin: posted security patch for Patchworks - who will receive it and apply it? Michael: ok with Django change. Michael went ahead and tested the patch during the call, and got support to post the update to the repo. * Richard: mentioned that Sandy from WR is working on getting up to speed on PatchTest, but realized that she may not be also covering PatchWorks. We need to review how PatchWorks has diverged from the community. * Tim: concerned about patches from Martin that dropping rdepends for Perl in core might affect native Perl, and concerned about potential broader scope of the issues/changes across Perl. Richard noted that (a) native Perl not split like target Perl is, (b) there is an open bug about the whole issue plus Ross is also concerned, and that (c) the big problem is that to fix it we probable need to change "PN-native" to "native-PN". Tim posted this link that may show unexpected target rdepends contamination on native Perl: https://git.openembedded.org/meta-openembedded-contrib/commit/?h=jansa/warrior&id=d98e62e64219b365063fdb299d35f2af999d8f6e * Richard: had sync meeting last week while North America was on vacation. Short meeting, no minutes. * Tim: Khem travelling and patches are backing up. Richard: Khem should be back next week and will address queue. Discussion whether Tim as maintainer of Perl should go ahead and push patches himself to help relieve queue. - David -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Stuck to build zImage-initramfs
Hi Zoran, On 7/9/19, Zoran Stojsavljevic wrote: > Jupiter, > > I never read carefully the whole mechanism how to bundle kernel with > initramfs in YOCTO. Given Yocto reach features and powerful capacities, I would thought there must be some simple mechanism to bundle the kernel with initramfs which is an essential Linux feature, I would be surprised if Yocto doesn't have that simple solution. > I have there a description how to organize kernel image WITHOUT > initramfs (only kernel image by itself) and separately initramfs as > final stage, so I can do the tests with Lava, but I developed another > meanings with such a configuration: some another way of testing > various proofs of concepts. Ideally, it should all be done in Yocto without separate external manual steps. > What you are asking is a classical approach: kernel bundled with > initramfs, which is called Dracut phase, before mounting HDD/SSD > permanent rootfs... It is non-trivial process, controlled by various > kernel scripts. The popularity of initramfs will be beyond traditional PC world, Cloud and HPC have already use it to boot in virtual computing. For embedded system, it might not be the only way, but I am using it to burn imx6 nand. > I also need to analyse this @ thread regarding what you have asked > for... Maybe this is good time do to such a analysis! If? I am keen to involve as well. Here is what I have a zImage-initrafs built from OpenWrt: $ file zImage-initrafs zImage-initramfs: Linux kernel ARM boot executable zImage (little-endian) It can be downloaded to imx6 to burn imx6 nand. I have my zImage built from Yocto which failed to start rootfs (apparently not bundle the rootfs well), I am still debugging it, will post more information if you are interested. Thank you. - jupiter > Zoran > ___ > > On Tue, Jul 9, 2019 at 1:47 PM JH wrote: >> >> Thanks Zoran, I did see that link and your post to run mkimage. Did >> you get zImage-initramfs? I have to admit, I lost in that long email >> discussion with different approaches, I tried all set up, but there is >> no zImage-initramfs to be generated, files built in deploy/images just >> could not be used to run uuu on imx6 RAM. >> >> There is post for add KERNEL_INITRAMFS = "-initramfs", it looks like >> very close to generate zImage-initramfs, but I could still not get it >> :-(. >> >> Thank you very much. >> >> On 7/9/19, Zoran Stojsavljevic wrote: >> > Please, read the following thread: >> > https://lists.yoctoproject.org/pipermail/yocto/2018-July/041680.html >> > >> > Zoran >> > ___ >> > >> > On Mon, Jul 8, 2019 at 11:43 PM JH wrote: >> >> >> >> Hi, >> >> >> >> I have been stuck to build zImage-initramfs for weeks. I've read Yocto >> >> latest document, but still failed to generate the initarmfs to run on >> >> RAM. I added following statements in local.conf: >> >> >> >> UBOOT_CONFIG = "ram" >> >> INITRAMFS_IMAGE_BUNDLE = "1" >> >> DISTRO_FEATURES_append = " ram" >> >> IMAGE_FSTYPES_append = " cpio.xz" >> >> >> >> It built to following images: >> >> >> >> dev-image.rootfs.cpio.xz >> >> u-boot.imx-ram >> >> zImage.bin >> >> >> >> If I extract the dev-image.rootfs.cpio.xz, it contains zImage at boot >> >> directory. >> >> >> >> What I need is the zImage-initramfs to contain the rootfs in initramfs >> >> format. >> >> >> >> I see there is document ramfs-rootfs-initramfs.txt, but it did not >> >> mention how to generate zImage-initramfs. >> >> >> >> There is core-image-minimal-initramfs.bb, but it cannot be run: >> >> >> >> $ MACHINE="imx6evk" DISTRO="imx6evk" bitbake >> >> core-image-minimal-initramfs >> >> ERROR: Nothing PROVIDES 'core-image-minimal-initramfs' >> >> core-image-minimal-initramfs was skipped: incompatible with host >> >> arm-oe-linux-gnueabi (not in COMPATIBLE_HOST) >> >> >> >> Could any one help what I am missing here and how to build the >> >> zImage-initramfs? >> >> >> >> Thank you. >> >> >> >> Kind regards, >> >> >> >> - jh >> >> -- >> >> ___ >> >> yocto mailing list >> >> yocto@yoctoproject.org >> >> https://lists.yoctoproject.org/listinfo/yocto >> > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to load into u-boot binary (srec) file
On Mon, Jul 8, 2019 at 9:27 AM Szabolcs Báder wrote:
> Hello,
>
> I created this code:
>
> ```
> # u-boot standalone hello-world.c test image
> require recipes-core/images/core-image-base.bb
>
> COMPATIBLE_MACHINE = "^rpi$"
>
> ENABLE_UART="1"
> RPI_USE_U_BOOT="1"
>
> # maybe works??
> CONFIG_STANDALONE_LOAD_ADDR="0x1000"
>
> DEPENDS = "u-boot-mkimage-native"
>
> SUMMARY="Helloworld"
> DESCRIPTION="Helloworld"
> LICENSE="CLOSED"
> # LIC_FILES_CHCKSUM = "file://COPYING;md5=1fec1f350300594d23a1d03379c0c989"
>
> SRC_URI += "file://hello_world.c"
> HELLO ?= "hello_world.c"
> do_compile() {
> mkimage -A arm -O linux -T standalone -C none -a ${LOAD_ADDR} -e 0 \
> -n "standalone example script" \
> -d ${WORKDIR}/${HELLO} ${B}/helloworld.srec
> }
>
> inherit deploy
>
> do_deploy() {
> install -d ${DEPLOYDIR}
> install -m 0644 ${B}/helloworld.srec ${DEPLOYDIR}/
> }
>
> addtask do_deploy after do_compile before do_build
> ```
>
> I get errors, because I think.. the mkimage part.. isn't working..
> somebody could help me, how to solve this?
>
> Regards,
> Szabolcs
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to load into u-boot binary (srec) file
On Mon, Jul 8, 2019 at 9:27 AM Szabolcs Báder wrote:
> Hello,
>
> I created this code:
>
> ```
> # u-boot standalone hello-world.c test image
> require recipes-core/images/core-image-base.bb
>
> COMPATIBLE_MACHINE = "^rpi$"
>
> ENABLE_UART="1"
> RPI_USE_U_BOOT="1"
>
> # maybe works??
> CONFIG_STANDALONE_LOAD_ADDR="0x1000"
>
> DEPENDS = "u-boot-mkimage-native"
>
> SUMMARY="Helloworld"
> DESCRIPTION="Helloworld"
> LICENSE="CLOSED"
> # LIC_FILES_CHCKSUM = "file://COPYING;md5=1fec1f350300594d23a1d03379c0c989"
>
> SRC_URI += "file://hello_world.c"
> HELLO ?= "hello_world.c"
> do_compile() {
> mkimage -A arm -O linux -T standalone -C none -a ${LOAD_ADDR} -e 0 \
> -n "standalone example script" \
> -d ${WORKDIR}/${HELLO} ${B}/helloworld.srec
> }
>
> inherit deploy
>
> do_deploy() {
> install -d ${DEPLOYDIR}
> install -m 0644 ${B}/helloworld.srec ${DEPLOYDIR}/
> }
>
> addtask do_deploy after do_compile before do_build
> ```
>
> I get errors, because I think.. the mkimage part.. isn't working..
> somebody could help me, how to solve this?
>
>
if you post error messages that you see. It might provide more context
> Regards,
> Szabolcs
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
