advancedtelematic / meta-updater-qemux86-64

BSP layer for updating QEMU x86-64 guests with OSTree

OSTree bootloader integration for qemu-x86-64. Add it to BBLAYERS when using meta-updater with QEMU.

For more documentation on using this layer and HERE OTA Connect, please see the OTA Connect documentation portal, in particular the guide on building a QEMU image.

License

This code is licensed under the MIT license, a copy of which can be found in this repository. All code is copyright HERE Europe B.V., 2016-2020.

We require that contributors accept the terms of Linux Foundation's Developer Certificate of Origin. Please see the contribution instructions of aktualizr for more information.

meta-updater-qemux86-64's Issues

TOOLCHAIN_OPTIONS_append in u-boot_%.bbappend breaks building for other platforms

I have an image that I am building for raspberrypi4-64 for production, and for which I also have a qemux86-64 target for development purposes. To that end, along with the meta-updater layer, I include both this layer and meta-updater-raspberrypi in my project.

It seems like the TOOLCHAIN_OPTIONS_append in u-boot_%.bbappend prevents u-boot from building for raspberrypi4-64 and raspberrypi3-64, though it builds fine for raspberrypi3, raspberrypi4, and qemux86-64.

With this line enabled, building u-boot for raspberrypi4-64 fails because it can't find libgcc:

|   aarch64-bantha-linux-ld.bfd    -Ttext 0xc100000 -g -o examples/standalone/hello_world -e hello_world examples/standalone/hello_world.o examples/standalone/libstubs.o -L . -lgcc
| aarch64-bantha-linux-ld.bfd: cannot find -lgcc

If I comment the line out, or BBMASK the file out of my build, then u-boot builds successfully.

See agherzan/meta-raspberrypi#766 for more details

meta-updater-qemux86-64 and ubuntu 16.04.5 docker image Qemu error

Hi,
I've built meta-updater with Yocto Thud (-m thud.xml) according to https://docs.ota.here.com/quickstarts/qemuvirtualbox.html with ubuntu 16.04.5 docker image. When I try to start it, it returns the next python error. Please note it works well with ubuntu 18.04.2 (on the host). I'm wondering how to resolve this issue. Is there any additional package to install not mentioned in the 'quickstarts' manual?

Update: the same issue reconstructed with Yocto Rocko compilation. So it looks like this issue is not connected to Yocto version itself.
Update2 the same issue reconstructed with Yocto Rocko compilation without docker (with ubuntu 16.04.5 host). So it looks like this issue is not connected to the docker environment as well.

c@3e31dc934d8e:~/w/myproject_qemu_thud/build$ ../meta-updater/scripts/run-qemu-ota
Launching core-image-minimal with mac address ca:fe:63:30:15:37
To connect via SSH:
 ssh -o StrictHostKeyChecking=no root@localhost -p 2222
To connect to the serial console:
 nc localhost 8990
Traceback (most recent call last):
  File "../meta-updater/scripts/run-qemu-ota", line 73, in <module>
    main()
  File "../meta-updater/scripts/run-qemu-ota", line 65, in main
    s = Popen(cmdline)
  File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

Thanks

Yocto Thud compilation: got "ERROR: No boot files defined, IMAGE_BOOT_FILES unset for entry #1"

Hi All,

I tried to build Yocto Thud with meta-updater and I got the next error (see below).
IMAGE_BOOT_FILES is not set in meta-updater/classes/sota_qemux86-64.bbclass, however, it is defined in other 'classes' files. Please describe how to compile it properly in case of Yocto Thud.

| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_image_wic
| INFO: Creating image(s)...
|
| WARNING: bootloader config not specified, using defaults
|
| ERROR: No boot files defined, IMAGE_BOOT_FILES unset for entry #1
|
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_image_wic (log file is located at /home/c/w/poky_thud/build/tmp/work/qemux86-poky-linux/core-image-sato/1.0-r0/temp/log.do_image_wic.18268)

Thanks