i tried the following bitbake -c clean rpi-basic-image (to clean the build)
added the following to the local IMAGE_FSTYPES_append = " rpi-sdimg" => when i copied the text from the email, it gave class unavailable and then i found that there is a hidden character before the end quotes from another language. By writing it, it worked. thank you On Thu, Dec 7, 2017 at 6:45 AM, Sherif Omran <sherifomran2...@gmail.com> wrote: > I trid the rpi-sdimg as mentioned but i get IMAGE_CMD defined for > IMAGE_FSTYOE entry 'rpi-sdimg' possibly invalid type name or missing > support class. > any idea how to create the rpi image. > > On Sun, Nov 19, 2017 at 2:59 AM, Khem Raj <raj.k...@gmail.com> wrote: > >> I think you can generate a SD card image which can be dd’ed into a sd card >> poky tiny by default generates an initramfs image only. >> >> you can add >> >> IMAGE_FSTYPES_append = " rpi-sdimg" >> >> in local.conf and see if you get a rpi-sdimag >> >> >> >> On Sat, Nov 18, 2017 at 10:47 AM Sherif Omran <sherifomran2...@gmail.com> >> wrote: >> >>> I have it now being compiled and created a file called >>> rpi-basic-image-raspberrypi0-wifi-20171118102213.rootfs.cpio.gz >>> but how can i burn it? it is not an img file. >>> Any clue is appreciated. >>> >>> On Sat, Nov 18, 2017 at 12:21 PM, Sherif Omran < >>> sherifomran2...@gmail.com> wrote: >>> >>>> it worked well with >>>> >>>> PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-tini" >>>> >>>> in local.conf. However i don't know if it will work with real time >>>> kernel .. to be tested later >>>> >>>> thank you >>>> >>>> On Sat, Nov 18, 2017 at 10:19 AM, Khem Raj <raj.k...@gmail.com> wrote: >>>> >>>>> On Fri, Nov 17, 2017 at 5:34 PM, Michael Gloff <mgl...@emacinc.com> >>>>> wrote: >>>>> > This looks to be because poky-tiny.conf does not allow overriding of >>>>> the >>>>> > kernel provider. You could try the below patch to use a different >>>>> kernel. >>>>> > >>>>> > Michael Gloff >>>>> > >>>>> > diff --git a/meta-poky/conf/distro/poky-tiny.conf >>>>> > b/meta-poky/conf/distro/poky-tiny.conf >>>>> > index 2032bfde32..acafd9fef4 100644 >>>>> > --- a/meta-poky/conf/distro/poky-tiny.conf >>>>> > +++ b/meta-poky/conf/distro/poky-tiny.conf >>>>> > @@ -37,7 +37,7 @@ TCLIBC = "musl" >>>>> > >>>>> > # Distro config is evaluated after the machine config, so we have to >>>>> > explicitly >>>>> > # set the kernel provider to override a machine config. >>>>> > -PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-tiny" >>>>> > +PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto-tiny" >>>>> > PREFERRED_VERSION_linux-yocto-tiny ?= "4.12%" >>>>> > >>>>> >>>>> please submit this patch with sign off and git format, its good for >>>>> inclusion upstream >>>>> >>>>> > # We can use packagegroup-core-boot, but in the future we may need >>>>> a new >>>>> > packagegroup-core-tiny >>>>> > >>>>> > >>>>> > On Thu, Nov 16, 2017 at 7:05 PM, Sherif Omran < >>>>> sherifomran2...@gmail.com> >>>>> > wrote: >>>>> >> >>>>> >> hi >>>>> >> >>>>> >> i am trying to compile the yocto-tiny for raspberry pi by adding the >>>>> >> distro to my local.conf >>>>> >> >>>>> >> DISTRO = "poky-tiny" and i get the following >>>>> >> >>>>> >> >>>>> >> ERROR: nothing provides 'virtual/kernel' >>>>> >> ERROR: linux-yocto-tiny Provides virtual/kernel but was skipped: >>>>> >> incompatible with machine raspberrypi0-wifi (not in >>>>> compatible_machine) >>>>> >> ERROR: linux-yocto-rt Provides virtual/kernel but was skipped: >>>>> >> incompatible with machine raspberrypi0-wifi (not in >>>>> compatible_machine) >>>>> >> ERROR: linux-yocto Provides virtual/kernel but was skipped: >>>>> incompatible >>>>> >> with machine raspberrypi0-wifi (not in compatible_machine) >>>>> >> ERROR: linux-yocto-dev Provides virtual/kernel but was skipped: >>>>> >> incompatible with machine raspberrypi0-wifi (not in >>>>> compatible_machine) >>>>> >> ERROR: required build target 'rpi-basic-image' has no buildable >>>>> providers. >>>>> >> Missing or unbuildable depency chain was: 'rpi-basic-image', >>>>> >> 'virtual/kernel' >>>>> >> >>>>> >> >>>>> >> any body has a clue to solve it? >>>>> >> >>>>> >> thanks >>>>> >> >>>>> >> -- >>>>> >> _______________________________________________ >>>>> >> 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 mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto