[Bug 1805668] Re: Building armhf and arm64 Raspberry Pi 3 images

[Łukasz Zemczak]

Adam: we are currently working on base support of the raspi3 boards
based on the old work that was done for the raspi2 (and please note
those did not get much love since a while anyway). The way they work
right now is not perfect, but this is the first 'iteration' we intend to
set as a baseline for further work. We're trying to get everything for
that 'baseline' landed in bionic right now to make work on this easier
(e.g. having daily builds etc). There are some things we could already
do better but there's a tight time-frame we need to fit into.

To address some of your concerns: you probably checked an outdated
flash-kernel since for the need of the beta images we have added Pi3 B+
support and a modified boot.scr for our uses. Currently both the boot
partition and flash-kernel come with compatible bootscripts so there
should be no conflict here. I also don't see how you tell that the
config.txt generated by livecd-rootfs will not work. The config.txt we
use in the boot partition in the current build scheme comes from the pi3
classic gadget tree and has device_tree_address=0x03000000, which is
what all of our planned boot.scr for pi3 are using (both in the boot
partition during image boot + what flash-kernel uses).

I would for now recommend to wait a bit until the base, surely far from
perfect, images are ready and then we can all work together on getting a
satisfying, clean raspi2/raspi3 experience. We are aware of the fact
that the system architecture here is flawed - and we promise it will be
made better. Especially now that Dave's around to help us out exactly
with that.

What I would recommend: once we have all the 'beta' work landed, I most
certainly recommend posting bugs about things that don't work or seem to
work suboptimal and letting us know.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to u-boot in Ubuntu.
https://bugs.launchpad.net/bugs/1805668

Title:
  Building armhf and arm64 Raspberry Pi 3 images

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in raspi3-firmware package in Ubuntu:
  Fix Released
Status in u-boot package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Fix Committed
Status in raspi3-firmware source package in Bionic:
  Fix Committed
Status in u-boot source package in Bionic:
  Confirmed
Status in livecd-rootfs source package in Cosmic:
  Won't Fix
Status in raspi3-firmware source package in Cosmic:
  Confirmed
Status in u-boot source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

  One of our long-term goals is to support the same set of platforms for both classical Ubuntu and ubuntu-core. We currently provide official images for the Raspberry Pi 3 for both the core16 and core18 bases but do not provide the same for Ubuntu classic.
  Since it's a 'feature' we're essentially lacking since long, we want to have the new device also supported in our current LTS (bionic).

  [Fix]

  For the classic raspi3 support we will be using the ubuntu-image classic image building tool which is specifically designed for creating preinstalled images. The support for that has already been SRUed in the latest ubuntu-image.
  For the full image build support to be complete, the following list of changes need to be backported (SRUed) into the respective stable series:

   * livecd-rootfs - all the changes regarding classic image build, gadget tree selection and raspi3 rootfs generation.
   * u-boot - bionic will need to be updated to at least 2018.03+dfsg1-2ubuntu2.
   * raspi3-firmware (bionic only) - needs to be updated to at least the version we have in cosmic. Without this change, the console is flooded with firmware error messages every 2 seconds.
   (vorlon) this should be updated specifically to the version of raspi3-firmware that we are using in the gadget snap - currently 1.20180919 - and not to another.

  [Test Case]

   * Run a bionic livefs build of raspi3+armhf with proposed enabled (IMAGEFORMAT=ubuntu-image and PROJECT=ubuntu-cpc), make sure the build succeeds and that the resulting image boots on a raspi3.
   * Run a bionic livefs build of raspi3+arm64 with proposed enabled (IMAGEFORMAT=ubuntu-image and PROJECT=ubuntu-cpc), make sure the build succeeds and that the resulting image boots on a raspi3.
   * Make sure that none of the other bionic daily images fail to build

  [Regression Potential]

  There is some potential that an invalid backport of livecd-rootfs
  functionality could result in the inability to create new ubuntu-core
  images or any of the other existing flavors. But in case of such a
  regression we would see it instantly after the package lands in
  bionic-proposed as we are building daily images with -proposed
  enabled. As for the other packages, there probably is some regression
  potential, but since the versions are backports from disco/cosmic, the
  risk is probably very small.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1805668/+subscriptions