Raspberry Pi 4 Model B - Yocto 5.0 "scarthgap" and later

Board Integrations Yocto Project
, ,
5

HI @wlbdv,

Thanks a lot for reaching out, and nice to hear you found this helpful. For your questions:

  1. The core concept of kas is that the whole build is defined by the data given, and hence it re-creates local.conf based on the passed .yml files every time. The way to augment the information in meta-mender-community with your local settings is to use an override file as described at Using kas to reproduce your Yocto builds. You would put your additions into a file like wlbdev-mender.yml, and then invoke kas like kas shell ../kas/raspberrypi4.yml:wlbdev-mender.yml. This way, whatever assignments you have in wlbdev-mender.yml will overwrite the given defaults.
  2. good catch, that’s a leftover from the original repo-based tutorial. Fixed now.
  3. the core-image-base-raspberrypi4.mender file is in fact a symlink to the last built artifact. I have just given it a test build, and after the second build the link is pointing to the newly created .mender file. Can you check if this is the case for you?

Greetz,
Josef