Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: No recipes available for: ..../meta-updater-raspberrypi/recipes-bsp/u-boot/libubootenv_%.bbappend #79

Open
GWLindberg opened this issue Feb 24, 2020 · 5 comments

Comments

@GWLindberg
Copy link

GWLindberg commented Feb 24, 2020

I'm trying to add support for ostree to out boot2qt yocto warrior build for raspberry pi4. I've added meta-updater & meta-updater-raspberrypi to the build and when I start bitbake I get the following error:

ERROR: No recipes available for:
  .../sources/meta-updater-raspberrypi/recipes-bsp/u-boot/libubootenv_%.bbappend

I've tried downloading the HereOtaConnect sample project but it doesn't have the libubootenv recipe.
I researched where libubootenv is from and it is part of the sbabic swupddate system. Does this mean that I need to install meta-swupdate to get the libuboot? Does libubootenv automatically disable the fw* utilities from uboot?

From our bblayers.conf:

  ${BSPDIR}/sources/meta-openembedded/meta-filesystems \
  ${BSPDIR}/sources/meta-updater \
  ${BSPDIR}/sources/meta-updater-raspberrypi \

From our local.conf:

# first, need to use u-boot to boot to Linux
RPI_USE_U_BOOT = "1"

# then, need to use initramfs
KERNEL_INITRAMFS = "-initramfs"
INITRAMFS_IMAGE = "initramfs-ostree-image.bb"
INITRAMFS_IMAGE_BUNDLE = "1"
BOOT_SPACE = "1073741"
INITRAMFS_MAXSIZE = "315400"
IMAGE_FSTYPES_pn-${INITRAMFS_IMAGE} = "${INITRAMFS_FSTYPES}"

# make sure to inherit OTA functionality from the meta-updater* layers
INHERIT += " sota"
DISTRO_FEATURES += " usrmerge"

Is there something else that I'm missing?

Regards,
Greg Wilson-Lindberg

@GWLindberg
Copy link
Author

It seems that my copying of code in to the message has triggered some formatting, the bold text is supposed to be comments preceded by a hashtag sign.

@pattivacek
Copy link
Collaborator

pattivacek commented Feb 25, 2020

the bold text is supposed to be comments preceded by a hashtag sign.

Fixed by inserting the triple backticks. :)

when I start bitbake I get the following error:

ERROR: No recipes available for:
  .../sources/meta-updater-raspberrypi/recipes-bsp/u-boot/libubootenv_%.bbappend

I've tried downloading the HereOtaConnect sample project but it doesn't have the libubootenv recipe.
I researched where libubootenv is from and it is part of the sbabic swupddate system. Does this mean that I need to install meta-swupdate to get the libuboot? Does libubootenv automatically disable the fw* utilities from uboot?

libubootenv was not added to meta-updater-raspberrypi until quite recently, so it's only in master, but not in warrior. Something must be wrong with your build environment. Are you sure you're using the warrior branch and not master? Can you share the output of repo manifest -r? Or if you aren't using repo, I just want to know what revisions of our layers you are using.

(Updated after further investigation.)

@lbonn
Copy link
Contributor

lbonn commented Feb 25, 2020

@patrickvacek actually we have introduced the libubootenv bbappend after a recent change on poky master: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=cfdaad287b8bfe6909acc0257d120c58abe8ae5e.

@GWLindberg since you said you're using warrior layers, I think the mistake was to use the master branch of meta-updater-raspberrypi (maybe meta-updater as well?) and the fix is to switch to the corresponding master branches in our repos.

@GWLindberg
Copy link
Author

GWLindberg commented Feb 25, 2020 via email

@pattivacek
Copy link
Collaborator

I did a git clone from the [github.com/advancedtelematic/meta-updater.git] and [github.com/advancedtelematic/meta-updater-raspberrypi.git] repo’s to download the directories that I’m using. And my bblayers.conf has meta-raspberrypi and meta-openembedded/meta-python in it. Is there a different repo I should be using or a different branch in the repo that I have? Or is there a different way to get the libubootenv tools?

The problem appears to simply be that you are using mismatched branches of your layers. It sounds like you may be trying to use the master branch of our repos. You should git checkout warrior on both of them, and you should probably verify that the other layers you are using are indeed also on compatible branches based on warrior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants